A non-PO invoice often gets treated as an Accounts Payable exception.
AP receives the invoice, finds the business owner, gets approval, codes the charge, and moves the payment through. The invoice is usually valid. The approver is the right person. The expense belongs to the company.
By the time AP sees it, though, the purchase has already happened. That changes what the approval can accomplish.
Approval after commitment is a different control
If a department ordered a service without a purchase order, the later invoice approval can confirm that the charge is legitimate and should be paid. It cannot create competitive bidding, budget review, contract review, or purchasing authority that was supposed to happen before the commitment.
Sometimes a PO is raised after the invoice arrives. The transaction then appears to have a PO, even though the purchasing decision was already made before the PO existed. A PO compliance report can improve while the underlying behavior stays the same.
Look at where they cluster
If non-PO invoices cluster around certain departments, vendors, or spend types, either people are going around purchasing or the purchasing process does not fit how the business buys those items.
Ask before blaming AP
If the purchase was already made before AP received the invoice, what is the approval actually approving?
That question separates invoice validation from purchasing authorization.
← Back to all Insights