SOA
A Statement of Account (SOA) is a periodic summary a supplier sends to a customer listing all open invoices, payments received, credits applied, aging buckets, and the current balance owed. It is the primary reconciliation document in B2B AR and a core tool for collections and month-end close.
A Statement of Account, often abbreviated SOA, is a document a supplier sends to a customer that summarizes the customer's account activity over a defined period. It lists open invoices, payments received, credits applied, the current balance, and usually an aging breakdown. In B2B, the statement is the document AR teams use to align their sub-ledger with the customer's accounts payable ledger.
The distinction from an invoice matters. An invoice is a legal demand for payment tied to a single transaction. A statement is a periodic summary of many transactions. An invoice asks the customer to pay one specific amount by one specific date. A statement answers a different question: what is the total state of our trading relationship right now, and what is still outstanding? Most large customers expect both, on different cycles, and treat them as separate inputs into their AP workflow.
A well-structured statement contains a predictable set of elements that allow the customer's AP team to reconcile quickly:
Statements show up in four main moments in the order-to-cash cycle. The first is the monthly send, where every active customer receives a statement on a set day so their AP team can reconcile. The second is the on-demand statement, generated when a customer requests proof of balance, often during their own audit or a payment run.
The third is dunning correspondence. Embedding a statement inside a reminder turns a generic chase email into a specific, reconciled view of what is owed. It removes the standard customer objection of send me a list of what's outstanding before I can pay. The fourth is period close. Statements support the AR team's own close by confirming customer balances, surfacing reconciliation gaps, and feeding the bad-debt provision review.
Statements exist because the customer needs them, not because the supplier wants to send them. The AP team uses the statement to perform a portfolio-level three-way match against their own ledger. They are checking three things: every invoice the supplier shows as open also exists in their system, every payment they sent has been correctly applied, and the closing balance agrees.
That reconciliation process is the single most reliable way to detect missing invoices, unapplied payments, and duplicate postings. It is also the document auditors ask for when validating year-end balances on both sides. A clear, timely statement protects the customer relationship by giving the AP contact something concrete to work from, instead of a flurry of single-invoice queries.
Statements look simple, but they are easy to get wrong in ways that cost time and goodwill:
An AI-native AR platform treats the Statement of Account as a live, personalized customer touchpoint rather than a batch print job. Agentic workflows generate statements at each customer's preferred cadence, aligned to their AP cycle. They include tailored notes such as flagged disputes, promised payment dates, and items pending credit approval.
Delivery is multi-channel by default: PDF for the inbox, a structured EDI 867 feed for retailers and large enterprises that consume it that way, and a live portal view that the customer can refresh anytime. Engagement signals such as open events, dispute clicks, and payment reactions feed back into the collections strategy, so the next statement, dunning email, or call is informed by what the customer actually did. The result is fewer reconciliation queries, faster cash application, and a statement that finally feels useful on both sides of the trading relationship.
A Statement of Account is a periodic document a supplier sends to a customer summarizing all account activity over a defined period, including open invoices, payments received, credits applied, an aging summary, and the current balance owed. It is the primary reconciliation document between a supplier's AR ledger and a customer's AP ledger.
An invoice is a legal demand for payment on a single transaction, with a specific amount and due date. A Statement of Account is a periodic summary of many transactions across a customer relationship, showing the overall balance and aging. Most B2B customers expect both, used for different purposes in their AP workflow.
Monthly is the standard cadence, but the right answer is whatever aligns with each customer's AP cycle. A customer that runs payments on the 25th gets little value from a statement dated the 1st. AI-native AR platforms set per-customer cadences so statements arrive when the AP team is actually preparing the next payment run.
A complete statement includes customer details, opening balance, a list of open invoices with original and remaining amounts, payments received, credits and adjustments, an aging summary bucketed by days past due, the closing balance, and clear payment instructions. Many modern statements also include a dispute log so customers can see the status of contested items.
Yes, and it is one of the most effective tools available. Embedding a statement inside a dunning email removes the common objection of send me a list first. The customer receives a reconciled view of what is owed, with payment instructions attached, in a single message. This turns a generic reminder into an actionable document.
An AI-native AR platform generates statements at customer-specific cadences, personalizes the content with dispute flags and payment promises, delivers through whichever channel the customer prefers (PDF, EDI 867, or live portal), and tracks engagement signals such as opens and dispute clicks. Those signals then inform the next collections touch, creating a closed loop between statement, customer behavior, and cash collected.
