If an observation report does not display year-to-date values and only shows totals for the current period, several factors might be causing this issue.
We have compiled a list of possible causes, along with steps to resolve them.
Timing issue
If the report was generated after the PAY355 Complete Update job, it may not reflect the correct year-to-date values.
To resolve this, our support team needs to rebuild the PY_HIST_PAY_CODE_ANAL view on the database. Please raise a new case online, referencing this article's title.
HISTORY_PAY_CODE_ANALYSIS job
If the HISTORY_PAY_CODE_ANALYSIS job has not run, this could also result in missing year-to-date values.
To resolve this, our support team needs to rebuild the PY_HIST_PAY_CODE_ANAL view on the database. Please raise a new case online, referencing this article's title.
Payrolls for the same pay group
Running two payrolls for the same pay group on the same day can lead to discrepancies in year-to-date reporting.
To resolve this, re-run the payroll the next morning.
Incorrect pay group start period
An incorrect pay group start period can affect year-to-date figures in the PAYB300DET report.
To resolve this, set the pay group start period to the first payroll week of the current tax year. For example, if you are processing payroll period 202504, the start period should be 202501.
To view and update the pay group start period in Back Office, follow these steps:
1. Click on CorePay then select Update.
2. Click Utilities then click Pay Group Utilities.
3. Enter the relevant pay group in the pay group field.
4. Press Tab on your keyboard to review the start period.
📌Note: Ensure that you set this to the first payroll week of the current year. Only change the tax year if you are certain that all cumulative values have been cleared.