Pilot site attendance to payroll with a correction trail

Choose one employer or clearly governed payroll population, a limited number of sites and a known shift pattern. Record who is included, how transfers and agency changes are handled, and which payroll period is being tested. A mixed population with different employers and rules can obscure whether the mapping is correct.

HR owns identity and employment/assignment history. Site reviewers own attendance evidence. Payroll owns calculation rules, cutoff handling and pay-run approval. The integration owner manages interfaces, rejected records and recovery. The privacy and security owners review the data flow and access.

Keep the first output as a validated import file or draft batch. The payroll reviewer checks totals and exceptions before accepting it. Automatic pay-run release or payment is outside this proposed first scope.

The raw attendance feed may contain more personal data than payroll requires. Define the minimum exported fields. A payroll import normally needs the approved input and its reference, not a copy of every photograph, location point or device credential.

Frappe HR’s check-in documentation illustrates separating captured events from attendance records. Verify how the actual installed systems expose approval status and corrections before defining the export.

Illustrative example: a September attendance record for worker W-104 has a missing check-out. The source records the case for review. Payroll processes September under the authorised treatment for that unresolved case. On 3 October, the supervisor accepts supporting evidence and approves the corrected attendance input.

The integration should preserve the original September export and create a linked correction case. Payroll determines the lawful and policy-compliant adjustment route and timing. The pilot must not assume the correction can wait indefinitely, automatically reopen a closed pay run or silently replace the historical input.

The correction record should show the original input, approved revised input, difference, reviewer, decision date, affected period and payroll disposition. The worker or authorised representative should be able to receive a clear status through the established HR process.

Agree whether the target accepts a replacement value or a difference. In a synthetic test, a reviewed input changes from four hours to eight hours under the population's approved rules. A replacement field receives eight; an additive adjustment receives plus four. Sending eight as an addition would produce twelve. This tests import meaning, not a rule for payable hours or a decision about how a closed pay run should be amended.

Now retry the correction import after a connection timeout. The payroll side should not accept the same adjustment twice. Use the accepted target reference or a stable batch/record identity to verify the outcome before retrying. Safe retry design provides the underlying principle; the business test is one approved correction with one explained payroll effect.

Before import, compare included workers, shifts, approved input totals and excluded exceptions with the source. After import, reconcile accepted and rejected rows to target references. A matching grand total can still hide two workers receiving each other’s inputs, so verify identity and record-level mapping as well.

Keep rejected rows in an owned queue. An unknown worker ID should not be mapped by a name guess. A missing approval should not be converted to absence. A conflicting site assignment should return to HR or the site reviewer with the relevant evidence.

Use a manifest for each batch: period, included population, source cutoff, record count, approval reference and export identity. If a file is regenerated, distinguish an exact replay from a revised batch. The reviewer needs to know which version payroll accepted.

The payroll and labour specialists should validate employer responsibility, appropriate government, applicable state/sector requirements, wage and overtime treatment, and record obligations. The OSHWC Central Rules, 2026 include record provisions in rule 72; applicability to the pilot population needs qualified review.

Do not hardcode a universal working day, overtime threshold or deduction rule into an integration specification. The connector should carry validated inputs to the authorised payroll configuration. If the configuration itself is wrong, moving data accurately will not fix the pay result.

Privacy review should cover access, retention, worker information, processors and applicable commencement dates of relevant requirements. Give site reviewers only the payroll information needed to resolve their cases. Restrict exports and avoid putting personal records in general integration logs.

Baseline the time spent preparing attendance inputs, resolving rejected imports, correcting identities and processing late changes. Include unresolved cases and worker follow-ups. Compare the same population and period definitions during the pilot.

Acceptance should require complete traceability for exported records, no duplicate accepted input or adjustment, and no payroll action without the required approval. Agree any efficiency target after measuring the baseline. Run at least one reviewed payroll cycle and a controlled late-correction exercise before considering expansion.

Stop expansion for wrong-person mapping, duplicate payroll effect, unauthorised disclosure or approval bypass. Pause affected exports and retain manifests, source snapshots and target receipts. Payroll should assess any accepted records and use its approved correction process; deleting an integration batch does not reverse a pay run.

Return to the established reviewed input process while the issue is repaired. Preserve pending worker corrections and assign a named owner so recovery does not strand them. Resume only after HR and payroll reconcile the affected population and the failed scenario passes again.

Isolate the affected records or batch where practical. Stopping a connector must not silently stop the organisation's payroll obligations. The payroll owner should activate the authorised fallback, reconcile unaffected inputs and arrange timely treatment of unresolved cases under the applicable requirements.

1. Define one population, its owners and its cutoff rules.
2. Reconcile identities and baseline the current preparation/correction effort.
3. Test the late correction, duplicate import and partial failure cases.
4. Run a reviewed live batch with row-level reconciliation.
5. Expand only after payroll accepts both ordinary inputs and the correction trail.

To scope the payroll handover, describe the workforce population, sites, attendance and payroll systems, and how late corrections are handled today. Use an anonymised correction scenario for the initial discussion.