TL;DR (for Controllers and AP teams)

• A non-PO invoice is a bill that arrives with no purchase order behind it, so there is nothing to match it against before payment.
• Non-PO invoices are normal for recurring services (rent, utilities, subscriptions) and small ad hoc buys, but they are also where maverick spend and invoice fraud hide.
• Non-PO invoices typically make up 30 to 50% of all invoices a finance team receives (IOFM). A rising share is a warning sign about procurement policy, so track it as a KPI.
• Because three-way matching cannot run without a PO, you need replacement controls: vendor validation, GL coding at intake, approval routing, and duplicate or fraud checks.
• The mid-market bind: a two-to-three-person finance team cannot eyeball every non-PO invoice. The control has to live in the workflow, not in a person.

Non-PO invoice management is the process of receiving, coding, approving, and paying invoices that were never tied to a purchase order. A PO invoice checks itself through three-way matching. A non-PO invoice does not, so it depends entirely on the controls the finance team wraps around it. Done manually, that is slow and leaky. Done through a structured procurement management and AP workflow, every non-PO invoice gets validated, coded, and routed the same way, and the exceptions surface before money moves.

What is a non-PO invoice – definition and common examples

A non-PO invoice is a vendor bill that has no purchase order attached to it. The purchase happened without a PO being raised first, so when the invoice lands in accounts payable, there is no order to check it against. It is sometimes called an ad hoc invoice or a non-purchase-order invoice.

Companies rely on non-PO invoices because forcing every transaction through a formal PO cycle is impractical for low-value, urgent, or recurring purchases, and some vendors simply will not accept a purchase order. Common examples of invoices that don’t require a purchase order include:

Emergency or low-dollar purchases: transactions where the cost of creating a PO exceeds the value of the purchase itself

Utility and telecom bills: electricity, water, internet, and phone charges billed on a recurring cycle

Professional services: legal counsel, consulting, or accounting fees billed periodically or on milestones

Software subscriptions: SaaS licenses and renewal invoices

Employee reimbursements: travel, parking, or mileage expenses

Facility and maintenance costs: building repairs or equipment servicing

None of these started life as a purchase requisition, so none of them has a matching PO. They usually represent indirect spend rather than planned, direct procurement.

Why do companies use non-PO invoices?

Companies use non-PO invoices when raising a PO first would be impractical or unnecessary. Recurring fixed costs (rent, utilities) do not change month to month, so a PO adds friction without adding control. Small or urgent buys often happen faster than the purchase order process allows, and some vendors will not accept a PO. The tradeoff is that every non-PO invoice gives up the automatic check a PO provides.

Which invoices don’t require a purchase order?

Invoices that typically do not require a purchase order include recurring utilities and rent, tax and government payments, employee reimbursements, and low-value ad hoc purchases below your PO threshold. The test is whether the spend is predictable and already approved through a budget or contract. If it is not, it should have started as a purchase requisition, and paying it as a non-PO invoice is a warning sign, not a shortcut.

Difference between PO and non-PO invoices – key distinctions explained

The core difference is how the invoice gets verified. A PO invoice is checked automatically against the purchase order and the receipt. A non-PO invoice has no order to check against, so a person has to confirm it is legitimate, correctly priced, and coded to the right account.

	PO invoice	Non-PO invoice
Approval	Pre-approved at the PO stage	Approved after the invoice arrives
Matching	Automated three-way match	Manual review, no match possible
Coding	Carried from the PO	Assigned by AP at intake
Control	Built in before the spend	Wrapped around it after the spend
Typical use	Direct, planned procurement	Indirect, recurring, or urgent costs
Risk	Lower	Higher (maverick spend, fraud)

Three-way matching vs. non-PO invoices

Three-way matching compares the purchase order, the goods receipt, and the invoice, and flags any mismatch before payment. It is the strongest control in the accounts payable invoice matching process. It cannot run on a non-PO invoice, because two of the three documents (the PO and, often, the receipt) do not exist. That absence is exactly why non-PO invoices need replacement controls.

