Advanced Ledger Features

Four optional features reshape how the ledger is recorded — not what the business owes or owns, but where the ledger writes it down. They share one idea worth understanding once: the control account.

Why control accounts#

A ledger can record "customer X owes 5,000" two ways: give X their own account head, or post to one Customer Receivable control account with X recorded on the line. The first is fine for twenty customers and catastrophic for four thousand — the chart of accounts becomes a phone book, and the trial balance takes minutes to say nothing. The control-account pattern keeps the chart the size the accountant designed while a sub-ledger — the per-party breakdown that always sums to the control balance — carries the detail. That sum-equals-control identity is checkable at any time, and it's the pattern's whole guarantee.

The four features#

• Contact Sub-Ledger — the control-account pattern for customers and suppliers.
• Staff Sub-Ledger — the same pattern for cashier custody balances (one mechanism with tender clearing, enabled together).
• Tender Clearing — clearing accounts for card money in transit, making bank reconciliation match (one mechanism with the staff sub-ledger, enabled together).
• Branch Dimension — per-line branch attribution with automatic inter-branch balancing.

Enabling any of them#

All four are enabled by support per business, because they come with a data migration (folding existing per-party heads onto control accounts, mapping clearing heads) that keeps history intact. The ritual is always the same: accountant aware, period boundary, first week's reports compared against expectations. Each page states its specifics.