Every ERP Needs a Partner: The Case for a System of Action in Accounts Payable

Summary: What happens to an invoice before your ERP ever sees it? This blog explores the approvals, exceptions, and vendor changes that happen in email before each entry posts. Learn how a system of action pairs with your ERP to unify finance and operations workflows. You'll also get a 10-minute test to run on your own books.

Pick any invoice your team paid last month, and the ERP can tell you plenty about it. Vendor, amount, GL coding, and payment date are all there. Now try to find who approved it, under what limit, and how long it sat before anyone touched it. For most controllers, those answers live somewhere else: an inbox, a shared drive, or a department head's phone.

That gap matters more as budgets shift toward technology. In Gartner's 2026 budget research, 75% of CFOs planned to raise technology budgets this year. Nearly half (48%) planned increases of 10% or more. Gartner also ranks cloud ERP as the highest-performing finance technology. Companies are putting real money into the ledger, and they should.

But a better ledger doesn't change where the work happens. There are two jobs here: recording the business and running it. Your ERP is the system of record. The approvals, exceptions, vendor changes, and payment decisions that come before each entry need a system of action.

Why the ERP Alone Can't Close the Gap

Your ERP does its core job well. It records the financial outcome of every transaction, and month-end close depends on it. The catch is that it records what happened only after someone tells it what happened.

Many ERPs also offer approval workflows, and plenty of finance teams have tried to use them. The trouble is who has to use them. Plant managers, project leads, and department heads approve spend, but they rarely work inside the ERP all day. They're on a shop floor, at a job site, or in back-to-back meetings. So approvals drift back to email. When the one person who can sign off is on vacation, the invoice stalls with them.

Controllers often see this most clearly after a migration or upgrade. The new system goes live, the chart of accounts is cleaner, and the reports look better. Three months later, AP still waits on the same approvals, and invoices still sit in the same shared inbox.

Where Accounts Payable Work Actually Happens

Follow one invoice from the moment it arrives. It lands in a general AP mailbox, or in a facilities manager's inbox because the vendor had that address. Someone has to notice it, read it, and figure out who owns the spend.

Sometimes the first sign of a problem is a vendor calling about an invoice your team never received. A bill that lands in the wrong inbox or department can sit untouched. That happens even when the company fully intends to pay on time.

From there, the work spreads across people who rarely open the ERP at all:

• Operations approvers sign off on spend for their departments, locations, or projects, often from a phone between meetings.
• Purchasing teams answer questions about quantities, pricing, and partial receipts or packing slips that don't match the purchase order.
• AP specialists track down answers, key data, and keep spreadsheets of what's waiting on whom.

Everyone in that chain is doing their part well. The process just wasn't built to connect them.

Every one of those steps involves a decision. Very few of them leave a clean record in the system of record. The ERP sees the final entry, while the approvals, questions, and judgment calls stay in email.

This is the visibility gap between finance and operations that shows up every budget season. Finance sees what was spent, and operations sees what was ordered. Nobody has one view of what's in motion between them.

The Real Cost of Running AP Outside Your Systems

Work that happens in email is slow, and the delay is the smallest part of the cost. Risk, audit exposure, and decisions made without current numbers cost far more.

Fraud targets the handoffs

In the AFP 2026 Payments Fraud and Control Survey, 76% of U.S. organizations experienced attempted or actual payments fraud in 2025, and 74% were affected by business email compromise (BEC).

BEC arrives by email, a channel the ERP doesn't watch. A convincing request to change a supplier's bank account can reach AP looking exactly like a routine update. Once the new account reaches the vendor master, the ERP records each payment to the wrong place.

That's why accounts payable fraud lives in the seams of your process, in the handoffs between people and systems.

Audit questions get harder to answer

Your auditors don't only ask what was paid. They ask who approved it, under what limit, and with what supporting documents. The ERP can show the payment, while the "approved" reply sits in an email thread from last spring.

