Home › Academy › Post

Invoice vs. Receipt: What's the Difference?

An invoice is a request for payment. A receipt is proof that payment happened. They look alike, but mixing them up causes confused clients, delayed payments, and awkward conversations. Here's the clean distinction.

The one-sentence difference

An invoice says you owe me this much — please pay by this date. You send it before money changes hands. A receipt says you paid this much on this date. You send it after money changes hands.

Think of it as a timeline. The invoice opens the conversation about money; the receipt closes it. Sending an invoice after you've already been paid is confusing — the client wonders whether you think they still owe you. Sending a receipt before payment arrives is worse — it tells their accounting system the bill is settled when it isn't.

The distinction also matters for your books. An invoice creates a receivable — money someone owes you. A receipt documents a completed transaction. If you ever get audited or need to prove income, the pair together (invoice + matching receipt) tells the full story of each job.

When you send each one

Use an invoice whenever the client hasn't paid yet: after finishing a project, at the end of a billing cycle, or when a milestone is reached. Use a receipt whenever payment arrives — cash, bank transfer, card, or check. For recurring clients, each billing period gets its own invoice and, once paid, its own receipt.

	Invoice	Receipt
When to use	Before payment — to request it	After payment — to confirm it
Who sends it	The seller or freelancer	The seller or freelancer
Is it binding	Yes — it's a formal payment demand	Informational — proves payment happened
When payment happens	Later, by the due date	Already happened

One practical rule: if the client could reasonably ask "do I still owe you?" — the answer to that question is an invoice. If they could ask "can I prove I paid?" — the answer is a receipt.

What each document must include

Both documents share basics: your business name and contact details, the client's name, a unique document number, the date, and a breakdown of what was sold. But the details differ in one crucial spot.

• An invoice needs a due date and payment instructions. The client has to know when to pay and how. No due date, no urgency.
• A receipt needs the payment date, the amount actually paid, and the payment method (cash, ACH, check number). It doesn't need a due date — the money is already in.

An invoice also shows the balance due — what remains after any deposits or partial payments. A receipt shows what's been settled. If a client paid half up front, the invoice shows the remaining half; the receipt for that half shows zero balance outstanding on that portion.

Number them in separate sequences. INV-001 and RCP-001 can coexist without confusion, and separate sequences make tax time dramatically easier.

Common mix-ups to avoid

The classic mistake: emailing the invoice again when the client asks for a receipt. That reads as a second demand for money and reliably produces a stressed reply. If you keep copies of both (you should), the receipt takes ten seconds to find and send.

The reverse mistake: sending a receipt-style document with the word "paid" on it before the check clears. A check isn't money until it clears. Date receipts on the day funds actually arrive, not the day the client said they'd pay.

Another one: issuing a receipt for a deposit but never issuing an invoice for the balance. The deposit receipt covers the deposit; the final invoice covers the full project minus the deposit, and it still needs to go out. Follow our guide on how to send an invoice so the sequence stays clean.