Skip to content

Statement of Account

A periodic summary sent to a customer listing all open invoices, credits, payments, and the total balance owed as of a date.

A statement of account is a customer-level summary, typically issued monthly, showing all activity and open items on the account: unpaid invoices with dates and amounts, unapplied credits and credit memos, payments received, and the resulting total balance, often broken out by aging bucket. Unlike an invoice, which demands payment for one transaction, a statement is a reconciliation document: it shows the whole relationship as the seller's ledger sees it.

Statements do quiet but real work in the collection cycle. They surface invoices the customer never received (the single most common cause of B2B late payment), prompt AP teams to schedule older items, expose unapplied credits the customer may want to use, and give both sides a shared basis for account reconciliation. Many AP departments will not process a past-due balance without a statement, and in some industries (construction, dealer networks) the monthly statement, not the invoice, is the primary payment trigger.

The design details determine whether statements get used or ignored: include remit-to details and electronic payment instructions, show credits as clearly as debits, age the items, and deliver through the channel the customer actually processes, email, portal upload, or EDI, rather than assuming print. A statement run also functions as a light-touch dunning event: for slow-but-good customers, the statement plus a subject line noting the past-due amount often collects without a call.

Customer Portal

See SCREDIT on your own workflows.

A 30-minute walkthrough with the team that built it — using scenarios from your credit operation, not canned demo data.