Testing the UKG Accrual Carryover Process
UKG accrual carryover testing verifies the end-to-end business process that moves an employee's unused leave balance across a plan-year or anniversary boundary in UKG Pro Workforce Management — carrying eligible hours forward, truncating anything above the carryover limit, forfeiting or paying out the excess, and resetting the plan for the new period. SyntraFlow is an AI-powered UKG payroll and workforce assurance platform, Oracle-native and expanding to UKG, whose architecture is designed to run this rollover process against real employee profiles and assert every resulting balance, rather than confirming a screen merely refreshed on January 1.
Process overview
Accrual carryover is the scheduled, high-blast-radius event where every employee on a plan crosses into a new accrual period at once. UKG applies the carryover rule to each remaining balance: eligible hours move forward, a carryover cap truncates what exceeds the limit, and the excess is either forfeited or converted to a payout depending on the plan. The plan then resets its earned-to-date and used-to-date counters for the new year. Unlike day-to-day accrual earning, this process fires only at a plan-year end or on an employee anniversary, so it is rarely rehearsed and almost never tested at scale before it runs against the whole population.
Testing this process matters because a single misconfigured carryover rule touches thousands of balances in one run, and the errors are financial. Over-carrying inflates liability on the balance sheet and hands employees leave they were not entitled to keep; under-carrying or wrongly forfeiting strips earned time and invites grievances and wage claims; a broken payout of excess sends the wrong dollars to the paycheck. Because the event is annual, a defect that slips through is often discovered a full year later, after balances have compounded. This runbook sits within UKG business process testing and builds directly on the capability described in UKG accrual testing.
Preconditions
The carryover process depends on state that must exist before rollover runs. Testing has to establish or confirm each of these, because a wrong precondition produces a wrong balance that looks like a process defect.
- ▸Plan configuration in place. Each accrual plan has a defined carryover method, carryover cap, forfeiture-or-payout treatment and reset date, with the correct effective date for the period being rolled.
- ▸Known prior-year balances. Test employees hold seeded earned, used and remaining balances that straddle the carryover limit — below, at, and above — so every branch of the rule is exercised.
- ▸Correct plan-year or anniversary date. The system or test calendar is positioned at the exact rollover boundary; anniversary plans require each employee's hire-date anchor to be right.
- ▸Eligibility and employment status. Active, on-leave and pending-termination employees are staged, since status changes how carryover, forfeiture and payout resolve.
- ▸Downstream targets ready. Where excess is paid out, the payroll interface and pay period that will receive the payout are open and mapped for the run.
User roles
Carryover is largely system-driven, but several roles set it up, trigger it and consume its results. Coverage should reflect what each role sees and approves.
| Role | Responsibility in the carryover process |
|---|---|
| WFM / accrual administrator | Configures the carryover rule, cap, forfeiture or payout treatment and reset date, and initiates or schedules the rollover. |
| Payroll administrator | Confirms that any payout of excess reaches the correct pay period at the correct rate, and reconciles the accrual liability. |
| Manager | Reviews team balances before and after rollover and fields questions when forfeiture or a reset changes an employee's available time. |
| Employee | Sees the new-year opening balance in self-service and expects carried, forfeited and paid-out amounts to match plan policy. |
| HR / compliance reviewer | Confirms carryover and forfeiture align with leave policy and applicable rules, and retains evidence of the run for audit. |
Required test data
Carryover only proves out when the population deliberately spans every branch of the rule. A useful data set includes employee profiles positioned on each side of the limit, plus edge cases that expose forfeiture, payout and reset behaviour.
- ▸Balance below the cap. An hourly hospital employee with a remainder under the carryover limit, whose full balance should carry forward untouched.
- ▸Balance exactly at the cap. A retail associate sitting on the limit, to prove the boundary carries in full with nothing forfeited.
- ▸Balance above the cap. A manufacturing worker over the limit on a forfeiture plan and another on a payout plan, so both excess treatments are exercised.
- ▸Anniversary-dated employee. A salaried employee whose plan rolls on hire-date anniversary rather than a calendar year-end.
- ▸Status edge cases. An on-leave employee, a union employee with a policy-specific carryover rule, and a pending-termination employee whose excess must pay out or forfeit correctly.
Staging these profiles by hand is slow and error-prone; reusable, parameterised data generation keeps the same permutations available for every rehearsal, which is where accrual calculation testing and this carryover runbook share inputs.
Main process steps
The happy-path flow for a plan-year or anniversary rollover moves through a predictable sequence. Each step is an assertion point where a defect can enter.
- 1.Reach the rollover boundary. The plan-year end or employee anniversary date arrives, and the accrual plan is flagged for carryover processing.
- 2.Determine the remaining balance. UKG closes the ending period and computes each employee's final earned-minus-used balance to be carried.
- 3.Apply the carryover rule and cap. Eligible hours carry forward up to the carryover limit; anything above the cap is set aside as excess.
- 4.Resolve the excess. Excess above the cap is forfeited on a use-it-or-lose-it plan, or converted to a payout amount on a pay-out plan.
- 5.Post the payout to payroll. Where excess pays out, the value is handed to the payroll interface at the correct rate and pay period.
- 6.Reset the plan for the new period. The opening balance for the new year is set to the carried amount, and earned-to-date and used-to-date counters reset.
- 7.Surface the result. The new opening balance appears in employee and manager self-service, and the run is recorded for audit.
Positive test scenarios
Positive coverage proves that each branch of the carryover rule resolves to the balance the plan promises. The table pairs these with negative scenarios, where the process should truncate, forfeit or block rather than carry.
| Type | Scenario | Expected outcome |
|---|---|---|
| Positive | Hospital employee below the carryover cap rolls into the new plan year | Full remaining balance carries forward; nothing is forfeited or paid out |
| Positive | Retail associate sitting exactly at the carryover limit | Balance carries in full at the boundary; no truncation triggered |
| Positive | Manufacturing worker above the cap on a forfeiture plan | Carried amount truncates to the cap; excess is forfeited and logged |
| Positive | Employee above the cap on a pay-out plan | Carried amount caps; excess converts to a payout at the correct rate and posts to payroll |
| Positive | Salaried employee on an anniversary-dated plan reaches hire-date rollover | Carryover fires on the anniversary, not calendar year-end; balance rolls correctly |
| Positive | Plan reset after carryover | Opening balance equals the carried amount; earned- and used-to-date counters reset to zero |
| Positive | Union employee under a policy-specific carryover limit | The union rule's limit and treatment apply, overriding the default plan behaviour |
| Negative | Balance above the cap carries in full | Defect: carried amount must be truncated to the limit; over-carry is caught before it inflates liability |
| Negative | Excess forfeited on a plan configured to pay out | Defect: excess should have posted a payout, not been lost; forfeiture is flagged |
| Negative | Payout of excess posts at the wrong rate or wrong pay period | Defect: payout amount and timing must match the plan rate and open period; mismatch blocks sign-off |
| Negative | Reset over-writes the carried balance to zero | Defect: opening balance must equal the carried amount; a wrongful reset to zero is a failure |
| Negative | Retroactive prior-year adjustment lands after rollover | Carried balance must recalculate for the true prior-year total; no double-count or lost adjustment |
| Negative | Anniversary rollover fires on the wrong date | Defect: carryover triggering on calendar year-end for an anniversary plan is caught |
Negative test scenarios
The negative rows above carry the weight of this process. Because carryover is irreversible once it posts against a live population, the guardrails — truncation at the cap, correct excess treatment, an accurate reset and clean handling of late adjustments — are precisely what testing must force to fail safely in a rehearsal environment first. Bundling them into regression automation means every plan change and UKG release re-checks them before the next year-end.
Rule variations
The same rollover event resolves to different balances depending on how the plan and the employee are configured. Coverage has to walk these variations rather than assume one correct answer.
- ▸Carryover method. A flat carryover cap, a percentage-of-earned carryover and an unlimited-carry plan each produce a different carried amount from the same starting balance.
- ▸Excess treatment. Forfeiture, payout of excess, and a grace-period extension are mutually exclusive branches that must be tested independently.
- ▸Rollover anchor. Calendar plan-year, fiscal-year and hire-date-anniversary plans fire on different dates and require different calendar positioning.
- ▸Eligibility and union overrides. A union or location-specific policy can override the default carryover limit and treatment, so the applicable rule, not the base plan, governs the outcome.
- ▸Effective-dated rule changes. A carryover limit changed with a future effective date must apply to the correct plan year, and a backdated change may trigger a retroactive recalculation of the carried balance.
Integration checkpoints
Carryover does not end inside UKG Pro Workforce Management. Its outputs cross into payroll, the general ledger and neighbouring HCM systems, so this runbook connects to the boundaries that UKG integration testing covers in depth.
- ▸WFM to payroll. A payout of excess must export to the payroll interface at the correct rate and land in an open pay period, making every payout scenario an interface test as well as a balance test.
- ▸Accrual liability to the GL. Carried, forfeited and paid-out totals change the leave-liability figure that posts to the general ledger, so finance reconciliation depends on the rollover being right.
- ▸Cross-application HCM. Where the same leave plans exist in Workday, Oracle or SAP, carried balances may need to reconcile across systems — a differentiator where SyntraFlow follows the balance end to end.
- ▸Downstream request approvals. The new opening balance immediately governs what a time-off request can draw, so a wrong carryover ripples straight into approvals on day one of the new year.
Expected outcome & evidence
A correct carryover run leaves each employee with a new-period opening balance equal to their eligible carried hours, excess handled exactly as the plan dictates, payroll and the ledger reconciled, and the plan reset for the year ahead. Proving that requires captured evidence, not a visual glance.
- ▸Expected-versus-actual balances. Per-employee records of prior-year remainder, carried amount, forfeited amount and payout, each compared against the calculated expectation.
- ▸Reset confirmation. Evidence that opening balances equal carried amounts and that earned- and used-to-date counters were cleared for the new period.
- ▸Payout and GL reconciliation. The payout file handed to payroll and the liability change posted to the ledger, tied back to the rollover run.
- ▸Audit record. A timestamped, repeatable log of the run and its results, retained so HR and compliance can review carryover and forfeiture against policy.
Compliance dimensions — leave laws, use-it-or-lose-it restrictions, union agreements and multi-state rules — are considerations to confirm with your accountable teams, not legal certification. SyntraFlow produces the evidence to support that review; payroll, HR and legal stakeholders retain responsibility for approval.
SyntraFlow automation approach
SyntraFlow is designed to treat carryover as one reusable master scenario driven by data, not a one-off manual rehearsal. The platform can be configured to seed employees across every branch of the rule, advance the calendar to the rollover boundary, run the process, and assert the carried, forfeited, paid-out and reset balances against expected values in a single pass.
- ▸Reusable master scenario. One carryover flow parameterised across plans, caps and excess treatments, so a new plan is added as data rather than a new script.
- ▸Data-driven permutations. The same run exercises below-cap, at-cap and above-cap balances across calendar, fiscal and anniversary anchors and union overrides in one execution.
- ▸Self-healing stability. Tests are designed to stay green when UKG UI or navigation shifts between releases, so year-end coverage survives the updates that precede it.
- ▸Evidence capture built in. Every run records expected-versus-actual balances, payout files and reset confirmation as audit-ready output.
AI is designed to assist and recommend — drafting carryover scenarios from plain-language intent and suggesting the plan, cap and date combinations worth covering — while humans remain responsible for approving payroll and confirming compliance; AI never approves pay or makes compliance decisions. These capabilities reflect design intent for an early, roadmap-stage UKG offering and are available for demonstration and proof-of-concept validation. A scoped assessment is the right way to confirm which carryover scenarios fit your plan configuration today.
Frequently asked questions
What is UKG accrual carryover testing?
UKG accrual carryover testing verifies the year-end or anniversary rollover process in UKG Pro Workforce Management. It confirms that eligible balances carry forward, carryover caps truncate excess, that excess is forfeited or paid out as the plan dictates, and that the plan resets correctly for the new period — for every employee group and rollover anchor.
Why is the carryover process so risky to leave untested?
Because it fires once a year against the entire population at once and its errors are financial. Over-carrying inflates leave liability, wrongful forfeiture strips earned time and invites claims, and a broken payout sends the wrong dollars to payroll. A defect can surface a full year later, after balances have already compounded across thousands of records.
What is the difference between carryover and accrual calculation testing?
Accrual calculation testing checks how a balance earns during the period. Carryover testing checks the boundary event that moves that ending balance into the next period — applying the cap, forfeiting or paying out the excess and resetting the plan. Both share test data, but carryover focuses on the rollover, cap and reset behaviour that only fires at period end.
How does SyntraFlow test carryover caps and forfeiture?
SyntraFlow is designed to seed employees with balances below, at and above the carryover limit, advance the calendar to the rollover boundary, run the process, and assert the carried amount truncates to the cap while excess is forfeited or paid out per the plan. Parameterised runs exercise every branch across plans in one pass.
Does carryover testing cover payout of excess to payroll?
Yes. Where a plan pays out excess rather than forfeiting it, testing confirms the payout amount is calculated at the correct rate and posts to the right pay period through the payroll interface. That makes payout scenarios both balance tests and integration tests, reconciled against payroll and the accrual liability posted to the ledger.
How are anniversary-based carryover plans handled?
Anniversary plans roll on each employee's hire-date anchor rather than a shared calendar year-end, so the rollover fires on different dates across the population. Testing positions each employee's calendar to their anniversary and confirms carryover triggers on the correct date, catching the common defect where an anniversary plan wrongly rolls at calendar year-end.
How does AI help with UKG carryover testing?
AI is designed to assist and recommend — drafting carryover scenarios from plain-language intent, suggesting the plan, cap, anchor and status combinations worth covering, and keeping tests stable through self-healing when the UI shifts. It accelerates analysis and authoring. Humans remain responsible for approving payroll and compliance; AI never approves pay or makes compliance decisions.
Does SyntraFlow support UKG carryover testing today?
SyntraFlow is an established Oracle-native testing platform now expanding to UKG. UKG coverage is early and on the active roadmap; the capabilities described reflect design intent and are available for demonstration and proof-of-concept validation. We recommend a scoped assessment to confirm which carryover scenarios fit your plan configuration.
Related UKG testing
UKG accrual testing
The capability behind this process — validating earning rules, carryover, caps and balances as calculated outcomes.
Accrual calculation process
Test how balances earn during the period before they reach the carryover boundary.
Accrual adjustment process
Validate manual grants and corrections, including retroactive edits that recalculate a carried balance.
Time-off request process
Confirm the new opening balance correctly governs what employees can request on day one of the new year.
Regression automation
Re-run carryover, cap and reset scenarios automatically on every plan change and UKG release.
UKG testing overview
The pillar hub for validating UKG Pro and UKG Pro WFM across timekeeping, payroll and releases.
Rehearse your UKG year-end carryover before it runs for real
Bring your carryover rules, caps and forfeiture-or-payout policies, and we will scope a proof-of-concept that runs the rollover against seeded employees and asserts every carried, forfeited, paid-out and reset balance — with audit-ready evidence.