PO vs Non-PO Invoice: How the Approval Process Differs

Summary

A PO and non-PO invoice look almost identical on paper, but they travel through completely different approval paths once they reach accounts payable. A PO invoice arrives with its approval built in, tied to a purchase order that was already reviewed and signed off before the goods or services showed up. A non-PO invoice has no such head start. It lands in AP cold, and someone has to figure out who owns that spend, code it correctly, and route it to the right approver, often more than once. Understanding where these two paths actually diverge, not just that they're different, is what separates a controlled approval process from one that quietly bottlenecks every month, and it's the difference that decides whether growth adds headcount or just adds delay.

What Actually Separates a PO Invoice From a Non-PO Invoice

A PO invoice is generated after a purchase order has already been approved. It references that purchase order by number, and its job in accounts payable is confirmation: does what arrived match what was ordered. A non-PO invoice has no purchase order to check against. It usually covers spend that didn't go through a formal procurement step, such as a one-off service contract, a utility bill, or an employee reimbursement.

The practical difference comes down to when approval happens. A PO invoice is approved before the purchase, so by the time the invoice shows up, the approval decision has already been made. A non-PO invoice is approved after the fact, which means the approval decision and the payment decision happen at the same time, under time pressure, and usually by someone who wasn't involved in the original spend.

	PO Invoice	Non-PO Invoice
Tied to a purchase order	Yes	No
When approval happens	Before the invoice arrives	After the invoice arrives
Typical use	Direct procurement: inventory, raw materials, recurring vendor orders	Indirect spend: services, reimbursements, one-off purchases
Who gets involved	AP team, matched automatically in most cases	AP team plus a manager or budget owner
Where delays happen	Mismatches between PO, invoice, and goods receipt	Finding the right approver and getting a response
Audit trail	Built from the PO, receipt, and invoice record	Depends on whether coding and approval steps were logged consistently
Risk if mishandled	Overpayment on quantity or price errors	Duplicate payment, misclassified spend, or unauthorized purchases going through unnoticed

‍

How the Approval Process Works for PO Invoices

Because a PO invoice is tied to a purchase order that's already been approved, AP's job is matching, not deciding. Most organizations run either a two-way match, checking the invoice against the purchase order, or a three-way match, which adds the goods receipt to confirm the order was actually fulfilled. If the numbers line up: quantity, price, vendor, the invoice can move to payment without a human making a fresh approval decision.

The exception is a mismatch. If the invoice states a different price than the PO, or the goods receipt shows a partial delivery, the invoice stops and gets routed back for review. This is where PO-based processing earns its reputation for speed: most invoices clear without intervention, and the ones that don't are flagged automatically instead of sitting in someone's inbox.

Matching Mechanics, Briefly

A two-way match compares only the purchase order and the invoice, confirming vendor, quantity, and price. It's common for services or purchases where a physical goods receipt doesn't apply, such as software licenses. A three-way match adds the goods receipt into the comparison, confirming that what was ordered, billed, and received all agree, which is standard for physical inventory. When a mismatch turns up, a price discrepancy from an added freight charge or a quantity gap between what was ordered and what arrived, the invoice stops and routes back to the person who issued the PO rather than getting paid as submitted.

Matching is a large enough topic to deserve its own treatment. For a deeper look at where three-way matching actually breaks on real ERPs, and how two-way matching works and when to use it instead, those are covered in full elsewhere on the blog.

‍

How the Approval Process Differs for Non-PO Invoices

A non-PO invoice skips the matching step entirely because there's nothing to match against. Instead, it needs three things before it can be paid: correct coding to a cost center or GL account, identification of the right approver, and that approver's sign-off, sometimes from more than one person depending on the amount.

Consider a logistics company with 40 active vendors that receives a $1,200 invoice from a law firm for a one-off contract review. There's no purchase order, because outside counsel spend was never run through procurement. The invoice lands in AP, gets coded to the legal expense line, and then has to reach whichever manager owns outside counsel spend, who may or may not check email that day. Multiply that single invoice by the dozens of ad hoc, non-PO invoices a mid-sized company receives every month, and the pattern becomes clear: each one depends on someone in AP correctly guessing who should approve it.

How Approval Thresholds and Delegation of Authority Work

Most companies handle non-PO approval risk with a delegation of authority table: a manager can approve invoices up to a set dollar amount on their own, and anything above that requires a second sign-off, often from a director or VP. A typical structure might allow a department manager to approve up to $2,500 alone, require a director's sign-off between $2,500 and $15,000, and route anything above $15,000 to a VP or controller.

