Receipts: what they are, and why they matter
2 min readLast updated 16 September 2026 Read as plain text
What a receipt proves, who it goes to, and why issuing one automatically removes an entire category of argument.
A receipt is the record that a specific payment happened: who paid, how much, for what, when, and by which method. An invoice asks for money. A receipt confirms it arrived. Businesses conflate them constantly, and it causes trouble at exactly the wrong moment.
Why an automatic one is worth more than a careful one
A receipt written by a person is written when that person has time. That is usually later, sometimes never, and almost always after the customer has already asked for it.
A receipt issued the moment a payment clears arrives while the customer is still holding their phone. Most disputes never start, because the thing the customer would have been chasing is already in their inbox.
What a good receipt contains
- The amount, and the currency it was actually paid in.
- What it was for, in the customer’s words rather than an internal code.
- The method and the last part of the account or number used, so they can match it to their own statement.
- A reference they can quote back to you.
- Your business name and contact, because a receipt is often forwarded to somebody who has never heard of you.
Receipts and your books
The same record that goes to the customer is the one that feeds your reconciliation. That is the point: one event, one number, two audiences. When the receipt and the ledger come from different places, they eventually disagree, and finding out which one is wrong costs more than the payment was worth.
On fees
A receipt should show what the customer paid, not what you netted after fees. If you pass fees on to the payer, show that as a line, not as a quietly larger total.