Statements and aging

Know precisely what is overdue and how much, and hand a customer or vendor a collection-ready statement of account.

Due dates and aging

Due dates from payment terms

Every invoice’s due date is set at registration from the party’s payment terms:

Due date = invoice date + credit days

So an invoice dated 10 May 2026 for a customer with 30 credit days is due 9 June 2026.

Aging buckets

The aging view buckets each open balance, as of a date you choose, by how far past its due date it is:

• Current: not yet due
• 1-30 days past due
• 31-60 days past due
• 61-90 days past due
• 90+ days past due

A balance whose due date is still in the future sits in Current; one 45 days past due sits in 31-60. The buckets always add up exactly to the party’s total outstanding, so the aging reconciles.

Both customer (AR) and vendor (AP) aging are supported.

📷 Image placeholder

Add a screenshot here: the aging view with the as-of date selector and the Current / 1-30 / 31-60 / 61-90 / 90+ buckets, with the total matching the party’s outstanding.

Statement of account

A statement of account (SOA) gives a party a full, dated record of their transactions and running balance.

1. Open Finance → Statements.
2. Choose a customer or vendor and an as-of date.
3. Generate the statement. It shows:
   • Opening balance
   • Dated transactions: invoices, payments, credit/debit notes and advances/adjustments
   • A running balance
   • An aging summary at the foot
4. Export it as PDF or as XLS (Excel).
5. Email it directly to the party’s billing contact.

📷 Image placeholder

Add a short recording here: choosing a customer and an as-of date, generating the statement, then exporting it as PDF and emailing it to the party’s contact.

The statement includes only that party’s transactions within your organisation, and its closing running balance reconciles to the party’s outstanding shown in the aging summary for the same date.