Skip to main content

Receipts

Receipt information makes a recorded payment traceable to the business's official receipt process. A payment may include a system-generated reference together with a manual receipt number, receipt date, issuer, notes, and an optional generated receipt document.

The receipt supports the payment record. It does not replace the need to verify the customer, contract, amount, method, date, and transaction evidence.

Receipt information to verify​

Review:

  • system receipt reference;
  • manual receipt number;
  • receipt date;
  • issuer or authorized staff member;
  • customer and contract;
  • payment amount and method;
  • notes or correction reason; and
  • generated receipt document, where supported.

Manual receipt-number standards​

Use the number exactly as issued. The business should define:

  • format and sequence;
  • who may issue receipts;
  • whether locations or payment methods use separate ranges;
  • how voided receipts are recorded;
  • whether a replacement receipt receives a new number; and
  • who investigates missing or duplicate numbers.

Do not invent, reuse, shorten, or alter a manual receipt number to clear an alert.

After recording a payment​

  1. Confirm the payment saved once.
  2. Check that the manual receipt number is present when required.
  3. Verify receipt date and issuer.
  4. Confirm the receipt amount and customer match the payment.
  5. Generate or review the receipt document where supported.
  6. Confirm the receipt is associated with the correct payment.
  7. Share or deliver it only through the approved process.

Missing receipt number​

When a report or collections queue flags a missing receipt number:

  • open the payment;
  • confirm whether the transaction required a manual receipt;
  • check the approved receipt source;
  • identify whether the receipt exists but was not entered;
  • do not guess the value;
  • obtain Finance/Admin confirmation; and
  • update the payment through the approved correction process.

Duplicate receipt number​

If the same manual number appears on more than one payment:

  1. stop issuing or communicating the affected receipt information;
  2. review both payments and source documents;
  3. confirm whether one entry is duplicated, one number was mistyped, or the source itself has a problem;
  4. follow the authorized correction/void process;
  5. record the reason; and
  6. confirm statements, customer history, and reports afterward.

Generated receipt documents​

Before relying on or sharing a generated receipt:

  • confirm the business details;
  • confirm customer, amount, date, method, and receipt number;
  • verify that the document does not expose another customer's information;
  • use an approved file path or delivery method; and
  • regenerate only after correcting the source payment data.

Do not edit the exported PDF or image separately and leave the source payment incorrect.

Example: cash receipt number omitted​

A fictional cash payment for Nadia Training was recorded correctly, but the manual receipt number was left blank.

  1. Finance opens the payment and confirms it is a cash transaction requiring a receipt.
  2. The paper or approved receipt source is reviewed.
  3. TRAIN-RCPT-001 is confirmed as the fictional receipt number.
  4. The payment is corrected with the authorized reason.
  5. The generated receipt is reviewed.
  6. The missing-information report is rerun to confirm the exception cleared.

Common mistakes​

  • Using a screenshot or buyer message as the receipt record.
  • Entering the system reference in the manual receipt field.
  • Reusing a number after a void without following policy.
  • Generating a receipt before verifying payment details.
  • Sharing a receipt document with the wrong customer.
  • Editing the document instead of correcting the payment record.

Suggested training media​

Screenshot space: Add a payment-detail screenshot showing system reference, manual receipt number, receipt date, issuer, amount, method, and generated document action.
Screenshot space: Add a missing-receipt exception from Reports and the corrected payment record side by side.
Screenshot space: Add a fictional generated receipt with every field labelled and a large Training Data watermark.
Diagram space: Add a receipt-control flow: Verify payment → Assign/confirm receipt number → Record metadata → Generate/review document → Deliver securely → Investigate exceptions.
Video space: Record a 5-minute walkthrough correcting a missing receipt number and reviewing the generated receipt without changing the verified payment amount.