How to Build a Monthly Payroll Change Report HR and Finance Can Trust

The monthly payroll change report is the handoff between employee operations and payroll execution. Its job is not to run payroll. Its job is to present complete, approved, effective-dated changes in a form the payroll owner can review and process.

The IRS Employer’s Tax Guide, Publication 15, sets out federal employer responsibilities and deadlines. Your payroll provider and qualified advisers should determine the actual calculation, filing, and location-specific process. The HR change report should support that work without pretending to replace it.

Define the reporting period and cut-off

Every report needs three dates:

1. Period start: the earliest effective date included.
2. Period end: the latest effective date included.
3. Submission cut-off: when HR must provide approved changes to payroll.

Also define how late changes are handled. Do they enter an exception process, move to the next cycle, or require named approval? Silent additions after sign-off undermine the report.

Include the change types payroll needs

A practical register usually covers:

• New starters
• Leavers
• Salary or compensation changes
• Job, department, location, legal entity, or cost-centre changes
• Payroll group or identifier changes
• Changes to payroll-relevant working arrangements
• Missing required payroll fields

Keep informational HR changes out unless the payroll process genuinely needs them. A narrower report is easier to review and exposes fewer personal details.

Use one row per actionable change

| Field | Purpose | | --- | --- | | Employee identifier | Stable match to the payroll record | | Employee name | Human review | | Change type | Starter, leaver, salary, organization, or other approved category | | Effective date | When the change takes effect | | Previous value | Reconciliation where appropriate | | New value | The approved target value | | Payroll group | Routing to the correct cycle or provider | | Source owner | Person or team accountable for the change | | Approval state | Evidence the change is ready | | Exception note | Missing or late information requiring action |

Do not place bank details, identity documents, or unrelated personal information into a broad change report. Transfer sensitive payroll inputs through the approved secure process.

Build the report from canonical events

Avoid asking HR to retype every change into a separate month-end file. The register should be derived from the employee lifecycle and compensation records where possible:

• A hire comes from the approved employee start and status data.
• A leaver comes from the effective departure record.
• A salary change comes from the approved compensation change.
• A department or entity change comes from the effective employee work record.

This makes the report a review surface rather than a second data-entry system.

Add a validation queue

Before sign-off, run deterministic checks:

• Effective date falls in the selected period.
• Employee identifier is present and unique where required.
• Payroll group is assigned.
• New starters have the agreed minimum payroll fields.
• Leaver dates are complete and consistent.
• Compensation changes include the approved amount, currency, frequency, and effective date.
• Organization values match the current approved list.
• No change remains in draft or unapproved status.

Separate blocking errors from warnings. A missing payroll identifier may block processing; an optional reporting dimension may only require follow-up.

Use a two-stage review

HR review

HR confirms the employee event, effective date, source record, and internal approval.

Payroll or finance review

The receiving owner confirms the report is complete for processing, raises exceptions, and records acceptance. This is a handoff control, not permission for payroll users to rewrite the HR source record without an agreed correction process.

Reconcile after payroll

The process is not complete when the file is sent. After the run:

• Confirm every submitted change was processed, rejected, or deferred.
• Record provider or payroll exceptions.
• Correct the canonical source where the original HR data was wrong.
• Keep the final submitted output and sign-off according to the approved retention policy.
• Feed recurring failure reasons back into onboarding, offboarding, and compensation workflows.

Monthly sign-off checklist

• [ ] Period and cut-off confirmed
• [ ] Starters and leavers reconciled
• [ ] Approved compensation changes included
• [ ] Organization and payroll-group changes included
• [ ] Missing-field checks resolved
• [ ] HR owner signed off
• [ ] Payroll or finance owner accepted the handoff
• [ ] Late changes recorded as exceptions
• [ ] Post-payroll reconciliation completed

SalsaHR’s payroll-ready reporting workspace brings lifecycle changes, compensation records, finance dimensions, and controlled exports into one reviewable handoff. SalsaHR does not process payroll, calculate taxes, or file returns.