Research · Published:
Non-PO invoice exceptions: evidence before approval
A research method for separating missing purchase-order evidence from authorized non-PO treatment, coding, receipt, and payment decisions.
Methodology
A missing purchase-order number does not prove that an invoice is invalid, and a familiar supplier does not prove that the charge is authorized. This study asks what evidence an accounts-payable preparer should assemble before a company owner decides how a non-PO invoice will be handled. The practical problem is common in subscriptions, utilities, professional services, emergency purchases, taxes, and approved categories that may follow a different procurement path. It also appears when a purchase order should exist but was never created, was issued to another entity, or cannot be found. The method deliberately separates those conditions. Its output is a decision packet that identifies the commitment, benefit, policy path, accounting question, and approving owner. It is not permission to create a retrospective order, choose a bypass code, assert that services were received, assign an expense account, approve a policy exception, or release payment. That boundary lets outsourced AP support make the queue clearer without converting incomplete evidence into apparent authorization.
Evidence and scope
The population begins with every invoice entering the declared workflow without a valid order reference at a fixed UTC cutoff. The register keeps the original document, intake channel and timestamp, invoice and supplier identifiers, legal entity, amount and currency, service or delivery period, contract or request references, submitter, proposed cost owner, and every system search performed. It distinguishes no order cited, cited order not found, cited order closed, cited order belongs to another entity, order exists but the line is absent, and category designated by policy as non-PO. Those are facts about the available record. Calling the invoice an approved exception is a conclusion that requires an authoritative rule and owner disposition. Exclusions remain reconciled to the intake total so that a tidy review set does not hide credits, zero-value invoices, disputed duplicates, or records already routed elsewhere. Sensitive attachments remain in approved systems; the working file uses stable links and controlled identifiers.
Key Stats
Commitment reconstruction starts before coding. The preparer searches the approved contract repository, requisition history, correspondence retained in the business record, supplier master, recurring-charge register, and prior invoices only within the assigned access. A prior payment can suggest where evidence may exist, but it does not authorize the current charge. A signed agreement can establish terms without proving that the billed milestone occurred. An employee email may identify a requester without establishing purchasing authority. The packet states what each source shows, its version, effective period, and any conflict. If the company has a policy listing permitted non-PO categories, the exact category and current policy version are cited. If the invoice falls outside it, the result is “policy path unresolved,” not an improvised category chosen because it resembles a previous transaction. This keeps fact, comparison, inference, and decision visibly separate.
Research-to-practice
Benefit and receipt evidence require a second track. Goods may have arrived at a site that cannot create a system receipt; a service owner may need to confirm a deliverable; a utility statement may cover an active company account; or a subscription roster may show use without proving contractual acceptance. The preparer records the named recipient, source event, date, quantity or period, location, and unresolved variance. It does not copy the invoice description into a receipt field and call that confirmation. When an employee attests to performance, the packet retains the attestation, identity, time, scope, and authority under company policy. Partial or disputed performance remains split from the undisputed portion. A later confirmation is appended rather than backdated. That chronology allows the approver to see what was known when the invoice first entered review and prevents a successful later resolution from making the initial control gap disappear.
Implementation
The authority map tests four separate questions: who may confirm the business need, who may confirm receipt or service performance, who may decide accounting treatment, and who may approve the financial commitment or exception. One person may hold more than one role under company policy, but the packet should not assume that job title alone grants all four. Thresholds are tested against the correct entity, currency rule, cumulative commitment, and effective delegation date. A requestor's approval cannot cure a missing authority if the policy assigns the decision elsewhere. Technical ability to change workflow status also does not create business authority. GAO's 2025 Green Book supports documented control activities, quality information, and clear responsibility, while NIST least-privilege and audit-record concepts support bounded access and attributable actions. These public frameworks guide method design; they do not dictate a private company's purchasing or approval policy.
Key Takeaways
A challenge set makes the method falsifiable. Cases include an emergency repair with an authorized retrospective process; a recurring software invoice after the contract owner left; legal services with a matter reference but no order; an invoice citing another entity's order; a supplier that omitted a valid order from the document; a closed order with remaining service evidence; a duplicate candidate submitted as non-PO; and an employee request above their limit. A second reviewer receives the frozen sources and independently identifies the missing evidence, available policy path, and next authorized owner. Agreement is expected about source facts and calculation, not about decisions that policy reserves to management. The method fails if the reviewers can clear the invoice only by relying on oral history, if the route changes without retained evidence, or if “non-PO approved” hides whether commitment, receipt, coding, and payment approval were actually distinct.
Findings
Queue states should name the unresolved question: order reference missing, order search incomplete, authorized non-PO category evidenced, commitment owner needed, receipt or service confirmation needed, entity conflict, accounting review needed, threshold escalation, duplicate review, supplier correction requested, or owner disposition recorded. Each state has one current owner and one last evidence event. Metrics count the full population, source-complete packets, policy-path gaps, owner response states, later order creation, duplicate candidates, entity corrections, and second-review reproducibility. They should not reward support staff merely for converting invoices to an approved status. A falling exception count could reflect better procurement, but it could also reflect broad bypass coding or premature closure. Any rate therefore discloses numerator, denominator, scope, cutoff, exclusions, and policy version. Monetary totals remain separated by entity and currency rather than being combined into a misleading headline.
Findings
Limitations are explicit. Repository searches can miss informal commitments, system migrations can break links, policy language can be ambiguous, and the preparer may not have access to legal, procurement, or accounting records. The cited federal control frameworks do not make a non-PO invoice allowable, determine contract enforceability, assign tax or accounting treatment, or identify the correct private-company approver. A bounded exception sample cannot estimate fraud, savings, or outsourcing performance. The supported conclusion is narrower: a non-PO invoice becomes decision-ready when its intake source, commitment evidence, benefit or receipt record, applicable policy path, entity, amount, authority questions, and owner disposition are reconstructable. Outsourced AP can organize and monitor that evidence. Accountable employees decide whether the charge is accepted, how it is recorded, whether an exception is authorized, and whether payment may proceed.
Findings
The final handoff should be brief enough to act on but complete enough to audit. It names the invoice, declared exception type, strongest commitment source, benefit evidence, unresolved conflict, applicable policy version, amount and entity, current owner, and requested decision. It also links the full chronology and states the cutoff. If a retrospective order is later created, the record should distinguish that corrective event from the original condition. Preserving both states lets procurement leaders identify recurring intake failures without asking AP support to conceal them. The reader outcome is therefore not a faster bypass. It is a bounded decision request whose facts can be checked and whose eventual disposition can be traced back to the evidence available at the time.
Prepare non-PO evidence without inventing authority
AP support can assemble the source packet and route the precise exception. Company owners retain purchasing, receipt, coding, approval, and payment decisions.
Review invoice data captureSources
These primary sources support the control principles and evidence boundaries in this report.
FAQs
Are the planning numbers benchmarks?
No. They describe a testable workflow shape and are not promises, market averages, or production targets.
What should an outsourced AP assistant own?
Repeatable preparation, documentation, status tracking, and follow-up within least-privilege access. Named finance owners retain approval and payment decisions.
When should an item be escalated?
When evidence is missing, a request changes payment details, a duplicate or fraud signal appears, or the item falls outside the written rule.