Invoices and receipts: the fields that survive contact with reality

Invoices and receipts do two jobs. An invoice asks for money. A receipt confirms it arrived. Most trouble comes from using one where the other was needed, or from omitting a field that seemed obvious then became the whole argument months later. Below are the skeletons, field by field, with why each field earns its place.

What to take away

An invoice asks for money and a receipt confirms it arrived. Using one where the other was needed causes most of the trouble.
Every field on the skeleton closes off a specific way a payment stalls. Delete the ones that do not apply to you, not the ones that look fussy.
What an invoice must legally contain depends on where you are and how you are registered. Take that from your tax authority, never from a template.

What separates them

An invoice is a request. You issue it before payment. It states an amount owed and carries a due date. Until settled, it sits as an open item on somebody's ledger: yours as money in, theirs as money out. Before you issue that invoice, you need a quotes and estimates process that locks in scope and price.

A receipt is an acknowledgment. You issue it after payment. It states an amount received and names the method. It closes the item.

A document that says 'paid in full' and also says 'due on receipt' is neither. If you take payment on the spot (cash across a counter, a card that clears while the customer waits), one document can do both jobs. It must say plainly that the balance is zero and how it was settled. Any other time, issue two.

The invoice skeleton

Copy this and delete what does not apply to you.

Invoice skeleton fields

Fromtrading name, address, named billing contact
Bill toregistered name, billing address, accounts contact
Invoice numberunique, never reused
Invoice date and calendar due date
Their referencePO, job, contract, ticket
Line itemsdescription, qty, unit price, amount
Totalssubtotal, tax, deposit, total due, currency
How to pay and payment terms

INVOICE

