Leave and balances

Leave and balances brings the relevant source records into one operating path. An employee requests a paid week away. The approver checks the date range against the relevant leave type and dated balance, then approves or rejects the submitted request. Admin checks that pending and taken amounts reflect the final outcome. The person link, effective date and current status give the next team a way to understand the decision without relying on a typed name or an email thread.

A preparer should check the record before handing it off. The reviewer needs the source dates and amounts in context, plus the authority to return a disputed item. When a correction is needed later, the team should retain the original record and explain the new effective value.

• Prepare. Employee starts with request dates and leave type; Admin checks the dated balance and checks the employee link.
• Review. The assigned reviewer checks the record and its dates before a downstream team relies on it.
• Follow through. An employee requests a paid week away. The approver checks the date range against the relevant leave type and dated balance, then approves or rejects the submitted request. Admin checks that pending and taken amounts reflect the final outcome.

Agree country and person-class rules, accrual rate, carryover cap, documentation requirement and the person who reviews a request. The payroll cutoff should use the approved outcome. Define which person owns initial entry, who makes the decision, and which point closes further routine edits. Review the same rule for a normal cycle and a late correction. If the relevant employee changes role or department, keep the source period understandable to the next reviewer.

Use a representative worker and one pay period to settle the convention. Enter a real date range, assign a responsible reviewer and inspect the resulting status. The team can then compare the source against the next record before broadening access to everyone.

An employee requests a paid week away. The approver checks the date range against the relevant leave type and dated balance, then approves or rejects the submitted request. Admin checks that pending and taken amounts reflect the final outcome. Ask the recipient to find the source record using the person and period, then explain what was accepted and what would be returned. Rehearse a rejected or corrected version as well. A decision is useful only when the preparer can see what to change and the next team can tell which value is final.

• My leave requests — The main worklist for request dates, leave type and dated balance, with the person and current state in view.
• Leave awaiting approval — Submitted requests with dates and the named reviewer.

Read hours and leave, payroll, the data model and roles to rehearse the complete path.