Track your PO coverage rate

PO coverage rate is the share of invoices that come in against a purchase order. It is the single most useful diagnostic for non-PO health. When the non-PO share climbs toward or past half of all invoices, it usually means POs are being raised too slowly or procurement policy has gaps. Watching that ratio over time tells a finance leader whether the process is maturing or slipping.

How the non-PO invoice management process works – step-by-step workflow

The non-PO invoice management process moves an invoice from receipt to payment through a sequence of verification and approval steps designed to substitute for the missing purchase order. Because responsibility shifts between departments at each stage, a clearly defined non-PO invoice approval workflow is what keeps these invoices from stalling and is central to managing non-PO invoices in accounts payable.

1. Invoice receipt and capture: following vendor invoice submission guidelines without a PO, the vendor sends the invoice by email, portal, or mail, and AP logs the key fields (vendor, amount, date, description) into the accounting or AP platform.
2. Initial review: AP checks that the invoice is legitimate, not a duplicate, and includes enough detail to identify what was purchased and why.
3. Routing to the requester or department owner: since there is no PO to identify who authorized the spend, AP must locate the employee or department that incurred the cost.
4. Verification of the purchase: the department confirms the goods or services were actually received and that the amount is reasonable and within policy.
5. GL coding: the invoice is assigned to the correct general ledger account and cost center.
6. Approval routing: depending on invoice value, one or several approvers sign off, often following a tiered approval matrix that defines how to approve non-PO invoices.
7. Payment processing: once approved, the invoice is scheduled and paid according to agreed vendor terms.
8. Recording and audit trail: the approved invoice, coding, and approval history are archived for future reference and audit.

Automating this sequence with defined business logic that routes invoices to designated approvers based on department or expense type removes much of the manual hunting for approvers that otherwise slows non-PO invoices down.

How to approve non-PO invoices without email chaos

Approve non-PO invoices through a single routing rule, not a forwarded email. Define who can approve which amounts for which cost centers, and let the system escalate anything above a threshold. Managing non-PO invoices in accounts payable breaks down when approvals live in inboxes, because there is no record of who approved what, and that is the exact gap auditors and fraudsters both find.

GL coding and invoice coding best practices for non-PO invoices

Invoice coding is assigning each invoice to the correct general ledger account, cost center, and tax treatment so the spend lands in the right place in your books. For non-PO invoices it is especially critical, because there is no PO to carry the coding, so an error here flows straight into your financials.

Common coding errors and how to avoid them:

• Wrong cost center. Ambiguous invoices get coded to a catch-all. Fix: capture the cost center at intake from the requester, not at month-end from memory.
• Inconsistent vendor coding. The same vendor gets coded differently across invoices. Fix: default a GL code per repeat vendor and apply it automatically.
• Missing a business justification. No one records why the purchase was made. Fix: require a short justification field alongside the coding.
• Missed accruals or service periods. A non-PO invoice spanning two periods gets booked to one. Fix: record the service period during coding.
• Duplicate payment. The same invoice gets coded and paid twice. Fix: automated duplicate detection during exception handling in AP.

The pattern: code at intake, not at close. The earlier the coding is captured, the fewer exceptions pile up at month-end.

Non-PO invoice fraud risk controls and managing maverick spend

Non-PO invoices carry more fraud risk than PO invoices because they skip the check a PO provides. The two exposures to control are fraud (a fake or inflated invoice paid because nothing verified it) and maverick spend (off-policy buying that shows up only as an invoice after the money is committed). Since non-PO invoices are commonly 30 to 50% of all invoices received (IOFM), this is not an edge case, it is half the pile.

Replacement controls that close the gap:

• Validated vendor master: no payment to a vendor that was not vetted, which stops phantom-vendor schemes.
• Duplicate and anomaly checks: catch the same invoice twice and round-number or just-under-threshold amounts.
• Approval thresholds and segregation of duties: the person who codes an invoice should not be the one who approves and pays it. Our related guide on procurement fraud maps each scheme to the control that stops it.
• A real audit trail: every non-PO invoice records who coded, approved, and paid it.

