Accounting Settings

These settings shape what your ledger records. None of them should be changed casually, and the big ones should be decided with your accountant before the first month of trading.

Costing method#

FIFO, LIFO or weighted average — governs how consumption, wastage and stock values are calculated everywhere. Decide once, before real purchases; changing it later is an accounting event that support should be involved in.

Voucher approval chains#

Up to four approval levels for manual vouchers, each satisfied by a role or named users. While a chain is active, no manual voucher touches the books until it clears the chain, and every approve/reject is journaled. System-generated vouchers (daily sales, consumption, settlements) never queue. See Accounting for the full picture.

Audit reporting#

The audit email address receives exception reports: day-close consumption failures, manager overrides, and similar events that someone senior should read the next morning. Treat it as required configuration, not optional — it's the difference between an exception being a report and being a surprise.

Account mappings#

The advanced ledger features rely on mapped accounts: bank clearing accounts for tender clearing, the staff clearing head for the staff sub-ledger, control accounts for the contact sub-ledger. These mappings are configured with support when the feature is enabled — the settings exist here so you know where they live, not so you change them alone.

Post-dated cheques#

If PDC handling is enabled, one policy choice matters: does a received cheque reduce the customer's due at receipt (control-account method, the default) or only at clearing (memo method — no ledger effect until the bank clears it)? Your accountant will have an opinion; the setting follows it.

The theme of this page: every switch here changes what the books say. The features are reversible; the ledger entries they write are not. Period boundaries and accountant sign-off are the habit.