What Is a Billing Statement?

A billing statement is a summary of everything a customer owes you at the end of a period — the balance they started with, every charge and payment in between, and the balance still outstanding. It's one document covering many transactions, and that's what makes it different from an invoice.

If you received a billing statement, this page won't help you. A credit card, phone or utility statement uses the same logic, but those come from companies with their own dispute processes. Everything below is written for the person sending* the statement to a customer.

Billing statement vs invoice

An invoice says: for this job, you owe me this much. A statement says: across this period, here's everything that happened on your account, and here's where we stand.

The cleanest way to hold the difference: a statement doesn't create new debt. Every amount on it already exists on an invoice you sent earlier. The statement pulls those amounts together, subtracts what's been paid, and shows what's left.

Which gives you a rule worth following: if a charge appears on a statement and nowhere else, you skipped a step. The customer has nothing to check it against, and that's where disputes start. Statements summarise; they don't introduce.

Depending on where you are and who you ask, the same document is called a statement of account, a customer statement, or just the monthly statement. There's no meaningful difference between them.

How the balance is worked out

Every statement is the same equation, and it only has four parts:

Opening balance + charges this period − payments and credits this period = Closing balance

The opening balance is last statement's closing balance. If August's opening balance doesn't match July's closing balance, there's a gap in your records — and the customer, who kept both, will find it before you do.

Charges are the invoices you issued during the period, one line per invoice, under its own invoice number and date. Payments are what actually landed, dated the day the money arrived, with the method named — a customer who paid cash three weeks ago and doesn't see it on the statement will assume you lost it. Credits sit on the same side as payments: a refund, a discount agreed after the fact, a visit you billed and didn't make — each on its own line with its own reference, never quietly netted off a charge to make the numbers come out right.

The closing balance is what falls out of those four. It should never be typed in by hand.

What goes on a billing statement

A statement is a short document with a long table in the middle. These are the parts that have to be there:

One thing that doesn't belong: a due date for the whole balance — each invoice already has its own, and inventing one for the total quietly changes the terms your customer agreed to.

Statement date and statement period — both, with the period written out: 1–31 August 2026. A statement without a stated period is unauditable.
Your business details and the customer's — the same block that sits on your invoices.
An account reference — whatever you call this customer in your own records; if they gave you a supplier number, use theirs.
Opening balance — as its own line at the top of the table, dated the first day of the period.
The transaction lines — for each one: date, reference (the invoice or credit note number), a short description, the charge, the payment or credit, and a running balance — the column that makes a statement readable.
Closing balance — the amount currently outstanding, stated once, prominently.
An aging summary — see the next section. This is the field most small businesses leave off, and it's the one that does the most work.
Payment instructions — how to pay and what reference to quote. The same details as on your invoices, not different ones.
A cut-off note — one line: Payments received after 31 August 2026 are not reflected on this statement. It pre-empts the most common reply you'll get: someone telling you they already paid.

Aging: the 30/60/90 columns, and why they matter

Aging is the outstanding balance split by how overdue each piece of it is. The standard buckets are:

Current · 1–30 days · 31–60 days · 61–90 days · 90+ days

Each unpaid invoice drops into a bucket by how far past its due date it is; the buckets add up to the closing balance. That's the whole mechanism — it's arithmetic, not a technique.

The reason it earns its space on the page: it tells the customer which invoice is late. "Your account is behind" is not something an accounts payable clerk can act on. "$520 sitting in the 1–30 column, against invoices 0311 and 0318" is.

If you strip a statement down to the minimum, keep this. A statement without aging is a receipt for information you already had.

Aging is measured per invoice, not per customer. A customer with a 90-day-old $200 invoice and a brand-new $2,000 one is not a "90-day customer"; they have $200 in the 90+ bucket and $2,000 in Current.
Pick your start date and say which it is. Aging runs from the due date or from the invoice date, both are used in practice, and they give different answers. Print it on the statement: Aged from due date.
Partial payments split. Pay $100 against a $260 invoice and $160 stays in that invoice's bucket, aging with it. It doesn't reset.

What one actually looks like

A commercial cleaning business, one customer, one month. Terms are Net 14, and aging runs from the due date.

Statement of account · Bright & Tidy Cleaning · Harbour Point Dental

Period: 1–31 August 2026 · Issued 2 September 2026

Opening balance 520.00 · Charges 1,220.00 · Payments and credits 580.00 · Closing balance 1,160.00

Aged from due date. Payments received after 31 August 2026 are not reflected on this statement.

Two things about how it's laid out, because neither is obvious:

Every charge carries an invoice number. The customer can pull INV-0329 out of their inbox and check it. That single column is the difference between a statement someone pays and a statement someone queries.

The aging table says something the transaction table doesn't. The closing balance is $1,160, but only $520 of it — the two mid-month cleans past their Net 14 date — is actually late. Without the split, $1,160 reads as one overdue lump, and the conversation starts in the wrong place.

Which businesses should send statements — and which shouldn't

Statements are for repeat customers, and only for repeat customers. The test is simple: does this customer receive more than one invoice from you in a typical month? If not, a statement has nothing to summarise.

The businesses this fits:

If that's you, the part worth fixing first sits underneath the statement: one numbered invoice per visit, issued on the day. A statement built on top of guesswork is just a tidier guess.

The businesses it doesn't fit, and this is the longer list:

And one thing a statement is not: a way to make a late invoice feel more urgent. A statement sent to someone who owes you exactly one overdue invoice is a chase wearing a costume, and everyone can tell. If an invoice is late, chase that invoice by its number.

Weekly or fortnightly service work on the same premises — commercial cleaning, lawn and grounds maintenance, pool servicing, pest control, window cleaning.
Ongoing monthly work with a fixed scope — IT support, virtual assistant and back-office admin, retained maintenance contracts.
Any customer with an accounts payable department that pays on a cycle. They're expecting a statement, and some of them will not release a payment run without one.
One-off jobs paid on completion. Nothing is carried forward. A statement here is a worse invoice with extra steps.
Customers with a single open invoice. Send a reminder about that invoice. A one-line statement reads as evasive — like you're avoiding naming the thing you want paid.
Anyone you bill less often than monthly. Two invoices a year don't need a period summary.
Emergency and call-out work with no repeat pattern. Every job stands alone; every invoice stands alone.