Contract, invoice, receipt: what's the difference?

Early-stage freelancers often blur these three documents together — sending an "invoice" that's really a quote, or a "receipt" that's really an invoice. Each has a specific legal and accounting purpose. Knowing the difference makes you look professional and keeps your books clean at year end.

The contract: an agreement, before any work happens

A contract (or its lighter cousin, a statement of work) is a forward-looking document. It sets out the scope, price, timeline, and responsibilities of both sides before work begins. It does not request payment. Its job is to make sure you and the client agree on what is being built and at what price.

Even a one-page email contract is enforceable in most jurisdictions if it contains offer, acceptance, and consideration (i.e., what each side will give the other). The biggest mistake is starting work on a verbal "let's do it" and discovering, two months in, that you and the client had different scopes in mind.

The invoice: a request for payment, after work is delivered

An invoice is a formal demand for payment for goods or services already delivered (or, in the case of deposits, for a milestone that has been reached). It includes the amount owed, the payment terms, and your details. It is dated, numbered, and kept on file for your accounting.

Critically, an invoice is unpaid. The moment the client pays it, it stops being an invoice and becomes a paid invoice — which is recorded but does not, by itself, prove payment to a third party.

The receipt: proof of payment, after the money lands

A receipt is issued after the invoice has been paid. Its job is to prove the transaction occurred. The client uses it as evidence of expenditure (for their own bookkeeping, for reimbursement, or for tax). You issue it as a courtesy — many clients will request it explicitly.

Some payment platforms (Stripe, Wise, PayPal) auto-issue a receipt-style confirmation. That's usually enough for the client, but you can also send a branded receipt that references the original invoice number. It builds trust and makes it easier for your client to file.

Common mistakes

• Calling a quote an "invoice." A quote is non-binding and doesn't go in your accounts ledger. Invoices do.
• Sending a "receipt" before payment. You're effectively confirming you've been paid when you haven't. If the payment fails, you've created a discrepancy.
• Reusing the same number across an invoice and its receipt. Use the invoice number on the receipt as a reference, not as the receipt's own number.
• Skipping the contract for "small" jobs. Scope creep is most common precisely when nothing is written down.

A simple workflow

• 1. Agree on scope and price — send a short statement of work.
• 2. Deliver the work (or hit the agreed milestone).
• 3. Issue an invoice with a clear due date.
• 4. When paid, issue a receipt referencing the invoice number.
• 5. File all three documents together for the engagement.

That sequence — contract, invoice, receipt — is the backbone of almost every legitimate business transaction, from one-person freelancing to multinational procurement. The format scales; the principles don't change.