A payroll change may look like one amount in one cell, but it affects employee data, the pay period, approval records, and payment files. When spreadsheets hold different versions, an administrator may enter an outdated figure and a reviewer may not know whether it was approved. A reliable process links each change to its evidence, effective period, independent review, payment-batch reconciliation, and preserved versions. This guide follows a general workflow from request through payment. Set roles and deadlines to match company authority and payroll cycles. Record approval, entry, and payment-batch dates separately: they show when a decision was made, when data was entered, and which payment run it affects.
What evidence should accompany a payroll change?
Evidence should explain why the amount is changing, who requested it, and where the information came from. Classify base salary, allowances, bonuses, deductions, and role changes under internal approval rules. Use a retrievable source for each, such as an approved personnel notice, employment-term amendment, manager-approved bonus detail, or employee-confirmed correction request. A verbal message or chat screenshot may be a lead; if used as formal support, record the requester, approver, date, and change, and retain the original.
At intake, capture six fields: before, after, reason, effective date, evidence file, and requester and approver. Keep them consistent in the source document and payroll entry. For a one-time bonus, record its calculation period, amount unit, and one-time status. For recurring pay, identify the period covered by the new amount so a single payment is not set to recur.
For a transport allowance correction, attach the original notice or other evidence of the correct amount, and identify the current record, corrected record, and affected month. Check the source and employee; return discrepancies for completion. “The manager knows” is not evidence, and do not guess a missing effective date. Mark incomplete changes pending and keep them off the payment list. Name files with a change ID, employee identifier, and version date. Store personal data in a controlled location; use only a case ID and link in notifications.
How should the effective date align with the pay period?
Record the date in the source document, the company-confirmed effective date, applicable start and end dates, and the calculation run. For a monthly cycle, apply the company’s approved rule for full or partial periods. The reviewer should see that rule and its source, not just a prorated result; no jurisdiction-specific statutory method is assumed here.
For changes after cutoff, mid-period, or across months, check whether the period is locked, the payment file exported, and the change assigned to this run or the next. For a closed period, show the difference, period, person who calculated it, and approval separately instead of overwriting the original salary. Retain any manual proration formula, day-count basis, and rounding method so the reviewer can recalculate it.
Assume monthly salary changes from 40,000 to 44,000, effective June 16, within an internal cycle from the first through the last day of each month. This example illustrates recordkeeping, not a universal statutory formula. Confirm the company’s mid-month rule, then record the old and new amounts, their applicable periods, and the June calculation. The reviewer checks the total against the approved method and confirms that July carries only 44,000. If the document says only “from June,” return it for clarification rather than guessing. Set internal deadlines for receiving changes, review, and freezing the payment list. If approval comes after the freeze, record whether it moves to the next batch.
Who should review a change in amount?
The requester supplies evidence, the data-entry person enters the approved terms, and the reviewer checks the source, calculation, and payment-list result. A small team may combine roles, but it should record who performed each task and when; an authorized person still gives final approval. If full separation is not possible, a second manager can review high-impact changes, with that limitation recorded. Dual review means the second person can independently inspect evidence and recalculate.
Check the employee identifier, item category, before-and-after amounts, effective period, calculation, duplicate entries, and payroll-system result against the approved version. Open the source and change record directly. For missing information, identify the missing field, who must supply it, and the paused status; “reviewed” alone is not a conclusion.
For a manager-approved monthly allowance increase of 1,200, confirm it is recurring, check the difference, date, and employee ID, and verify it appears once on the list. A wrong employee ID blocks release even if the amount is right. Record reviewer, time, version, and result; review every resubmission anew. If the reviewer can edit payroll, keep approval and editing as separate recorded actions. A spot check of an unchanged item can catch unintended import changes.
How should urgent changes receive later approval?
Urgent cases may involve missing documents, an approaching deadline, or an unavailable approval route. Later approval must complete the decision trail, not justify a payment after the fact. Define eligible change types, amount or risk thresholds, substitute approvers, maximum pending time, and items that cannot enter a payment batch first. Without clear authority, pause the update and refer it to a manager.
Record the request time, requester, employee, item, amount or calculation, effective period, missing documents, temporary approver, and reason. Obtain a clear, retainable decision from an identifiable approver, then mark the change temporary and list outstanding items. A verbal approval may create a follow-up task, but request written confirmation before recording it as formal approval. Urgency does not remove dual review: a second person should confirm the entry stays within the temporary approval.
For example, a payment list is close to lock and a manager has confirmed a shift allowance, but its written detail is pending. Limit the amount and period; the payroll owner checks whether internal rules permit temporary processing. Otherwise keep it pending and out of the batch. When the document arrives, compare it with the temporary approval and record its date, version, and closure status. A changed amount or effective date is a new version requiring approval. Assign an owner to resolve overdue temporary statuses under internal rules.
How should the list be reconciled with the payment batch?
Compare approved changes, payroll entries, and the payment export using one traceable process. Identify the batch cutoff version and freeze a list with employee ID, pay item, period, approved amount, calculated amount, and payment status. Check headcount, each person’s items, and the total. A matching total is insufficient: an overpayment and an omission can cancel each other. Fix comparison fields and discrepancy owners in advance.
Group results as approved and entered consistently; listed without approval; or approved but absent from payment data. Match employee and bank-recipient identifiers, not names alone. If a batch is exported but not submitted, follow internal payment controls to determine whether it can be withdrawn or rebuilt. If already submitted, retain its batch ID and have the responsible person determine the correction process. Do not alter the original file and erase the comparison basis.
Assume the list and export each contain 12 employees. Comparison finds an approved allowance increase of 800 that was not entered and a former employee still on the list. Equal counts do not prove a match, and do not offset the 800 against the other discrepancy. Confirm the approval version, employee status, and whether the batch can change; assign both items for resolution. Afterward, someone who did not enter the data confirms count, individual amounts, and total, and records the file version and release time. After payment, archive the final list with the approval register.
How should corrections preserve before-and-after versions?
Give each change a unique ID and retain its request, approval evidence, pre- and post-entry data, calculation basis, review record, and payment-batch link. Keep supplements and returns under that ID, but assign each submission a new version number and date. The history should show who requested, approved, changed, reviewed, and released each item, when, and which field changed.
Do not overwrite the original row. Record when and how the discrepancy was found, the affected version, and the reason; obtain required approval, then add a correction version identifying what it replaces and the pay period it affects. If an already-paid period is affected, list the difference, period, and pending decision separately for an authorized person. Do not delete the original payment record. Limit access, keep personal data out of unrelated messages, and set retention and deletion under company policy and applicable requirements rather than assuming a fixed period.
For example, assume the June allowance was entered as 1,500 but the approved amount is 1,050: the difference is 1,500 − 1,050 = 450. These figures illustrate the arithmetic only. Preserve both amounts, the source link, whether the amount reached the payment file, and who confirmed the handling. Link the correction, second review, and replacement batch or final status so the incorrect value is not loaded again.
To apply this workflow, trace a recent payroll change from request and approval through effective date, entry, and payment. If your company is also mapping cross-border operations through a Hong Kong company, visit the Chan & Chung homepage.