A receipt, an invoice and a statement are three different documents

Three documents, three separate jobs

The words get used interchangeably in ordinary speech and are strictly distinct in every system that handles them. An invoice is a request for payment: it says an amount is owed, by whom, for what, and by when. A receipt is evidence that a payment happened: it says money moved on a date by a method. A statement is a summary of activity over a period, listing what was charged and what was paid and where that leaves the balance.

Each answers a different question, and none of them substitutes for another. An invoice does not show that you paid. A receipt does not show what you owed. A statement shows the shape of a relationship and is a poor proof of any individual transaction within it, because it is a derived view rather than a source document.

The invoice is where the obligation is described

An invoice carries the detail nothing else carries: line items, quantities, rates, tax treatment, the period covered and the reference the supplier’s own system uses. It is also the document that starts a clock, since payment terms are counted from its date rather than from when the work happened or when the document was opened.

That is why finance departments are so particular about invoices and so unmoved by other paperwork. An invoice can be entered into an accounts system, matched against an order and approved for payment. A friendly email confirming an amount cannot, whatever it says, because there is nowhere in the process for it to go.

The receipt proves the movement and nothing more

A receipt is narrow by design. It confirms that a specified amount was received on a specified date by a specified method, and its power lies in being issued by the party receiving the money. A card slip, a bank confirmation and a supplier’s receipt are three different receipts describing the same event from three positions, and they are not equivalent.

The distinction matters when something goes wrong. A card slip shows your side of the transaction and proves the payment left you; it does not prove the supplier applied it to the right account. This is why a disputed payment can be entirely real and still not visible on your account: the money moved, the allocation did not follow, and only the receiving organisation holds the record that would show why.

The statement is a view, and views are assembled

A statement is generated by running a query over transactions between two dates. That has consequences people find surprising. It reflects what had been posted at the moment of generation, so a payment made shortly before the cut-off may appear on the following statement rather than on the one covering the date it was made. Timing differences of this kind account for most of the alarm statements cause.

Statements also carry a closing balance that is not a bill. Balance and amount due are different fields and can differ substantially, because a balance includes items not yet payable and excludes things not yet charged. Reading a statement as an invoice is one of the commonest sources of unnecessary payment, and reading an invoice as a statement is one of the commonest sources of missed ones.

Which document to quote, and when

Match the document to the question. Disputing what you owe means quoting the invoice number, because the query is about the obligation. Proving you have paid means producing the receipt or the payment confirmation with its own reference, because the query is about a movement of money. Asking why a balance looks wrong means starting from the statement, since only the statement shows the sequence.

Quoting the wrong reference is one of those small errors that costs a surprising amount of time. Systems index these documents separately, and a statement reference searched against an invoice table returns nothing at all. The person searching cannot tell whether the document does not exist or whether the wrong reference has been supplied, so the query goes back and forth.

A note on the documents that pretend to be receipts

A confirmation of an order is not a receipt, though it often looks like one. A pro forma invoice is a quotation dressed as an invoice and does not create an obligation. An email saying a payment is being processed records an intention, not an event. Each of these is genuinely useful, and none of them will function as evidence at the point where evidence is required.

The practical habit is to notice, when a piece of paper or an email arrives, which of the three jobs it is doing. Filing by supplier is common and unhelpful. Filing by function — what is owed, what has been paid, what the period looked like — matches the way any organisation will later ask you to produce it.