HCM Studio
Sign in

Absence Management

Qualification plans: paying an absence with no balance

The plan type that pays workers who qualify for it during an absence without accruing a balance — the four rule areas (term, eligibility, enrollment/termination, payments), the four term types and when each applies, the overlap rules that decide how straddling absences count on rolling-backward terms, the entitlement band matrix that maps worker criteria to duration and payment percentage, and open-ended absences calculated for 365 days.

advanced18 min readFor HCM Functional Consultant, Absence Management Specialist, Payroll Integration Specialist, Learner new to Oracle HCMRelease FA Latest

Learning objectives

  1. 1.Contrast a qualification plan with an accrual plan: no balance is maintained; the plan decides entitlement and payment directly
  2. 2.Name the four qualification plan term types and say which one a rolling-backward assessment period is
  3. 3.Apply the Include, Exclude and Split overlap rules to an absence that straddles a rolling-backward term
  4. 4.Build the entitlement band matrix from derived factors or person attributes, with Qualification Details rows of duration and payment percentage
  5. 5.Decide enrollment/termination behaviour — whether payments continue on termination versus loss of eligibility — and read the entitlement result on the Manage Absences and Entitlements page, including the open-ended 365-day rule

Why this matters

An accrual plan says *how much* leave a worker has banked; a qualification plan says *whether the worker is paid during this absence, and at what percentage, for how long*. Maternity, statutory sickness and similar leaves are not a balance you spend down — they are an entitlement evaluated per absence. Configuring one as an accrual plan produces a balance that never moves and payments that never fire.

If you skip this: A maternity absence wired to an accrual plan accrues a balance nobody consumes and pays nothing during the leave — the worker is entitled in name only, and the misconfiguration surfaces at the first payroll that should have paid the absence.

What it is, why it exists, what breaks

What it is

A qualification plan configures four rule areas. Plan term: an assessment period for which the Evaluate Absence process calculates entitlements for the total absent time recorded in it — one of four term types: Calendar year (starts on the selected month/day/year, one-year duration), Rolling backward (entitlements based on absence duration in a period preceding the absence start date; needs an overlap rule), Rolling forward (starts on the first absence start date, ends at start + duration), Absence duration (the absence itself is the term). Plan eligibility: an eligibility profile determines the eligible set. Enrollment and termination: workers enroll when an absence using an associated absence type is scheduled (or via formula), and the plan decides separately whether payments continue on termination versus loss of plan eligibility. Payments: an entitlement band matrix sets payment percentages for specific periods during the absence; the payment rate of a single unit can come from a rate definition or a formula. No balance is maintained.

Why it exists

The term defines *when* entitlement is assessed; the eligibility profile defines *who*; enrollment/termination defines *what happens at the edges of employment*; and the band matrix defines *how much and for how long* — the four answers a qualification plan exists to give.

What breaks without it

Three silent breaks: treating the plan as an accrual plan (no balance is ever maintained, so balance-based rules do nothing); choosing a rolling-backward term without an overlap rule (absences straddling the term boundary are assessed inconsistently); and building bands on derived factors that were never created in Manage Derived Factors (the band matches nobody, silently).

Source: ABS-QUAL-001, ABS-QUAL-002, ABS-QUAL-004, ABS-QUAL-005

A qualification plan as an evaluation, not an accrual

The term picks the assessment window, the profile picks the worker, the band matrix converts absence duration into payment rows — and no balance is ever written. Listed in order: Plan term picks the assessment window, then Overlap rule decides straddling absences, then Eligibility profile picks the worker, then Band matrix converts duration into payment rows, then Enrollment/termination and the entitlement result.

A qualification plan read as an evaluation pipeline. Unlike an accrual plan, no balance is maintained — the plan decides entitlement and payment directly. Four rule areas configure it. Plan term: the assessment period for which Evaluate Absence calculates entitlements for the total absent time — Calendar year (selected start, one year), Rolling backward (period preceding the absence start date; requires an overlap rule: Include counts the whole overlapping absence, Exclude ignores it, Split counts only the part inside the current term — the worked scenario gives 5 vs 20 vs 15 full-pay days), Rolling forward (from the first absence start date for the term duration), or Absence duration (the absence itself). Plan eligibility: an eligibility profile determines the eligible set. Enrollment and termination: enrollment when an associated absence type is scheduled (or per formula), and separate decisions on whether payments continue on termination versus loss of eligibility. Payments: the entitlement band matrix builds rows with the expression builder over derived factors (length of service) or person attributes (grade), each with Qualification Details rows of duration and payment percentage; the unit rate comes from a rate definition or formula via the Absence Payment Rate Rule. Open-ended absences are calculated for 365 days regardless of the estimated end date, with a Pending Evaluation record for a 90-day extension. The entitlement result reads on the Manage Absences and Entitlements page as plan period, qualified entitlement, and remaining.

