Invoice Routing Stamps for AP Matching and Exceptions

An invoice-routing stamp should tell accounts payable which check is complete and which question is still open. It should not turn a received invoice into an approved payment. For an AP desk, the useful distinction is between receiving the document, matching it to supporting records, resolving exceptions, obtaining authorization, and confirming the actual payment event.

Use a routing cover or a reserved margin. The supplier's invoice number, tax information, bank details, totals, and machine-readable content must remain unobscured.

Start by looking at the invoices that wait, not the ones that pass straight through. Missing purchase orders, absent receipts, price differences, incorrect entities, duplicate submissions, and disputed services require different owners.

A stamp with only APPROVED and REJECTED leaves every unresolved case between those choices. An EXCEPTION OPEN block can instead show the invoice reference, reason, responsible team, request date, and next review date. Detailed correspondence stays in the invoice record.

The organization decides which checks and approvals apply. This is a design model, not a substitute for accounting policy or a universal control standard.

A supplier might send an invoice by email and then attach it to a reminder. Preserve both communications, but connect them to the same payable record if the duplicate review confirms that relationship.

A duplicate-check mark should identify the candidate invoice and review result. Avoid automatically declaring two documents duplicates just because their amounts match. Entity, supplier, invoice number, currency, date, credit notes, and revised invoices can change the interpretation.

Mark a duplicate copy as a reference to the retained record rather than deleting the evidence or posting another obligation.

Consider a hypothetical invoice for 100 units when the warehouse has recorded only 80 received. AP needs to know whether 20 are in transit, rejected, missing from the receipt, or incorrectly invoiced. Simply stamping HOLD gives purchasing no useful question to answer.

Record the affected line, quantity difference, supporting receipt reference, owner, and permitted next action. Use the to distinguish a dock arrival from a verified quantity and posted receipt.

The payment decision still follows the contract and authorized AP process; the example does not imply that partial payment is always appropriate.

A service invoice may have no physical goods receipt. Its evidence could be a signed service confirmation, milestone acceptance, timesheet, or another record required by the agreement.

Use wording such as SERVICE CONFIRMATION REFERENCED rather than forcing the invoice through a goods-count box. The responsible business owner should confirm the relevant service evidence through the approved workflow, not through AP's assumption that a supplier's description is accurate.

An invoice can be matched but not authorized. An authorized invoice can be scheduled but not paid. A payment can be initiated and later fail. Keep these states separate, and only record the event supported by the payment system.

Do not embed an executive signature in a general stamp or use a generated image as evidence of approval. Bank-account changes deserve the business's independent verification process; a note on an invoice must not bypass it.

For small teams establishing these boundaries, the explains how to keep a limited paper process without creating an informal approval system.

An exception at month end needs a visible owner and accounting disposition. Whether an accrual, adjustment, or other treatment is appropriate is a decision for authorized finance staff under the relevant policy.

The stamp should point to that decision and keep the unresolved operational issue visible. The connects workpapers, journal references, and subsequent corrections.

If a revised invoice arrives after review, identify the revision and determine which checks must be repeated. Do not transfer an old approval mark onto changed amounts.

Use the for design references. For the actual block, prioritize status, invoice intake ID, evidence reference, owner, and date. The invoice-oriented fields in can be simplified into a narrow routing block without a decorative border consuming the writing area.

Before adoption, print the longest invoice ID, copy the impression in black-and-white, and verify that the date and initials remain legible. Large schedules of line differences belong on an exception form.

Walk through a reminder copy, a partial receipt, a non-PO service, a disputed price, a corrected tax invoice, and a failed payment. Ask whether the next colleague can identify the issue and its owner without rereading the whole email chain.

Track unresolved age and repeated requests for the same evidence. If a state consistently needs verbal explanation, rewrite that state or improve its supporting record. Do not solve the problem by applying more APPROVED marks.