The batch-based AP model was designed around the constraints of manual processing. Weekly payment runs existed because preparing a payment run manually took significant staff time. Monthly reporting cycles existed because producing an AP status report required pulling data from multiple sources and assembling it by hand.
Those constraints are gone for organizations that have fully implemented AP automation. But the batch-based operating model often persists by habit rather than necessity. Finance teams with automated AP still run payments twice a week, still produce monthly AP summaries, still treat invoice processing as a discrete workflow that runs on a cycle rather than continuously.
Real-time AP is the operating model that matches the capability of the technology. It treats payables as a continuous flow rather than a periodic batch and it changes what is possible for cash management, supplier relationships, and the close cycle.
What Real-Time AP Actually Means
Real-time AP has three distinct dimensions. They are often conflated but each requires different capabilities:
Real-time processing
Invoices are captured, extracted, coded, matched, and routed for approval the moment they arrive, not in a daily or weekly processing batch. An invoice that arrives at 3pm on a Friday enters the approval workflow immediately rather than waiting for the Monday processing run.
Real-time visibility
The CFO and treasury team can see the current state of all payables at any moment, not the state as of the last month end report or the last weekly reconciliation. Live outstanding balances, invoices in the approval queue, upcoming payment obligations, and cash outflow forecasts are all current.
Real-time payment capability
For organizations with access to real time payment rails like FedNow, RTP in the US, Faster Payments in the UK, SEPA Instant in Europe, payment can be executed on approval rather than queued for the next payment run. This is the most operationally significant change and the one with the clearest impact on supplier relationships.
What Changes for the AP Team
The AP team's workflow changes in three meaningful ways:
Exception management replaces batch processing
Instead of processing a queue of invoices each day, the AP team manages exceptions that the automated system cannot resolve. Clean invoices with good data and valid PO matches flow through without human touch. The AP team reviews the 10 to 20% of invoices that require judgment disputed amounts, coding questions, invoices from new vendors, or invoices above the auto-approval threshold.
This is a different kind of work. It requires more judgment per transaction but handles a smaller volume. The skill profile shifts from data entry competence to problem solving and vendor communication.
Supplier inquiry management becomes proactive
With live invoice status visible to the supplier through a self service portal, the volume of supplier inquiry calls and emails drops significantly. Suppliers can check their invoice status, approval progress, and expected payment date without contacting the AP team. The AP team handles only the inquiries where there is a genuine dispute or an issue requiring investigation.
Payment timing becomes a strategic decision
When payments can execute on demand rather than on a fixed run schedule, the treasury team gains flexibility. Early payment can be offered to specific suppliers when cash is available and the discount is value accretive. Payment can be held to the due date when cash optimization requires extending DPO. The timing decision becomes a deliberate treasury call rather than a default set by the payment run schedule.
What Changes for the CFO
The shift that matters most to the CFO is visibility. In a batch-based AP model, the CFO's view of upcoming cash outflows is always somewhat stal, it reflects the state of the AP queue as of the last report, not as of today.
In a real-time AP model:
- The 13-week cash flow model updates automatically as invoices are approved and payment dates are confirmed
- Covenant compliance calculations reflect current AP obligations, not period-end snapshots
- The CFO can make same-day decisions about whether to offer dynamic discounting based on current available cash
- Supplier concentration risk and payment obligation timing are visible across all entities simultaneously
The Close Cycle Impact
Batch-based AP creates close cycle drag because the books are never fully current at period end. Invoices in the processing queue, approvals pending in inboxes, and payment runs not yet executed create reconciling items that the close team has to work through.
Real-time AP eliminates most of this drag. At period end, the AP queue is current. Invoices approved that day are in the system. Payment runs are current. The close team reconciles against a live picture rather than reconstructing the state as of midnight on the last day of the period.
Hackett Group benchmarks show that organizations with real-time AP visibility close their books 1.5 to 2 days faster than organizations with batch-based processes, not because the accounting work is faster, but because the starting data is cleaner.
The Prerequisites for Real-Time AP
Real-time AP requires a technology foundation that batch based processes do not:
- API-connected ERP integration: invoice data must flow to and from the ERP in real time, not via nightly batch file. Batch integrations cannot support real time visibility.
- Event-driven approval workflows: approvals must trigger immediately on invoice completion, not on a scheduled workflow run.
- Real-time payment rail access: same-day or on-demand payment requires either a real-time payment rail (RTP, FedNow, Faster Payments) or a banking relationship that supports same-day ACH.
- Continuous supplier portal access: suppliers need a portal where they can see live status rather than calling or emailing the AP team for updates.
Is Real-Time AP Feasible for Mid-Market Finance Teams?
The technology is available and the cost is within reach for mid market organizations. The practical constraints are usually the payment rail access and the ERP integration quality rather than the AP platform itself.
A realistic transition path: start with real time processing and visibility, which requires only AP platform and ERP integration improvements. Add real time payment capability as a second phase once the core processing flow is continuous and the payment timing decision framework is in place.
The batch based payment run schedule is often the last element to change, because it requires both technical payment rail capability and a treasury policy decision about when payments should execute. Both are achievable. They require deliberate decisions rather than default operating mode.
