Revenue and reconciliation
What Is a Statement of Accounts? SOA Guide
Direct answer
A Statement of Accounts, or SOA, is a periodic transaction summary exchanged between counterparties or produced for an account. In an order-to-cash workflow it normally shows opening balance, invoices, debit and credit notes, receipts, allocations and closing balance. It is a reconciliation aid rather than proof that every underlying transaction is correct, accepted, tax-compliant or paid.
Acronym: SOA. Also known as: account statement, customer ledger statement, supplier statement.
Key takeaways
- A business SOA summarizes ledger movements; it does not replace invoices, notes, contracts, delivery evidence or bank records.
- The statement period, cut-off, legal entity, currency, opening balance and document-level allocations must be explicit.
- Supplier and customer balances can differ because of missing documents, timing, unapplied receipts, disputes or different cut-offs.
- Reconcile each side independently before building a bridge; net difference alone can conceal offsetting errors.
- The B2B SOA workflow here is operational practice, distinct from RBI-regulated bank or card statements.
What a Statement of Accounts shows
Operational-practice note: there is no single universal statutory format for the supplier-to-customer SOA described here. It is usually a ledger extract or agreed commercial statement used to confirm balances. RBI separately regulates statements in specific banking and card contexts. For example, its Credit Card and Debit Card Directions define total amount due by reference to a credit-card statement and prescribe billing conduct. Those rules do not define a trade supplier’s B2B SOA.
A useful trade SOA identifies issuer and recipient legal entities, account number, currency, period, opening balance and each document movement. Lines commonly include invoice, supplier debit note, supplier credit note, receipt, refund, withholding allocation, adjustment and closing balance. Document number, date, due date, original reference, amount and open amount allow the recipient to reproduce the balance.
The statement is secondary evidence. An invoice line may exist but be disputed; a receipt may appear in the bank but remain unapplied; a credit note may be valid commercially but have a separate GST treatment. “Agreed SOA” means the balance comparison was completed under a stated cut-off, not that every legal, tax or accounting question vanished.
How to prepare a reliable SOA
- Freeze the legal entity, counterparty account, currency, period end and transaction cut-off.
- Bring forward the prior agreed closing balance and list any later corrections separately.
- Extract invoices and supplier debit notes with document date, due date and original reference.
- Extract credit notes, receipts, refunds, withholding amounts and approved adjustments.
- Allocate receipts and notes to documents; expose unidentified or unapplied cash rather than netting it silently.
- Calculate each document’s open amount and the statement closing balance.
- Reconcile the SOA total to the receivables subledger and control account.
- Send it through an approved channel, track customer confirmation and retain each version.
Use a stable sign convention. From the supplier view, invoices and debit notes increase the receivable while credit notes and receipts reduce it. A customer payable statement may display the same economics with opposite debit and credit labels. Include plain-language transaction types so sign orientation is not guessed.
Quarterly SOA reconciliation example
Fictional B2B quarter: A packaging supplier opens the quarter with ₹1,20,000 due from a consumer brand, issues ₹4,80,000 of invoices, issues ₹30,000 of supported credit notes, and allocates ₹4,00,000 of receipts. Its closing balance is ₹1,70,000. The customer’s payable ledger closes at ₹1,60,000 because it recorded a further ₹10,000 payment on the final day; the supplier received the bank credit but had not allocated it at cut-off.
| Bridge component | Amount | Position |
|---|---|---|
| Supplier opening balance | ₹1,20,000 | Agreed prior close |
| Quarter invoices | ₹4,80,000 | Increase receivable |
| Quarter credit notes | ₹30,000 | Reduce receivable |
| Receipts already allocated | ₹4,00,000 | Reduce receivable |
| Supplier closing balance | ₹1,70,000 | SOA before final receipt allocation |
| Final-day unapplied receipt | ₹10,000 | In supplier bank, not yet allocated |
| Customer closing payable | ₹1,60,000 | Customer has recorded payment |
The supplier balance is exact: ₹1,20,000 + ₹4,80,000 − ₹30,000 − ₹4,00,000 = ₹1,70,000. The bridge is also exact: ₹1,70,000 − ₹10,000 = ₹1,60,000. The supplier verifies the bank reference and customer remittance, allocates ₹10,000, and produces a revised SOA at ₹1,60,000. It does not create a credit note, because the difference is cash allocation rather than a price, return or supply adjustment.
Common SOA differences
| Difference | Investigation | Resolution evidence |
|---|---|---|
| Invoice on supplier side only | Check delivery, acceptance, transmission, legal entity and customer posting. | Customer booking, corrected invoice or documented dispute. |
| Credit note on one side only | Check issue date, original invoice, customer allocation and transmission. | Accepted allocation and applicable GST reporting trail. |
| Receipt on customer side only | Trace bank value date, account, payer, reference and remittance. | Supplier bank match and allocation. |
| Different open amount | Compare partial allocations, withholding, deductions and prior credits. | Document-level allocation bridge. |
| Same document, different period | Compare cut-off, time zone, posting date and reversal history. | Agreed timing item with later clearing. |
RBI’s RTGS FAQ describes transaction references and bank-credit confirmation in that payment rail. Such bank evidence can help prove cash movement, but it does not decide which trade invoice the customer intended to pay; remittance and allocation evidence are still needed.
SOA control checklist
- State issuer, recipient, account, currency, period and cut-off.
- Tie opening balance to the prior agreed or explained close.
- Include document number, date, due date, type, original reference and open amount.
- Use a documented sign convention and supplier or customer perspective.
- Reconcile the statement to the receivables subledger and general-ledger control account.
- Keep unidentified and unapplied receipts visible with bank references.
- Show disputed deductions separately from accepted credit notes.
- Version every statement and preserve customer comments and confirmation.
- Reissue after material corrections instead of editing the sent copy.
- Age from approved due dates and retain promised-payment dates separately.
Protect statements as confidential financial records and use approved delivery channels and access controls.
How SOA reconciliation supports DSO
An accurate SOA improves the receivables balance and collection facts used in Days Sales Outstanding analysis. It identifies invoices that are genuinely open, credits awaiting allocation, cash awaiting allocation and disputes. However, agreeing a statement does not make an overdue amount current, and clearing an unapplied receipt changes receivables without changing historical sales.
Complete statement reconciliation before interpreting a DSO movement. A lower DSO caused by bulk write-offs, unposted invoices or credits against the wrong customer is not a collection improvement.
Frequently asked questions
Is a Statement of Accounts the same as an invoice?
No. An invoice documents a specific billing event. An SOA summarizes multiple documents, payments and open balances for a period.
Does a customer-confirmed SOA prove every transaction?
No. It supports balance confirmation under a cut-off, but contracts, delivery, tax, accounting and disputed-item evidence remain necessary.
How often should an SOA be sent?
Choose a cadence that supports collection risk and volume, such as monthly for active accounts and more frequent review for material overdue balances.
What is an unapplied receipt?
It is cash received but not yet allocated to a customer or document. Keep it visible and trace payer, bank reference and remittance before allocation.
Why can supplier and customer balances differ?
Common causes include cut-off, missing invoices or notes, unapplied cash, partial allocations, deductions, wrong legal entity and duplicate postings.
Is a trade SOA regulated by RBI?
The workflow here is operational B2B practice. RBI separately regulates statements in specified bank, payment and card contexts.
Sources and further reading
- Reserve Bank of India: Credit Card and Debit Card – Issuance and Conduct Directions, 2022Verified Jul 25, 2026
- Reserve Bank of India: Real Time Gross Settlement System FAQsVerified Jul 25, 2026
Educational disclaimer: This material is general information, not legal, tax, or accounting advice. Check current official guidance and your facts with a qualified professional.
From definition to workflow
Apply this concept with connected finance operations
Finnoto connects source records, approvals, reconciliation evidence, and exception ownership so teams can move from knowing the rule to operating the control.
Explore settlement reconciliation