Configured as an accrual plan, the leave accrues a balance nobody spends and pays nothing during the absence.

What to take from this: Read the diagram as an evaluation, not an accrual: the term picks the assessment window, the eligibility profile picks the worker, the band matrix converts the absence duration into payment rows, the overlap rule decides how a straddling absence counts, and enrollment/termination rules decide whether payments survive the end of employment — no balance is ever written.

Source: ABS-QUAL-002, ABS-QUAL-003, ABS-QUAL-006, ABS-QUAL-004

The absence that straddles the term

A qualification plan has a six-month rolling-backward term with bands of 20 days at full pay then 15 days at half pay. The worker was already paid 15 working days of absence from Dec 20 2013 to Jan 7 2014, and now records a new absence from Jul 1 2014 that partially overlaps the current term.

  1. 1.With the Include overlap rule, the whole overlapping absence counts in the current period: 20 minus 15 already used leaves 5 days at full pay, then 15 at half pay.
  2. 2.With the Exclude rule, the overlap is ignored: the full 20 days are available at full pay, then 15 at half.
  3. 3.With the Split rule, only the part of the absence inside the current term counts: 15 days at full pay, then 15 at half.
  4. 4.The same absence, the same bands — three materially different payments, decided entirely by the overlap rule chosen on the term.

Takeaway: On a rolling-backward term the overlap rule is a money decision, not a technicality: Include (5 full-pay days left), Exclude (20) and Split (15) produce three different outcomes for the identical absence. Set it deliberately, and expect the term boundary to be where the disputes are.

Source: ABS-QUAL-003

Configuration model

Navigation paths

  • Absences work area > Tasks panel > Manage Absence Plans > Create > Plan Type QualificationABS-QUAL-012
  • Absence Plan setup page > Participation tab — eligibility profile, enroll-when rules, continue-payments-on-termination, Evaluate remaining entitlement without absence recordABS-QUAL-004
  • Absence Plan setup page > Entitlements tab — Entitlement Attributes Matrix, Qualification Band Matrix rows via the expression builder, Qualification Details rows (duration, payment percentage)ABS-QUAL-006
  • Absence Plan setup page > Entries and Balances tab — Absence Payment Rate Rule, element, Transfer absence payment informationABS-QUAL-010
  • Manage Absences and Entitlements page > Qualification Entitlements section — plan period, qualified entitlement, remainingABS-QUAL-008

Objects

Qualification plan header

Legislation, plan, legislative data group, status, Plan UOM, Type (the term type, e.g. Rolling backward), Term Duration and UOM, Start Rule (e.g. Absence Start Date), Overlap Rule (Include, Exclude, Split — required for rolling backward).

Risk if wrong: A rolling-backward term without an overlap rule leaves straddling absences to an undefined interpretation; a term duration in the wrong UOM scales the whole assessment period.

Participation tab

The eligibility profile that determines the eligible set; enroll workers when an absence using an associated absence type is scheduled (or a formula for other rules); whether ongoing payments continue if the worker is terminated or loses plan eligibility; Evaluate remaining entitlement without absence record, which controls whether full entitlement details display without an absence record.

Risk if wrong: Continuing payments on termination when legislation does not require it pays leavers; stopping on loss of eligibility when it should continue breaks statutory leaves.

Qualification Band Matrix

Expression-builder rows over derived factors (e.g. [LengthOfService.GreaterThan5_LessThan10]) or person attributes (e.g. [Person.Grade] >= "A1"), each with Qualification Details rows of duration and payment percentage — e.g. 5–10 years of service: 75% up to 10 days; grade A1+: 100% up to 10 days then 75% for the next 15.

Risk if wrong: A plan with multiple expression builders where all are satisfied is explicitly warned against — create multiple plans instead; and the length-of-service derived factors must exist first (Manage Derived Factors), or the band silently matches nobody.

Entries and Balances tab

The Absence Payment Rate Rule selecting a rate definition (or formula) for one unit of absence, the nonrecurring element carrying Qualification Absences to payroll (primary classification Absences), and Transfer absence payment information.

Risk if wrong: Without a payment rate rule and a transfer selection, the entitlement exists but nothing reaches payroll — the absence is qualified and unpaid.

