Payroll Links
Part of Payroll software integration
Mapping employee changes into payroll systems
Define payroll events, effective dates, identifiers and correction rules before transferring employee changes.
Map an employee change as an approved event with an effective date, a stable employee identifier and a defined payroll effect. A field list alone is not enough: the same value can mean something different when it arrives late, replaces an earlier value, or applies to only part of a pay period.
Start with changes that can affect pay
Write an event catalogue with HR and payroll. For each change, identify the approval, the fields sent, the effective date and the person who checks the payroll outcome.
| Change | Mapping question |
|---|---|
| New starter | Which identity, commencement and employment details must payroll receive before the first pay is calculated? |
| Pay or hours change | Is the effective date distinct from when HR entered or approved the change? |
| Leave or absence | Does payroll need a transaction, a balance, a pay code or more than one of these? |
| Transfer or classification change | Which old value ends, which new value begins and who confirms the pay rule? |
| End of employment | Which final-period inputs and approvals are needed before payroll calculates the result? |
These are business events. A receiving product may import them as fields, transactions or files rather than separate messages; check its actual import specification.
Define the event contract
For each field, specify the source name, destination name, data type, permitted values and owner. Include a change identifier or other traceable reference so a reviewer can tell which approval payroll received. State how the interface treats a missing field, an explicit blank and a request to remove a value.
Keep the effective date separate from transmission time. If a pay change is approved after the period to which it applies, the interface can pass it, but a payroll reviewer must determine its pay effect and any correction.
If two approved changes affect the same field, define their order and preserve enough history to explain the result.
Map each time-system or HR pay-category code to the corresponding payroll code and calculation rule. A time-system label or HR classification is not a substitute for an award, agreement or other applicable pay rule. Check the applicable award or agreement when establishing pay due, and have a knowledgeable reviewer check the code dictionary and any linked calculation rule.
Trace one person across the systems
Use synthetic or appropriately protected records to test a starter followed by a mid-period hours change. Record the expected result before importing. Compare approved HR events with the outgoing payload, accepted payroll values and calculated pay. Then send a correction and check whether payroll replaces, adjusts or duplicates the earlier input.
The acceptance record should identify the employee, source change, effective date, approval, receiving status, payroll result and reviewer. If the product cannot display one of these, decide how to retain it elsewhere.
Retain the approved event and resulting payroll value with a traceable link, so reviewers can explain the current value and how it was derived.
