
Maintenance
Part of Invoices and receipts: the fields that survive contact with reality
Invoices and receipts template: one shared header and five document layouts
A shared invoice and receipt header plus deposit, balance, recurring, credit note and receipt layout, with field notes for each line and which one to send.
One invoice layout is never enough. When you take a deposit, correct a figure, or bill the same customer monthly, you need a second document with the same header but a different middle.
Businesses that keep one template and improvise the rest get a credit note that looks like an invoice and a receipt that reads like a demand.
What follows is a family of five: one header block, then a deposit invoice, a balance invoice, a recurring invoice, a credit note, and a receipt for a payment on account. Every field carries a note saying what goes in it. Square brackets mark the parts you fill in.
What to take away
- Build the header once and reuse it unchanged; only the middle of the document changes between the five.
- A deposit and its balance are two invoices with two numbers, never one invoice edited twice.
- A credit note is the only correct way to reduce an invoice you have already sent.
The shared header
The invoices and receipts overview explains why each header field exists. This table is about which fields stay fixed across the family and which change per document.
Header fields: fixed or changing
Fixed
- Trading name, address
- Yes
- Customer name, address
- No
- Document type
- No
- Document number
- No
- Document date
- No
- Due date
- No
- Their reference
- Yes
- Currency code
- Yes
Per customer
- Trading name, address
- No
- Customer name, address
- Yes
- Document type
- No
- Document number
- No
- Document date
- No
- Due date
- No
- Their reference
- No
- Currency code
- No
Changes
- Trading name, address
- No
- Customer name, address
- No
- Document type
- Yes
- Document number
- Yes
- Document date
- Yes
- Due date
- Invoices only
- Their reference
- No
- Currency code
- No
| Field | Same on every document? | Note |
|---|---|---|
| Your trading name, address, billing contact | Yes | Change it in one place. A stale address on the credit note but not the invoice is how two documents stop matching. |
| Customer's registered name and billing address | Yes, per customer | Take it from their accounts team, not from the email signature of the person who ordered. |
| Document type in large type | Changes | INVOICE, CREDIT NOTE, RECEIPT. Never leave a reader to infer it from the layout. |
| Document number | Changes | One sequence for invoices, a separate sequence for credit notes and receipts, or a prefix that makes the type obvious. |
| Document date | Changes | The date you issued it, not the date of the work. |
| Due date | Invoices only | A calendar date. Omit it from receipts and credit notes entirely, or a machine will treat them as payable. |
| Their reference | Yes | Purchase order, job or contract number. Repeat it on every document in the chain so the customer can tie them together. |
| Currency code | Yes | Written once in the header, not guessed from a symbol. |
Deposit invoice
Sent when the customer has accepted a quote that asked for money up front.
Deposit invoice key lines
- Deposit againstjob name and quote number
- Work coveredone line naming the scope
- Balance of x.xxinvoiced on completion or sign-off
- Less nothing furtherdeposit credited, not deducted again
INVOICE Number [INV-xxxx]
Date [issue date]
Due [calendar date]
Deposit against: [job name], as quoted on [quote number, date]
Description Amount
Deposit: [n]% of agreed total of [x.xx] [x.xx]
Work covered: [one line naming the scope]
Subtotal [x.xx]
[Tax, named] [x.xx]
TOTAL DUE [x.xx]
Balance of [x.xx] will be invoiced on [trigger: completion,
delivery, sign-off], less nothing further.
Field notes. The first line under the heading ties this document to the quote, which is what the customer's approver will look for. The "work covered" line stops a deposit being read as payment for part of the job rather than a down payment on all of it.
The closing sentence tells the customer what the next invoice will look like before it arrives. "Less nothing further" says the deposit will be shown as a credit on that invoice and not deducted again.
Balance invoice
Same header, new number. Do not reopen the deposit invoice and change it.
Balance invoice build order
- New number, same header
- List deliverables with dates
- Add agreed change with approval reference
- Show total for job
- Deduct deposit paid, INV-n, date
- State total due
INVOICE Number [INV-xxxx+1]
Final invoice for: [job name], quote [number]
Description Qty Unit Amount
[Deliverable 1, with the date
delivered or the period] [n] [x.xx] [x.xx]
[Deliverable 2] [n] [x.xx] [x.xx]
[Agreed change: reference the
written approval and its date] [n] [x.xx] [x.xx]
Subtotal [x.xx]
[Tax, named] [x.xx]
Total for job [x.xx]
Less deposit
paid, INV-[n],
received [date] [-x.xx]
TOTAL DUE [x.xx]
Field notes. The job total appears before the deposit is deducted, so the customer can check it against the quote. The deposit line names the earlier invoice number and the date the money arrived, which lets their accounts team match the two.
Any scope change gets its own line pointing at the written approval. Never fold it into a deliverable's price.
Recurring invoice
For a retainer, a subscription, or a monthly service. The trap here is an invoice that is identical every month except the date, because then a customer paying twice cannot tell which month they paid.
Recurring invoice must-haves
- Period covered in the description
- Month named in words
- Volume line if agreement has one
- Overage as separate line, same month
- Sequential number, no month inside
- Actual due date stated each time
- Change notice only when something moved
Field / Enter
- Period covered
- [first day] to [last day] · The most important line on the document. Put it in the description, not only in the header.
- Description
- [Service name] for [month, year] · Name the month in words. Numbers alone get transposed.
- Volume line, if any
- [n] [units] included; [n] used · Only when the agreement has a volume. Shows the customer they are inside the allowance.
- Overage line
- [n] extra [units] at [rate] · A separate line, in the month it happened, never rolled into next month's fee.
- Number
- Sequential, like any invoice · Do not build the month into the number; a sequence gap then looks like a missing month.
- Due date
- Fixed offset from issue, as agreed · State the actual date each time.
- Change notice
- One line, only when something changed · "Fee revised from [date] as agreed on [date]." The absence of this line is a promise that nothing moved.
Credit note
The document that reduces an invoice already sent. It never carries a due date and it never replaces the original.
Credit note settlement paths
- Credit note issued against INV-xxxx
- Refunded to original payment method
- Held on account for next invoice
- Offsets open balance of INV-xxxx
- If figure wrong: new invoice, new number
CREDIT NOTE Number [CN-xxxx]
Date [issue date]
Against invoice: [INV-xxxx] dated [date]
Reason: [one plain sentence: returned goods, agreed
reduction, pricing error, service not delivered]
Description Amount
[The exact line from the original invoice,
quoted as it appeared there] [-x.xx]
[Tax, named] [-x.xx]
TOTAL CREDIT [-x.xx]
How this credit is settled: [refunded to the original
payment method on or before date / held on account and
applied to the next invoice / offsets the open balance
of INV-xxxx, leaving x.xx due]
Field notes. The reason line is written for a third party reading the file a year later, and the settlement sentence is the one people forget. Without it, a credit sits unapplied on both sides while each party assumes the other holds the money.
If the original invoice needs re-issuing at the correct figure, issue a fresh invoice with a fresh number and reference both documents on it.
Receipt for a payment on account
Issued when money arrives that does not settle a single invoice exactly.
Receipt applied-to block
- INV-nin full
- INV-npart payment, x.xx remains
- Held on accountunallocated
- Open balanceafter this receipt
RECEIPT Number [RCT-xxxx]
Received from [payer, which may not be the customer]
Date received [when the funds cleared]
Amount [x.xx] [currency]
Method [transfer / card / cash, with reference]
Applied to
INV-[n] in full [x.xx]
INV-[n] part payment, [x.xx] remains [x.xx]
Held on account, unallocated [x.xx]
Open balance on your account after this receipt [x.xx]
Field notes: "Date received" is the date the money cleared, not the date the customer says they sent it. The unallocated line is honest bookkeeping: money you hold and have not matched. The closing balance is the sentence the customer's bookkeeper actually wants.
If that unallocated line keeps appearing, the invoices and receipts mistakes list shows which ones cause the most delay.
Choosing which one to send
- Money asked for before workdeposit invoice.
- Money asked for after work, with a deposit already takenbalance invoice, showing the deposit as a credit.
- Same service, every periodrecurring invoice with the period in the description.
- You need to reduce an invoice already sentcredit note, then a new invoice if a corrected figure is needed.
- Money arrivedreceipt, with an "applied to" block whenever it covers more or less than one invoice.
Where the work was sold through a staged proposal, each milestone gets a balance-style invoice referencing the milestone. The deposit is credited once, on the last one.
Writing the chain down as a short procedure keeps it consistent when someone else raises the invoices. When several people raise invoices, a written procedure belongs in your operational checklists so the deposit credit lands on the same milestone every time.







