Statement generated per customer
Open invoices, receipts, credit notes and running balance per customer. Date range configurable. Multi-currency where the customer has foreign-currency exposure.
Accounts Receivable | Customer Statement of Account
Per-customer statement of account showing all open invoices, receipts, credit notes and the running balance. Bulk send via email or WhatsApp on a schedule. FY-end balance confirmation packages export hash-verified for the auditor's SA 505 procedure.
How it works
Open invoices, receipts, credit notes and running balance per customer. Date range configurable. Multi-currency where the customer has foreign-currency exposure.
Schedule the statement send (monthly, quarterly). Email or WhatsApp delivery on customer preference. Templated message with statement attached.
At FY-end, the system generates a confirmation request to every customer (Form B per SA 505). Customer signs and returns; signed confirmations hash-verify and package for the auditor.
What the system does
| Capability | Input | Output |
|---|---|---|
| Statement generation | Customer + date range | PDF statement with running balance |
| Bulk send | Customer set + delivery preference | Email or WhatsApp delivery with receipts |
| Schedule | Frequency + start date | Auto-trigger on the schedule |
| FY-end confirmation | All customers + cutoff date | Confirmation requests + signed responses package |
Statement generation
Bulk send
Schedule
FY-end confirmation
Compliance + integrations
SA 505 (External Confirmations) is the auditor's standard for confirming receivable balances. The FY-end confirmation package fits the procedure; signed responses hash-verify for trust.
Regulations we work within
SA 505 (External Confirmations)
FY-end confirmation procedure aligned.
Schedule III
Trade receivable disclosure reconciled to statements.
Connects to
Customer Statement of Account FAQ
Yes. Statement format is configurable. Show all transactions (paid + open) or only open. Running balance always reflects the net position. Customer-specific format preferences are stored at the customer record.
A Form B confirmation request goes to every customer at FY-end. The customer signs and returns (digitally via portal, or physically via post). Signed confirmations are stored, hash-verified, and packaged for the auditor's SA 505 procedure.
Yes. WhatsApp Business templated messages with the PDF attached. Delivery and read receipts captured per customer. Replies route to the AR inbox.
More in Accounts Receivable
Quotes, SOs, invoices, receipts, credit limits, contacts and documents on one customer record.
See Customer 360Automated reminders across email, WhatsApp, call queues. Customer-history-aware tone.
See Payment Follow-upsAging buckets sliced by branch, region, sales rep, business unit.
See Branch / Region AgingConnect one entity. Configure the schedule and the delivery channel. The statements go out on day 1; the receipts confirm; the FY-end confirmation pack starts building itself.