Non-PO invoice: definition and how it works in accounts payable

What it means

A Non-PO invoice is a supplier invoice with no purchase order behind it. Rent, utilities, professional fees and ad-hoc purchases are common examples. Instead of matching the bill to a PO and receiving document, the AP team routes it to a person who recognizes the charge and approves it.

The absence of a PO changes the control. On a PO invoice, the match ties the bill to an approved commitment, a receipt and a price. On a non-PO invoice, the approval is the main evidence that the expense is real and properly coded. The approver is confirming both that the supplier should be paid and that the charge belongs to the right account or cost center.

Also called a non-purchase-order invoice, this type of bill is normal in many AP processes. It is not automatically a problem. The risk rises because coding rules and approval limits carry most of the control weight. Those rules differ by company, so the local policy, not a generic rule, determines who may approve and how the charge should be coded.

How it works in practice

In practice, a non-PO invoice arrives by mail, email or vendor portal. AP checks the vendor record, enters the invoice, and sends it to the approver named in policy. The approver confirms the bill, assigns or verifies coding, and approves within the assigned limit. AP then posts the invoice for payment.

Recurring non-PO bills often have similar amounts each month. Rent, utilities and professional fees can look familiar, so an approver may recognize the supplier and approve without re-reading the invoice number or date. That habit is where duplicate risk builds. The approval step needs a real check of the document, not just a recollection that a bill usually comes from that vendor.

Supporting evidence should travel with the approval: the invoice copy, invoice number, invoice date, vendor name, amount, coding and the approver's identity. Segregation of duties matters here as a passing principle: the person who requests an ad-hoc purchase should not be the only person who approves and posts it. Approval routing and coding rules differ by company, so follow your own policy rather than assuming one universal sequence.

Where it goes wrong

Non-PO invoices depend on approvers recognizing the bill, so duplicates and re-sent invoices are harder to spot. A vendor resends a copy, the approver sees a familiar charge and approves it again, and AP pays the same bill twice. Without a PO match, nothing in the routine process flags the re-sent copy.

Recurring non-PO bills with similar amounts each month are where the same invoice is most easily paid twice. The amount looks ordinary, the vendor is known, and the coding may be identical to the prior month. If AP does not check the invoice number and date against prior payments, the duplicate can pass through as a normal recurring charge.

Other failures are just as practical. An approver may approve outside the assigned limit, code the bill to the wrong cost center, or approve a charge without knowing what was purchased. A stale vendor record, a missing approval, or an ad-hoc purchase with no stated reason weakens the trail. Duplicate payment is the costliest version, but poor coding and weak approval evidence cause rework and inaccurate reporting even when the payment itself is valid.

What to check

Before posting a non-PO invoice, search the vendor record and payment history for the same invoice number, invoice date and amount. Check whether an earlier copy was already approved or paid. For recurring bills, compare the current invoice with the prior bill, not only with the vendor name. If a vendor statement is available, use it to confirm which invoices remain open.

Check the approval against the current limit and the coding against the expense. Confirm that an ad-hoc purchase has a stated business reason and that the approver is authorized for that amount or category. Keep the invoice copy and approval evidence with the transaction. A verbal approval may be convenient, but it leaves little to check later if the bill is questioned.

For recurring non-PO bills, look for duplicate copies with different dates, credits that were never applied, and payments that do not match the vendor statement. Coding rules and approval limits vary by country, company and contract, so apply your own policy and document any exception. The point of the check is simple: make sure the bill is owed, coded correctly, approved by the right person and not already paid.

Questions