Why you can trust this page
- Last reviewed
- September 20, 2026
- Evidence basis
- InvoiceVerdict editorial guidance
- Affiliate relationship
- This page may contain commission-earning links; editorial criteria are independent.
An invoice asks for payment. A receipt proves that payment was received. That difference determines when each document is created, what it should contain, and how it fits into your records.
| Invoice | Receipt | |
|---|---|---|
| Purpose | Request payment | Confirm payment |
| Timing | Before payment is completed | After payment |
| Status | Can be draft, sent, overdue, paid | Represents a completed payment |
| Common fields | Invoice number, due date, terms, line items | Amount paid, payment date, payment method, reference |
When to send an invoice
Send an invoice when a client owes you for completed work, a milestone, a recurring service period, or an agreed deposit. A good invoice makes the amount, due date, tax, and payment instructions unambiguous.
When to issue a receipt
Issue or make a receipt available after the payment has been recorded. Modern invoicing tools often automate this step so the customer sees the payment against the original invoice.
Why software helps
The biggest advantage is not the PDF. It is the state change: sent → viewed → partially paid → paid. Software can keep that history connected instead of forcing you to reconcile separate documents manually.
Update history
- Initial publication and editorial review.