A supplier invoice is ready for processing except for one detail: the amount differs from the approved order. The accounts payable specialist can enter the invoice accurately, but cannot establish whether the extra amount should be accepted. Treating data entry as approval would conceal the decision the business still needs to make.
An accounts payable exception matrix defines what the preparation team may do for each recurring issue, which evidence is required and who decides the next step. It is an illustrative working aid to adapt to your actual purchasing and payment controls. It does not grant spending or banking authority.
“Processed” is an ambiguous label. It can mean received, entered, matched, approved or paid. Agree a small set of statuses whose meanings are visible to the client and outsourced team. A recorded invoice with an open exception should not look ready for release merely because entry is complete.
A practical record retains the supplier, invoice reference, amount, currency, receipt date and evidence location. It also shows the exception and the authorised action pending. Use your approved accounting system as the primary record; avoid creating competing versions of the invoice across spreadsheets and messages.
Where accounts payable preparation is outsourced, document who owns the purchasing decision and who owns payment approval. They may be different people.
| Exception | Preparation work that may be authorised | Decision requiring an owner |
|---|---|---|
| Possible duplicate | Compare references, dates, amounts and existing payment records; preserve both documents. | Whether the records represent the same obligation and how to treat the duplicate. |
| Missing purchasing approval | Locate the request and ask the named requester for the missing evidence. | Whether the expenditure is approved under the business’s actual rules. |
| Amount or service disputed | Document the difference and gather order, delivery and correspondence references. | Whether to accept, dispute or request a corrected invoice. |
| Changed payment instructions | Flag the change and follow the separately approved verification route. | Whether verified instructions are authorised for release. |
Do not use the same approval shortcut for all four cases. A supplier confirming that an invoice is genuine does not resolve a dispute over the amount. An internal requester recognising a purchase does not necessarily have the spending limit to approve it.
An approaching due date is relevant information for the decision owner. Include it in the escalation along with the consequences that are known. Avoid promising a payment date or accepting additional terms without authority. If the owner is unavailable, use the documented fallback and make the unresolved status visible.
The DCV delegation matrix is useful here because it distinguishes a role’s work from its decisions. The preparation team can complete unaffected approved checks while the specific exception remains held. A broad label such as “waiting on client” should be replaced with a named decision and next checkpoint.
A useful request identifies the invoice, the discrepancy and the evidence already compared. It proposes the next step within the sender’s role and asks the authorised owner for a specific disposition. Refer to protected documents in the approved system rather than sending unnecessary financial details through general team channels.
After the decision, record whether the invoice was corrected, approved, declined or remains unresolved. Preserve the original invoice and link the replacement or credit note where applicable. A changed status alone is not enough to explain why the obligation or amount changed.
Walk through a fictional duplicate and a fictional disputed charge with the people who will operate the process. Each should identify what they can prepare, what they must escalate and who can decide. Check absence cover explicitly; a familiar colleague is not automatically an authorised substitute.
Use those findings when scoping operational and accounting roles. Clear boundaries let a specialist progress useful work and send a complete exception to the person equipped to resolve it. Review recurring exceptions to improve purchasing instructions and source records, without retrospectively treating an unresolved invoice as approved.