PO vs. Invoice: What's the Difference and Why Matching Matters

An invoice lands in your inbox for $14,500. The vendor name looks right, the logo is there, and the amount sits close enough to what you expected that nobody blinks. So you pay it. Three weeks later you learn the real vendor never sent it, the bank details were swapped, and your money is sitting in an account you'll never see again.

That scenario plays out more often than most finance teams want to admit. The FBI's Internet Crime Complaint Center logged $3.04 billion in business email compromise losses in 2025 alone, much of it tied to fake invoices and spoofed vendor requests. The thing standing between a clean payment and an expensive mistake is usually something unglamorous: a purchase order, and the habit of matching it against the invoice before any money moves.

For finance leaders, this is less about paperwork and more about control. So let's clear up what a PO actually is, how it differs from an invoice, and why matching the two quietly does more to protect your company than almost anything else in the AP workflow.

What's the Difference Between a PO and an Invoice?

A purchase order is the document your company sends out. It's the buyer saying, in writing, "here's exactly what we want to buy, at this price, in this quantity, delivered here." Your team creates it before anything ships, which sets the terms and locks in the agreement so there are no surprises later.

An invoice is the document the vendor sends back. It's the seller saying, "here's what we delivered, and here's what you owe us." The invoice arrives after the goods or services change hands, and it's the vendor's formal request to get paid.

Think of the PO as the promise and the invoice as the bill that follows. One looks forward to what's coming, the other looks back at what happened. When the two agree, everyone stays on the same page. When they don't, that gap is exactly where errors and fraud like to hide.

What's a PO number, and where does it live on the invoice?

Every purchase order gets a unique PO number the moment it's created. That number's the thread that ties the whole transaction together, from the original request all the way to the final payment.

When the vendor sends their invoice, they're supposed to print that same PO number on it, usually near the top or in a clearly labeled field. That single reference lets your AP team pull up the matching purchase order in seconds instead of playing detective across email threads and spreadsheets. A PO number on the invoice is the difference between a five-second lookup and a twenty-minute scavenger hunt.

PO matching: the part that actually protects you

Matching invoices to purchase orders means lining up the invoice against the original PO, and often the receiving record, to confirm three things agree: what was ordered, what showed up, and what you're being billed for. When all three line up, the invoice clears for payment. When something is off, it gets flagged before a dollar leaves the building.

Most teams run one of two versions. A two-way match compares the invoice to the PO and asks a simple question: did we order this, at this price? A three-way match adds the receiving record and asks one more: did we actually get it? That third check is what stops you from paying for a shipment that never arrived, and it's the version most controllers lean on for anything that touches inventory or equipment.

This is where the real value sits, because matching is a control, and a good one. Most of what it catches comes down to honest mistakes, not crime. A quantity that doesn't add up, a duplicate invoice that's already been paid, a price that drifted from what you agreed to. Those slip through quietly and add up over a year, and a disciplined match stops them before the money goes out.

Fraud is the high-stakes end of that same spectrum. The Association for Financial Professionals found that 79% of organizations faced attempted or actual payments fraud, with fake invoices and vendor impersonation ranking among the fastest-growing schemes. Those are the increasingly common fraud vectors, and a match is what catches the invoice with no PO behind it or the vendor name that's almost right but not quite.

What a broken match actually costs you

The damage from weak matching rarely shows up as one big number. It accumulates quietly, in overpayments that never get clawed back, duplicate invoices paid twice, late fees on invoices stuck in review, and early-payment discounts left on the table because an approval took too long. APQC's benchmarking data shows that even top-performing AP teams pay out 0.8% of their annual disbursements as duplicate or erroneous payments, while weaker performers hit 2%. On a large spend, that gap turns into real money you never decided to spend.

Then there's the human cost. PYMNTS Intelligence reports that 68% of firms still process invoices manually, which means the majority of AP teams are still one distracted moment away from a missed match. That work is slow, repetitive, and exactly the kind of task where focus drifts and mistakes creep in. The more invoices your team touches by hand, the more chances a bad one has to slip through.

At the far extreme sits outright fraud. The ACFE estimates the typical organization loses 5% of revenue to fraud every year, and a meaningful share of that runs through billing schemes and bogus invoices that a solid match would've caught. Matching isn't busywork. It's the cheapest insurance policy your AP team will ever run.

When should you require a PO, and when is a non-PO invoice fine?

Not every purchase needs a PO, and forcing one onto everything will only slow your team down. The trick is knowing where to draw the line.

Require a PO for anything planned, repeatable, or high-dollar: inventory, equipment, parts, recurring vendor contracts, large service engagements. These are the spends where a match gives you real protection and a clean audit trail, and any purchase where the amount or quantity matters is a strong candidate.

Non-PO invoices make sense for the small, one-off, or unpredictable stuff, like a utility bill, a quick reimbursement, or a low-dollar subscription. The key is to set a clear dollar threshold and an approval path so non-PO spend gets a second set of eyes instead of a free pass. The goal is sensible controls, not bureaucracy for its own sake.

The everyday errors that break a match

Most match failures aren't fraud. They're small, human discrepancies that gum up the works and force someone to chase down an answer. A few show up over and over:

Vendor name mismatches. The PO says "Acme Manufacturing Inc." and the invoice says "Acme Mfg." A person knows those are the same company, but a rigid system stops cold and kicks it to a human.

Partial deliveries. You ordered 100 units, 60 arrived, and the invoice bills for 60. The numbers don't match the PO total even though nothing's actually wrong, so someone has to confirm the rest is still coming.

Freight and surcharges. The invoice includes shipping or a fuel surcharge that never appeared on the PO. The charge is legitimate, but it throws off the dollar match and triggers a review.

Tax discrepancies. Sales tax gets calculated differently, or applied where the PO didn't account for it, and the totals drift apart by a few dollars. Small gap, same result: a stuck invoice.

None of these are disasters on their own. Pile up a few hundred of them a month, though, and your team spends its days resolving exceptions instead of doing higher-value work.

How AI-powered matching handles the messy edge cases

Older systems matched on exact values, so every "Acme Mfg." and every freight charge landed in a manual exception pile. Modern AP automation reads context instead of characters, working through those gaps the way an experienced clerk would.

AI-powered capture pulls the data off any invoice, in any format, and knows that "Acme Mfg." and "Acme Manufacturing Inc." are the same vendor. It checks line items against what was actually received, so a partial delivery clears on its own, and it treats freight and tax as the expected variances they are instead of stopping the match. Clean invoices move through untouched, and only the ones that truly need a person land on the right approver's desk.

That changes the math for your team. Instead of touching every invoice, they review the small slice that actually warrants attention. Approvals move faster, fraud has fewer places to hide, and the controller gets real visibility into what's been matched, what's pending, and what's been flagged. The control gets stronger and the work gets lighter at the same time.

The bottom line

A purchase order and an invoice are two sides of the same deal: one sets the terms, the other asks for payment. Matching them is how you confirm the story holds together before the money moves, and it's one of the most reliable defenses against the fraud and errors quietly draining finance teams every year.

The companies doing this well aren't matching by hand anymore. They've handed the repetitive, error-prone work to automation and freed their people to focus on the exceptions that matter. That's the shift onPhase was built for: turning AP from a backlog of manual checks into a fast, controlled process you can actually trust.

Matching is one piece of that picture. Once it's running clean, the real payoff comes from seeing how the whole AP process performs, and the metrics that show you where it still slips.