Invoice vs Receipt: What's the Difference?
By the docmonkee team · Updated July 13, 2026 · 5 min read
Invoices and receipts look nearly identical — a header, a customer, line items, a total. The difference is timing and purpose: an invoice asks for money that's still owed, and a receipt confirms money that's already been paid.
Mixing them up isn't just a vocabulary slip. Sending a "receipt" before payment can muddy your books, and failing to send a receipt after payment leaves your customer without proof of purchase. Here's the clean breakdown.
The difference in one table
| Invoice | Receipt | |
|---|---|---|
| When it's sent | After the work, before payment | After payment is made |
| What it does | Requests payment | Confirms payment |
| Key date | Due date | Payment date |
| Key amount | Amount due | Amount paid |
| Who needs it | The customer's payables | The customer's records and yours |
What an invoice does
An invoice is a formal request for payment. It itemizes what was delivered, shows the total owed, and sets a due date. Until the customer pays, the invoice is an open item in your records — something to track, follow up on, and eventually mark paid.
Because it's a request, the invoice's most important fields are the amount due and the due date. Everything else on the document exists to justify those two numbers.
What a receipt does
A receipt is proof that payment happened. It records what was purchased, how much was paid, and on what date. Customers keep receipts for expense reports, warranties, reimbursements, and taxes; you keep copies to match your income records.
A receipt's most important fields are the amount paid and the payment date. If a customer paid partially, the receipt should show the payment received and the balance still outstanding.
The typical flow: invoice first, receipt after
In Docmonkee, this flow is built in: you can record a payment against an invoice manually, and once it's paid, convert the invoice into a receipt in one step — the line items and details carry over automatically.
- 1You finish the work or deliver the product.
- 2You send an invoice requesting payment by a due date.
- 3The customer pays — by whatever method you've agreed.
- 4You record the payment against the invoice.
- 5You send a receipt confirming the payment.
Do you always need to send both?
Not always. Retail-style transactions where payment happens immediately often skip the invoice entirely — the receipt is the only document. Project and service work usually needs both: the invoice to request payment, the receipt to close the loop.
When in doubt, send the receipt. It costs nothing, customers appreciate it, and it prevents the "did you get my payment?" email exchange.
Put this into practice
Create your document free — print or download a PDF in minutes, no signup required.
Frequently asked questions
Can an invoice act as a receipt?
Not on its own. An invoice marked "PAID" with a payment date recorded can serve a similar purpose, but a proper receipt showing the amount paid and payment date is clearer for the customer's records.
Do I legally have to give a receipt?
Requirements vary by location and business type. Regardless of the rules where you operate, providing receipts is standard good practice and keeps both sides' records aligned.
How do I turn an invoice into a receipt?
In Docmonkee, record the payment on the invoice, then use the convert option — the paid invoice becomes a receipt with the details carried over.