Order-to-cash vs procure-to-pay: how do the buyer’s and the seller’s cycles fit together?
Short answer
Procure-to-pay is the buyer’s cycle from need to payment; order-to-cash is the seller’s cycle from order to cash received. Each document one side sends, the other side receives.
Key takeaways
- Procure-to-pay (P2P) is how a buyer requests, orders, receives, checks and pays. Order-to-cash (O2C) is how a seller takes the order, delivers, invoices and collects the money. One company’s purchase is another company’s sale.
- The two cycles meet at three points: the purchase order, which becomes the seller’s sales order and is confirmed by an order response; the invoice; and the payment with its remittance advice.
- Shared references make the match work. A Peppol e-invoice can carry both the buyer’s purchase order number and the seller’s sales order number, so each side finds its own document.
- Most problems cross the line. An order placed by phone without a PO number becomes an invoice the buyer cannot match and a payment the seller does not receive.
- Payment terms link the cycles: the days the buyer takes to pay are the days the seller waits for cash. Laws on payment periods differ by country, such as 60 days between businesses in the EU unless expressly agreed.
What is the difference between order-to-cash and procure-to-pay?
Procure-to-pay is the buyer’s process: a need is approved, a purchase order goes to the supplier, goods are received, the invoice is checked and the supplier is paid. Order-to-cash is the seller’s process: the order is accepted, goods are delivered, an invoice is issued and the customer’s payment is collected and recorded.
They are two views of the same sale. Take an invented case: a hospital orders 200 boxes of gloves from a medical distributor. For the hospital, this is a purchase order in its procure-to-pay cycle. For the distributor, the same order becomes a sales order in its order-to-cash cycle. The invoice the distributor sends is the invoice the hospital matches. The payment the hospital makes is the cash the distributor applies to its open invoice.
The cycles are mirrors, not copies. Each side has steps the other never sees. The buyer approves the request and records the receipt; the seller checks the customer’s credit and collects late payments. The full steps of the buyer’s side are on the procure-to-pay guide; this page explains how the two sides fit together.
How do the steps of the two cycles line up?
Read the table from left to right: what the buyer does, the document that crosses between the companies, and what the seller does with it. Steps without a crossing document stay inside one company. The message names in brackets are examples from two common electronic standards, X12 in North America and Peppol in Europe and other countries.
| Buyer: procure-to-pay | Document that crosses | Seller: order-to-cash |
|---|---|---|
| A requester raises a purchase requisition; the budget holder approves it | Nothing yet, or a request for quotation | Sends a quote, a price list or a catalogue |
| The buyer issues a purchase order | Purchase order (X12 850, Peppol Order) | Creates a sales order, checks credit and stock |
| The buyer records the supplier’s confirmation and any change | Order response (X12 855, Peppol Order Response) | Accepts, accepts with changes or rejects the order |
| The receiver records a goods receipt or confirms the service | Delivery note or advance ship notice (X12 856) | Picks, packs and ships, or performs the service |
| Accounts payable matches the invoice with the order and the receipt | Invoice (X12 810, Peppol invoice) | Issues the invoice and books a receivable |
| Accounts payable runs the payment | Payment and remittance advice (X12 820) | Applies the cash to open invoices and clears the receivable |
| Raises a dispute or a debit note when something is wrong | Credit note or corrected invoice | Handles the dispute and chases unpaid invoices |
Only the documents in the middle column cross between the companies; approvals, receipts, credit checks and collections happen inside one side.
Many buyers and sellers still exchange these documents as PDFs and emails. The electronic standards matter because they fix which fields each document carries. In Peppol, for example, an order response lets the seller accept, reject or accept with changes, and an accepted order has the status of a contract.
Where do the documents of the two cycles meet?
The cycles meet at three points: the order, the invoice and the payment. At each point, both companies must be able to find their own record from the other side’s document. That only works if the document carries the other side’s reference.
- Purchase order ↔ sales order
- The buyer’s purchase order becomes the seller’s sales order. The seller keeps the buyer’s PO number on its sales order, because the buyer will ask for it on the invoice. A guide to the difference between a sales order and a purchase order is in preparation.
- Invoice ↔ invoice
- The seller’s invoice is the buyer’s supplier invoice. In a Peppol BIS Billing 3.0 invoice, the purchase order reference is “issued by the Buyer” and the sales order reference is “issued by the Seller”, so one invoice carries both numbers.
- Payment ↔ cash application
- The buyer’s payment run is the seller’s incoming cash. Cash application is the seller’s step of linking each payment to the invoices it pays. It needs the buyer to say which invoices the payment covers.
The payment is where most matching breaks, because bank transfers carry little space. In a standard SEPA credit transfer, for example, the remittance information field holds up to 140 characters, structured or not. The European Association of Corporate Treasurers recommends using the seller’s structured creditor reference (ISO 11649) when the seller provides one, and a separate remittance advice when the details do not fit.
Here is what that means in practice. A buyer pays twelve invoices in one transfer with the text “March invoices”. The seller’s bank receives the money, but its receivables team cannot tell which twelve invoices are paid, so the cash sits unapplied and some customers receive reminders for invoices already paid. A remittance advice listing the twelve invoice numbers, with any deduction and its reason, avoids the problem.
On the buyer’s side, the same references decide whether the invoice can be checked. The three-way match compares the invoice with the purchase order and the goods receipt; without a PO number on the invoice, invoice processing stops while someone searches for the order.
Why does a problem on one side become a problem on the other?
Because the cycles share documents, an error made by one company shows up in the other company’s process, often weeks later. The table lists common cases. They are typical patterns, not measured frequencies.
| What happens on one side | What the other side sees | Usual fix |
|---|---|---|
| The buyer orders by phone or email without a purchase order | The seller’s invoice has no PO number; the buyer returns it or leaves it unpaid | Buyer: no PO, no order. Seller: refuse orders without a PO number from customers who require one |
| The purchase order uses an old price | The invoice fails the price check; payment is blocked until someone agrees the price | Load the contract price on the PO and the seller’s price list before ordering |
| The seller ships part of the order but invoices all of it | The buyer’s receipt shows a smaller quantity; the invoice fails the quantity check | Invoice what was delivered; send the rest when it ships |
| The buyer pays several invoices in one transfer without references | The seller cannot apply the cash and sends reminders for paid invoices | Send a remittance advice with invoice numbers, amounts and deductions |
| The buyer deducts an amount without a debit note | The seller sees a short payment and opens a dispute | Document every deduction; in VAT countries, adjust the amount through a credit or debit note |
| The seller changes its bank details by email | The buyer may pay a fraudster if it does not check the change | Buyer: confirm changes through a known contact before updating the supplier record |
Most cross-cycle problems start with a missing or wrong reference; fixing the reference at the source is cheaper than chasing it at payment.
Electronic invoicing reduces some of these errors because the structured invoice must carry the agreed fields. Some countries now require it between businesses: Belgium since 1 January 2026 for VAT-registered enterprises, and France in phases from 1 September 2026. Other countries have their own timetables.
How do payment terms connect the two cycles?
Payment terms are the same number seen from two sides. When a buyer pays on day 60 instead of day 30, its cash stays longer in its account and the seller waits 30 more days for its money. Finance teams measure this with two mirror ratios.
- Days payable outstanding (DPO), on the buyer’s side: average accounts payable ÷ cost of goods sold × number of days in the period. It shows how long the company takes, on average, to pay its suppliers.
- Days sales outstanding (DSO), on the seller’s side: accounts receivable ÷ net credit sales × number of days. It shows how long the company waits, on average, to collect from its customers.
A worked example with invented figures: a seller has €1,200,000 of receivables and €7,300,000 of credit sales in a year, so its DSO is 1,200,000 ÷ 7,300,000 × 365 = 60 days. A buyer has €500,000 of average payables and a cost of goods sold of €4,562,500, so its DPO is 500,000 ÷ 4,562,500 × 365 = 40 days. Both ratios cover the whole company, not one customer or one supplier.
The law sets limits in many places, and the limits differ. The table shows two systems; check the rules of the country and sector that apply to each contract.
| System | Who it covers | Payment period | If the buyer pays late |
|---|---|---|---|
| European Union: Directive 2011/7/EU, as transposed into national law | Commercial transactions between businesses, and between businesses and public authorities | Between businesses, no more than 60 calendar days unless expressly agreed and not grossly unfair to the creditor; public authorities 30 days, 60 at most in defined cases | Statutory interest of the reference rate plus at least 8 percentage points, and at least €40 for recovery costs |
| United States: Prompt Payment Act (31 U.S.C. 3902 and 3903) | Federal agencies paying businesses | The date in the contract or, if the contract sets none, 30 days after a proper invoice is received | An interest penalty paid automatically from the day after the due date |
A legal payment period is a ceiling, not a target; the contract’s payment term is what both cycles run on.
For procurement, the lesson is that the payment term is a contract decision with two owners. Treasury may want a longer DPO, but suppliers price their own wait into their offers, and small suppliers may not survive it. The payment term agreed in the contract must reach the supplier record and the order, as the guide to source-to-pay vs procure-to-pay explains.
How do order-to-cash and procure-to-pay connect to record-to-report?
Finance teams often group their work into three cycles: procure-to-pay for money going out, order-to-cash for money coming in, and record-to-report (R2R) for the books. Record-to-report takes the entries from the first two, closes the period and produces the financial statements.
The links are concrete. Procure-to-pay feeds the accounts payable ledger; order-to-cash feeds the accounts receivable ledger; both post to the general ledger. At month end, record-to-report needs both cycles to be up to date. A delivery received but not yet invoiced, for example, must be booked as an accrual, or the month’s costs look too low. This is one reason goods receipts need to be recorded on time, not only when the invoice arrives.
Who owns each cycle, and which systems run it?
Different teams own each cycle. Procure-to-pay sits with requesters, buyers, receivers and accounts payable. Order-to-cash sits with sales, customer service, billing, credit control and accounts receivable. Inside one company, both cycles usually run in the same ERP, but they rarely share owners, targets or meetings.
| — | Procure-to-pay (buyer) | Order-to-cash (seller) |
|---|---|---|
| Money | Goes out | Comes in |
| Starts with | A need inside the company | A customer’s order |
| Ends with | A paid supplier invoice | Cash applied to the customer’s invoice |
| Main owners | Procurement and accounts payable | Sales, billing and accounts receivable |
| Ledger | Accounts payable | Accounts receivable |
| Typical measures | Share of spend on purchase orders, first-time match rate, DPO | Order-to-invoice time, unapplied cash, DSO |
| Main systems | ERP purchasing, procure-to-pay tools, accounts payable tools | ERP sales and billing, credit and collections tools |
| Connected through | Supplier portals, EDI, e-invoicing networks | Customer portals, EDI, e-invoicing networks |
The cycles run on separate teams and ledgers but on shared documents, so they are only as good as the references both sides keep.
Every company runs both cycles, because every company buys and sells. A buyer that improves its procure-to-pay process also improves its suppliers’ order-to-cash: clear orders, fast matching and payments with remittance details mean fewer disputes for both. Tools for the buyer’s side are compared in the procure-to-pay software guide, and automating the invoice side is covered in accounts payable automation. A supplier portal lets suppliers see order and payment status without calling the buyer.
Questions
Is order-to-cash the opposite of procure-to-pay?
It is the mirror, not the opposite. Procure-to-pay is the buyer’s cycle and order-to-cash is the seller’s cycle for the same sale. They share the order, the invoice and the payment, but each side also has steps the other never sees, such as approvals for the buyer and credit checks for the seller.
Is order-to-cash part of procurement?
No. Order-to-cash belongs to the selling side: sales, billing and accounts receivable. Procurement owns procure-to-pay. Procurement still has reasons to understand its suppliers’ order-to-cash, because orders without references and unclear payments create disputes and delays on both sides.
What is the difference between a sales order and a purchase order?
A purchase order is the buyer’s document asking a supplier to deliver goods or services at an agreed price. A sales order is the seller’s internal record of that same order, used to deliver and invoice. A detailed guide to the difference is in preparation.
What is record-to-report?
Record-to-report (R2R) is the finance cycle that records transactions in the general ledger, closes each period and produces financial statements. It takes its entries from procure-to-pay, through accounts payable, and from order-to-cash, through accounts receivable.
What is cash application?
Cash application is the seller’s step of matching each incoming payment to the invoices it pays and clearing them from accounts receivable. It is fast when the buyer sends invoice numbers with the payment, and slow when the payment arrives with a vague reference.
New guides on the procure‑to‑pay line
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.