Absence numbers finance can sign

Balances disagree between screens, liability is only right at the moment payroll last ran, and nobody can say who was on leave last March. This module rebuilds absence on a daily balance snapshot you own.

RuleSnapshot every balance daily and price liability from the balance and the rate as of the same date. Both halves are dated or the number is fiction.

Neversign a liability computed from live balances and current rates alone. It was correct at the last payroll run and drifts every day after.

◆ The pagesone model, eight pages, arithmetic checked.

Page	What it answers
The absence star	The model: a daily balance fact, an event fact, and the rate dimension that makes liability honest.
Time off liability	The auditable number: hours times rate, both as of the date, movement explained, crossfooted.
Balances as of any date	The balance history the tenant does not keep, and why screens disagree today.
Workers on leave	Who is out, since when, expected back, and the overdue list, as of any date.
Intermittent leave	Protected leave taken in pieces against a rolling entitlement, with exhaustion flagged, the compliance case delivered tracking handles worst.
Balance roll-forward	Opening plus accrued minus taken equals closing, to the hour, tying the liability report to its movement.
Carryover expiry	The 2,400 hours above the cap, worth 126,715.00, priced in July instead of apologized for in December.
Absence rate	Unplanned days over scheduled worker-days, with vacation kept out of the rate on purpose.

◆ The one mechanismbalances are computed, not kept.

Workday computes a balance when asked: accruals to date, minus usage, plus adjustments, under the plan's rules. Practitioners meet the consequences constantly: front-loaded grants with no delivered proration when someone leaves mid-year, termination-month accruals that surprise both sides, and balances imported from prior systems that never quite agree with the plan math.

The owned model stores the computed balance once per worker per plan per day. History stops being a recomputation, liability gets a dated basis, and every disagreement between screens becomes a diff between two stored days. The same snapshot discipline as headcount, applied to hours.

◆ Where the numbers tiethe arithmetic the battery checks.

Check	Where
Liability rows multiply exactly: hours times rate equals dollars, rows sum to totals	Time off liability, crossfooted by the battery.
Departments are the payroll module's: Sales, Technology Delivery, Support	The same three the labor cost report prices, same population of 351.
On-leave counts reconcile to the headcount snapshot's active flags	Workers on leave against headcount history.

Sample values are illustrative, never client data.

Use case

Problem

Absence balances disagree between screens, liability drifts between payroll runs, and leave history cannot be reconstructed.

What we build

A daily balance snapshot and event fact in your warehouse, with the rate dimension that dates both halves of liability.

What you get

Balances that derive instead of disagree, liability finance can sign, and leave answered as of any date.

Could finance sign your time off liability today?

We ship the balance snapshot and the liability report that crossfoots, in 10 days.

Talk to us

Terms on this page

battery: The automated set of checks, including the crossfoot arithmetic, run on every build of this catalog.
balance: Hours a worker holds in one plan on one date. Computed by the tenant, stored by the model.
accrual: Hours granted by plan rules over time.
front-loaded grant: A full year of hours granted on day one. Proration on exit is the trap.
liability: The money the balances represent: hours times pay rate, both as of a date.
repricing: A raise changing the value of every accrued hour at once.
plan: The ruleset a balance lives under: accrual rate, caps, carryover.
snapshot: A dated copy of a state, kept so the past stays queryable.