Invoice vs Receipt vs Bill: Who Sends What

Quick answer

English usage overlaps, but accounting roles do not. An invoice creates (or supports) a receivable. A bill is usually the buyer's name for an invoice they owe. A receipt closes the loop after payment.

Three-way definition table

Retail "bill" on a restaurant check is casual English; in B2B ERP, prefer invoice/bill terminology above so integrations map cleanly.

Common mix-ups

Emailing a PDF titled Receipt before ACH clears creates chargeback disputes. Likewise, customers who upload a packing slip as a "receipt" for expense reports fail audit. Teach staff: unpaid → invoice/bill; paid → receipt.

Definitions that survive an audit

An invoice is the seller's itemized request for payment for goods or services delivered (or contractually billable). It usually carries a unique number, dates, line items, tax, and payment terms. Until it is paid, it sits in accounts receivable for the seller and accounts payable for the buyer.

A receipt is evidence that payment occurred. It may reference the invoice number, show tender type, and close the receivable. Issuing only a receipt when the customer still needs an invoice for their PO match will fail AP's three-way match.

Bill is everyday language. Customers say "send me the bill" when they mean invoice; consumers say "phone bill" for a recurring invoice-like statement. In accounting documentation, prefer invoice vs receipt to avoid ambiguity.

Where processes break

Sales closes a deal and sends a receipt-style PayPal email without an invoice number. Finance cannot match to the sales order. Fix: every payment links to an invoice ID.

A freelancer sends invoices late, then wonders why cash is lumpy. Fix: invoice on delivery milestones stated in the SOW, not when you remember.

A marketplace pays you while the end customer gets the marketplace receipt. Know which legal entity must issue tax invoices in your jurisdiction.

Sales order and PO boundaries

A sales order confirms what the seller will supply; it is not a demand for payment. An invoice is the demand. See sales order vs invoice. Purchase orders are the buyer's authorization to spend; AP often requires PO + receipt of goods + invoice before paying.

Net terms such as net 60 live on the invoice (and contract), not on the receipt. See net 60 payment terms.

Document checklist

Invoice fields: seller and buyer legal names, invoice number, invoice date, due date/terms, line descriptions, quantities, rates, taxes, total, remittance instructions.

Receipt fields: payment date, amount, method, invoice reference, payer identity.

If a document lacks an invoice number but asks for money, relabel and renumber before sending to AP-heavy customers.

Systems mapping

In most ERPs the customer-facing invoice object posts to AR; the receipt/payment object clears AR. If your Stripe or PayPal plugin creates payment records without invoices, build a nightly exception report for payments with null invoice_id.

Customer portals should expose invoices and payment receipts as different tabs. Mixing them trains customers to forward the wrong PDF to their AP team.

Tax engines key off invoices, not informal bills. If you must charge tax, you need invoice-level tax calculation artifacts.

For refunds, issue credit memos against invoices, then pay. A raw card refund without a credit memo breaks revenue reports.

Train sales never to paste bank details into email without an invoice number reference. Fraudsters impersonate vendors; invoice numbers are a weak but useful binding agent.

AP three-way match in plain language

Accounts payable matches purchase order, receiving record, and invoice. A payment receipt proves money moved; it does not replace the invoice in that match. If your customer AP rejects a Stripe email, send a numbered invoice that cites their PO.

Sellers who only email gateway receipts create unpaid-looking AR in the buyer world even though cash already arrived. Issue the invoice, then apply the payment against it.

Consumer checkouts can stop at a receipt. B2B renewals should not.

Tax and evidence

Sales tax engines calculate on invoices. If you never create an invoice object, your tax filing export will understate taxable sales even when the gateway collected tax.

Keep the invoice PDF and the payment receipt in the same folder keyed by invoice number. Auditors ask for both.

Credit memos reverse invoices; raw refunds without credit memos break revenue waterfalls.

Worked micro-scenario

Agency delivers a May retainer. Sends INV-220 on 1 May, net 15. Client pays 10 May; receipt R-881 references INV-220. Books show AR opened then cleared. If the agency had only forwarded a PayPal thanks note, the client AP would lack a document to code to the PO, and the agency revenue report would depend on PayPal CSV archaeology.

Language for support macros

Macro A: here is invoice INV-sharp requesting payment; reply with remittance advice when paid. Macro B: here is receipt R-sharp confirming we received payment against INV-sharp. Never send Macro B when Macro A is what AP filed.

If a customer says bill, clarify in one sentence whether they need a payment request or a payment proof. That single clarification prevents duplicate charges.

For refunds, lead with the credit memo number, then the refund receipt. Credit memo first keeps revenue schedules honest.

Localized words still map to invoice versus receipt concepts. Keep English object names stable in the ERP even if the PDF title is translated.

Prohibit staff from editing PDF titles to Invoice on a receipt file. Create the correct object instead.

Consumer vs B2B send rules

Consumer checkout can end on a gateway receipt because the buyer is also the payer and rarely runs three-way match. B2B renewals almost always need a numbered invoice that AP can code, even when a card already charged.

If you sell both ways, configure two email templates: receipt-first for self-serve SKUs, invoice-first for PO-backed SKUs. Mixing them is how support volume explodes.

When a consumer later asks for a tax invoice for reimbursement, generate a proper invoice keyed to the original payment rather than renaming the receipt PDF.

Month-end close hooks for AR clerks

On the last two business days of the month, forbid deleting invoices that already reached a customer portal. Issue credit memos instead so period comparisons stay auditable.

Reconcile gateway settlement reports to invoice applications, not to free-floating receipts. Unapplied cash should age in a suspense queue with an owner and a five-day SLA.

Sample ten random paid invoices and confirm each has a receipt or payment object with the same invoice ID. Failures usually mean a plugin that created payments without applications.

Publish a close checklist that names who sends customer statements: statements list open invoices, not receipts. Confusing those documents triggers “I already paid” disputes that waste the first week of the new month.

If you use multiple legal entities, make sure the invoice letterhead entity matches the bank account on the remittance block. Cross-entity remittance details are a common fraud and misapplication vector.

Before any customer escalation about “missing paperwork,” ask which object they expected: payment request or payment proof. That one question cuts most invoice-versus-receipt tickets in half.

Keep a one-page glossary in the finance shared drive that defines invoice, receipt, sales order, and credit memo with a sample PDF for each. New hires should open that page before their first customer email.

FAQ

Is a receipt the same as an invoice?
No. One asks to be paid; the other proves payment already happened. [Source: definitions section]

Can I send only a Stripe receipt?
Fine for many consumer checkouts; B2B AP usually still wants a numbered ask-for-payment document tied to their PO. [Source: process-break examples]

Where do net 60 terms belong?
Put them on the MSA and on each ask-for-payment document; payment proofs should only reference the paid document ID. [Source: SO/PO boundaries; net 60 guide]

What if my customer calls the invoice a bill?
Fine in conversation; keep the PDF titled Invoice with a number. [Source: this article definitions]