The same issue now shows up with AI. In a 2026 Datarails survey of 270 U.S. finance executives at companies with at least $100 million in revenue, 75% named the inability to audit or explain how AI reached its output as the top reason they hesitate to trust it.

Both problems have the same root. Work that isn't recorded step by step can't be explained later, whether a person or a model did it.

Month-end runs on estimates

Month-end accruals show the gap most clearly. You know invoices exist for work already done, but some are sitting in inboxes you can't see. So you estimate, book the accrual, and hope next month's true-up is small.

Weekly cash planning has the same blind spot. The ERP knows only what has posted, so what's approved, disputed, or still on someone's desk lives in a spreadsheet. Early-pay discounts expire while an invoice waits for a signature. Payment timing ends up following the approvals instead of your cash strategy. That's working capital sitting idle: discounts you could have taken and cash you could have planned around.

What a System of Action Adds to Your ERP

Your ERP remains the system of record for accounting. A system of action pairs with it and moves the work that leads up to each entry forward. A platform becomes a system of action because of what it does. It takes in data from finance and operations documents, like receipts and work orders, and from connected systems. It runs the workflows and prompts the right person to act at each step. Embedded controls guide each step, and every action is logged.

In practice, a few things change right away. Invoices are captured and read as they arrive, instead of waiting for someone to open an inbox. Matching against purchase orders and receipts happens before a person touches the invoice. Exceptions route to the right approver with the documents attached.

Embedded controls handle the checks that email can't. Approval limits, separation of duties, and vendor change verification are built into the workflow itself. An invoice can't skip a required approver, and a bank change can't go live without the verification step.

Every step also leaves a record: what happened, when it happened, who was involved, and why. That record answers the auditor's question in minutes. AI tools need that same traceable history before a finance team can check and trust their suggestions. Because every step is logged, the workflow also shows where work stalls. Over time, that same data can surface patterns, like a supplier whose invoices keep landing in exceptions.

The connection to the ERP runs both ways. Approved, coded invoices post to the ledger. Vendor master, chart of accounts, purchase order, and receipt data flow back to the workflow. Your ERP keeps its role as the system of record, and nobody rekeys data between systems. Payments follow in the same workflow, with each one tied to its invoice, approvals, and documents.

Benchmarking data shows the median organization reports a 45% cumulative return on investment from finance process automation. That return covers the previous 12 months. The same research notes that automation often changes transactional work rather than eliminating it. Your team spends less time keying data and more time reviewing exceptions, finding cash, and supporting the business.

None of this stops at AP. The same approach supports purchase requests, vendor onboarding, capital approvals, and other finance and operations workflows that cross departments. Teams that start in AP often find the next workflow is already waiting. Business process automation extends the same controls to it.

A 10-Minute Test Before You Customize Your ERP Again

Finance teams often try to close these gaps by customizing the ERP. Before you open that project, run a quick test on your own books. Pull five paid invoices from last quarter, including at least one that needed an exception. For each one, give yourself 10 minutes to answer three questions:

• Who approved it? Find the actual name and date. A status flag in the ERP doesn't count.
• Was it within their limit? Confirm the approver had authority for that amount.
• What backs it up? Locate the invoice, PO, receipt, and any emails that explain the exception.

Anywhere the trail leads to someone's inbox or memory, you've found work the system of record never saw. Ledger problems belong in the ERP, while that work needs a system of action. As you compare options, ask for current SOC 1 Type II and SOC 2 Type II reports. Any platform storing vendor bank details should have them.

Let Your ERP Record, and Give the Work a System of Action

Your ERP will keep doing what it does well. What needs a home is the work before each entry posts. You also need a record you can explain when an auditor or vendor asks.

onPhase pairs with the ERP you already run as that system of action, unifying finance and operations workflows. Approvals, exceptions, and payments move in one place, with a record behind every step.

Planning an ERP upgrade or migration? Start with Beyond Go-Live: How CFOs Drive ERP Transformations That Last. It covers the process and ownership questions that decide whether a new system pays off. The next time someone asks who approved an invoice, the answer should take minutes, not a search through old email.