Purchase Order to Invoice Process: PO to Payment Flow

The purchase order to invoice process is the sequence that turns a buying decision into a paid supplier bill: a requisition is approved, a purchase order is issued to the supplier, the goods or services arrive and are receipted, the supplier sends an invoice, and accounts payable matches that invoice to the PO and the receipt before releasing payment. Finance teams call the whole cycle procure-to-pay. The purchase order is the buyer's commitment; the invoice is the supplier's demand for money against it.

Last updated July 2026.

Every step below depends on one thing: knowing exactly what the purchase order said. If your POs arrive as PDFs, upload one above and the PO number, supplier, dates, and every line item come back as Excel, CSV, or JSON in about ten seconds, so accounts payable is matching against real data instead of scrolling a scanned attachment.

What is the purchase order to invoice process?

The purchase order to invoice process is the workflow that runs from raising a purchase order through to paying the supplier's invoice for it. It exists to make sure a company only pays for what it actually ordered, actually received, and actually agreed a price for. Each document in the chain, the PO, the goods receipt, and the invoice, is evidence for the next step, and the match between them is the control that protects the cash.

Larger organizations wrap the same chain in more approvals, but the spine does not change. A purchase requisition starts it internally, the purchase order makes it external and binding, receiving confirms delivery, and accounts payable closes it out. If you want the procurement half in more depth, the purchase order process steps and workflow guide covers stages one through four in detail.

The purchase order to invoice process flow, step by step

Here is the standard flow most US finance teams run, with the document each stage produces and the team that owns it. Read it as a flow chart in table form: each row hands off to the one below it.

Notice that stages 2, 4, and 5 each produce a document, and stage 6 is where those three documents meet. That meeting point is the three-way match, and it is the single most important control in the whole cycle.

Which comes first, the purchase order or the invoice?

The purchase order comes first. The buyer issues the PO before anything is delivered, setting out what is being bought, at what price, and on what terms. The supplier sends the invoice afterward, once the goods or services have been provided, and quotes the PO number on it so the buyer can tie the bill back to the original order. An invoice that arrives with no PO reference is the classic source of AP delays.

What is the difference between a purchase order and an invoice?

A purchase order is created by the buyer and is a commitment to buy; an invoice is created by the seller and is a request to be paid. The PO comes first and states what was ordered, the invoice comes last and states what is owed. Both list the same line items, which is precisely why they can be matched against each other. Our fuller breakdown of purchase order vs invoice covers the legal and accounting differences.

What is the PO to invoice cycle called?

Finance and procurement teams call it procure-to-pay, often shortened to P2P. Some organizations use the narrower term "PO to invoice" for just the back half, from the issued order to the paid bill, and reserve procure-to-pay for the full cycle starting at sourcing and supplier selection. In practice the two phrases get used interchangeably in software marketing, so it is worth checking what a vendor means before comparing scope.

How does three-way matching fit into the purchase order to invoice process?

Three-way matching is stage six. Accounts payable compares three things before payment: the purchase order (what you agreed to buy), the goods receipt note (what actually arrived), and the supplier invoice (what you are being billed for). If all three agree on quantity and price within tolerance, the invoice is approved. If any of them disagree, the invoice is held as an exception. We explain the mechanics in what is a 3-way match, and the receipt document itself in the goods receipt note guide.

Some organizations run a two-way match instead, comparing only the invoice and the PO. That is faster and appropriate for services with no physical delivery, but it removes the check that anything was ever received. The tradeoff is laid out in 2-way vs 3-way match.

What happens if an invoice does not match the purchase order?

The invoice is held as an exception and payment stops until the difference is resolved. AP investigates the cause, which is usually one of four things: a price on the invoice that was never agreed on the PO, a quantity billed that exceeds what was received, freight or tax added that the order did not authorize, or a unit-of-measure mismatch where the supplier billed per case and the PO was written per each.

Resolution normally means contacting the supplier for a corrected invoice or a credit memo, or getting an authorized buyer to approve the variance. Most companies set tolerance thresholds, for example a few dollars or a small percentage, below which small differences auto-approve rather than consuming a person's afternoon. Exceptions are expensive: each one adds days to the cycle and puts early-payment discounts at risk.

Where the purchase order to invoice process actually breaks

The process is not usually broken by policy. It breaks in the handoffs, and almost always for one of these reasons.

• The PO number is missing from the invoice. AP cannot match what it cannot identify, so the bill sits in a queue while someone emails the supplier.
• Nobody receipted the delivery. Goods arrived, the warehouse never entered a receipt, and a perfectly valid invoice fails the match. This shows up in the ledger as received-not-invoiced or invoiced-not-received balances.
• The PO lives as a PDF, not as data. If the order was emailed and never keyed into a system, matching is a human reading two documents side by side. That is slow, and it is where transposed digits enter the ledger.
• Line-level detail was never captured. A header total is enough to match a single-line order and useless on a fifty-line one. Without purchase order line item extraction, line-level matching is impossible.
• Approvals are chased over email. Invoices wait on a manager who is traveling, and the discount window closes.

Can the purchase order to invoice process be automated?

Yes, and most of the savings come from automating the two document-reading steps rather than the approvals. Software can capture the purchase order and the invoice into structured data, then let your ERP compare them automatically and route only the exceptions to a human. Approval routing, tolerances, and payment runs are then handled by your ERP or AP platform, which already holds the rules and the audit trail.

Be clear about what each tool in your stack does. PurchaseOrders extracts purchase order documents into clean data. It does not perform the match, hold budgets, or pay suppliers. What it removes is the transcription: instead of an AP clerk reading a supplier PDF and typing the PO number, quantities, and unit prices into a matching screen, the fields arrive as rows. On the invoice side of the same chain, teams typically pull invoice data into a spreadsheet the same way, so both documents reach the match as structured records.

If you want a concrete starting point: pick the highest-volume supplier you have, run a month of their purchase orders through bulk purchase order processing, and see how many of the exceptions your AP team logged last month were caused by data entry rather than by the supplier. That number usually decides the business case on its own. Teams whose main job is the match will want the walkthrough on purchase order extraction for accounts payable, and anyone evaluating tools should start with AI purchase order software.

How long should the purchase order to invoice cycle take?

For a clean, matched invoice on a standard order, a well-run team closes the loop from invoice receipt to payment approval within a few days, then pays on the agreed terms such as Net 30. Exceptions are what stretch it. Every invoice that fails the match adds days of email, and organizations that measure the cycle usually find that a small share of exception invoices consumes most of the AP team's time.

The lever, then, is not to approve faster. It is to have fewer exceptions, and most exceptions trace back to bad data at stage two or stage four. Get the purchase order into your system accurately, receipt deliveries promptly, and the match takes care of itself.