Absence Management
Configuring an accrual plan: term, frequency, limits and carryover
The eleven rule areas of an accrual plan, the two term types, the two balance frequency sources, the five carryover limit rules, and the difference between the annual accrual limit and the ceiling — using Oracle’s own vacation-plan example as the worked case.
Learning objectives
- 1.Name the eleven rule areas configured on an accrual plan and say what each decides
- 2.Choose between a calendar-year and an anniversary-year term, and state what the continuous service date does and does not affect
- 3.Choose between person primary frequency and a repeating time period for accrual, including the 7-day minimum on a repeating period
- 4.Configure a carryover limit rule and an expiration, and state the 1-year cap on expiration and the rerun needed after a change
- 5.Distinguish the annual accrual limit from the ceiling, and explain when each reduces an accrual
Why this matters
An accrual plan is where a leave policy becomes numbers: who accrues, how much, how often, what happens to the leftover at year end, and what it is worth when paid. Most configuration defects in Absence Management are not in the absence type — they are in a plan field nobody read, and the two fields most often confused are the carryover limit and the ceiling, which sound alike and do different things.
If you skip this: A plan with the wrong carryover rule silently forfeits or over-pays leave at year end; a plan with the wrong limit rule accrues the wrong amount every period, and the error compounds until payroll reconciliation catches it.
What it is, why it exists, what breaks
What it is
Eleven rule areas on one plan: plan term, plan eligibility, enrollment and termination, transfer and rollover, prior balance reinstatement, vesting period, plan limits, balance updates, payments, disbursement and donation. The term decides when the year runs; the frequency decides how often leave is awarded inside it; the limits and carryover decide what the balance may reach and what passes to the next term.
Why it exists
Because a leave policy is a set of numeric promises — accrue X per period, never exceed Y, carry at most Z — and each promise maps to exactly one field group on the plan. The plan, not the type, is where the money is decided.
What breaks without it
When the carryover limit is set but the plan change is never recalculated, the old carryover value keeps applying: after changing carryover configuration you must rerun Calculate Accruals and Balances with the last day of the previous plan term as the effective date. And when the term is anniversary year, the term still starts on the hire date — the continuous service date entered at enrollment only feeds length-of-service calculations, never the term start.
Source: ABS-ACCRUAL-001, ABS-ACCRUAL-009, ABS-ACCRUAL-003
The accrual plan as a pipeline
The term sets the year, the frequency slices it, the bands set the rate, the limit and ceiling cap it, and the carryover decides what survives the year end. Listed in order: Accrual term, then Balance frequency, then Accrual bands, then Annual accrual limit and ceiling, then Year-end: rollover, then carryover, then Payments and disbursement.
An accrual plan read as a pipeline. The accrual term sets the plan year: calendar year, restarting the same day next year, or anniversary year, starting on the hire date and restarting each anniversary — the continuous service date never moves the term start. The balance frequency source slices the term into accrual periods: person primary frequency accrues at the start of each payroll period, or a repeating time period of at least 7 days created in Manage Repeating Time Periods, which updates automatically when the payroll relationship changes and accruals run. Each period awards the band rate from the accrual matrix, which varies accrual rate, carryover and ceiling by length of service, location, grade or other derived factors, and bands can be date-effective. Two limits apply during the year: the annual accrual limit caps what accrues within the plan year and reduces that period’s accrual when exceeded, and the ceiling caps the total balance and can reduce it further. At year end the rollover is processed first, then the carryover with the leftover; a balance above both is paid out only if Disburse remaining balance is selected, otherwise it expires, carryovers can expire after a set time (at most 1 year unless the rule is No Limit), and negative balances carry over even at limit 0. Branching off the balance, the payment, disbursement, liability and final-balance rules price the leave with rate definitions and a payroll element. After any carryover or limit change, Calculate Accruals and Balances must be rerun with the last day of the previous term as the effective date.
What to take from this: Read the plan as a pipeline: the term sets the year, the frequency slices the year into accrual periods, the matrix or formula sets the rate per band, the annual limit and ceiling cap what accrues and what the balance can reach, and at year end the rollover runs first and the carryover limit decides what survives into the next term. The payment and disbursement rules are not part of the accrual math — they price the balance when it is used or paid out.
Source: ABS-ACCRUAL-011
The year-end surprise
A vacation plan is configured with a carryover limit of 5 days and a ceiling of 40. At year end a worker has 22 days of balance. The next January the worker sees 5 days, and the remaining 17 are gone — and the payroll team is asked where they went.
- 1.The plan’s Year End Processing section is checked: the carryover rule is Flat Amount, limit 5, and Disburse remaining balance is not selected.
- 2.The rule is explicit: the unused balance above the rollover and carryover limit expires unless the disburse option is selected. 22 minus the 5-day carryover leaves 17 expired.
- 3.The ceiling of 40 was never the constraint here — the balance never exceeded 40 during the year, so the ceiling never reduced an accrual; the carryover rule is what removed the 17 days.
- 4.The fix is a policy decision, not a bug fix: either select Disburse remaining balance, or raise the carryover limit, then rerun Calculate Accruals and Balances with the last day of the previous term as the effective date so the change is recalculated.
Takeaway: The ceiling caps the balance during the year; the carryover limit caps what survives the year end. They are different numbers in different sections, and confusing them is how leave silently disappears.
Source: ABS-ACCRUAL-006, ABS-ACCRUAL-010, ABS-ACCRUAL-011
Configuration model
Navigation paths
Absences work area > Absence Plans task > Create > Plan Type: AccrualABS-ACCRUAL-001Create Absence Plan page > Accruals tab > Year End Processing section (carryover rule) and Balance Frequency SourceABS-ACCRUAL-004Create Absence Plan page > Participation tab (waiting period, enrollment) and Re-enrollment Rules section (prior balance reinstatement)ABS-ACCRUAL-012Absences work area > Manage Repeating Time Periods task (for a repeating-period balance frequency)ABS-ACCRUAL-004Schedule and Monitor Absence Processes task > Calculate Accruals and Balances (rerun after carryover or limit changes)ABS-ACCRUAL-009
Objects
Accrual term
The period during which workers accrue: calendar year (starts on a selected date, restarts the same day next year) or anniversary year (starts on the hire date, restarts each anniversary).
Risk if wrong: An anniversary term built on the continuous service date instead of the hire date misaligns every year-end boundary for anyone whose service date differs from the hire date.
Balance frequency source
Person primary frequency awards time at the start of each payroll period; a repeating time period awards it at the start of each instance of a period created in Manage Repeating Time Periods (minimum duration 7 days).
Risk if wrong: A repeating period shorter than 7 days is invalid, and a payroll change that is not followed by a rerun of accruals leaves the repeating period stale even though the page says it updates automatically.
Carryover limit rule
No Carryover, No Limit, Flat Amount, Include in Matrix or Formula (Global Absence Carryover, which sets only the upper limit); negative balances are carried over even when the limit is 0.
Risk if wrong: A Flat Amount limit with no disbursement configured expires the excess silently at year end, and a negative balance still carries over even at limit 0.
Plan limits (annual accrual limit and ceiling)
The annual accrual limit caps what accrues within a plan year and reduces that period’s accrual when exceeded; the ceiling caps the total balance and can reduce the accrual further. Both can use an accrual band matrix or a formula.
Risk if wrong: Treating the annual limit as the ceiling under-caps the balance for workers who carry over; treating the ceiling as the annual limit over-caps each period.
Accrual matrix (bands)
Varies accrual rate, maximum carryover and ceiling by criteria such as length of service, location or grade, using derived factors and the expression builder; bands can be date-effective.
Risk if wrong: Bands written against the wrong attribute (for example grade instead of a length-of-service derived factor) give the wrong workers the wrong rate, silently.
Rate definitions and payroll element
Price the balance: the vacation example creates rate definitions at 50% and 100% of salary and a nonrecurring element with Absences primary and Vacation secondary classification, wired to the payment, disbursement, liability and final-balance rate rules.
Risk if wrong: A plan with no rate rule pays absence at the wrong rate or not at all, and the failure appears in payroll, not in configuration.
Constraints
- An accrual term is either calendar year or anniversary year; the anniversary term starts on the hire date, and the continuous service date does not affect the term start.
- The balance frequency source is either person primary frequency or a repeating time period; a repeating time period must have a duration of at least 7 days.
- The carryover limit rule is one of No Carryover, No Limit, Flat Amount, Include in Matrix or Formula; negative balance is carried over even if the limit is 0.
- Carryovers can expire after a specific time; unless the rule is No Limit, the expiration period cannot exceed 1 year.
- After changing carryover configuration, rerun Calculate Accruals and Balances with the last day of the previous plan term as the effective date.
- Year-end processing runs the rollover first, then the carryover with the leftover balance; a balance above both limits is paid out only if Disburse remaining balance is selected, otherwise it expires.
- The annual accrual limit reduces the period accrual when the balance would exceed it; the ceiling can reduce it further.
- Workers are enrolled by employment and eligibility and disenrolled on termination or loss of eligibility; on termination, absences starting on/after the date are withdrawn, spanning absences are end-dated, open-ended absences end, and final disbursements go to payroll if configured.
Source: ABS-ACCRUAL-002, ABS-ACCRUAL-004, ABS-ACCRUAL-006, ABS-ACCRUAL-008, ABS-ACCRUAL-009, ABS-ACCRUAL-010, ABS-ACCRUAL-011, ABS-ACCRUAL-014
Common mistakes
Wrong: Setting the carryover limit and assuming the ceiling will handle the rest.
Symptom: At year end the balance above the carryover limit vanishes with no payout, and no error is raised.
Fix: The ceiling caps the balance during the year; only the carryover rule (plus the disburse option) decides what survives year end. Set them separately and deliberately.
Wrong: Using the continuous service date as the anniversary-term start.
Symptom: Year-end boundaries drift for anyone whose service date differs from the hire date, and carryover calculations land on the wrong day.
Fix: The anniversary term starts on the hire date and restarts each anniversary; the continuous service date only feeds length-of-service calculations for waiting, vesting and band matrices.
Wrong: Changing the carryover rule and expecting the current term to update.
Symptom: The old carryover value keeps applying to balances already calculated.
Fix: Rerun Calculate Accruals and Balances with the last day of the previous plan term as the effective date.
Wrong: Creating a repeating time period shorter than 7 days, or expecting a payroll change to update it without running accruals.
Symptom: The period is rejected, or accruals keep landing on the old cadence after a weekly-to-monthly payroll change.
Fix: Repeating periods need at least 7 days, and the repeating period is updated when accruals run after the payroll relationship changes.
Wrong: Assuming a terminated worker’s open-ended absence is simply abandoned.
Symptom: The absence shows as open while the enrollment has ended, and entitlement calculations disagree with payroll.
Fix: On termination the open-ended absence is end-dated at the termination date, spanning absences are end-dated, starting-later absences are withdrawn, and plan use is recalculated.
Diagnosing it
Symptom: A worker’s balance at the start of the new term is lower than expected, or an accrual this period is smaller than the band rate says it should be.
Category: configuration
- 1.
Was the carryover limit or expiration changed without rerunning Calculate Accruals and Balances?
If no: The carryover value from the previous calculation still applies; rerun the process with the last day of the previous term as the effective date.
Evidence to capture: The Accruals tab Year End Processing section and the accrual transaction history
- 2.
Is the carryover rule Flat Amount or Include in Matrix with the limit below the closing balance, and Disburse remaining balance not selected?
If no: The excess above the limit expired at year end by design — this is the expected behaviour of the rule, not a calculation error.
Evidence to capture: The carryover limit rule and the closing balance of the previous term
- 3.
Did the period accrual exceed the annual accrual limit, or does the balance exceed the ceiling?
If no: When the period accrual would exceed the annual limit it is reduced; a ceiling can reduce it further. Compare the accrued amount with the band rate and the two limits.
Evidence to capture: The Accrual Matrix bands, the Annual Accrual Limit Rule and the Ceiling Rule on the plan
- 4.
Does the worker’s band expression actually match them (grade, location, length-of-service derived factor)?
If no: The worker is accruing at a different band’s rate, which is why the amount differs from what was expected.
Evidence to capture: The Accrual Matrix section and the derived factors used in the expressions
Confirm: Separate the two limit questions first — annual limit affects each period’s accrual, ceiling affects the running balance, carryover affects only the year-end transfer — then rerun Calculate Accruals and Balances at the previous term’s last day if any of the three was changed.
Recall
Name the eleven rule areas of an accrual plan, state the two term types and what the continuous service date does not affect, and distinguish the annual accrual limit, the ceiling and the carryover limit.
Answer shape: Plan term, eligibility, enrollment and termination, transfer and rollover, prior balance reinstatement, vesting period, plan limits, balance updates, payments, disbursement, donation. Terms are calendar year (restarts the same day next year) or anniversary year (starts on the hire date; the continuous service date affects only length-of-service calculations, not the term). Balance frequency is person primary frequency (each payroll period) or a repeating time period of at least 7 days. The annual accrual limit caps accrual within the plan year and reduces the period accrual; the ceiling caps the total balance; the carryover limit (No Carryover, No Limit, Flat Amount, Include in Matrix or Formula) caps what passes to the next term, negative balances carry even at limit 0, carryover can expire after a set time (max 1 year unless No Limit), year-end runs rollover before carryover, and after a carryover change you rerun Calculate Accruals and Balances at the last day of the previous term.
Memory hook: Term sets the year, frequency slices it, bands set the rate, limit and ceiling cap it, carryover saves the rest. Rollover first, then carryover.
Source evidence
Chapter 9 of the Implementing Absence Management book (faiam) was read directly on 2026-11-06: the eleven rule areas, the two term types, the balance frequency sources and the 7-day minimum, the five carryover limit rules, carryover expiration and its 1-year cap, the annual limit versus ceiling, enrollment and termination behaviour, Oracle’s vacation-plan worked example and the accrual band examples.
- source-faiam-accrual-options
- source-faiam-accrual-term
- source-faiam-accrual-frequency
- source-faiam-carryover-limit
- source-faiam-carryover-expiration
- source-faiam-plan-limits
- source-faiam-accrual-enrollment
- source-faiam-vacation-plan-example
- source-faiam-accrual-bands
Release scope: FA Latest
Recorded gaps
- The pages name the Global Absence Carryover formula as the Formula carryover option but do not publish its text; this lesson states only that it sets the upper limit, not what it returns beyond that.
- The pages describe accrual bands and show expressions, but the full attribute list available in the expression builder is not enumerated on the pages read; this lesson names the attributes the examples use (Person.Grade, Person.Location, LengthOfService derived factors).
- The exact field labels of the Create Absence Plan tabs beyond those used in the vacation example are not all published on the pages read; the lesson names the sections the pages name and does not invent others.
Related concepts
- Absence planextends
The six plan types lesson says an accrual plan accrues a balance; this lesson is what configuring that plan actually means.
- Absence typedepends on
A type must be associated with a plan whose unit of measure matches, so the plan’s UOM constrains what types can be built against it.
Self-check
An auto-graded assessment is attached to this lesson: assessment-absence-accrual-plan
Lesson progress
Checking your progress…