Non-PO invoices in Accounts Payable: choosing the right approval route
An invoice arrives without a purchase order number. Instead of pushing it through the regular queue or rejecting it automatically, the team must identify the cost, the person authorised to confirm it and the evidence required before posting and payment.
A non-PO invoice is not automatically incorrect. It may relate to utilities, rent, recurring charges or an agreed one-off purchase for which no order was created. Without a PO, however, some standard reference points are missing. The process must replace them with explicit identification of the cost, owner and approval basis. The model below covers document control and exception handling in the client system; it does not replace the client’s purchasing policy, accounting rules or payment authority.
1. First confirm whether non-PO is permitted
Microsoft describes vendor invoices in Dynamics 365 that contain lines unrelated to a purchase order and invoices created without a PO, for example for ongoing services such as utilities. This is not permission to buy anything without an order. The first step is to check the category matrix: which costs may follow a non-PO route, what thresholds apply and who may approve an exception.
If the category requires a PO, AP should not attach the invoice to a convenient but unrelated order. Hold it, record the reason and route it to the purchasing process owner. If non-PO is permitted, move it into a controlled data-completion workflow.
2. Identify the cost owner from evidence
The sender’s email address or a name printed on the invoice is not proof of budget ownership. Useful evidence includes the contract, service period, location, customer reference, cost centre on previously approved invoices and confirmation from the requester. Each clue should lead to one accountable owner rather than a broadcast request to several departments.
If the owner cannot be identified, create an exception with a due date and a named investigator. Do not guess the cost centre. Prior invoice history is a clue only; changes to the contract, site or organisation require fresh confirmation.
3. Collect the minimum approval pack
A non-PO document should normally include four groups of information: business purpose, evidence of delivery or service period, proposed accounting allocation and an approver with the appropriate limit. SAP notes that simple non-PO invoices can include split accounting, validation and status history, and that supporting receipts may be required when an invoice is submitted for approval.
The pack can be concise, but it must make the decision reproducible. Rent may need a contract and billing period; a one-off service needs completion evidence; a statutory charge needs the relevant basis and deadline. A missing element should have a clear status instead of disappearing into email comments.
4. Separate formal control, coding and decision
AP can check supplier data, invoice number and date, amounts, currency, tax and duplicate risk. The business owner confirms the purpose and delivery. An authorised approver accepts the budget charge, while accounting validates the coding under client rules. Separating these roles reduces the risk of one person preparing and approving the entire record.
The system should show who performed each step, when and on what evidence. Forwarding an invoice must not imply approval. Useful distinct statuses include owner identification, evidence required, coding correction, pending approval and approved for further processing.
5. Build an exception queue, not a side channel
Risk increases when non-PO invoices are handled outside the system because they do not fit the standard process. Use one queue with reason codes, case owner, deadline and change history. Escalation may reflect the payment date and document age, but urgency must not remove the required approval.
Measure more than cycle time: track invoices without an owner, reasons for missing POs, rework and recurring categories. The evidence can support a framework agreement, recurring order, clearer supplier instruction or a revised exception matrix.
6. Checklist before posting hand-off
Before changing status, verify that non-PO is allowed for the category, no duplicate exists, invoice data are correct, the cost owner and delivery evidence are confirmed, coding is complete, approval level is appropriate and the audit trail is intact. Any unconfirmed item remains an exception with a specific reason.
A sound route is not a shortcut around purchasing. It handles justified cases safely, limits accidental posting and gives the process owner evidence to reduce future non-PO volume.
Sources and scope
- Microsoft Learn: Vendor invoices overview
- SAP Help: Understanding simple non-PO invoices
- SAP Help: Submitting a non-PO invoice
Microsoft and SAP documentation was checked on 27 October 2026. Features depend on the product and configuration. The proposed matrix, statuses and checklist are an editorial model to agree with the process owner. This guide is not a posting instruction or payment authorisation.
FAQ
Is every invoice without a PO incorrect?
No. Some categories, such as agreed recurring charges, may be permitted as non-PO, but only under the client policy.
Who should provide the cost centre?
A person who understands the business purpose and has the right authority. AP can collect evidence but should not guess the coding.
Can an urgent due date replace approval?
No. Urgency can trigger escalation, but it does not replace delivery evidence, authorised approval or duplicate control.
What should the non-PO history contain?
The cost source, owner, evidence, coding, dated decisions, exception status and the final control result.
