What an Invoice Does
An invoice is a request for payment. You send it to a client after delivering a product or completing a service, and it tells them what they owe, for what, and by when. The invoice creates a receivable on your books — money that is owed to you but has not arrived yet.
A properly formatted invoice includes your business details, the client details, line-item descriptions with amounts, the total due, payment terms, and a unique invoice number. It is both a billing document and a legal record that supports your claim to payment if a dispute arises. Sending an invoice promptly after delivery starts the payment clock and establishes the terms under which you expect to be paid.
Invoices are issued before payment. That timing distinction is the single clearest difference between an invoice and a receipt, and it is the one that matters most for your workflow and your books.
An invoice also establishes the payment terms that govern the transaction. It tells the client how long they have to pay, what payment methods you accept, and whether late fees apply. None of that information belongs on a receipt because by the time a receipt is issued, those terms have already been fulfilled. The invoice is the governing document; the receipt is the closing document that confirms the obligation was met.
What a Receipt Does
A receipt is a confirmation that payment has been received. You issue it after the client pays, and it serves as their proof of purchase. The receipt closes the transaction on both sides: you mark the receivable as collected, and the client records the expense as paid in their accounting records.
Receipts are important for the client's accounting and tax records. A client who pays you for a deductible business expense needs a receipt to substantiate that deduction. For you, the receipt confirms that the payment arrived and the amount matches what was invoiced.
A receipt typically includes the date of payment, the amount received, the payment method, a reference to the original invoice number, and your business details. It does not need to repeat the full line-item breakdown unless the client requests it — a reference to the invoice number is usually sufficient for both parties to trace the transaction back to its origin.
Where Confusion Creates Problems
Sending a receipt instead of an invoice is the most common mixup, and it causes real delays. A receipt does not include payment terms, so the client has no deadline. It does not create a receivable on your books, so your accounting shows the sale as already collected when it is not. The result is a gap between what your records say and what your bank account shows.
Sending an invoice after payment has already been received creates the opposite problem. The client sees a payment request for something they already paid, which triggers confusion and a back-and-forth email thread that wastes both parties' time. Your books show a receivable that was never outstanding, which complicates reconciliation.
The fix is a clear sequence: invoice first, then payment, then receipt. If you use invoicing software, this sequence can be automated so that a receipt generates automatically when a payment is recorded against an open invoice. The e-invoicing guide on this site covers how structured digital invoicing makes this handoff even cleaner by eliminating manual steps on both sides.
Getting the Workflow Right
The correct document flow is straightforward. Deliver the product or complete the service. Send an invoice with clear payment terms. Receive payment. Issue a receipt confirming the amount and method. Record both documents in your bookkeeping system so the transaction trail is complete.
Invoicing software handles most of this sequence automatically. The tool creates the invoice from a template, sends it with a payment link, records the incoming payment, and generates a receipt without you touching each step manually. If your current process involves creating invoices and receipts in separate documents or spreadsheets, the time-savings estimator on this site shows how much of that labor automation can absorb.
The key discipline is consistency. Every completed transaction should have both an invoice and a receipt on file, linked by the invoice number. This pairing makes reconciliation simple, tax preparation straightforward, and dispute resolution faster because every step in the payment cycle has a corresponding document that both parties can reference.
Document requirements differ by jurisdiction and business type — check local rules for mandatory fields on invoices and receipts.