AI agents · November 2026
Where the ERP Stops: Payments Processes Against O2C, P2P and R2R
Finance teams describe their work in three ERP cycles: order to cash, procure to pay and record to report. Of the 57 back-office processes on the ScalePoint Research process map, 11 fit one of those cycles. Here is what sits outside them, and why the 11 that fit still take so much staff time.
- 11 of the 57 back-office processes on the map sit in a standard ERP cycle: five in order to cash, three in procure to pay and three in record to report.
- The other 46 are payments work the three cycles weren't built for, such as scheme settlement, safeguarding, sanctions alerts and payout reconciliation.
- Nine of the 11 cut the cost of handling each case. None of them is about growth or control, so the processes that lift approval rates or cut false alerts all sit outside the cycles.
- Five of the 11 start from a file the firm didn't produce, such as an acquirer settlement file or a bank statement. The work sits where that file meets the ledger, and the map rates agent fit highest there.
- All 11 are core for a business that sells goods or services. The map shows four more processes for those businesses outside the cycles: statement reading, decline analysis, payment routing and failed payment retries.
Finance software is sold around three cycles. Order to cash (O2C) runs from a customer's order to the money arriving in the bank, covering invoicing, cash application and collections. Procure to pay (P2P) runs from a purchase order to paying the supplier, covering invoices, approvals and payment runs. Record to report (R2R) turns the books into accounts, covering journals, reconciliations, intercompany and the month-end close. ERPs such as SAP, Oracle NetSuite and Microsoft Dynamics have a module for each.
Readers from payments may know these as accounts receivable, accounts payable and the general ledger. The cycles matter here because they shape what a CFO thinks the ERP already covers. The process map tags each process with its cycle where it has one, and the cycle shows when you open a process.
The 11 that sit in a cycle
| Process | Cycle | Agent fit on the map | Where the data comes from |
|---|---|---|---|
| Card settlement reconciliation | O2C | Agent workflow | Acquirer settlement file, bank statement, sales ledger |
| Alternative payment method reconciliation | O2C | Agent workflow | Wallet, buy now pay later and account-to-account provider reports, bank statement, sales ledger |
| Merchant chargebacks | O2C | Agent workflow | Acquirer dispute notice, order and delivery records |
| Cash application | O2C | Agent-assisted | Bank statement, remittance advice, open invoices |
| Collections | O2C | Agent workflow | Sales ledger, customer correspondence |
| Supplier invoices | P2P | Agent-assisted | Supplier invoices, purchase orders, contracts |
| Payment runs | P2P | Agent-assisted | Purchase ledger, supplier bank details |
| Expense checks | P2P | Single step | Company card feed, receipts, expense policy |
| Month-end close | R2R | Agent-assisted | Ledger, accruals, variance reports |
| Bank reconciliation | R2R | Agent-assisted | Bank statement, ledger |
| Intercompany | R2R | Agent workflow | Ledgers of each group company |
Five of the 11 are rated agent workflow, five agent-assisted and one single step. Agent workflow means the work comes as a queue of cases and an agent can work each case through. Across all 57 back-office processes, 25 get that rating.
The map also tags each process with the main thing it does for the business. Nine of the 11 cycle processes are about cost to serve: fewer hours per case and a team that doesn't grow with volume. Collections and chargebacks are about margin and cash, because they bring money in sooner or stop it leaking. None of the 11 is tagged growth or control. Across the back office, the 12 growth processes, such as failed payment retries and decline analysis, and the 15 control processes, such as sanctions alerts and transaction monitoring, all sit outside the cycles. Hence an AI plan built only around the ERP cycles will mostly cut cost per case.
Where the provider's data meets the ledger
Card settlement and alternative payment method reconciliation sit in order to cash, and the work is matching three sources. An acquirer pays a retailer one net amount for a day's card sales, after taking off fees, refunds and chargebacks. The bank statement shows that net amount, often a day or two later. The sales ledger in the ERP shows the gross sales from the tills and the website. Someone has to break the payout back into sales, fees and refunds, match it to the ledger and explain each difference.
The ERP holds one of those three sources. The other two arrive from outside, in a format that differs by acquirer and payment method. Five of the 11 processes start this way: card settlement, alternative payment method reconciliation, chargebacks, cash application and bank reconciliation. Each begins with a file the firm didn't produce.
Matching on amount, date and reference is rules work, and a reconciliation tool does it well. What's left for the finance team are the breaks: a payout short by a fee nobody expected, a refund that crossed a month end, a wallet payment with no reference. Working a break means pulling the three sources, finding the cause and writing it up. That's the case-by-case work the agent workflow rating describes, and How an AI agent works a reconciliation break walks through one.
The 46 that don't fit a cycle
The other 46 back-office processes are payments work. Payments firms run most of them as their core business, and the three ERP cycles weren't built for them. They fall into three groups by why they sit outside.
| Group | Processes | Examples | Why it sits outside the cycles |
|---|---|---|---|
| Regulated money and financial crime | 19 | Safeguarding reconciliation, sanctions alerts, transaction monitoring, SAR drafting, KYC and KYB, APP scam claims, regulatory returns, stablecoin reserves | Regulators set how the work is done and what must be kept |
| Scheme rules | 8 | Scheme settlement and interchange, acquirer and cardholder disputes, Direct Debit and account-to-account returns, payment repairs and tracing | Card and payment schemes set the time limits, reason codes, fee tables and file formats |
| Provider data and pricing | 19 | Merchant and split payouts, statement reading, decline analysis, payment routing, failed payment retries, merchant fee billing, FX quotes, nostro reconciliation, prefunding, B2B credit underwriting | The data is the payment provider's own, and the work is what a payments firm earns, pays out and holds |
The first group answers to rules that differ by country. Safeguarding follows the UK Payment Services and Electronic Money Regulations and, in the EU, PSD2 and the E-Money Directive. Sanctions screening checks against the OFAC, OFSI and EU lists. Suspicious activity goes to FinCEN in the US and the National Crime Agency in the UK. The ledger records the balances, while the checks on whose money it is and whether it may move happen in screening, case management and safeguarding systems.
The scheme group runs on Visa, Mastercard and payment scheme rulebooks, which change several times a year. A cardholder dispute has a reason code and a deadline set by the scheme, and the evidence has to match that reason code.
The provider data group is mostly single step on the map: 12 of its 19 processes are one read or one calculation, such as pulling every fee line out of a statement. It's the group where a model alone, without an agent around it, does most of the job.
The map also shows four customer and commercial processes next to the back office: customer support, churn and retention, upsell and partner performance. They live in CRM and support systems, and none of them sits in an ERP cycle either. Customer support rates as agent workflow, because each ticket needs the account, the payment history and a reply.
What a business should look at first
Pick Merchant on the map, the label it uses for any business selling goods or services, and 15 processes show as core. All 11 cycle processes are among them. The other four, statement reading, decline analysis, payment routing and failed payment retries, are provider data work outside the cycles.
How much a business saves on each process depends on how it gets paid. A subscription business with a million small card payments a month spends far more staff time on chargebacks and settlement breaks than a distributor whose trade customers pay invoices by bank transfer. For the distributor, cash application and supplier invoices take most of the time. A separate piece will set out estimates by type of business.
Hence the place to start is a process where a provider's file meets the ledger and each case takes real staff time. For a business paid mostly by card, that's card settlement reconciliation or chargebacks. For one paid by bank transfer, it's cash application. Alternative payment method reconciliation comes next where wallets and buy now pay later take a large share of sales. The order to cash module will already be in place for all of these. What matters is how many breaks still land with the finance team each month, and how long each one takes to clear.
Last reviewed 19 November 2026.
Part of ScalePoint Research. Related reading: