The absence star, balances daily

Two facts and five dimensions. The balance fact stores what the tenant only computes: every worker, every plan, every day. The event fact keeps each accrual, use, and adjustment. Liability is one join between them and the rate.

RuleStore the computed balance daily. A balance you can only recompute is a balance you can only argue about.

Neverprice liability off a rate from a different date than the balance. Raises reprice every accrued hour; the join must be date-consistent.

Two facts, five dimensions. Liability is the balance fact joined to the rate dimension, both as of the same date.

◆ The tablestwo facts, five dimensions, one join that prices everything.

Table	Grain	Feeds
fct_balance_day	One worker, one plan, one day: the computed balance, stored.	Liability, balances as of any date.
fct_absence_event	One accrual, use, adjustment, or leave interval event.	Movement analysis, workers on leave.
dim_worker	Who. Shared with the Core HR star.	Every report's population.
dim_absence_plan	The plan and its rules: accrual rate, caps, carryover, front-loading.	Per-plan reporting and the proration logic.
dim_org	The department rollup, same as payroll's.	Liability by department that ties to cost.
dim_comp_rate	Pay rate per worker, effective-dated.	The pricing half of liability.
dim_date	The calendar, shared with every module star.	As-of filters and trends.

◆ Why the balance fact existsthe tenant computes; the model remembers.

Delivered balances are recomputed on request under current plan rules, which is why two screens can disagree and why last March is unanswerable. The pipeline asks the tenant for every balance once a day, on the extraction pattern, and stores the answer. Recomputation risk becomes a stored row; plan-rule changes stop rewriting history.

The event fact explains movement between any two days: accrued, used, adjusted, forfeited, repriced. Liability movement is the bridge auditors ask for, and it is a grouping of this fact.

Use case

Problem

Balances exist only as recomputations, so history, movement, and dated liability have nothing to stand on.

What we build

A daily balance fact and an event fact in your warehouse, joined to an effective-dated rate dimension.

What you get

Stored balances, explained movement, and liability priced from a consistent date, all one model.

Does your balance history exist anywhere but a recomputation?

We ship the balance snapshot, the event fact, and the reports on them.

Talk to us

Terms on this page

HR: Human resources. The Core HR star shares its dimensions with this one.
fact: A table of measured rows. Here, balance days and absence events.
dimension: A table describing what facts point at: workers, plans, rates, dates.
grain: What one row means. One worker, one plan, one day.
effective-dated: Carrying each value with the dates it was true for.
movement: The events explaining a balance change between two dates.
recomputation: Deriving a value again on request. What delivered balances are.