From                            Bill to
[Your trading name]             [Customer's registered name]
[Your address]                  [Their billing address, which is
[Your billing contact: often not their delivery address]
 a name, not just info@]        [Their accounts contact or
                                 department]

Invoice number    [unique, never reused]
Invoice date      [the date you issued it]
Due date          [an actual calendar date]
Their reference   [purchase order, job number, contract, ticket]

Description                       Qty    Unit price    Amount
[What was delivered, described     [n]    [x.xx]        [x.xx]
 the way the customer's own
 records describe it, with the
 date or period it covers]
[...]

                                  Subtotal              [x.xx]
                                  [Tax line, named      [x.xx]
                                   and shown separately]
                                  Less deposit paid     [-x.xx]
                                  TOTAL DUE             [x.xx]
                                  Currency              [code]

How to pay
[Account details, payment link, or accepted methods]
[The reference you want quoted on the payment]

Terms
[The payment window, and what happens once it passes]

Why each field is there

The fields below are not decoration. Each one closes off a specific way a payment stalls.

Each field prevents a stall

Field

Registered name: Refusal: wrong entity on contract
Named billing contact: Question dying in shared mailbox
Unique invoice number: Two amounts under one reference
Calendar due date: The net 30 from when argument
Their PO reference: Invoice parked, cannot match order
Customer-language description: Approver cannot confirm work happened
Qty and unit price: Partial delivery becomes all-or-nothing

What it prevents

Registered name
Named billing contact
Unique invoice number
Calendar due date
Their PO reference
Customer-language description
Qty and unit price

Field	What it prevents
Customer's registered name	A finance team refusing the invoice because the entity named on it is not the entity that holds the contract. Trading names and legal names diverge more often than people expect.
A named billing contact on your side	The customer's question dying in a shared mailbox while the clock runs.
Unique invoice number	Two different amounts arriving under one reference, which is unresolvable without going back through your own records.
Invoice date separate from due date	An argument about whether the clock started when you issued it, when they opened it, or when they logged it.
A calendar due date	The "net 30 from when?" conversation. Write the date out.
Their purchase order or job reference	The single most common reason an invoice is parked. Many organizations cannot pay an invoice their system cannot match to an approved order.
Description in the customer's language	An approver who was not in the room being unable to confirm the work happened.
Period or delivery date per line	A dispute about whether a line was already billed on an earlier invoice.
Quantity and unit price shown, not just a total	A partial-delivery dispute becoming an all-or-nothing dispute. If they received eight of ten, you can both see what to credit.
Deposits and credits shown as lines	A customer paying the headline figure and overpaying, or paying the net and appearing to underpay.
Currency stated explicitly	Cross-border confusion between currencies that share a symbol.
Payment instructions on the document itself	A payer having to find an old email to work out where the money goes.

The receipt skeleton

A receipt is shorter, and its job is to be findable later.

Receipt skeleton fields

Your trading name and address
Receipt numberunique
Date receivedwhen money cleared
Received fromthe actual payer
Amount received and currency
Methodcash, card, transfer, reference
Applied toinvoice numbers and amounts
Balance remaining on those invoices

RECEIPT

[Your trading name and address]

Receipt number    [unique]
Date received     [when the money actually cleared or was handed over]
Received from [the payer: sometimes not the customer]
Amount received   [x.xx] [currency]
Method            [cash / card / transfer / other, and the last
                   four digits or transaction reference]

Applied to
Invoice [number]                    [x.xx]
Invoice [number]                    [x.xx]
[Unapplied credit on account]       [x.xx]

Balance remaining on those invoices [x.xx]

The 'applied to' block is the part people leave out, and the part that matters. A payer who settles three invoices with one transfer needs to see which three.

Otherwise reconciliation fails and they ask you to redo the work. If money arrived and you have not allocated it, say so on the receipt instead of holding it silently.

Note the payer field. When a parent company, a client's client, or an individual pays for the named customer, the receipt should record who actually sent the money. That detail untangles things later.

One worked example, invoice and receipt

A web design job billed to Northline Studio LLC. The invoice went out on 3 March 2025 and the money arrived on 28 March 2025.

Invoice 2025-0007, invoice date 3 March 2025, due 2 April 2025, their purchase order 4471.

Line	Qty	Unit price	Amount
Landing page design, delivered 14 to 21 February 2025	1	1,800.00	1,800.00
Copywriting, six pages, delivered 24 February 2025	6	95.00	570.00
Analytics setup, delivered 26 February 2025	1	150.00	150.00

Totals / Amount

Subtotal: 2,520.00
Sales tax, at the rate for the customer's address: 207.90
Less deposit paid 3 February 2025: -500.00
TOTAL DUE, USD: 2,227.90

The deposit appears on the invoice because it appeared on the quote. The tax line carries the rate for that customer's address, which is not a national figure.

The payment cleared on 28 March 2025, so the receipt reads:

Field / Value

Receipt number: R-2025-0007
Date received: 28 March 2025
Received from: Bridgeport Holdings LLC, paying for Northline Studio LLC
Amount received: 2,227.90 USD
Method: Bank transfer, reference NL-4471
Applied to invoice 2025-0007: 2,227.90
Balance remaining: 0.00

Two details here earn their place. The payer is not the customer, so the payer field carries the answer. The receipt number tracks the invoice number, which makes the pair easy to find later.

Numbering that survives contact with reality

Invoice numbers do two things: make a document unique, and let you notice a gap. A few rules save trouble:

Numbering rules that survive

Never reuse a number, even for canceled documents
Never renumber after the fact; use credit note
Decide global or per-customer before starting
Avoid encoding customer codes or year formats
Keep the number short enough to retype

Numbering that survives

One sequence per entity.If you trade through two companies, run two sequences. A single shared run makes each company's records hard to account for.
Sequential, no reuse.Each new invoice takes the next number in the run. Never reuse a number, not even to correct an invoice you voided.
No gaps.If a number is issued, a document exists behind it. Do not skip numbers to start a clean block in a new year.
Prefix by year or entity.2025-0001 and ACME-2025-0001 both work. Keep the year and the sequence as separate parts, and do not reset to 1 part way through a year.
Voids.When an invoice must be cancelled, keep the file, mark it void, and note the date and the reason. The replacement takes the next number, never the voided one.

The format is yours to choose. Whether the sequence has to be unbroken is a question for your tax authority, so check the rule that applies to your registration.

Writing payment terms so they cannot be read two ways

'Net 30' is a phrase people think they agree on. Spell out what you mean:

Terms to spell out

Window startsinvoice, delivery, or receipt date
30 days or 30 business days
Does partial payment restart anything
What happens after the date passes
Who to contact to dispute a line, by when
Put terms on invoice and agreement

Writing payment terms

Due date, written out.Instead of 'Net 30', write 'Payment due 2 April 2025, that is 30 days from the invoice date.' A calendar date ends the argument about when the clock started.
Late interest.Write 'Overdue amounts carry interest at 1.5 percent per month from the day after the due date.' What you may charge is capped by state law, so set the figure with your accountant. Common commercial figures sit around 1 to 2 percent per month.
Dispute window.Write 'If you dispute a line, tell us in writing within 10 days of the invoice date. Undisputed lines stay payable on the due date.' Where the contract is silent, the window is yours to set.

Put the terms on the invoice and in the underlying agreement. Terms that appear for the first time on the invoice are terms the customer never accepted.

What you have to check locally

No template can do this part for you. The questions depend on your location and your customer's, what you sell, and your registration. They cover whether an invoice is legally required, what it must contain, and how sales tax or VAT is described and calculated.

Check locally before sending

National or regional tax authoritycompliant content
Accountant or bookkeeperyour registration and trade
Customer accounts payablePO, format, portal, entity
Retention ruleshow long to keep copies
E-invoice format and receipt-on-request rules

Other rules cover how long you must keep copies, whether electronic invoices need a particular format, and whether you must issue a receipt on request.

It changes, and it differs between two businesses on the same street with different registrations.

So do not take required content from a template, including this one. Check:

Your national or regional tax authority, for what a compliant invoice contains and how tax is shown. In the United States, the IRS publishes its own guidance on recordkeeping for small businesses, and it is a sensible first stop. The UK's page on invoicing and taking payment from customers and the European Union's VAT invoicing rules are two published examples of the level of detail such a requirement reaches.
Your accountant or bookkeeper, for how it applies to your specific registration and to the way you actually trade.
Your customer's accounts payable team, before the first invoice. They will tell you exactly what their system needs: a PO number, a particular file format, a portal upload, a specific entity name. This one conversation prevents most late payments.
The contract, for anything about invoicing frequency, milestones, or approval steps that overrides your standard terms.
For readers in the United States, the SBA's business guide is one starting point for orienting yourself before you talk to a professional. It is a starting point, not an answer.

Treat the skeleton above as a layout. Treat compliance as a question for someone who knows your jurisdiction.

Where invoices actually go wrong

Not in the design. In the handling.

Where invoices go wrong

Sent to the wrong personask billing contact
Sent too lateraise within days of delivery
Description too thinname dates and deliverables
Rounding driftdecide where you round
No copy of what you sentstore exact document
Chasing without a recordlog every reminder

Sent to the wrong person. The person who commissioned the work often is not the person who pays for it. Ask for the billing contact when you agree the job.

Sent too late. An invoice raised six weeks after delivery lands on someone who no longer remembers approving it and now has to reconstruct it.

Description too thin. 'Consulting, August' is not something an approver can verify. 'Consulting, August: two workshops on 6 and 20 August, plus written summary' is.

Rounding drift. When you round each line amount and then round the total again, the invoice disagrees with itself by a cent and a machine rejects it. Decide where you round and stay consistent.

No copy of what you sent. Store the exact document you issued, not the ability to regenerate it from current data. If your prices or address change, a regenerated copy of an old invoice is a different document.

Chasing without a record. Log the date and channel of every reminder against the invoice. When a payment goes bad, the chase history is the only evidence that you did your part.

Before you send

A short pass, in this order:

Before you send

Customer entity name exactly right
Their reference number on it
Every line says what and when
Arithmetic holds, including deposits and credits
Due date is a real date
Payment details are current
Copy stored for tax retention period

Names.Your trading name and the customer's registered name match the contract, and a named billing contact appears on both sides.
Number and dates.The invoice number is next in sequence, the invoice date is the day you issue it, and the due date is a real calendar date.
Arithmetic.The lines add to the subtotal, the deposit is subtracted, and the total due matches the accepted quote.
Tax.The rate and the amount it applies to are both visible, not folded into the total.
References.Their purchase order, job number, or ticket is on the document and in your own records.
Payment details.The account or link is current, and the reference you want quoted is stated on the face of the invoice.
Description.Each line names what was delivered, when it was delivered, and uses the words the customer's own records use.

Where the invoice follows an accepted price, keep the wording consistent with the quote so the customer's accounts team can match them easily. The covering message that carries it is worth writing like any other business letter: what is attached, what you need back, and by when.

Common questions

Can one document be both an invoice and a receipt?

Only where payment is taken on the spot, and only if it says plainly that the balance is zero and how it was settled. Any other time, issue two.

What do I do if the customer says they never received it?

Reissue the same document, with its original number and date, and note the resend. Raising a fresh invoice with a new number creates two open items for the same work.

Should the invoice repeat my full terms?

Put the payment window and the dispute route on the face of it, and reference the agreement for the rest.

How soon after the work should an invoice go out?

As soon as the work is done and verifiable. An invoice arriving weeks later lands on someone who must reconstruct the approval, and that reconstruction is where the delay comes from.