An invoice marked REVIEWED can still be unpaid. A payment released to the bank can still be pending, rejected, or returned. Treating these events as interchangeable makes the paper file appear complete while the financial system tells a different story.
Paid and reviewed stamps work best as visible references to recorded events. The accounting system holds the amount, authorization, settlement information, and correction history. The impression helps someone holding a printout find that evidence without guessing what happened.
Write a definition for each status used by the finance team. Do not buy a combined "approved and paid" device unless the same controlled event genuinely supports both statements.
| Status | Evidence to reference | What remains unresolved |
|---|---|---|
| RECEIVED | Invoice intake record | Validity, approval, and payment |
| REVIEWED | Completed check and reviewer identity | Authorization to pay |
| APPROVED FOR PAYMENT | Authorized decision within delegated limits | Release and settlement |
| PAYMENT RELEASED | Payment batch or transaction instruction | Bank acceptance and final outcome |
| PAID | Evidence meeting the organization's defined paid criterion | Later returns, disputes, or adjustments |
There is no universal operational meaning of "paid" suitable for every payment method. Finance leadership should define the event that permits the mark and explain how later reversals are handled. A stamp cannot decide the accounting treatment.
The guides can help compare layouts once these definitions are settled. Choosing the wording is a control decision, not an artwork decision.
A useful review block is small enough to fit on a working copy:
REVIEWED — date — reviewer code — review record reference
A payment block should point to the relevant transaction or batch, not repeat sensitive banking information. Include an invoice reference when the page may be separated from the packet. Keep full account numbers, credentials, and unnecessary supplier contact details out of the impression.
When comparing a , evaluate the space left for handwritten references at actual size. Decorative borders are less valuable than a clearly written transaction identifier.
Draw the actual sequence from invoice receipt to reconciliation. Identify who checks the invoice, who authorizes payment, who releases the payment instruction, and who checks the result. If one person performs several tasks, document how the organization reviews that concentration of responsibility.
The describes an internal-control framework for U.S. federal agencies covering operations, reporting, and compliance. It is a useful reference for thinking about documented controls, but it does not prescribe this particular stamp workflow or make it mandatory for every business.
For a small team, a practical review might be a periodic check by an authorized person who did not prepare the payment. The appropriate control depends on the organization's risks and policies. Adding a second impression without an actual independent check creates paperwork, not assurance.
A single PAID mark is especially confusing when an invoice has installments, retainage, offsets, credit notes, or disputed lines. Use the payment system to show each transaction and the open balance.
On the working copy, a phrase such as PAYMENT RECORDED — SEE LEDGER may be clearer than a full-payment claim. If a remaining-balance field is used, define who updates it and how a later printout is distinguished from an earlier one.
Consider this illustrative case: an invoice is approved for its full amount, but only the first scheduled installment is released. The approval record can be complete while the settlement record remains open. Neither a reviewer nor a stamp designer should collapse those states.
Invoices arrive through email, supplier portals, postal mail, and internal forwarding. Two copies do not necessarily represent two obligations. Conversely, similar-looking documents may represent separate valid invoices.
Use the accounting system's matching process before recording payment. A duplicate working copy can carry REFERENCE COPY — SEE INVOICE RECORD, with a link or identifier for the authoritative entry. Do not stamp every duplicate PAID as a shortcut; that obscures which document was used in the payment process.
Supplier identity and account changes belong in a separate controlled record. The explains that boundary before a new supplier reaches the payment queue.
A failed or returned payment does not erase the earlier release event. Keep that event visible and add the later outcome in the system. On paper, use a clearly dated annotation or routing cover sheet that directs the reviewer to the updated record.
The exception procedure should answer:
- Who receives the rejection or return notice?
- Who may authorize a replacement payment?
- How is the original transaction linked to the replacement?
- What happens if a supplier asks to change banking details at the same time?
- How are all copies prevented from appearing finally settled?
Do not cover an old impression with a new one. Preserving sequence matters more than keeping the page visually tidy.
Place marks away from invoice numbers, tax fields, barcodes, supplier identifiers, and the amounts the next reviewer must read. If there is no safe space, use a controlled cover sheet.
A plain can support a review block. For a changing date, compare a dedicated rather than embedding a fixed date in reusable artwork.
For deposit, remittance, or account-reference layouts, can help compare field spacing. They are artwork references, not evidence that account details were verified or a payment was settled.
Test the printout after scanning and grayscale copying. A status distinguished only by green or red ink may become indistinguishable in the electronic archive. The covers the final lettering and placement checks.
Choose a small mixed sample: a full payment, installment, credit adjustment, duplicate invoice, rejected payment, and an item approved but not yet released. Follow each mark to its evidence record.
The sample passes when another authorized reviewer can establish the event, date, responsible role, and current outcome without asking the original preparer. Investigate mismatches such as paper marked paid while the ledger remains open, or a payment record with no supporting authorization.
Record recurring causes, not just error counts. An ambiguous status label, a missing transaction reference, and an unowned exception queue call for different fixes.
Does "reviewed" mean approved?
Only if the organization explicitly defines and authorizes that meaning. It is usually clearer to distinguish an evidence check from the decision to pay.
Should the payment amount appear in the stamp?
Only when it solves a real working-copy need and has a defined update process. The authoritative amount and open balance should remain in the financial system.
Can a stamp prevent duplicate payment?
Not by itself. It can support a documented process, but duplicate detection depends on reliable invoice matching, controlled authorization, and reconciliation.
What should staff do with an obsolete finance stamp?
Remove it from use, record its retirement, and follow the organization's disposal policy. Retain the design and meaning where needed to interpret historical records.
A finance stamp should let the next person ask a precise question: which event occurred, and where is the evidence? Keep review, authorization, release, and settlement distinct. That makes the paper useful without allowing it to overrule the ledger.
