Statement of Account vs Invoice: Which to Send, and When

An invoice bills one piece of work. A statement of account shows the running score: every open invoice, every payment, every credit, and the balance still owed.

If you send the wrong one, clients get confused and payments stall. AP teams especially hate getting a fresh invoice when what they needed was a summary of three older ones their manager already approved.

This guide is for freelancers, consultants and small studios that bill the same clients more than once. It covers the difference, a worked example, when a statement speeds payment up, and how to keep statements from turning into soft, ignored PDFs.

Statement of account vs invoice

Invoice

• Answers: "What do I owe for this job?"
• Scope: One transaction or period of work
• Creates new debt?: Yes
• Best for: New deliverables, retainers billed for a period
• Typical ask: Pay this amount by this date

Statement of account

• Answers: "What is open between us right now?"
• Scope: Many invoices, payments and credits over a date range
• Creates new debt?: No. It summarises existing debt
• Best for: Clients with several open invoices or messy payment history
• Typical ask: Confirm the balance and clear the oldest items

A statement is not a polite substitute for an invoice. If the work was never billed, send an invoice first. The statement comes after there is something to summarise.

Why freelancers mix these up

Solo operators often use "invoice" for every money conversation. That works when you have one client and one open PDF. It breaks when:

• A retainer client has February, March and an extras invoice all open
• Someone paid the wrong invoice number
• A credit note reduced one job but the client still sees the old total in email
• Procurement asks for "a statement for audit" and you send another bill

In those cases a statement of account is clearer than a fourth invoice with a long note in the description field.

What belongs on each document

Invoice essentials

• Unique invoice number
• Issue and due dates
• Line items for that job only
• Total due and payment details
• Purchase order number if the client requires one

Statement essentials

• Client name and the statement date
• Period covered (for example 1 Sep–9 Nov 2026)
• List of invoices with numbers, dates, original amounts
• Payments received, with dates
• Credit notes applied
• Running or closing balance due
• Optional aging buckets: current, 1–30, 31–60, 61+

You can build the aging view from the same data you use in an invoice aging report. The statement is the client-facing version of that list.

Worked example

A studio has Client North on a monthly design retainer.

• Invoice #2108 — 1 Sep — €1,800 — unpaid
• Invoice #2122 — 1 Oct — €1,800 — unpaid
• Invoice #2139 — 1 Nov — €1,800 — unpaid
• Payment 12 Oct — €1,800 — applied to #2108
• Credit note 20 Oct — €200 — goodwill on #2122

Wrong move: email "please pay the outstanding €5,200" with no breakdown.

Better invoice move: if November work was never billed, send #2139 as a normal invoice.

Better statement move: send a statement dated 9 Nov showing:

• #2108 €1,800, paid 12 Oct, balance €0
• #2122 €1,800, credit €200, balance €1,600
• #2139 €1,800, balance €1,800
• Total due €3,400

Now AP can match lines. Your next reminder can point at the statement total instead of arguing about which PDF is current.

When to send an invoice

Send an invoice when:

• You finished a scoped piece of work
• A retainer period closed
• A deposit or milestone is due under the contract
• The client needs a PO-backed document for a new charge

Keep invoices specific. One job, one clear ask. If you need help getting that first ask paid without souring the relationship, use a calm overdue follow-up approach.

When to send a statement of account

Send a statement when:

• The client has two or more open invoices
• They ask "what do we still owe you?"
• Finance needs a period summary for close or audit
• Payments keep landing on the wrong invoice
• You are about to escalate and want one shared picture of the balance

A monthly statement to retainer clients can prevent surprise. End-of-month is enough for most freelancers. Weekly statements are usually noise unless the client asked for them.

Statements that get paid vs statements that get ignored

A useful statement is boring and exact. An ignored statement is vague and soft.

Do this:

• Use invoice numbers the client already has
• Show credits and payments as separate lines
• Put the total due near the top and again at the bottom
• Attach or link the open invoices
• Say what you want: "Please clear the €3,400 balance by 16 November" or "Confirm which invoices you will pay this week"

Avoid this:

• Long apology paragraphs with no total
• Mixing new unbilled work into the statement as if it were already invoiced
• Sending a statement instead of the first invoice for new work
• Changing historical amounts without a credit note trail

If a balance needs to shrink, issue the credit note first, then refresh the statement. Otherwise you will chase a number both of you already moved past.

How statements fit a reminder ladder

Think of the documents as layers:

1. Invoice creates the debt
2. Reminders keep attention on that debt
3. Statement clarifies several debts at once
4. Final notice closes the polite chapter on a specific unpaid amount

A statement mid-sequence is helpful when the client says they "thought everything was paid." It is less helpful as your very first message after a single invoice goes a few days late. For a single invoice, a normal reminder is enough. For the shape of a full sequence, see the reminder ladder.

Statement billing is not the same as delaying invoices

Some agencies bill on statement cycles: work accumulates, then one statement goes out. That can work for trusted retainers. It is risky if you never issue underlying invoices and the client disputes the whole period at once.

Safer pattern for freelancers:

• Invoice as work completes or as the retainer period ends
• Send a statement when multiple items are open
• Keep chasing at the invoice level when one item is stuck

That keeps disputes small and payment matching simple.

A simple monthly habit

Once a week, or at least once a month:

1. List clients with more than one open invoice
2. Rebuild their statement from your tracker
3. Send it with a clear total and a reply ask
4. Log the send date so you do not repeat it three days later

This sits cleanly inside a weekly AR routine. The point is not more PDFs. The point is fewer "which invoice?" replies.

FAQ

Is a statement of account a payment request?

It can include a request to pay the closing balance, but it does not create new charges. The invoices underneath create the debt.

Can a statement replace invoices for a retainer client?

Not safely. Keep issuing invoices for each period, then use statements to summarise what is still open.

What if the client only pays from statements?

Fine. Still generate invoices so each line on the statement has a source document, PO match and audit trail.

Should I include paid invoices on the statement?

Include them for the period if it helps reconciliation. Mark them paid. The closing balance should only reflect what is still owed.

Does DueChat generate formal statements of account?

DueChat focuses on chasing open invoices with a reminder flow you control. Keep formal statement PDFs in your invoicing or accounting tool, and make sure the balances you chase match that statement.

If open invoices are scattered across email threads, put the chase in one place. DueChat Pro is €19/month or €190/year, with a 30-day trial. Start at duechat.io/signup.