An invoice is a request for payment covering one specific sale: what was delivered, how much is owed, and when it is due. A statement of account is a periodic summary of the whole customer account, listing every open invoice, the payments and credits applied, and the balance still outstanding. An invoice asks for money for a single transaction; a statement shows where the relationship stands. Customers should pay from invoices, never from statements.
Last updated: July 2026.
Most people meet both documents without ever being told the difference, and accounts receivable teams pay for that quietly. A customer who treats a month-end statement as a bill will either pay twice or pay a total nobody can match to a line item. A customer who ignores statements because "we already paid the invoice" leaves a credit memo unapplied for a year. Getting the two straight is a small piece of vocabulary that removes a surprising amount of friction from the payment side of the customer relationship.
What is the difference between an invoice and a statement of account?
An invoice is transactional. It is created at the moment a specific charge becomes due, it carries line items and quantities and prices, it has a unique invoice number, and it creates an entry in accounts receivable. It is the document a customer owes against. A statement of account is informational. It is generated on a schedule, usually at month end, and it reports on invoices that already exist: which ones are still open, what has been paid, what credits were applied, and what the closing balance is. It creates nothing new in the ledger.
The practical test is what happens if you delete the document. Delete an invoice and a real receivable disappears with it. Delete a statement and nothing in your books changes, because a statement is a report, not a transaction. That is also why a statement can be regenerated at any time and will simply show the current picture, while an invoice is a fixed record of a moment.
Invoice vs statement of account: side by side
| Dimension | Invoice | Statement of account |
|---|---|---|
| What it covers | One sale or one billing event | Every open item on the account |
| Purpose | Request payment for specific goods or services | Summarize account status and prompt payment of anything outstanding |
| When it is sent | When the charge becomes due | On a schedule, most often at month end |
| What is on it | Line items, quantities, prices, terms, due date | Invoice numbers, dates, amounts, payments, credits, running balance |
| Effect on the ledger | Creates an accounts receivable entry | None, it reports entries that already exist |
| Pay from it? | Yes, this is the payable document | No, pay the individual invoices it lists |
| Numbering | Unique invoice number | Account number plus a statement period |
What goes on a statement of account?
A useful statement is more than a total. At minimum it should carry the customer name and account number, the period it covers, an opening balance, and then a line for every document that hit the account in that window: invoices with their numbers, dates, and amounts, plus payments received and any credit memos applied. It closes with the outstanding balance and remit-to instructions.
Good statements also age the balance into buckets, typically current, 1 to 30 days, 31 to 60, 61 to 90, and over 90. That turns a flat number into a conversation, because the customer can see that $4,000 of their balance is fine and $900 of it is two months late. It is the same view your team works from in the accounts receivable aging report, just pointed outward.
There are two common formats. An open-item statement lists only invoices that are still unpaid, which suits B2B accounts where each invoice is paid separately. A balance-forward statement carries the prior balance and shows all activity since, which suits revolving or consumer-style accounts. Open-item is the safer default for business customers, because it removes any doubt about which invoices are actually being asked for.
Invoice vs statement vs receipt: what is the difference?
These three documents sit at different points on the same timeline. An invoice comes before payment and requests it. A receipt comes after payment and proves it. A statement sits above both and summarizes the account across a period, including invoices that are still open and payments already made. Only the invoice creates an obligation, only the receipt closes one, and the statement just narrates.
A worked example
A food distributor bills a restaurant weekly. In March it issues four invoices: $2,400 on the 4th, $1,850 on the 11th, $2,100 on the 18th, and $1,975 on the 25th, all net 30. The restaurant pays the first two invoices in full during the month.
On March 31 the distributor sends a statement of account. It lists all four invoices with their numbers and dates, shows $4,250 in payments applied, and closes with a $4,075 balance made up of the two most recent invoices, neither of which is late yet. No new charge was created. If the restaurant's bookkeeper paid $4,075 against "the statement" without referencing invoice numbers, the distributor's AR clerk would have to guess how to apply it, and an unapplied cash line would sit on the account until someone chased it. That single habit is responsible for a large share of manual invoice reconciliation work.
Should a customer pay from the invoice or the statement?
Always from the invoice. The invoice is the document with the detail a payables team needs: purchase order reference, line items, tax, and terms, all of which get matched before payment is approved. A statement has none of that at line level, so paying from one invites duplicate payments, misapplied cash, and disputes nobody can trace. Statements are reminders and reconciliation aids, not payable documents.
This is exactly how a disciplined accounts payable process works on the other side of the transaction: the AP team matches an invoice to a purchase order and a receiving record before anything is scheduled for payment. A statement fails that match on arrival, because it is not tied to a single delivery.
How do accounting systems treat statements and invoices?
In QuickBooks, Xero, NetSuite, and every system built on the same logic, an invoice is a transaction and a statement is a report. Creating an invoice debits accounts receivable and credits revenue. Generating a statement does neither: it queries the invoices and payments already on the customer record and formats them. That is why you can email a statement ten times without changing a single number, and why a statement will never appear in a revenue report.
The practical consequence is that you fix problems on invoices, not on statements. If a customer says the statement is wrong, the error is nearly always in an invoice that was issued incorrectly, a payment applied to the wrong invoice, or a credit memo that was never applied. Correct the underlying record and regenerate the statement.
When should you send a statement of account?
Monthly, at or just after close, is the standard rhythm for B2B accounts, and it works because it matches how most customers run their own payables cycle. Businesses with high transaction volume sometimes go semi-monthly. What matters more than frequency is consistency: a statement that lands on the same day each month becomes part of the customer's routine, and routine is what gets balances checked.
Treat the statement as a nudge, not a demand. It is the polite, informational layer of collections. When an invoice actually goes past due, the follow-up belongs in a proper reminder sequence with a specific invoice number and amount, which is a different job with different language, covered in our guide to past due invoice emails. Statements keep the account visible; reminders and escalation collect the money.
Frequently asked questions about invoices and statements
What is the difference between an invoice and a statement? An invoice requests payment for one specific sale and creates a receivable. A statement summarizes a customer's whole account over a period, listing open invoices, payments, credits, and the closing balance. The invoice is a transaction; the statement is a report on transactions that already exist.
Is a statement of account the same as an invoice? No. They are different documents with different jobs. An invoice covers a single charge and is the document a customer pays against. A statement of account covers many charges across a period and exists to show the balance and prompt review. A statement never replaces the invoices it lists.
Can you pay from a statement of account? You should not. Statements lack the line-level detail and references that payables teams match before approving payment, so paying from one causes duplicate payments and cash that cannot be applied. Use the statement to spot what is outstanding, then pay each open invoice by its invoice number.
Is a statement of account a legal document? A statement is a business record rather than a demand for payment, and it does not by itself create an obligation. The invoice, backed by the underlying contract or order, is what establishes the debt. Statements are still useful evidence in a dispute because they show what was billed, paid, and outstanding at a point in time.
Keep the two roles clean and most billing confusion disappears: invoice per transaction, statement per period, payment against invoice numbers. It sits alongside the wider distinction between billing and invoicing, and both feed the same goal, a receivables process your customers can follow without picking up the phone. The way those documents land is part of the customer experience too, which is why billing accuracy shapes trust well beyond the finance team.