Payment receipt template

The person or business receiving money issues a payment receipt to acknowledge the verified payment and explain what it was applied to.

It is not a request for payment, a payer's allocation instruction or automatic evidence that every bank or provider settlement condition has completed.

• Issued by: The payment recipient after verifying receipt
• Given to: The payer and the recipient's retained payment record
• Keep the source and approval with the final document.
• Confirm jurisdiction-specific requirements before issue.

Put this into practice with remittance advice.

The downloadable HTML provides a printable starting structure. Complete every field that explains the parties, document identity, commercial basis and resulting amount or movement. Remove irrelevant prompts only after confirming that they are not required for the transaction.

A field list cannot determine classification, tax, authority or legal effect. Those decisions come from the underlying agreement, actual event and current applicable rules.

• Receipt number and date
• Recipient name and contact detail
• Payer name and contact detail
• Amount received and currency
• Payment method and transaction reference
• Related invoice or purpose
• Allocation and remaining balance if any
• Authorised acknowledgement

Put this into practice with what is an invoice.

Begin with the source record rather than typing from memory. Confirm the issuer, recipient, reference, date and currency or movement context, then complete the line detail and arithmetic. A second person should review material or regulated documents before release.

Keep the final issued version immutable in ordinary operations. If a fact changes, use the appropriate revision, cancellation, credit or replacement process instead of silently overwriting history.

• Verify the payment event.
• Identify payer, amount, currency and reference.
• Match the payment to the intended invoice or purpose.
• Record any remaining balance.
• Issue the receipt and retain matching evidence.

Put this into practice with reconciliation.

The example below demonstrates how the fields relate. It is not a claim that the same tax, rate, wording or commercial treatment applies to another transaction.

Retain the calculation and evidence behind every total. A reader should be able to connect the final document to the authorised order, delivered item, accepted work or verified payment without reconstructing it from private messages.

• Invoice total: $5,000
• Verified payment received: $3,000
• Receipt amount: $3,000
• Applied to: Invoice INV-1042
• Remaining open balance: $2,000

Put this into practice with credit note.

Check identity, direction, date, reference, quantity, rate, amount, currency, tax treatment where applicable, delivery or payment evidence and authorised sign-off. Confirm that the document name matches the event it records.

A complete-looking template can still be wrong when it uses the incorrect issuer, duplicates an existing number, confuses a preliminary document with a final one or records intent as though the underlying event occurred.

• Issuing before funds are verified
• Omitting currency or payment reference
• Calling the receipt an invoice
• Ignoring a partial remaining balance
• Confusing payer advice with recipient acknowledgement

Put this into practice with invoice management.