Verify Holiday Premium Inputs Without Recalculating the Law

Anchor to one approved calendar version

Store the approved holiday calendar with an identifier, a publication date, an effective period, and the owner who released it. Record where it came from and which version the payroll run is supposed to use. If a new version appears, keep the old one and show the change rather than overwriting the file.

Before verification starts, confirm that the checklist, the payroll system, and the client communication all reference the same version. A mismatch between two calendars is a control failure, not a data entry error. Stop the check and resolve the version question with the calendar owner before reviewing individual employees.

Keep the release notice with the calendar. The notice should name the version, the effective dates, the owner, and the systems that must update. A calendar without its release record is just a file, and a file cannot show who approved it or when it changed.

Separate holiday type from premium rule

A holiday calendar may label a date as a regular holiday, a special non-working day, or a local observance. The payroll rule that applies is a separate decision owned by payroll and, where needed, qualified counsel. Keep two fields in the verification record: the calendar label and the payroll code. Do not infer one from the other.

This separation lets the support lane check consistency without interpreting the law. If the calendar label and the payroll code disagree, the lane records the expected value from the approved mapping and routes the difference. The payroll owner decides whether the mapping is correct or the record needs correction.

Match time records to the scheduled window

For each employee and date, compare the actual time record with the scheduled window. Record the source system, the extraction time, the time zone, and any manual adjustment. A holiday check is only as good as the time evidence behind it, and an adjusted record needs its approver visible.

Do not assume that a rostered shift was worked or that a holiday absence was paid. Missing time, a double punch, or a shift that crosses midnight should become a flag. The reviewer needs enough evidence to see the actual state, not a cleaned summary that hides the uncertainty.

Check rest day and holiday overlap flags

When a holiday falls on a rest day or overlaps another premium condition, the payroll code may depend on a rule the support lane should not choose. Record both conditions and the approved code from the mapping. If the mapping does not cover the combination, create a question for the payroll owner.

Keep these overlap cases in a separate count so they do not disappear inside a general exception rate. They are often the cases most likely to be handled inconsistently between cycles. A short list of overlap cases with the owner decision is more useful than a note that says see payroll.

Verify the payroll code against the owner map

The owner map names who can approve each code, which changes require a new mapping, and what evidence supports an override. The verification lane checks the code against the map and flags any code that is absent, inactive, or used outside its approved period.

An override should have a reason, an approver, and an expiry. A permanent override is a sign that the mapping is wrong or the process is being bypassed. Report overrides by type and owner so the payroll owner can see whether the exception is becoming the normal path.

Log mismatches with a reason and owner

Use a mismatch log with the employee key, date, calendar version, expected code, observed code, evidence link, reason code, owner, and status. Reason codes should distinguish a calendar version issue, a time record gap, a mapping gap, a data entry error, and an unresolved policy question.

Do not close a mismatch by editing the payroll record from the verification sheet. The payroll owner or the authorized system owner makes the correction, and the log records the correction reference. This keeps the evidence trail intact and prevents the support lane from becoming an unaudited second payroll system.

Sample the quiet cases too

It is easy to review only the records that look unusual. Add a random sample of records with no flag and check them against the calendar and time source. This estimates whether the quiet population is actually clean or simply unexamined.

Report the sample size, the population, the number of mismatches found, and the review period. If the quiet sample produces mismatches, expand the check before approving the run. A clean exception queue with a dirty base population is not a control.

Record the sample frame as well as the result. If the sample covers only one shift or one site, say so. A quiet sample from a narrow frame does not support a claim about the whole population, and the report should not imply that it does.

Close with a reconciliation count

At the end of the check, reconcile eligible records to checked records, checked records to mismatches, and mismatches to open or resolved status. Show the counts by owner and by reason code. The payroll owner should be able to see what remains before approving the run.

Keep the final pack with the calendar version, the extraction evidence, the mismatch log, and the reconciliation. If a later question arises, the pack should show what was checked, what was not, and who accepted the remaining risk. That is more valuable than a statement that the holiday run was reviewed.