Constraints

  • A qualification plan maintains no balance — it decides entitlement and payment directly; do not configure balance rules (accrual, ceiling, carryover) on it as if it were an accrual plan.
  • Four term types: Calendar year, Rolling backward, Rolling forward, Absence duration. Rolling backward requires an overlap rule: Include counts the whole overlapping absence in the current period, Exclude ignores it, Split counts only the part inside the current term.
  • Workers are enrolled when a worker or administrator schedules an absence using an absence type associated with the plan (Participation tab), or per a formula; entitlements stop on termination or loss of plan eligibility, and the plan decides these two cases separately.
  • The payment rate of a single unit of absence can come from a rate definition or a formula (see the rate-definitions lesson); the entitlement band matrix sets the payment percentages for specific periods during the absence.
  • Do not create a qualification plan with multiple expression builders where all are satisfied — create multiple plans instead; create length-of-service derived factors in Manage Derived Factors before building bands.
  • Open-ended absences (Open-ended check box, e.g. maternity or illness) have no required end date; the estimated end date is not used — entitlement is calculated for 365 days, beyond which a Pending Evaluation record allows a 90-day extension when Evaluate Absences runs. When an end date is later entered, entitlement recalculates on the actual end date and an Entitlement exceeded row is generated for unpaid days.

Source: ABS-QUAL-001, ABS-QUAL-002, ABS-QUAL-003, ABS-QUAL-004, ABS-QUAL-005, ABS-QUAL-006, ABS-QUAL-009, ABS-QUAL-010, ABS-QUAL-011, ABS-QUAL-012

Common mistakes

Wrong: Configuring a qualification plan with accrual-style balance rules.

Symptom: The plan shows a balance that never accrues and payments that never fire during the absence — the leave is tracked but unpaid.

Fix: A qualification plan maintains no balance; it evaluates entitlement per absence over the term and pays via the band matrix. Use an accrual plan only when time is actually banked.

Wrong: Choosing a rolling-backward term and leaving the overlap rule to whatever default.

Symptom: Two identical straddling absences are paid differently depending on which overlap rule was in effect — 5 vs 20 vs 15 full-pay days in the worked scenario.

Fix: Set Include, Exclude or Split deliberately; the overlap rule is a payment decision for absences that straddle the term boundary.

Wrong: Building bands over length-of-service derived factors that were never created.

Symptom: The band matrix looks right but matches nobody — the worker gets no qualification entitlement at all, silently.

Fix: Create the derived factors in Manage Derived Factors first (e.g. [LengthOfService.GreaterThan5_LessThan10]), then reference them in the expression builder.

Wrong: One plan with multiple expression builders where all are satisfied.

Symptom: Oracle explicitly warns against this: the evaluation is ambiguous and the wrong band may win.

Fix: Create multiple plans — one per specific scenario — rather than overlapping expression builders in a single plan.

Wrong: Assuming an open-ended absence’s estimated end date drives entitlement.

Symptom: The worker enters an estimated end date and expects the entitlement to stop there; instead it is calculated for 365 days.

Fix: For open-ended absences the estimated end date is not used; entitlement is calculated for 365 days, with a Pending Evaluation record allowing a 90-day extension beyond that when Evaluate Absences runs.

Diagnosing it

Symptom: A worker on a maternity qualification plan records the absence, but the Manage Absences and Entitlements page shows no qualification entitlement (or only partial details).

Category: configuration

  1. 1.

    Is the worker in the eligible set — does the plan’s eligibility profile (Participation tab) actually match the worker (e.g. Assignment Category = Full-time regular)?

    If no: The worker never qualifies; no entitlement is evaluated at all. Check the profile criteria and any dangling derived-factor references.

    Evidence to capture: The Participation tab eligibility profile versus the worker’s assignment category

  2. 2.

    Was an absence using an absence type associated with the qualification plan actually scheduled (the enrollment trigger)?

    If no: Enrollment happens when an absence with an associated type is scheduled (or per the enrollment formula) — no scheduled absence, no enrollment.

    Evidence to capture: The absence record’s type and its association with the plan

  3. 3.

    For full details without an absence record, is Evaluate remaining entitlement without absence record selected on the Participation tab?

    If no: Without the check box, the Qualification Entitlements section shows only partial details for scheduled absences and nothing for a worker with no scheduled absence.

    Evidence to capture: The Participation tab check box versus the Qualification Entitlements section

  4. 4.

    On a rolling-backward term, is an overlap rule set, and does the term window actually contain the absence (e.g. one-year rolling period from Jan 2 2014 for an absence starting Jan 1 2015)?

    If no: The entitlement is calculated for the term period, not the absence dates — an absence outside the window (or mis-windowed) evaluates to nothing.

    Evidence to capture: The term type, duration, start rule and overlap rule versus the absence dates

  5. 5.

    Do the band matrix rows reference derived factors or attributes that exist, and is there more than one expression builder where all are satisfied?

    If no: A dangling factor matches nobody; multiple always-true builders are warned against — create multiple plans instead.

    Evidence to capture: The Qualification Band Matrix versus Manage Derived Factors

