purchase order exception log
A purchase order exception log gives accounts payable and procurement teams one place to record why an invoice cannot follow the normal matching path, who must act, and what evidence supports the eventual disposition. It should capture the purchase order, invoice line, receipt evidence, variance, owner, age, and next action without turning an unresolved difference into an assumed approval.
Decide what belongs in the exception queue
Start by defining the normal path. Write down which records must agree before an invoice can move forward and which event proves that each check occurred. Your organization's approved procedure should control those rules. The exception log begins only when a named check fails or a required record is absent.
Keep ordinary matching work out of the log. If every invoice appears there, reviewers must search through routine items to find the cases that need attention. The entry rule might cover a missing purchase order, quantity difference, unexpected price, incomplete receipt evidence, possible duplicate, or supplier detail that conflicts with the approved record. Use only categories that reflect your written process.
Give a new situation an "unclassified" route with a required explanation and named process owner. That owner decides whether the case fits an existing category, needs a new one, or belongs outside the purchase order workflow.
Closing a row should require a recorded disposition and reference to the authorized decision or corrected source. A reply in email is not enough if the procedure requires approval in another system. The log points to the decision record. It does not replace it.
Give every row enough evidence
The log needs enough detail to support routing without becoming a second invoice repository. Use stable record identifiers and approved links rather than copying full documents or sensitive payment details into a general tracker.
| Log field | Question it answers | Administrative rule |
|---|---|---|
| Purchase order and invoice reference | Which records are being compared? | Use the approved system identifiers |
| Affected line | Where does the difference appear? | Identify the line without rewriting the source |
| Exception category | Which written route applies? | Choose only from defined categories |
| Observed variance | What do the records show? | State both visible values without interpreting policy |
| Receipt evidence | What delivery or service record is available? | Link to the approved source or mark it missing |
| Current owner | Who has the next action? | Assign a person or accountable role |
| Opened and next review dates | How old is the case, and when is it checked again? | Record dates as separate events |
| Disposition reference | Where is the authorized outcome? | Link the decision or corrected record before closure |
Write variance notes as comparisons. "Invoice line shows X; purchase order line shows Y" identifies the records and leaves the reviewer to apply policy. "Amount wrong" hides both the evidence and the judgment. If the log has weaker access controls than the source system, use a safe summary and direct the authorized reviewer to the controlled source.
Separate what happened from what happens next. The last action may be "receipt record requested from site manager." The next action may belong to that manager on a specified review date. Combining both into "waiting" makes follow up unreliable.
Route the exception to the right decision owner
Different mismatches require different owners. A buyer may address a purchase order term, a receiving owner may confirm delivery evidence, and an accounts payable reviewer may control the invoice review path. Map each defined category to the role authorized to resolve it.
The coordinator can collect named records, compare visible fields, identify a difference, request missing material with approved wording, and assemble a review packet. The coordinator should stop when sources conflict, the procedure does not cover the case, approval is missing, or the next action would change money, supplier data, contractual terms, or a controlled system record.
A useful escalation includes the invoice and purchase order references, affected line, category, exact values observed, sources checked, missing evidence, decision needed, and paused action. Avoid "please advise" with a long message chain attached. That forces the owner to repeat the administrative work.
Keep authority visible in the status. "Ready for review" means the permitted preparation is complete. It does not mean approved. Reserve a closed or approved status for the event specified in the procedure, and require the disposition reference before using it.
Handle common exception paths consistently
For a missing purchase order, confirm that the approved search was performed against the correct supplier, business unit, and period. Then route the invoice according to the organization's no-order procedure. A coordinator should not create an order after the fact or select an approver simply to clear the queue.
For quantity or price differences, record the purchase order value and invoice value from their respective sources. Link the available receipt evidence. If tolerances exist, the written procedure should identify them and state who owns changes. Do not encode an informal tolerance learned through private messages.
For missing receipt evidence, name the item or service line and the role expected to confirm it. Record when the request was sent and when it will be reviewed again. Silence is not confirmation, and an invoice due date does not establish that goods arrived or services were accepted.
For a possible duplicate, preserve both invoice references and the fields used in the approved duplicate check. Flag the case for the designated reviewer. Do not delete, merge, or mark a source record as duplicate unless the role is authorized and the procedure defines that action.
Payment details and supplier-master changes should use their own controlled routes. The exception log may point to those cases, but it should not hold account details or become an alternate approval channel. If a mismatch arrives through an unapproved channel, use the documented security and verification procedure.
Design follow up that does not hide age
Show age from the event that opened the exception, not from the most recent note. Repeated follow ups can otherwise make an old case look new. Keep the opened date fixed, store the last action date separately, and assign a next review date based on the approved cadence.
Group open rows by current owner and reason. This shows whether work is waiting on buyers, receiving evidence, accounts payable review, supplier correction, or an internal decision. Within each group, sort by age and documented business priority.
Follow up messages should refer to the stable case and state the exact missing answer. Avoid forwarding the complete invoice chain to a wider audience when a safe reference will do. Record the message event in the log, but keep attachments and substantive decisions in their approved systems.
A paused state still needs an owner, reason, and review point. Without those fields, "on hold" becomes a place where difficult items disappear.
Review the log for process defects
Review open exceptions before counting closures. Look for old cases, rows with no owner, missed review dates, repeated returns, and many unclassified entries. These conditions identify cases worth examining against the source records.
Sample closed rows and trace them back to the purchase order, invoice, receipt evidence, and authorized disposition. Check that the category matched the observed difference, the owner was correct, the decision reference exists, and the final status did not overstate what occurred. Preserve corrections.
Classify process defects separately from invoice exceptions. A missing receipt may be the immediate exception. An unclear receiving responsibility may be the process defect that causes it to recur. Frequent unclassified rows may point to stale category definitions rather than poor coordinator performance.
Keep elapsed time, coordinator handling time, and reviewer time separate. Elapsed time shows how long the exception remained open. Handling time helps with workload planning. Reviewer time may reveal a decision bottleneck. Use consistent definitions and avoid broad performance claims from a small sample.
The IRS guidance on business records supports the limited recordkeeping principle used here: businesses need records that support entries in their books and returns. Your finance, tax, legal, security, and retention owners should decide which records your organization must keep and for how long.
Turn the log into a delegated workflow
Before assigning recurring exception work, document entry rules, field definitions, reason codes, source systems, permitted checks, stopping rules, escalation owners, follow up language, review cadence, access approvals, backup method, and offboarding steps. Include examples for a clean resolution and cases that must stop.
Run a pilot with a missing order, price difference, quantity difference, absent receipt, possible duplicate, conflicting supplier detail, and unclassified exception. Ask the coordinator to point to the written rule behind each action. Give the active queue to a trained backup without an oral briefing. The backup should find the evidence, owner, paused action, next review point, and decision route.
Grant only the access required for assigned checks. Prohibit shared credentials and record who can approve additions or removals. Test removal as part of the handoff. If the coordinator cannot work safely without broad access or private explanations, narrow the assignment and repair the procedure first.
HireBackOffice bookkeeping assistants can support recurring exception intake, evidence gathering, log maintenance, and follow up once decision boundaries are documented. Use the virtual assistant access checklist to plan controlled access, and consider document management support when source files are scattered. Contact HireBackOffice with anonymized examples, approximate monthly volume, systems involved, and the decisions that remain with your team. This article provides general operational information, not legal, tax, accounting, procurement, privacy, or security advice.