Before sending a customer statement, reconcile what it says is due

A customer statement should give the recipient a clear account of transactions and the amount outstanding at a stated date. Before sending it, confirm the customer legal entity, account number, billing contact, currency, and cutoff. A statement for the wrong group company can create confusion even when every listed invoice is genuine.

Decide whether the statement shows open items only or a full transaction history for the period. Both formats can be useful, but they answer different questions. An open-item statement may omit invoices already paid, while a balance-forward statement needs an opening amount and all movements that explain the closing balance.

Keep the statement's extraction time and source report. Receipts posted after extraction can make a correct statement look outdated by the time it is sent. For material accounts or active disputes, check recent activity immediately before distribution and make the date basis clear to the recipient.

For a balance-forward statement, start with the opening balance, add invoices and other approved debits, subtract credits and applied receipts, and compare the result with the closing balance. For an open-item statement, sum the remaining amounts on included items and reconcile them to the ledger population represented.

In a hypothetical month, the account opens at $18,000, receives $24,000 of new invoices, has $2,000 of approved credits, and records $25,000 of applied receipts. The closing balance is $15,000. If the statement shows $17,000, investigate whether the credit was omitted, posted to another account, or excluded by a report filter.

Explain legitimate differences between the statement and a broader ledger total. The ledger may include another currency, a separate customer location, or an unallocated receipt. Do not force agreement by hiding an item. Correct the population or show the relevant reconciliation so finance understands exactly what the customer will see.

Review receipts that identify the customer but have not been matched to invoices. A payment can be in the bank and recorded in the ledger while the statement still lists the related invoice as fully unpaid. Sending an aggressive collection message in that situation creates avoidable work and damages confidence in the account records.

Use the customer's remittance and payment references to apply cash through the approved process. If the allocation remains uncertain, show the receipt clearly and ask a specific question. Do not choose an invoice solely because its amount is close, particularly when the customer has several similar recurring charges.

Suppose the illustrative $15,000 statement balance excludes a separate, verified $4,000 customer receipt awaiting invoice allocation. The collections review then shows $15,000 of statement balances, $4,000 of unapplied cash, and $11,000 of net customer exposure before other adjustments. Confirm that the receipt has not already reduced the statement before making this subtraction. Preserve the unresolved invoice application without presenting an individual invoice as settled.

Confirm that approved credit notes are included and linked to the affected invoices where possible. A requested credit that has not been approved should remain a pending commercial issue, not an automatic reduction of the account. Keep the status understandable so the customer is not asked to infer whether a claim has been accepted.

Review due dates against the actual payment terms and invoice acceptance requirements. An invoice date is not always the same as the date from which agreed terms run. Where the customer disputes the due date, retain the relevant contract or acceptance evidence and route the question to the responsible commercial owner.

Separate a disputed amount from the rest of the balance. The statement can preserve the full accounting record while the accompanying collection process identifies which items are under review. Avoid deleting disputed invoices to make the statement appear less confrontational, and avoid describing them as undisputed merely because the system lacks a dispute field.

Include invoice and credit references, dates, original amounts where useful, remaining balances, currency, and a clear total. Use descriptions that help the customer locate its own records. A statement composed entirely of internal transaction identifiers may reconcile perfectly and still be difficult for the customer to act on.

Keep payment instructions consistent with the business's approved channels. A statement should not introduce an unverified new bank destination or rely on a manually edited account number. Follow the existing controls for communicating payment-detail changes, especially when a statement is sent during an active collection discussion.

Check the recipient list and attachments before distribution. Group customers can have different contacts for subsidiaries or locations, and financial documents may contain information that should not be shared across them. Send the statement through the authorized process and retain evidence of what was sent and when.

When the customer replies with a remittance, missing credit, or invoice dispute, link the response to the statement and affected transactions. A statement is a snapshot; the ledger should be updated only through supported posting or correction procedures. Do not maintain a separate emailed balance that drifts away from the system.

Track corrections identified by statement review. Repeated omitted credits may indicate an account-mapping problem, while recurring unapplied receipts may call for better remittance collection. Use those patterns to repair the process instead of repeatedly apologizing for an inaccurate balance.

IRS guidance lists invoices, deposit evidence, and other supporting documents as business records. Retain those sources behind the statement and the resolution of any differences. The review is complete when the displayed balance reconciles, recent receipts are understood, disputed items have a clear status, and the recipient can identify what action is being requested.