The Work > Balance History screen in People exposes a snapshot of entitlement balance transactions as they existed at the time of pay run commit. This information provides the inputs used to calculate the balance result displayed on the Earning Statement or the GL posting for the selected pay run.
In the Work > Balance History screen, you can select a specific entitlement balance and pay run, and Dayforce exposes the balance periods active for the selected balance during the selected pay run. You can view balance periods together or separately.
The Work > Balance History screen is for reference only: no user entry is supported.
- Transactions are displayed for the selected pay run to support the calculation of the balance result displayed on the employee earning statement.
- Transactions are displayed for the pay run prior to the selected pay run to support the calculation of the balance delta posted to the GL.
- Rounding of transaction amounts might differ between displays in the Balance and Balance History screens.
- The base rate as-of each committed pay run is shown for convenient conversion of units to expense if desired. Base rates aren't displayed for uncommitted pay runs.
- The Show Differences Only filter hides transactions irrelevant to the GL posting result when selected. Even without the filter, deltas are indicated by gray highlights for easy identification.
- The Taken filter hides balance taken transactions for customers who have GL configured for posting accruals only
- A legend is displayed to help you identify icons in the list of entries of interest:
- A GL Formula icon indicates for the selected period if the balance was configured on commit to be posted to GL or not.
- A Duplicate Balance Periods warning icon indicates transactions that apply to multiple balance periods during committed selected pay runs based on a transaction date that falls into an overlap between two balance periods, and thereby being double counted for balance results. Note that Dayforce doesn't support the Duplicate Balance Warning icon on the following:
- Preview of uncommitted pay runs.
- Backdated duplicate balance periods, although Dayforce does identify a delta caused by that condition using gray highlights in the transaction grid.
General Ledger Troubleshooting Supported by the Work > Balance History Screen
- Accrual transaction amounts can change due to entitlement recalc, causing the current GL posting to account for adjustments due to changed amounts.
- Initial value amounts can change due to rollover or user entry. In this case the initial value in the Balance Period record in the screen will be different, causing the current GL posting to account for adjustments due to changed amounts.
- Record population can change due to balance period date changes. In this case, the balance period in the latest pay run is different from the balance period in the prior pay run in the UI, causing different transactions to be included based on start and end dates. As a result, some entries that had been present will no longer be included, or some entries that weren't present will be included. The delta will hit the current GL posting. Dayforce will identify this delta by highlighting changed transactions in gray and displaying the start and end dates for the balance period as of the selected pay run. If you suspect the balance period date range was different in the prior pay run, select that pay run for review.
- Duplicate or overlapping balance periods can result from problems with imports and will be identified in the Balance Period grid with a warning icon, causing the amounts in the current GL posting to be doubled for any transactions in the overlapping time span. Note that Dayforce doesn't support the Duplicate Balance Warning icon on:
- Preview of uncommitted pay runs.
- Backdated duplicate balance periods, though Dayforce does identify a delta caused by this condition using gray highlights in the transaction grid.
- Liability dollar amounts can change due to base rate changing. The Balance History screen displays a base rate in the latest committed pay run that is different from the base rate in the prior pay run, causing the current GL posting to account for adjustments due to trued-up amounts.
- GL formula configuration can change from one pay run to the next. The UI will indicate this in the GL formula icon beside the balance selector, making the comparable results different from one pay run to the next and causing the current GL posting to account for adjustments due to reformulated amounts. Dayforce will identify this delta by highlighting changed transactions in gray and displaying the GL formula icon as of the selected pay run. If you suspect the formula was different in the prior pay run, select that pay run for review.
See General Ledger Setup in the Dayforce Implementation Guide.