Outsource Payroll CompanyPowered by StealthAgents
Table of contents
  1. What to keep in the plan
  2. Payroll handoff readiness check
  3. Freeze the export before comparing totals
  4. Match employees and earning codes separately
  5. Give every difference a named cause
  6. Correct the source, then re-import once
  7. Close with a repeatable reconciliation note
  8. Related articles
  9. Payroll support role brief
  10. Questions from payroll buyers
  11. Sources

Outsource Payroll Company guide

Reconcile Imported Payroll Hours Against the Timekeeping Export

A payroll import can complete without error and still carry the wrong hours. Compare the export, the import, and the register by employee, period, and earning code before anyone approves the run.

Payroll handoff readiness check

Use this table before a provider or Filipino payroll support worker receives access.

Work areaReady to hand off whenOwner check
Export versionthe file name, run time, and hash are recordedpayroll owner confirms the export is the final version
Employee matchevery employee in the export appears once in the importpreparer checks headcount and employee identifiers
Earning-code matchregular, overtime, and other hours reconcile separatelyreviewer compares code totals, not just gross hours
Difference logevery variance has a cause, owner, and correctionowner approves each correction before re-import
Close notebefore-and-after totals and the reviewer name are storedowner signs the reconciliation note

Freeze the export before comparing totals

An import reconciliation starts with a stable file. Ask the timekeeping owner to confirm the export is final, then record the file name, run time, and row count in the reconciliation note. Save a read-only copy in the payroll evidence folder so the comparison can be repeated later. If the source system can still change the file, the comparison has no fixed baseline. Freeze first, then compare.

Treat a late correction as a new export rather than an edit to the old one. Give the replacement file a new version label and keep both versions in the folder. Note why the first export was replaced and who requested the change. A reviewer should be able to see which file fed the payroll import. An unlabeled overwrite destroys the audit trail before the work begins.

Match employees and earning codes separately

Compare headcount before comparing dollars or hours. Confirm that every employee in the export appears once in the import and that no employee appears twice. Check employee identifiers rather than names, since duplicate names are common. Record any employee who was added, removed, or left inactive between the export and the import. A headcount difference explains many downstream variances.

Reconcile each earning code on its own instead of comparing gross hours. Regular, overtime, holiday, sick, and bonus hours can offset each other and produce a total that looks correct. Compare code by code and flag any code that appears in one file but not the other. Ask whether a missing code is a mapping problem or a genuine zero. Code-level matching finds errors that a gross total hides.

Give every difference a named cause

A variance without a cause is an open item, not a rounding issue. Write the employee, period, code, export value, import value, and difference in one line. Name the likely cause, such as a mapping rule, a duplicate row, a late edit, or an unsupported earning code. Assign the person who will confirm or correct it. Keep the line open until the cause is proven, not just explained.

Separate timing differences from true errors. A shift that crosses the pay period boundary may belong to the next run, while a missing overtime code is usually a mapping defect. Ask the timekeeping owner to confirm boundary rules in writing. Do not net a timing difference against an unrelated error to make the total match. Each explanation should stand on its own.

Correct the source, then re-import once

Fix the export or the mapping rule before running the import again. A manual adjustment inside payroll hides the source defect and creates a second record to reconcile. Document the correction in the source system or the mapping table, then produce a fresh export. Re-import from that file and keep the prior import result for comparison. One controlled re-import is easier to review than several small patches.

Re-run the same employee and code checks after the correction. Confirm that the fix changed the intended rows and did not create a new difference elsewhere. Compare the before-and-after totals and record the delta. If the correction touches a live pay run, ask the payroll owner to approve the new file before release. A second import without a second check repeats the original risk.

Close with a repeatable reconciliation note

Close the reconciliation only when the export, the import, and the payroll register agree. State the file versions, the employee count, the code totals, and every resolved difference. Name the preparer and the reviewer and record the date of the check. Store the note with the register and the source files. A reader should be able to repeat the comparison without asking for context.

Add one control change if the same cause appears twice. A recurring mapping error needs a rule update, not another manual fix. A late export needs a cutoff reminder on the timekeeping calendar. Assign the change to a role and set a review date. The reconciliation closes one cycle, while the change protects the next one.

Continue the workflow with operations support and reporting and QA support. For the access principle behind this routine, review NIST Zero Trust Architecture.

Related articles

Copy-ready brief

Payroll support role brief

Replace the tool names and owner details, then use this list in a provider call or job brief.

  • Role: Payroll hours import reconciler
  • First task lane: Compare the frozen timekeeping export with the payroll import and log differences
  • Tools: Timekeeping export, payroll import report, register, reconciliation tracker, evidence folder
  • Access: Read-only access to timekeeping and payroll, write access to the tracker only
  • Daily output: Employee and code match report, open difference list, and correction notes
  • Stop rules: No manual pay adjustment, no re-import, and no rate change without the payroll owner
  • Owner review: Payroll owner approves corrections and signs the close note

Questions from payroll buyers

Can we reconcile after the payroll run is approved?

Reconcile before approval, because a correction after release becomes an off-cycle adjustment. If the run is already approved, document the gap and treat the fix as a separate controlled event.

What if the timekeeping system cannot produce a stable export?

Record the export time and row count, then ask the system owner to lock the period. If the file can still change, label each version and compare the version that actually fed payroll.

How many differences should trigger a full re-check?

Any difference in employee count or in a paid earning code deserves a full re-check. A small number of explained timing differences can close with a note and reviewer approval.

Sources

  1. DOL Wage and Hour Division, FLSA Recordkeeping Fact SheetEmployers must keep payroll records that show hours worked and wages paid.
  2. DOL Wage and Hour Division, Hours Worked Fact SheetDefines hours worked and the records that support pay calculations.
  3. NIST Special Publication 800-53 Revision 5Control guidance for protecting payroll records and system activity.
  4. SBA: Manage your businessPractical guidance on payroll, recordkeeping, and small-business operations.

Philippines staffing

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to shape a practical Philippines staffing request.

Contact Us