Purchase order to invoice: How to flip a PO in 7 steps

A clean purchase order (PO) to invoice flip turns your customer's PO into an invoice their accounts payable (AP) team approves on the first pass. That's how you get paid on the terms you agreed to.
Most AP holds start in the gap between purchase orders and invoices, like a missing PO number or a price that drifted after the quote. The work runs from a received PO to applied cash, and each step is built to pass the buyer's match.
What is a PO flip?
A PO flip is turning a customer's purchase order into an invoice that carries over the PO number, line items, quantities, prices, and terms. The goal is an invoice that matches what the buyer approved, line for line.
Your accounts receivable (AR) or billing team does the flip after goods ship or the service is delivered. On partial fulfillment, you flip at each shipment or contract milestone and bill only the lines that went out.
The buyer's AP team then compares your invoice to their PO, usually with a 2-way or 3-way match. When the fields line up, the invoice moves to payment.
| PO field | Where it goes on the invoice |
|---|---|
| PO number | Invoice header, in a dedicated PO number field |
| Buyer entity | Bill-to name, using the exact legal entity shown on the PO |
| Ship-to and bill-to | Ship-to and bill-to blocks, copied as written on the PO |
| Line items and SKUs | Line detail, in the PO's line order with the same line numbers and SKUs |
| Quantities | Quantity column, showing units shipped or delivered for this invoice |
| Unit prices | Unit price column, at the PO price unless a change order updated it |
| Payment terms | Terms field in the header, such as net 30, with the due date based on those terms |
| Tax treatment | Tax lines, matching the PO's taxable status or the buyer's exemption certificate on file |
Copy each field the way the buyer wrote it, down to abbreviations in the entity name. AP clerks match on exact values.
What the buyer's AP team checks your invoice against
Once your invoice arrives, the buyer's AP team compares it to the PO, and often to their receiving record too. Their system flags anything that doesn't line up, and a flagged invoice waits until someone on their side clears it.
These mismatches put an invoice on hold most often:
- Price: A unit price above the PO price fails the match, even by a few cents, unless it falls inside the buyer's tolerance.
- Quantity: Billing more units than the PO allows, or more than the receiving dock logged, triggers a hold.
- Missing PO number: AP can't find the PO to match against, so the invoice often comes back to you.
- Wrong legal entity: An invoice addressed to the parent company won't match a PO issued by its subsidiary.
- Different terms: Net 15 on your invoice against net 45 on the PO gets flagged or paid on the buyer's terms.
| Match type | Documents compared | What fails it | What you control as the seller |
|---|---|---|---|
| 2-way match | Invoice and PO | Price or quantity outside tolerance, or no PO number | PO number, unit prices, and quantities billed |
| 3-way match | Invoice, PO, and receiving record | Billed quantity higher than what the buyer received | Billing only what shipped, backed by proof of delivery |
| 4-way match | Invoice, PO, receiving record, and inspection report | Goods billed before they pass the buyer's inspection | Invoice timing, sent after acceptance when the PO requires it |
For AR, an invoice that fails the match is cash that shows up late. Pass the match on your side first.
How to flip a purchase order to an invoice in 7 steps
The purchase order to invoice process has seven steps, and two of them happen before you draft anything. The PO data you confirm in step one is the data you bill from in step three.
1. Confirm the PO and acknowledge it
Check the PO against your quote or contract before you ship anything. Compare pricing and quantities first, then delivery dates and payment terms. Flag every difference to the customer in writing.
Send an acknowledgment that confirms the PO number and any corrections. If the buyer needs to change a price or quantity, ask for a revised PO or change order before fulfillment.
Record the PO number and the buyer's AP contact in the customer file. Add their invoicing instructions too, such as a supplier portal or electronic data interchange (EDI) requirements. A discrepancy you fix now never shows up on a rejected invoice.
2. Fulfill the order and capture proof of delivery
Your invoice holds up only as well as the delivery record behind it. Keep the signed packing slip or service sign-off for every delivery, and file it under the PO number.
The buyer's receiving team logs the same delivery on their side, which feeds their 3-way match. If your record and theirs disagree on quantity, your proof of delivery settles it.
For partial shipments, note which PO lines and quantities shipped on each date. Bill only from that record.
3. Draft the invoice from the PO data
Build the invoice from the PO fields already in your system, so nobody retypes a price or SKU. Most enterprise resource planning (ERP) systems and accounting tools can turn an order record into an invoice.
In Ramp Accounts Receivable, you upload the customer's purchase order. An agent extracts the customer details, line items, pricing, and payment terms, then prepares a draft invoice. Review the draft against the PO and your delivery record, then send it once the order ships.
Every invoice needs these fields:
- Invoice number
- Invoice date
- PO number
- Line items that follow the PO's line numbers and descriptions
- Quantities shipped for this invoice
- Unit prices from the PO
- Sales tax, or the exemption that applies
- Payment terms and due date
- Remit-to details for each payment method you accept
A missing field gives the buyer's AP team a reason to hold the invoice. Check all fields before you move to review.
4. Review the invoice against the PO before it goes out
Run your own match before the buyer runs theirs. Compare the invoice line by line with the PO and the delivery record, checking price and quantity on each line.
Stop the invoice if you find a price change, a product substitution, or an over-shipment. Each one needs a PO change order from the buyer before you bill it, or AP will hold the difference.
Have someone other than the drafter do the review. Send any invoice over $25,000 or any first invoice to a new customer to a second reviewer, usually the accounting manager. A second review takes minutes, while a rejected invoice can cost you a full payment cycle.
5. Send the invoice the way the buyer requires
Send each invoice through the channel named in the buyer's invoicing instructions. An invoice sent anywhere else often never enters their AP queue, and the channel also sets how quickly AP can see and approve it.
| Delivery method | When buyers require it | What to include | Common reason it's rejected |
|---|---|---|---|
| Supplier portal (Coupa, SAP Ariba) | Larger buyers that run procurement through a portal | Invoice flipped from the open PO in the portal, plus quantities and proof of delivery | Lines don't map to open PO lines, or quantity exceeds the remaining PO balance |
| EDI 810 | Retailers and distributors with EDI trading partner agreements | PO number, line numbers, and SKUs or UPCs that match the buyer's 850 PO | Codes or segments that don't follow the buyer's EDI spec |
| Email to an AP inbox | Buyers without a portal or EDI setup | PDF invoice, PO number in the subject line, payment link, and remittance instructions | Sent to the requester instead of AP, or PO number missing |
Put a payment link and remittance instructions for each method you accept on every invoice. Customers who can pay from the invoice don't have to email you for bank details.
Within 2 business days, confirm the buyer received it, either from portal status or a reply from AP. For EDI, look for the 997 acknowledgment. Log that confirmation in the customer file.
6. Record the receivable in your books
Post the invoice to AR on the invoice date, tied to the customer, the PO number, and the sales order. That link lets your team find the PO when a customer asks about a balance or a remittance arrives without an invoice number.
For partial invoicing, track the remaining balance on each PO line after every invoice. A PO for 1,000 units with 600 invoiced should show 400 open, which stops over-billing and flags lines you shipped but never billed. Review open PO balances at month-end so no shipped line goes unbilled.
7. Follow up, collect, and apply cash
Set a collections cadence tied to the due date, and put the PO number and invoice number in every message. Buyer AP teams search by PO, so that reference gets you a status answer quickly.
- 7 days before the due date: Send a reminder with the invoice copy and payment link attached.
- On the due date: Confirm with AP that the invoice is approved and scheduled for payment.
- 7 days past due: Send a second notice to the AP contact with the PO and invoice numbers.
- 15 days past due: Call the AP contact and ask where the invoice sits in their approval queue.
- 30 days past due: Escalate to the buyer's requester or PO owner, and loop in your account owner.
- 45 days past due: Apply your credit policy, such as holding new orders until the balance clears.
When payment arrives, match it to the invoice and the PO. Short-pays and deductions usually trace back to a PO difference, like a line the buyer paid at the PO price or units they didn't receive.
Reconcile each deduction against the PO and your delivery record. Then issue a credit memo or send the customer the backup to collect the balance.
The PO to invoice cycle is done when every line is invoiced and paid. Close it in your system once it is.
Common purchase order to invoice errors
Each of these errors gets your invoice held, rejected, or short-paid by the buyer's AP team. Every fix belongs in your pre-send review.
Missing or mistyped PO number
An invoice without the PO number, or with two digits transposed, can't be matched to anything in the buyer's system. AP rejects it back to you or parks it in an exception queue until someone finds the PO by hand.
Pull the PO number from the sales order record and confirm it against your acknowledgment. Make the PO number a required field on your invoice template.
Prices or quantities that don't match the PO
A price increase without a change order fails the match, and so does a quantity above what the buyer's dock logged. AP usually short-pays to the PO price or received quantity, or holds the full invoice until someone approves the variance.
Get the change order before you bill a new price, and bill quantities from your proof of delivery. Recovering a short-pay later takes a separate dispute with the buyer.
Invoicing the wrong legal entity or bill-to address
Buyers with subsidiaries issue POs from specific legal entities, and each entity has its own vendor record for you. An invoice addressed to the parent, or to an old bill-to address, gets rejected or routed to the wrong AP team.
Copy the entity name and bill-to address exactly from the PO, and update the customer record when a PO shows a new entity. Check the entity before the first invoice on every new PO.
Billing before delivery or over-billing a partial PO
Invoicing before goods arrive breaks the 3-way match, since the buyer has no receipt to compare against. Billing a line twice, or billing past the PO's remaining balance, gets the invoice rejected or the excess short-paid.
Date invoices on or after the ship or delivery date, and check the open PO balance before you bill a partial. Bill against the open balance and nothing more.
Sending the invoice to the wrong channel
An invoice emailed to your contact in operations never reaches AP when the buyer requires portal submission. The buyer can't hold or reject an invoice they never received, so it ages with no status.
Store each customer's invoicing channel in the customer record, and send every invoice there. Update the record as soon as a buyer announces a portal change.
Turn POs into paid invoices with Ramp Accounts Receivable
Flipping POs by hand means rekeying every price and term, writing each follow-up yourself, and matching deposits to invoices one at a time. Every retyped field is another chance to fail the buyer's match.
Ramp Accounts Receivable gives your finance team one workflow from invoice to applied cash. AI agents do the drafting and matching work, and your team signs off on every customer message.
With Ramp AR, the PO flip looks like this:
- Draft invoices from POs: An agent pulls pricing and payment terms from the purchase order with the customer's details, so you don't retype them.
- Add a payment link to every invoice: Customers pay by Automated Clearing House (ACH) debit, ACH credit, credit card (via Stripe), or check.
- Prepare follow-ups on your terms: An agent drafts each collections message using the timing and tone Finance sets. Your team reviews and edits each one, then sends it.
- Match payments to open invoices: Cash application reads the payer and amount on each payment, then pairs it with the right open invoice.
- Keep your books current: A one-way sync updates QuickBooks Online or NetSuite as invoices and payments post.
Try an interactive demo to see how Ramp turns purchase orders into paid invoices.

