1Purpose #
- One card per leave policy, figures over the employee's ACTIVE leave year — the hire-date anniversary year, clamped to the policy assignment's effective date. Available = Opening + Carry-over + Accrued − Utilized − Lapsed ± Adjustments.
- The postings table underneath is the drill-down: every ledger row, all years, newest first — the movement, the signed value, the description and its source (engine, manual, carry-over, lapse).
- The card also names the employee's CURRENT entitlement band — what a period earns at their present length of service, and the caps that apply.
- The balance panel is a reusable component: the leave-request screens embed the same panel, so the figure an approver sees is computed by exactly the same arithmetic.
2Where the figures come from #
- Opening — OPENING rows entered on the Manual Leave Posting page (go-live balances, transfers).
- Carry-over — the CARRYOVER row the accrual page's year close posts at the year's first day, capped by the policy band.
- Accrued — the ACCRUAL rows the accrual processing run posts per completed period.
- Utilized — UTILIZATION rows written by the leave-request workflow when leave is approved (each stamped with its request).
- Lapsed — LAPSE rows the year close writes off above the carry-over cap (setting 172).
- Adjustments — signed ADJUSTMENT rows from the Manual Leave Posting page.
3Reading the page, step by step #
- Pick the employee — the cards and the drill-down load together.
- Check the leave-year dates on each card: figures cover THAT window. History outside it lives in the drill-down below.
- A surprising figure? Find its rows in the drill-down — every movement carries a description saying why it exists.
- After posting accruals or manual rows elsewhere, press Refresh (F2) here to recompute.
4Shortcut keys #
- F2 Refresh the balance.
- Enter moves to the next field.
- Keys belong to the focused copy of the page; a dialog's own keys win while it is open.
5Why is a pick-list empty? #
- No policy cards means the employee has neither a leave-policy ASSIGNMENT (Employee master or Batch Assignment — policies themselves are created on the PAY-06 Leave Policy page) nor any posting yet.
- Everything zero usually means the accrual run has not been executed yet — run Leave Accrual Processing.
6Rules and integrity #
- Read-only. This page writes nothing — corrections go through Manual Leave Posting, accruals through Leave Accrual Processing.
- Computed, always. There is no stored balance to drift; two screens showing the same employee at the same moment show the same figure.
- Direction words decide. The arithmetic reads each row's direction (Opening/Earned add, Deducted subtracts), so even rows migrated from the legacy ledger's vocabulary sum correctly; legacy 'Projected' rows are ignored.
- History survives. A policy un-assigned later keeps its card as long as postings exist — the ledger is never rewritten.
7If something does not work #
An employee shows no balance at all
- Why
- A balance exists only where a leave policy is assigned to that employee.
- What to do
- Assign the policy (Employee master or Batch Assignment), then accrue.
The balance looks too low after a leave was cancelled
- Why
- Cancelling an approved leave reverses its utilization - if the cancellation failed, the utilization stands.
- What to do
- Check the request's own status; a reversal says so in its message.
"No leave policy assignments match the scope - assign policies to employees first (Employee master or Batch Assignment)."
- Why
- Nothing in the chosen scope has a policy, so there is nothing to show or accrue.
- What to do
- Assign policies first.
This is the help InvoiceNET® ERP shows beside the Leave Balance screen. Whether you have the screen depends on the modules of your licence and the rights your administrator has given you.
See this screen for yourself
The demo is the real product, with a company of your own.