Controlling maverick spend without purchase orders

Reduce maverick spend by making the compliant path the fast one, and by shrinking the pile of non-PO invoices that should have been POs. Two moves work well:

• Let people raise a quick purchase request in seconds through a purchasing system, so fewer buy first and expense it later.
• Convert repeat non-PO vendors to catalog or contract purchasing. A vendor you pay every month on a non-PO invoice is a prime candidate for a catalog or contract, which restores PO-level visibility and removes the recurring exposure.

This section is general information for building controls, not legal advice. If you suspect fraud, involve qualified counsel.

Accounts payable automation software for non-PO invoice processing

Automation streamlines non-PO invoice processing by running capture, coding, approval routing, and duplicate checks on every invoice automatically, instead of relying on someone to remember each step. The cost gap is real: Ardent Partners puts manual invoice processing at about $12.88 per invoice for typical teams, versus roughly $2.36 for best-in-class automated teams, with cycle times of 17.4 days against 3.1. For a full breakdown of tools, see our guide to AP automation software.

Features to prioritize when evaluating tools for non-PO workflows:

• Automatic invoice capture and data extraction
• Coding memory that applies a repeat vendor’s prior GL codes automatically
• Configurable approval routing by amount, cost center, and department
• Duplicate and exception detection before payment
• Two-way sync with your accounting system
• A complete audit trail on every invoice

How ProcureDesk handles the non-PO case specifically: it pairs invoices with purchase orders automatically on approval, and for spend that would otherwise arrive as an unstructured non-PO invoice, teams can issue a controlled virtual card straight from a purchase request with spend limits, vendor restrictions, and automatic reconciliation. That captures the spend up front instead of weeks later.

ProcureDesk integrates natively with QuickBooks (Online, Desktop, and Enterprise), Sage Intacct, NetSuite, Microsoft Business Central, and Xero, and connects with Bill.com for the payment step. Its punchout catalog network spans 200+ suppliers, including Amazon Business, Staples, Grainger, Thermo Fisher Scientific, and VWR.

A note on category: corporate-card and payment tools such as Bill.com, Tipalti, and Ramp process invoices and payments after the spend is committed. ProcureDesk sits earlier, at the request and approval stage, so non-PO spend is controlled before it becomes an invoice, not just processed after. The two are complementary.

Frequently asked questions

What is a non-PO invoice?

A non-PO invoice is a vendor bill with no purchase order attached, so it cannot be matched automatically and must be verified, coded, and approved manually before payment.

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

A PO invoice is pre-approved and verified through three-way matching against the purchase order and receipt. A non-PO invoice has no PO to match against, so approval and controls happen after the invoice arrives.

Which invoices don’t require a purchase order?

Recurring utilities and rent, tax and government payments, employee reimbursements, and low-value ad hoc purchases below your PO threshold typically do not require a purchase order.

How do you approve a non-PO invoice?

Route it through a defined approval workflow that assigns approvers by amount and cost center, validates the vendor, captures GL coding at intake, and flags duplicates or over-budget amounts before payment.

What is a healthy non-PO invoice rate?

IOFM benchmarks put non-PO invoices at roughly 30 to 50% of all invoices received. Track your own PO coverage rate over time; a rising non-PO share signals gaps in procurement policy or slow PO issuance.

How does accounts payable automation help with non-PO invoices?

It applies capture, coding, approval routing, and duplicate detection to every non-PO invoice automatically, so exceptions are caught before payment instead of at month-end close.

The bottom line

A non-PO invoice is not a problem on its own. The problem is paying it with nothing wrapped around it. Validate the vendor, code it at intake, route it through one approval workflow, check for duplicates before payment, and watch your PO coverage rate so the pile does not grow. For a mid-market finance team, that structure is what keeps non-PO spend controlled without adding headcount.