FAQs
Confirm the PO and fulfill the order with proof of delivery. Draft the invoice from the PO data, review it line by line, then send it the way the buyer requires. Record the receivable and follow up until cash is applied.
No. A PO authorizes a purchase, and an invoice requests payment for what you delivered. The buyer's AP team pays from your invoice after matching it to the PO, which is why purchase orders and invoices have to agree.
Put the PO number in a dedicated field in the invoice header, next to the invoice number and date. Most accounting tools let you add the field to your invoice template. AP uses it to find the PO, so leave it off and your invoice can't be matched.
The PO comes first. The buyer issues it and you fulfill the order. Then you invoice for what you delivered.
PO flip is AR shorthand for turning a customer's purchase order into a matching invoice. You do it after fulfillment, using the PO's number and line items.
“I assumed I would have to choose between speed and control. What I found is that you can have both. A well-designed system takes friction out, for the finance function and for everyone else.”
Justin Webster
CFO, Denver Broncos

“A well-run district should not have to choose between getting work done at the school site and keeping control of the dollars behind it. We're not hiring more people to do more jobs, so we have to be smarter about the process. With Ramp, the purchase, the receipt, and the record stay together from the start. ”
Nick Brizeno
Director of Purchasing, San Marcos Unified School District

“In senior living, scale only works if the communities still feel personal. We needed the back office to carry more of the complexity, not the people serving residents. Ramp helped us build that infrastructure, so the experience in the community could stay human.”
Ryan Cole
CFO, Agemark Senior Living

“AI is moving faster than the finance context around it. Prices change, models change, and the value is not always obvious from an invoice. We needed enough detail to know which bets deserved more investment — and which ones did not.”
Greg Cooley
Controller, AngelList

“Invoices, cards, tokens. The categories change but the principle doesn't: know where the money is going, remove the work around it, and make sure the spend is worth it.”
Maciej Mylik. Finance
ElevenLabs

“We weren’t trying to retrofit an old finance system. We had a blank canvas, and Ramp gave us the foundation to build a global finance function of the future.”
Justin Dourado
Director of Finance, Othership

“There's just no surprises anymore. No more waiting two months to find out how a job did. We know how it's doing as it's happening.”
Erich Kuss
Financial Systems Manager, Infinity Home Services

“More token spend isn’t proof that AI is working. Less isn’t proof that it isn’t. What matters is whether we’re buying the right level of intelligence for the work. Ramp lets us make that judgment in the same place we manage every other type of spend.”
Cody Nutt
Senior Director of Business Systems, Daxko



