Invoicing and Getting Paid

Customer Statements: What They Are and When to Send Them

A statement puts every invoice, payment and balance for one customer on a single page. What to include, how it differs from an invoice, when to send one, and why it often gets you paid faster than a reminder.

Illustrative example with fictional data.

An invoice asks for payment for one thing. A statement answers a different question: across everything we've billed you, what have you paid and what's still open? It's the document that settles "I thought we'd paid that" in one look, and it's one of the most under-used tools in a small finance team.

Invoice, receipt, statement: three different jobs

Document What it covers When it's issued The question it answers
Invoice One sale or one billing cycle When you bill "What do I owe for this?"
Receipt One payment When payment arrives "Did you get my money?"
Statement All activity over a period Monthly, or on request "Where do we stand overall?"

A statement doesn't replace invoices and doesn't create a new debt. It's a summary of documents the customer already has, which is exactly why it works: there's nothing new to dispute, only a picture to agree.

What a good statement shows

Keep it to one page if you can. It should include:

  1. Your details and the customer's, using the same legal names as on your invoices.
  2. The period covered, such as 1 September to 30 November 2026.
  3. An opening balance, carried from the end of the previous period.
  4. Every transaction in date order: invoices as debits, payments and credit notes as credits.
  5. A running balance after each line.
  6. The closing balance, and how much of it is overdue.
  7. How to pay, ideally a single link or clear payment details with a reference.

Here's what that looks like for one school customer of a logistics firm in Ikeja:

Date Detail Debit (₦) Credit (₦) Balance (₦)
01 Sep 2026 Opening balance 0.00
01 Sep 2026 INV-2026-0301 · First term transport 1,075,000.00 1,075,000.00
12 Sep 2026 Payment · bank transfer 1,075,000.00 0.00
01 Oct 2026 INV-2026-0355 · October excursions 430,000.00 430,000.00
03 Nov 2026 INV-2026-0418 · Fleet and excursions 1,343,750.00 1,773,750.00
03 Nov 2026 Payment · bank transfer 1,343,750.00 430,000.00
Closing balance 430,000.00
of which overdue (INV-2026-0355, 18 days) 430,000.00

Look at what this tells the customer's bursar. They paid November's invoice the day it arrived, but October's ₦430,000 is still open. Probably it was lost in someone's inbox. A reminder about INV-2026-0355 on its own might be ignored. A statement that shows they've paid everything else makes the gap obvious and easy to fix.

When to send statements

There's no single rule, but these four moments cover most businesses:

  • Monthly, to every customer with an open balance. Send them on the same day each month, so customers learn to expect them.
  • At the end of a term, quarter or contract, so both sides agree the position before the next cycle starts.
  • Before a difficult conversation. If you're about to pause service or escalate, start from a statement both sides can see.
  • When the customer asks. Corporate accounts teams often request one at their own year-end to reconcile their payables. Answer quickly. It's an easy win.

Don't send statements to customers with nothing outstanding unless they've asked. A ₦0.00 statement every month just teaches people to ignore the next one.

Statements as a collections tool

Statements get you paid for three reasons:

  1. They remove the excuse. "We never received that invoice" is hard to sustain when the statement lists it with its number and date.
  2. They show patterns. A customer who pays every invoice except one has a process problem, not a cash problem, and it's usually fixed in one email.
  3. They make the total feel real. Three small open invoices that each seem minor add up to a balance that gets attention.

Pair them with a short covering note:

Please find your statement to 30 November 2026. Your balance is ₦430,000, all relating to INV-2026-0355 (October excursions), which was due on 15 October. If you've already paid it, send us the transfer reference and we'll match it.

That last sentence matters. Sometimes the customer has paid, and the money is sitting unmatched in your bank account. The statement surfaces that too.

Common mistakes

  • Statements that don't match invoices. If a customer's own records show a different invoice total, the statement will start an argument. Fix the underlying invoice first.
  • Unexplained adjustments. Every credit note and write-off should appear with a reference, not as a bare "adjustment".
  • Short payments marked as paid. If a ₦1,500 shortfall was quietly absorbed, the statement can't show it. Our guide to short payments explains why invoices should stay open until paid in full.
  • Statements built by hand. Copying figures from three places into a spreadsheet is slow, and every copy is a chance to make a mistake. A statement should come straight from your invoicing records.

How Flux helps

Flux keeps every invoice, payment and receipt against the customer, so a statement is a report, not a project. Pull one for any customer, share it as a secure signed PDF link, and let your branding and sending domain carry it. Each open invoice already has its own Pay online link, so the customer can settle the balance by card or bank transfer. See Invoicing & Billing.

From the blog