email59

Small business email

Statement of account: the monthly email for a client with five open invoices

When one client owes you for five invoices, five separate reminders feel like nagging and still get lost. One statement of account, sent on the first working day of the month, lists every open invoice with its date, amount and days overdue, adds a total, and splits the lateness into ageing buckets. Below: the layout, a fully worked example, when to send it, and how it differs from a single reminder.

Statement or reminder: which one to send

A reminder is about one invoice and one date. A statement is about the relationship: everything open, as of one day. Use a reminder while a client has one late invoice. Switch to a statement when two or more are open, or when the client pays in batches, because the person paying then needs one list to approve rather than five emails to reconcile.

Payment reminderStatement of account
CoversOne invoiceEvery open invoice, plus credits
TriggerA due date passesA calendar date (monthly)
ToneEscalates (heads-up, plain, firm)Neutral: a snapshot, not a chase
Best forFirst late invoiceTwo or more open invoices, batch payers

A worked example: five invoices, £7,000.00

Shah Design sends a statement to Tom Reed on Monday 2 November 2026. Terms differ because the work did: net 30 on most jobs, net 14 on invoice 1040. Days overdue is the statement date minus the due date, shown only when positive.

InvoiceIssuedDueAmountDays overdue on 2 NovBucket
103120 Jul19 Aug£1,800.007560+
103624 Aug23 Sep£950.004031-60
104028 Sep12 Oct£2,400.00211-30
104312 Oct11 Nov£1,250.00not yet dueCurrent
104426 Oct25 Nov£600.00not yet dueCurrent
Total£7,000.00

Check one row by hand: invoice 1031 was due on 19 August. From 19 August to 2 November is 12 days left in August (to 31 Aug), 30 in September, 31 in October and 2 in November: 12 + 30 + 31 + 2 = 75 days, so it sits in the 60+ bucket.

The ageing buckets

Ageing sorts the open money by how late it is. The common split is current (not yet due), 1-30, 31-60 and 60+ days past due; some teams add 61-90 and 90+. Bucket by days past the due date, not days since the invoice date, or net-30 invoices look 30 days worse than they are. For the example:

BucketAmountShare of total
Current£1,850.0026%
1-30£2,400.0034%
31-60£950.0014%
60+£1,800.0026%
Total£7,000.00100%

The headline number, £7,000.00, hides the useful fact: £2,750.00 (39%) is more than 30 days past due, while £1,850.00 is not due at all. Printing the buckets tells Tom which invoices to look at first without a word of scolding. Many accounting tools print a single total only; Xero users, for instance, have asked for ageing totals on statements, and the usual workaround is the Aged Receivables report filtered by contact. If your tool cannot do it, add the bucket line by hand or generate the statement yourself.

The email, ready to copy

Subject: Statement of account: Shah Design, 2 November 2026, £7,000.00 outstanding

Hi Tom,

Here is where your account stands on Monday 2 November. Five
invoices are open, £7,000.00 in total, of which £5,150.00 is past due.

Invoice  Issued  Due     Amount     Days overdue
1031     20 Jul  19 Aug  £1,800.00  75
1036     24 Aug  23 Sep    £950.00  40
1040     28 Sep  12 Oct  £2,400.00  21
1043     12 Oct  11 Nov  £1,250.00  not yet due
1044     26 Oct  25 Nov    £600.00  not yet due

Total outstanding: £7,000.00
Past due: £5,150.00  (60+ days: £1,800.00; 31-60: £950.00; 1-30: £2,400.00)

Invoice 1031 is the oldest. Could you tell me whether it is waiting
on a purchase order number or a signature? All five can be paid
with one transfer: https://pay.example/stmt/reed-2026-11
Please quote "Statement 2 Nov" so I can match it.

Thanks,
Priya
  • Subject carries the date and total, so it is findable later and the bookkeeper sees the amount without opening it.
  • Body table in plain text, not an image, so it survives forwarding and screen readers. Attach a PDF only if the client's accounts team wants one for their files.
  • One question, aimed at the oldest invoice. A statement is neutral, but the oldest line is the one with a reason attached.
  • One payment link or reference for the whole balance, with the instruction to quote the statement date.

When to send it

Pick a fixed day and keep it. The first working day of the month works because clients run payment batches around month end and early month, and because a fixed day means nobody has to decide each time. In November 2026 that is Monday 2 November (1 November is a Sunday). Rules that work in practice:

  • Send only if a client has two or more open invoices, or any invoice past due. A client with one current invoice needs nothing.
  • Do not send a statement and a reminder for the same invoice in the same week. The statement replaces that week's reminder.
  • Show credit notes and part payments as negative lines, or the total will be wrong and the client will point it out in the reply.
  • If a payment arrived in the last two days, say "payments received to 30 Oct are included", so Tom knows the cut-off.

Escalating from the statement

The statement is a snapshot; the follow-up depends on the buckets. A workable ladder: nothing extra for current and 1-30 money; a phone call or direct note about any invoice in 31-60; and for 60+, a personal message from the owner that names the invoice and a date to pay by. Send the next statement on the same day next month either way: a client who sees an invoice move from 31-60 to 60+ in two consecutive statements has been told, in writing and without drama, that time is passing.

Keep the tone neutral: every figure should be checkable from the client's own records. If the statement is wrong, the conversation is about the statement, not about whether they pay.

Sending it from your own app

If your billing tool or script produces the list, send it from a real reply address so the answer ("1031 needs a PO number") lands with a person. With email59 that is one call to /v1/send with a reply_to; see the missed-payment email article for the pattern, and never change bank details by email: put the same line on every statement.

Send your first statement from the API

Sources and method

This article is general information, not accounting or legal advice. Xero and Tofu are trademarks of their owners; email59 is not affiliated with them.

Send your first email More articles