The problem isn't the concept, it's consistency. When these thresholds live in a policy document nobody has opened in a year, AP staff end up applying their own judgment about who to route an invoice to, and that judgment varies person to person. A threshold table only controls risk if it's actually the thing being followed at the moment an invoice is coded, not a reference document from onboarding.

‍

Where Non-PO Approval Breaks Down at Scale

The single-invoice version of this process is manageable. The problem shows up at volume. A manufacturer with 300 active suppliers does not have 300 versions of the same invoice, but it often ends up with close to 300 different informal understandings of who approves what, especially when those rules live in a spreadsheet, an email thread, or one person's memory.

Manual routing at that scale produces predictable failures: invoices sent to the wrong approver, approvers who've left the company still listed as the default contact, and inconsistent thresholds where one manager rubber-stamps everything over $5,000 while another questions anything over $500. A second failure mode shows up during headcount changes: when a department reorganizes, approval ownership for that department's non-PO spend often doesn't get updated anywhere formal, so invoices keep routing to someone who no longer owns that budget.

None of this is a training problem. It's a structural one: without a system that stores approval logic somewhere more durable than institutional memory, consistency degrades every time a company adds a supplier or an employee changes roles.

It's worth naming the trade-off honestly. Automating this process doesn't remove the need for a human to make judgment calls on genuine exceptions, like a disputed invoice or an unusual dollar amount. What it removes is the manual work of figuring out where to route the invoice in the first place, which is where most of the delay actually lives.

‍

Common Approval Bottlenecks, Compared

Bottleneck	PO Invoices	Non-PO Invoices
Most common delay	Price or quantity mismatch against the PO	Finding the correct approver
Who usually causes the delay	Vendor billing error	Internal routing gap
How it typically gets caught	Automated two-way or three-way match	Manual review, often after AP follows up
Fix that actually works	Clear PO terms agreed with the vendor upfront	Documented, current approval ownership by department and dollar amount

‍

Should You Convert More Non-PO Spend Into Purchase Orders?

It's tempting to conclude that the fix for non-PO delays is simply to run more spend through purchase orders. Sometimes that's right. Recurring vendors, predictable services, and anything above a meaningful dollar threshold usually benefit from a PO, because it moves the approval decision earlier and removes the after-the-fact scramble.

But forcing every purchase through a PO has its own cost. A one-off $300 repair or a single conference registration doesn't justify the overhead of a requisition, approval, and PO issuance before the purchase can even happen. The right approach isn't eliminating non-PO invoices, it's being deliberate about where the line sits, and making sure whatever falls below that line still has a clear, current approval path rather than an informal one.

‍

How to Reduce Non-PO Approval Delays Without New Software

Before evaluating any tool, a few changes cost nothing and remove a meaningful share of the delay. Keep a single, current document listing who approves what, by department and dollar amount, and treat any personnel change as a trigger to update it the same day. Standardize GL coding categories so AP isn't guessing which cost center a services invoice belongs to. Set a default escalation path, so an invoice that sits unapproved for more than a set number of days automatically goes to a backup approver instead of waiting indefinitely.

These steps won't fully close the gap at high supplier volume, but they remove the easiest failure points before automation becomes necessary, and they make whatever automation comes next easier to configure correctly.

‍

Applying Consistent Approval Rules Without Rebuilding the ERP

This is where most AP automation conversations stall, because a lot of legacy ERPs and accounting platforms used for approval routing don't expose an API. That's less unusual than it sounds. Many mid-sized and enterprise finance teams still run desktop-only accounting software or older ERP versions that were never built with integration in mind, which means most automation tools simply can't reach them.

LayerNext handles this with a computer use agent that operates the ERP through its own interface, the same way a person would, instead of requiring an API connection. That removes the usual blocker: no middleware, no IT integration project, just automation that works with the system already in place. The invoices themselves can also arrive through whichever channel a company already uses: a dedicated AP email inbox, a shared folder, cloud storage such as an AWS S3 bucket or Google Cloud, a SQL database, or direct retrieval from the accounting system, so the approval workflow doesn't depend on standardizing how every vendor sends its bills first.

The second piece is where the rules themselves live. LayerNext has a Business Rules section where the finance team can write and edit entity-specific approval logic in plain English, without involving IT. If a company has different approval rules for each of its 300 suppliers, the system's rule engine can retrieve the correct one by querying the supplier's name, even across thousands of rules. That's the difference between a policy that exists on paper and one that actually gets applied the same way every time.

‍

Measuring Whether Your Approval Process Is Actually Working

