Non-PO invoice approval workflow for restaurants: approve the evidence, not an imaginary order

A non-PO route should be designed as a controlled alternative, not a shortcut around purchasing discipline. The restaurant may have an agreement that creates obligations without a purchase order, or the event may be urgent enough that the normal request was recorded after the fact. Either way, reviewers need a coherent chain: what was requested or contracted, what the supplier delivered, which period or milestone the invoice covers, how the amount was coded, and who can accept the charge. If a document is unavailable, say so. An approval can acknowledge an unresolved exception, but it does not turn unsupported detail into proof.

Define the route and evidence before opening approval

Write local route definitions for the situations that may legitimately bypass a PO, such as a contract-led service, emergency response, utility, rent, statutory fee, or another category approved by the operator. The category, required evidence, reviewer, timing, and threshold are local decisions; do not copy a public-sector rule and present it as a universal restaurant requirement. HMRC’s procure-to-pay material supports thinking in linked requests, approvals, receipt evidence, and invoice records. The February 2026 UK procurement policy is useful public context for governance and documentation, but its scope does not automatically govern an independent restaurant. Reference the policy version and route used, then make the exception visible when the normal evidence was unavailable.

• Capture supplier identity, invoice number, invoice date, service or delivery period, description, amount, currency, tax fields, and original document.
• Link a contract, approved engagement, request, email trail, estimate, delivery confirmation, timesheet, acceptance note, or other evidence that the local route recognises.
• Record the accountable budget or service owner and the exact question they approved: scope, completion, quantity, rate, period, or another defined basis.
• Keep coding, cost centre, site, tax review, duplicate check, payment status, and exception status as review fields rather than burying them in comments.
• Set operator-defined materiality or escalation rules explicitly and preserve the unapproved state when a threshold or evidence condition is not met.

Approve the transaction without pretending a PO exists

The approval record should state what the approver knows and what remains outside the evidence. A service owner may confirm that work was completed for an operator-defined period; a receiver may confirm goods arrived; a contract owner may confirm that the rate and scope align with an agreement. Those confirmations are not interchangeable and should not be reduced to a single “approved” flag. Keep duplicate and tax checks on their own path. If the invoice describes a purchase that should have had a PO, classify the deviation and route it to the local exception process. If the amount, period, supplier identity, coding, or receipt is disputed, hold the relevant decision and assign an owner rather than creating a retrospective PO number only to make the report look complete.

Clearly labeled illustrative example: a non-PO service invoice

A repeatable non-PO invoice approval process

1. 1Classify the route. Select the contract, recurring, emergency, utility, expense, credit, or other operator-defined route and record why a purchase order is absent.
2. 2Assemble the commercial basis. Link request, contract, engagement, supplier record, invoice, period, rate, scope, and any local evidence that explains the obligation.
3. 3Confirm receipt or completion. Have the receiver, service owner, or other accountable role verify what arrived or was completed and state any limitation rather than assuming it.
4. 4Review coding and invoice fields. Check identity, number, date, currency, amount, tax fields, site, ledger coding, duplicate risk, and any operator-defined materiality rule.
5. 5Route approval and exception. Obtain the accountable decision, keep invoice approval distinct from tax and payment decisions, and open or maintain an exception when evidence conflicts.
6. 6Release, hold, and retain. Follow the local payment authority, record outcome and follow-up, preserve linked evidence, and never create a fictional PO to conceal the route.