How to Control Invoices Without a Purchase Order Number
For an invoice without a PO number, distinguish a missing reference from a genuine non-PO transaction. Bring spend justification, service acceptance and authorized approval into one control record.
How should an invoice without a purchase order number be controlled? First establish whether an existing PO reference is missing or the transaction genuinely has no PO. Then verify the spending basis, goods or service acceptance, accounting assignment and authorized approval. Non-PO should not mean uncontrolled payment. Accurate invoice extraction simplifies data entry; it does not by itself establish that the spend is appropriate or payment is authorized.
Distinguish missing references, permitted exceptions and off-process purchases
The same 'no PO' label can hide different problems. If an order exists but is absent from the invoice, investigate the existing record. If company policy permits a category without a PO, use its alternative evidence and approval route. If a required purchasing process was bypassed, record a control deviation for separate review. Do not invent an order number to enable matching or present a later record as prior authorization.
The UK Department for Work and Pensions' 'No Purchase Order, No Pay' policy defines exception agreements and specified categories alongside its general PO rule. This is DWP's own policy, not a universal payment or rejection rule for Turkish companies. The operational lesson is to define permitted non-PO categories and required evidence before invoices arrive.
- Missing reference: verify the existing order, contract or buyer reference and record who will complete the correction.
- Permitted non-PO: identify the applicable policy exception, spend owner and alternative approval route.
- Process deviation: keep missing prior authorization visible; assess existing liabilities and payment obligations separately with finance and legal where needed.
Submit an evidence pack, not just the invoice
In an illustrative maintenance invoice, the amount may be extracted correctly while the receiving site and completed work remain unclear. Instead of asking an approver only 'is this acceptable?', provide the service scope, period, delivery or acceptance evidence, quotation or contract basis and cost center together. Assign an owner and response date to each gap. Route uncertain account coding or tax treatment to authorized finance review instead of guessing.
Rule R003 in Peppol BIS Billing 3.0 requires either a buyer reference or a purchase order reference. A buyer reference is an identifier used for internal routing. This illustrates why routing and PO matching are different controls. The rule belongs to the Peppol context; it should not be assumed to apply identically to every Turkish e-invoice, nor should a buyer reference substitute for spend approval.
- Transaction identity: supplier, invoice number, date, currency and goods or service scope.
- Spending basis: contract, approved quotation, permitted exception or a process deviation under review.
- Acceptance and accounting context: goods or service acceptance, business unit, cost center and finance-validated account assignment.
- Decision record: reviewer, authorized approver, decision time, rationale and unresolved issues.
Separate extraction, spend verification and payment authority
GAO's May 2025 Green Book addresses separating incompatible responsibilities such as transaction authorization, processing, recording and review, with alternative controls where segregation is impractical. An operational lesson from this US federal framework is that the person extracting or coding an invoice should not control every critical decision alone. Design checks around your organization's authority matrix and transaction risk.
Quibas Invoice Management supports extracting data from different document formats and progressing discrepancies by requesting clarification from the relevant person through Teams or Outlook. This helps keep missing information associated with the right invoice. The scope and timing of approved-record transfer to ERP or accounting systems are defined in the integration project; receiving clarification should not by itself count as payment approval.
For example, the receiving department can confirm service completion without automatically approving budget availability or tax treatment. Finance reviews account assignment and its control responsibilities, while an authorized person decides within the defined spending limit. Keep outstanding documents or conflicting answers visible with a review status and next action instead of silently closing them.
Prevent the same exception from recurring
After closing an exception, classify its cause: missing invoice reference, late requisition, incorrectly routed permitted category or an unclear acceptance owner. Each needs a different remedy. For recurring services, clarifying the contract and acceptance owner is more durable than requesting the same explanation on every invoice. Send reminders as due dates approach without treating outstanding approvals as completed.
Quibas Purchase Requisition & Approval Management brings the need description, cost-center and account assignments, documents and conditional approvals into one requisition context. Approval steps can reflect amount, organization and request conditions. For recurring non-PO deviations, this helps capture justification and authority earlier, before purchasing; permitted exceptions still need their own company policy.
Start a pilot with a measurable exception group
Select one invoice group and track missing-reference cases separately from genuine non-PO transactions. Break waiting time into initial classification, clarification and authorized approval after receipt. Record rework causes and closure evidence. The goal is not automatic clearance of every invoice, but a clear explanation of why each record is waiting and what evidence allows it to proceed.