A few metrics reveal more about approval health than a general sense of whether things feel slow. Touchless processing rate is the share of invoices that move from receipt to payment with no manual intervention at all, which tends to be high for well-matched PO invoices and low for non-PO invoices unless routing is automated. Approval cycle time is the average number of days between an invoice arriving and receiving final sign-off, tracked separately for PO and non-PO invoices since they behave differently. Exception rate is the share of invoices that get flagged for manual review, which is useful for spotting whether a rising number reflects genuine problems with vendors and approvers, or a matching and routing setup that's too rigid.

Ardent Partners' State of ePayables 2025 report, published in January 2026, puts the average AP invoice exception rate across the industry at 18.4%. Best-in-Class AP teams, the top 20% of enterprises ranked by processing cost and cycle time, run exception rates 47% lower than that average and process invoices in a straight-through manner at nearly twice the rate of everyone else. The gap isn't a difference in how hard either group works. It's a difference in how much of the exception-routing decision still depends on a person guessing correctly instead of a rule already knowing the answer.

Tracking these by invoice type, rather than as one blended number, is what makes the metric useful. A blended cycle time can look fine while non-PO invoices are quietly taking three times as long as PO invoices to clear.

‍

What to Evaluate Before Changing Your Approval Workflow

Before adopting any new approval process, it's worth checking a few things beyond speed. First, what happens to exceptions: does the system just flag a mismatch and stop, or does it create something a human can actually act on. Second, how visible is the current state of approvals: can a controller see, at a glance, how many invoices are pending and where they're stuck. Third, how much does it cost in time to change a rule once it's live: if updating an approval threshold or adding a new supplier's rule requires a development cycle, the workflow will always lag behind how the business actually operates.

LayerNext creates a structured task any time it needs a human decision, searchable by invoice number, so an AP team member can look up a specific invoice instead of digging through an inbox. Its Insight Board gives managers a real-time view of how many invoices are processed versus pending clarification, which turns "is this under control" from a guess into a number anyone can check. Because workflow changes are configured without a development cycle, a finance team can adjust a routing rule the same way they'd edit a spreadsheet, rather than filing a ticket and waiting.

‍

FAQ

‍

1. What is the difference between a PO invoice and a non-PO invoice?

A PO invoice is tied to a purchase order that was approved before the purchase happened, so accounts payable only has to match the invoice against that order. A non-PO invoice has no purchase order attached, so it needs to be coded and routed to an approver after it arrives, which takes more time and more manual judgment.

2. What is a PO invoice?

A PO invoice is an invoice generated after a purchase order has already been issued and approved. It references the purchase order number and typically covers direct procurement, such as inventory or vendor orders placed through a formal process.

3. What is a non-PO invoice?

A non-PO invoice, sometimes called an expense invoice, is an invoice with no associated purchase order. It's common for indirect spend like professional services, utility bills, or employee reimbursements, and it requires approval after the invoice arrives rather than before.

4. How does the approval process differ between PO and non-PO invoices?

PO invoices are approved in advance through the purchase order, so accounts payable mainly confirms a match between the order, invoice, and goods received. Non-PO invoices require coding and routing to the correct approver after the fact, since there's no prior approval to check against.

5. What is the difference between two-way and three-way matching?

A two-way match compares the invoice against the purchase order only, checking vendor, quantity, and price. A three-way match adds the goods receipt, confirming that what was ordered, billed, and received all agree, which is standard for physical goods rather than services.

6. What are examples of non-PO invoices?

Common examples include employee expense reimbursements, one-off professional services like legal or consulting work, utility and subscription bills, and small purchases made outside the standard procurement process.

7. Why do non-PO invoices take longer to approve than PO invoices?

Non-PO invoices need a human to identify the correct approver and route the invoice manually, since there's no purchase order to confirm the spend was already authorized. PO invoices skip that step because the approval already happened when the purchase order was issued.

8. Can non-PO invoice approval be automated?

Yes. Coding, approver identification, and routing can all be automated using entity-specific business rules, which removes the manual guesswork while still routing genuine exceptions to a person for review.

9. What happens if a PO invoice doesn't match its purchase order?

If the price, quantity, or vendor on the invoice doesn't match the purchase order or goods receipt, the invoice is flagged as an exception and routed for manual review instead of being paid automatically.

10. Does every business need to use purchase orders?

No. Many businesses use purchase orders only for direct, repeatable procurement and handle smaller or one-off spend through the non-PO process instead. The right mix depends on transaction volume and how much control a company needs over indirect spend.

‍

Sayuru Karunathilaka

Content Contributor

Sayuru is a member of LayerNext's marketing team and a part-qualified Chartered Accountant, writing about AI-powered bookkeeping, AP automation, and cloud accounting for businesses of every size.

Get in Touch