Confirm: Work outward from the worker: eligibility profile matches the worker, an associated absence type was scheduled (enrollment), the term window and overlap rule contain the absence, the bands reference existing factors, and the display check box is set if full details are expected — then read the Qualification Entitlements section for plan period, qualified and remaining.

Recall

What distinguishes a qualification plan from an accrual plan, what are the four term types, and what does the overlap rule decide?

Answer shape: A qualification plan pays workers who qualify for it during an absence and maintains no balance — it decides entitlement and payment directly, unlike an accrual plan which banks time. It configures four rule areas: plan term, plan eligibility (an eligibility profile), enrollment and termination, and payments (an entitlement band matrix; the unit payment rate can come from a rate definition or formula). The four term types are Calendar year, Rolling backward (assessment period preceding the absence start date — requires an overlap rule), Rolling forward (from the first absence start date for the term duration), and Absence duration. On rolling-backward terms the overlap rule decides how a straddling absence counts: Include counts the whole overlapping absence (5 full-pay days left in the worked scenario), Exclude ignores it (20), Split counts only the part inside the current term (15). Enrollment happens when an associated absence type is scheduled; the plan separately decides whether payments continue on termination versus loss of eligibility. Open-ended absences are calculated for 365 days regardless of the estimated end date, with a Pending Evaluation record allowing a 90-day extension.

Memory hook: No balance, just bands. Four terms; rolling backward needs an overlap rule. Include counts all, Exclude none, Split the inside part.

Review these concepts

Source evidence

Chapter 10 of the Implementing Absence Management book (faiam) was read directly on 2026-11-07: the four rule areas and payments section, the four term types, the overlap-rule worked scenario (Include 5 / Exclude 20 / Split 15 full-pay days), enrollment and termination options, the qualification-band examples over derived factors and grades, the entitlement display worked calculations (88-day and 22-day absences), the open-ended 365-day rule with Pending Evaluation, and the full worked maternity plan.

Release scope: FA Latest

Recorded gaps

  • The expression builder’s full grammar beyond the worked [LengthOfService.GreaterThan5_LessThan10] and [Person.Grade] >= "A1" examples is not reproduced; the pages show those forms, not the complete operator set.
  • How the Evaluate Absence process internally walks the term window is described at the level of "calculates entitlements for the total absent time recorded in the period"; the per-day mechanics are not enumerated on these pages and are not asserted.
  • The compensatory and donation plan chapters (11–12) are the same shape of content and are not covered by this lesson.

Related concepts

  • The accrual plan, configuredcontrasts

    The accrual plan banks a balance and pays from it; the qualification plan maintains no balance and pays per absence via bands — the two plan types answer different questions.

  • Eligibility profiles and derived factorsdepends on

    The qualification plan’s eligible set is decided by the eligibility profile on the Participation tab — the same profile model the accrual-plan lesson builds.

  • Rate definitions for absence paymentsreferenced by

    The payment rate of a single unit of a qualification entitlement can come from a rate definition — the Absence Payment Rate Rule on the Entries and Balances tab points at the rate.

Self-check

An auto-graded assessment is attached to this lesson: assessment-absence-qualification-plans

Start self-check

Lesson progress

Checking your progress…

Qualification plans: paying an absence with no balance · Oracle Fusion Cloud HCM · HCM Studio by Digi Tracks · www.digitracks.net · contact@digitracks.net

Claims: ABS-QUAL-001, ABS-QUAL-002, ABS-QUAL-004, ABS-QUAL-005, ABS-QUAL-003, ABS-QUAL-006, ABS-QUAL-009, ABS-QUAL-010, ABS-QUAL-011, ABS-QUAL-012

Oracle, Oracle Fusion Cloud HCM and the Oracle logo are trademarks of Oracle Corporation. HCM Studio is an independent training product, not affiliated with or endorsed by Oracle.