Receipt or Invoice: Which One Your Client Needs

A client emails asking for a receipt. You already sent an invoice last week and got paid two days ago. Do you send the same document again? Something new? Most people guess, and the guess is usually wrong. The two documents do different jobs at different points in the same transaction, and sending the wrong one at the wrong time slows down bookkeeping on both sides.

Here are the questions that actually come up, answered directly.

What is the difference between an invoice and a receipt?

An invoice is a request for payment. You send it before the money moves, and it says what is owed, by whom, and by when. A receipt is proof of payment. You send it after the money has arrived, and it confirms that a specific amount was paid on a specific date.

The timing is the whole distinction. Same transaction, two moments. The invoice opens the loop and the receipt closes it. If you want the full breakdown with examples, the guide on the difference between an invoice and a receipt covers every field and edge case.

When should I send an invoice instead of a receipt?

Send an invoice whenever payment has not happened yet and you are billing for work already done or goods already delivered. That is the default for most B2B work: you finish a project, you invoice, the client pays on your terms, whether that is due on receipt or Net 30.

An invoice is also what a client's accounts payable team needs to process a payment at all. They will not release funds against a receipt, because a receipt implies the money already left. If the client works with a purchase order, your invoice has to carry that PO number or it gets bounced back. When you need to raise one from scratch, you can create an invoice in a few minutes.

When should I send a receipt instead?

Send a receipt after you have confirmed the money is in your account. The trigger is the cleared payment, not the promise of one. If a client pays a deposit up front, they may want a receipt for that portion immediately, then an invoice for the balance later.

Retail and point-of-sale work flips the usual order. A customer pays first and walks away with the goods, so the receipt is the only document they ever get. In that case there is no separate invoice because payment and delivery happen at the same moment.

What must an invoice include?

An invoice fails at accounts payable when it is missing a field they need. At minimum, include:

• The word "Invoice" and a unique invoice number
• Your business name, address, and tax ID where required
• The client's billing entity and address (not just a contact name)
• The issue date and the due date
• Itemized line items with quantities and rates
• Subtotal, any tax, and the total due
• Your payment details: bank account, or the method you accept
• The PO number, if the client uses one

If you want a field-by-field version to run against before sending, the invoice contents checklist is built for exactly that. Missing bank details or a wrong billing entity are the two mistakes that cause the most rework.

What must a receipt include?

A receipt is simpler because the negotiation is over. Include your business name, the client's name, the date payment was received, the amount paid, the payment method, and a reference back to the original invoice number. That reference matters: it lets both sides match the receipt to the right invoice without guessing.

You do not need due dates, payment terms, or bank details on a receipt. Payment already happened, so those fields are noise.

Can one document be both?

Not cleanly. Some tools stamp "Paid" on an invoice once payment clears and treat that as a receipt. It works for informal transactions, and a client who just wants a record for their books will often accept a paid invoice as proof. But a stamped invoice still reads as a payment request in its structure, which can confuse an AP system expecting a distinct receipt document.

For anything where tax treatment matters, keep them separate. A tax invoice and a receipt serve different purposes in most tax regimes, and combining them can create problems if you are ever audited.

My client already paid but now wants an invoice. What do I send?

Send the invoice you would have sent before payment, dated correctly, with the original amount and terms. Many clients pay first and then need the invoice for their own records or reimbursement. This is common with expense-based work where someone fronts the cost and claims it back internally.

If they specifically want proof the payment cleared, that is a receipt, not an invoice. Ask which one their finance team actually requires, because "invoice" and "receipt" get used loosely and the answer changes what you send.

Does the recipient ever need to change the document after I send it?

Often, yes, and usually on the invoice. A client discovers they need their group entity on the bill instead of the local office, or they realize a PO number was never added. Handling that over email means a new PDF every time. Tools that support letting the client edit their own invoice cut that loop by letting them fix the billing entity, address, and PO number directly, with you notified and able to revert.

Receipts rarely need editing because they record a fact that already happened. If a receipt is wrong, the underlying payment was wrong, and that is a different conversation.

The rule holds in one line: request for payment goes out as an invoice, proof of payment comes back as a receipt. When a client asks, confirm which stage they mean before you send anything. Ready to raise the next one? Start from a clean free invoice generator and fill in the fields above.