A receipt only means something if it's tied to a real invoice and a real payment — "$450 received against invoice #1042, paid August 12." A receipt made with nothing behind it isn't proof of anything; it's a piece of paper claiming a payment happened, which is exactly the kind of document that gets misused.
A usable receipt needs: who paid, who was paid, the amount received, the date received, the payment method (card, ACH, cash, check), and the invoice number the payment settles. If it's a partial payment, it should also show the balance still owed on that invoice.
Full payment and partial payment aren't the same receipt. A full-payment receipt should say so plainly — balance zero, paid in full. A partial-payment receipt should state the remaining balance, so the paper trail stays accurate as more payments and more receipts come in against the same invoice.
The order of operations matters: create the invoice, record the payment against it, then issue the receipt. Skipping straight to "a receipt" with nothing behind it is the exact mistake this guide is trying to prevent — a legitimate receipt can't be the first document in the chain.
Cash payments deserve extra care, since there's no card or bank record backing them up — the receipt becomes the main proof the payment happened. Get the amount, date, and method exact, and hand it to the client at the time of payment rather than reconstructing it from memory later.
Ready to write one? Try the free generator — no signup.