Accounting software where every figure has a route back

Accounting software must preserve why a balance changed. Posted journals are immutable business events, while correction uses reversal and replacement entries with linked reasons. Database constraints and transaction boundaries protect balance even when an interface or integration fails midway.

Subledgers add operational detail but must reconcile to their control accounts. Currency amounts require explicit transaction, functional and reporting values with defined rate sources and rounding. Seemingly minor choices here determine whether reports can later be explained.

Approval is more than a status dropdown. Thresholds, delegation, conflicts of interest and evidence retention shape who may prepare, approve and post a transaction. Emergency override routes should be narrow, recorded and reviewable.

Permissions are enforced in services, not only by hiding buttons. Period locks and close procedures prevent late change while allowing authorised adjustments through visible routes. Audit logs record meaningful business actions and before-and-after context without storing secrets or unnecessary personal data.

A payment provider, bank feed or sales platform may resend, reorder or correct events. Stable external identifiers and idempotent processing prevent duplicate journals. Import batches carry counts and amounts so finance teams can prove completeness, not merely connectivity.

Matching automation should expose its reasoning and confidence. Ambiguous items belong in a queue with supporting candidates, while deterministic matches remain reversible. This balance speeds ordinary work without concealing differences that require judgement.

Demonstrations should include credit notes, partial settlement, foreign exchange, period boundaries and failed imports, not only a straightforward invoice. Reports are checked from source document through journal to statement, and access tests verify that restricted roles cannot bypass workflow.

Accounting policy and statutory obligations vary. Software can implement agreed rules and evidence, but qualified finance and legal advisers must confirm the organisation’s treatment. We keep configurable policy separate from hard ledger invariants wherever practical.