Non-PO Invoice Handling: Coding and Controlling Services Spend

Three-way matching is the most reliable control in accounts payable. The invoice is checked against a purchase order that proves the spend was authorized in advance, and against a receipt that proves the goods or services were actually delivered. When all three agree, the invoice is almost certainly legitimate and correctly priced. Construction AP teams build a lot of process around getting that match to work.

But three-way matching only applies to invoices that have a purchase order. A large share of construction spend never gets one — professional services, utilities, software subscriptions, insurance premiums, dues and licenses, equipment rental arranged with a phone call. These non-PO invoices arrive at AP with no commitment to match against and no built-in answer to the most basic question: should this be paid at all? Handling them well requires a different set of controls, because the structure a PO provides simply is not there. This post covers how to code and control non-PO spend.

Why So Much Spend Has No Purchase Order

Purchase orders fit some kinds of spend naturally and others awkwardly. A PO works well when there is a discrete order with a defined quantity and price — 200 tons of rebar, a specific equipment purchase, a subcontract with a schedule of values. There is something concrete to commit to and something concrete to receive. A lot of construction spend does not have that shape.

Some of this could go through a PO and does not because the process is slower than the need. Some of it genuinely does not fit the PO model. Either way, the result is the same: a meaningful slice of total spend — often 20% to 40% in a construction company — arrives as non-PO invoices, and that slice is where the matching control does not reach.

The Control Gap a Missing PO Creates

A purchase order does three things at once. It proves the spend was authorized before it happened, by someone with authority. It pre-establishes the coding — the job, the cost code, the GL account — at the moment the commitment was made. And it gives matching a fixed reference for price and quantity. A non-PO invoice arrives with none of that.

The fraud point is the sharpest one. A fake invoice from a fake vendor for $4,000 of consulting services will not match any PO — but for a non-PO category, that is expected, so the absence of a match raises no flag. The only thing standing between that invoice and a payment is whether the person it routes to actually recognizes the service, remembers authorizing it, and looks. Non-PO spend is consistently where invoice fraud and unauthorized spend get through, precisely because the structural check is absent.

Two-Way Matching for Non-PO Invoices

Without a PO and a receipt, three-way matching is impossible. The control that replaces it is two-way matching: the invoice is matched against an approval. Instead of asking does this invoice match a purchase order, the process asks does someone with authority confirm this spend happened, was expected, and is correctly priced.

Two-way matching shifts the verification from a document comparison to a human judgment, which makes the quality of that judgment the whole control. The approver is not just initialing — they are performing the verification a PO and receipt would otherwise perform. For that to work, the invoice has to route to a person who genuinely has the knowledge to evaluate it: the attorney's invoice goes to whoever engaged the attorney, the utility bill goes to whoever owns the facility, the software renewal goes to whoever owns that tool. Routing a non-PO invoice to someone who cannot actually evaluate it produces an approval that looks like a control but is not one.

Some non-PO spend can be strengthened with a partial reference even without a formal PO — a service contract, a rental agreement, an insurance policy, a subscription order confirmation. When that underlying document exists, the invoice can be matched against it for rate and term, recovering part of what a PO match would provide. Capturing those agreements where they exist is a meaningful upgrade to non-PO control.

Coding Discipline Without a PO

With a PO, coding is settled upstream — whoever created the PO assigned the job and cost code, and the invoice inherits it. With a non-PO invoice, coding is an open question at AP time, and that creates two risks: the invoice gets miscoded because whoever codes it is guessing, or it gets coded slowly because the coder has to chase down what it was for.

The discipline starts with deciding who codes non-PO invoices and to what. An AP clerk can code recurring, predictable non-PO spend reliably — the monthly utility bill, the recurring software subscription — because the coding repeats and vendor history is a strong guide. Non-recurring or ambiguous non-PO spend should be coded, or at least confirmed, by the person who incurred it, because they are the only one who actually knows which job and cost code it belongs to. A consulting invoice could be project overhead, a general office expense, or chargeable to a specific job; only the person who hired the consultant knows.

The job-versus-overhead decision deserves emphasis in construction. Miscoding a non-PO invoice as overhead when it belongs to a job understates that job's cost and overstates the company's overhead — both of which corrupt the job-cost picture. Non-PO coding is where a lot of job-cost noise originates, simply because there was no PO to settle the coding in advance.

Approval Routing for Non-PO Spend

Because the approver is doing the verification a PO match would otherwise do, routing the non-PO invoice to the right approver is the heart of the control. The routing should reach the person who has the knowledge to confirm the spend — not just someone senior enough to approve a dollar amount. Routing also needs the standard dollar-threshold tiering so that a $300 non-PO invoice and a $30,000 one get proportionate scrutiny.

Recurring non-PO spend can be handled with lighter-touch approval once a baseline is established. A utility bill that lands within the normal range of recent months does not need the same scrutiny every month; the useful control is exception-based — flag the bill that jumps 40% over its trailing average, not the one that looks like every prior bill. That keeps approver attention on the invoices that actually warrant it instead of spreading it thin across predictable recurring spend.

Reducing the Non-PO Share

The strongest non-PO control is fewer non-PO invoices. Not all spend can or should get a PO, but a lot of spend lands in the non-PO bucket only because the PO process was too slow or too cumbersome to use. Shrinking the non-PO share moves spend back under the stronger three-way-matching control.

Blanket POs are especially useful for construction. Recurring spend that does not fit a one-time PO — monthly equipment rental, an ongoing service relationship, a long-term subscription — can sit under a blanket PO that invoices draw down against. That converts a stream of uncontrolled non-PO invoices into a stream that has a commitment behind it. The non-PO share never reaches zero, but moving the largest and most repetitive pieces under POs concentrates the genuine non-PO handling on the smaller, more irregular tail.

Where Automation Helps

Automated AP platforms close part of the non-PO gap by making the substitute controls structural. The system recognizes a non-PO invoice and routes it by a vendor-and-category map rather than relying on a clerk to decide. It predicts coding from vendor history for recurring non-PO spend and flags non-recurring spend for requester confirmation. It compares each recurring non-PO invoice to its trailing average and surfaces the ones that jump. Covinly applies the routing map and the exception checks automatically, so non-PO invoices get a real, consistent process instead of an ad hoc one.

Automation does not invent the authorization a missing PO never created — the approver still has to do the verifying. What it does is make sure the non-PO invoice reaches the right approver, carries a sensible coding suggestion, and gets flagged when it looks abnormal. For the 20% to 40% of construction spend that has no PO, that consistency is the difference between a controlled process and a stack of invoices that get paid because nobody had a reason to question them.

Bottom Line

A large share of construction spend — professional services, utilities, subscriptions, insurance, ad hoc rental — never gets a purchase order, and those non-PO invoices arrive with no pre-authorization, no coding, no price reference, and weak fraud resistance. The controls that replace three-way matching are two-way matching against an informed approval, deliberate coding discipline that gets the job-versus-overhead decision right, and a vendor-and-category routing map that guarantees each invoice reaches someone who can actually evaluate it. Then shrink the non-PO share with PO thresholds, blanket POs, and a PO process fast enough that people stop routing around it. Non-PO spend will always exist; handled with intent, it does not have to be the place control quietly fails.