Finance Index
What is a non-PO invoice, and how should it be processed differently from a PO-backed invoice?
Reference guide to non PO invoice processing, including invoice workflow, coding, approvals, ERP impact, and AP controls.
A non-PO invoice arrives with no purchase order behind it - there's nothing to match against, so the invoice itself must establish what was bought, who owns it, and whether it's legitimate. Processing differs in one fundamental way: validation comes from a human approval (the budget owner confirming "yes, we bought this") instead of a document match. Non-PO is not a failure mode - subscriptions, utilities, rent, and professional services will never have POs - but it needs its own deliberate workflow, not the PO workflow minus the PO.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| A non-PO invoice | A non-PO invoice arrives with no purchase order behind it - there's nothing to match against, so the invoice itself must establish what was bought, who owns it, and whether it's legitimate. | Helps finance decide what to do next. |
| Spend control | Accept it - and govern it. | Keeps spend tied to policy, ownership, and review. |
| Related terms | It varies too much by business model for one number: inventory- and project-heavy industries run high PO coverage, while services firms legitimately run majority non-PO. | Helps finance decide what to do next. |
| ERP alignment | Use the signals on the document - requester name, ship-to, department references, vendor history - and route to the most probable owner with an easy "not mine, try X" reassignment. | Keeps vendor records and payment decisions reliable. |
| Non-PO invoices sit for weeks | Make ownership a tracked workflow state with an SLA and automatic reminders, not an email thread. | Keeps work moving without losing accountability. |
Should we force POs for everything, or accept that some spend will always be non-PO?
Accept it - and govern it. Mandating POs for rent and utility bills creates retroactive POs: paperwork generated after the fact to satisfy a policy, which adds work and zero control. The honest framework is by spend type: goods and discretionary purchases benefit from pre-approval via PO; contractual recurring spend is controlled by the contract and a confirming approval; small-dollar tail spend is controlled by thresholds and card programs. Measure "spend under management" (pre-approved through any channel) rather than "PO coverage" - the former is control, the latter is often theater.
What percentage of invoices should be PO-backed vs non-PO - what's typical by industry?
It varies too much by business model for one number: inventory- and project-heavy industries run high PO coverage, while services firms legitimately run majority non-PO. Benchmark against your own spend types - the actionable question is whether each category is in its intended channel, not the blended ratio.
How do I route a non-PO invoice for coding and ownership when nobody in AP knows what it's for?
Use the signals on the document - requester name, ship-to, department references, vendor history - and route to the most probable owner with an easy "not mine, try X" reassignment. Systems that learn from past routing decisions get sharply better at this; the anti-pattern is AP emailing screenshots around.
Non-PO invoices sit for weeks because nobody claims them - how do I identify the right owner faster?
Make ownership a tracked workflow state with an SLA and automatic reminders, not an email thread. Persistent orphans are telling you about missing vendor-owner mapping - record who claimed each vendor's invoices and route there next time.
How should subscription, utility, rent, and legal invoices be processed when they'll never have POs?
Vendor-default coding, a designated approver, and amount-variance checking against history - the control that matters for contractual spend is "does this match what we agreed and what we usually pay," which automation checks better than a PO would.
How do I reduce maverick spend showing up as surprise non-PO invoices?
Make the sanctioned request path easier than going rogue, then use AP data as the detection layer: surprise invoices name the vendors, departments, and amounts bypassing procurement. Close the loop monthly with the worst offenders - AP sees maverick spend first; procurement has to act on it.
Stampli perspective
Stampli treats non-PO invoices as a first-class workflow: Stampli AI suggests coding from history and predicts the right approvers based on organizational structure and past behavior, so an invoice nobody in AP recognizes still finds its owner quickly. Approval, discussion, and documentation happen on the invoice itself, creating the control record a PO would otherwise provide - flexible workflows mean the non-PO path is designed, not improvised.