Invoice vs Receipt: What's the Difference?

The one-sentence difference

An invoice is a request: it tells a client what they owe and asks them to pay it. A receipt is an acknowledgement: it confirms that money has already arrived. An invoice looks forward to a payment; a receipt looks back at one.

That single distinction explains every practical question that follows — who issues which document, when it is legitimate to issue it, and why sending the wrong one at the wrong moment creates real problems rather than paperwork pedantry.

Side by side

Notice that nothing in the table is about layout. A well-made receipt can be five lines long; a well-made invoice has more to say because it has more to ask.

Deposits and part payments: where the two meet

A single job with a deposit produces the full relay of documents, and watching the sequence is the fastest way to internalise the rules. Take a photographer booking a shoot for R8,000 on 50% deposit.

1. The quote goes out first — no money involved, just an offer with a number.
2. The deposit invoice follows: R4,000, due before the booking is locked.
3. When the deposit clears, a receipt for R4,000 records that half the job is funded.
4. The shoot happens, and the final invoice goes out for the remaining R4,000.
5. The second receipt closes the loop and the file is complete.

Run the relay the other way and it breaks: a receipt issued before payment is a fiction, and a client who spots one has every right to wonder what else was recorded early.

Keep each pair adjacent in your records — the receipt filed beside the invoice it answers — so a question about the split is answered by one search rather than a reconstruction.

Do receipts follow the same rules as invoices?

Receipts are the simpler document of the two. Their job is narrow — say what was received, when, and against what — and ordinary accuracy does most of the work.

One boundary is worth knowing. Where a client is registered for VAT, the document that supports their tax position is the tax invoice, not the receipt — a payment confirmation is not a substitute for it. The VAT invoice requirements guide covers what that document must carry; the receipt's role is to prove the movement of money, which is a different question.

It is also good practice to number receipts and let each one name the invoice it answers. "Receipt 014 for INV-0187" takes six words and saves a future argument.

Receipts prove the movement of money; the tax invoice is what a VAT-registered client files. Keeping both roles in your head stops the two documents from being asked to do each other's work.

The mistake that costs freelancers money

The expensive mistake is treating a receipt as a courtesy you issue with the invoice — or worse, marking an invoice "paid" in a redesign because it looks finished. A client's accounts team reads acknowledgements literally: a document that says money arrived, arrived.

A five-line receipt that holds up

When you do issue a receipt, it needs fewer fields than an invoice — there is only one job for it to do. Five lines carry it:

• The amount received, in the currency it arrived in.
• The date it was received — the day the balance changed, not the day you noticed.
• The method, in plain words: bank transfer, card, cash.
• The document it settles: the invoice number, and whether it is full or part payment.
• Who issued the receipt, with enough detail to match it to your business.

Where FreeInvoices fits

The app deals in the request side of the relay: create a quote, convert it into an invoice when the client approves, keep the numbering per type, and download the finished A4 PDF. For the acknowledgement side, your bank's payment notification plus a numbered reference back to the invoice is the practical route most freelancers use — and it keeps the two roles cleanly separated.

For the request side in full — dates, terms, numbering and layout — the step-by-step guide to creating an invoice covers the fields in the order they matter.

Frequently asked questions