Leave transactions

Every change to a leave balance — grants and carry-overs when the leave year rolls over, accruals through the year, bookings on approval, reversals on revoke or withdrawal, expiries when carry-over deadlines pass — lands as a row in the leave-transactions ledger.

The ledger is append-only: existing rows are never edited or removed, but new ones can be added. Admins with the right permission see a ‘Create’ button — for posting a manual Adjustment, the tool for HR corrections and opening balances — and an ‘Import’ button, for loading balances owned by an external payroll system. Managers get a view-only ledger.

It’s the audit trail behind Leave policies and Leave requests — when a balance looks wrong, this is where you find out why.

On a new company, the ledger stays empty until the Owner has finished the company setup: no grants or accruals are written, and a manual Adjustment or an import is refused with ‘Leave can’t be booked until the company setup is complete. The Owner finishes it from the dashboard.’ See How to complete the company setup.

An external balance import processes rows in file order. If a person and leave type appear more than once, the preview includes the balance set by earlier rows when calculating later adjustments. Confirming recalculates against the current ledger.

Invalid or excessively large numbers are reported as row errors, and so is a person outside your management scope: ‘This person is outside your management scope.’ Fractional values in repeated rows are previewed at the ledger’s stored precision, and simultaneous imports do not double the balance.