Start here
Five rules for a safe first handoff
- Qualify the duplicate signal before changing either record
- Stabilize payroll without destroying evidence
- Trace creation events and downstream consumption
- Separate the identity resolution from financial correction
Task map
Split admin work from owner decisions
| Work lane | Philippines team | Company owner | Useful check |
|---|---|---|---|
| Qualify the duplicate signal before changing either record | Prepare and route the evidence for checkpoint 1. | Approve the decision described in “Qualify the duplicate signal before changing either record.” | Retain the source and destination result for checkpoint 1. |
| Stabilize payroll without destroying evidence | Prepare and route the evidence for checkpoint 2. | Approve the decision described in “Stabilize payroll without destroying evidence.” | Retain the source and destination result for checkpoint 2. |
| Trace creation events and downstream consumption | Prepare and route the evidence for checkpoint 3. | Approve the decision described in “Trace creation events and downstream consumption.” | Retain the source and destination result for checkpoint 3. |
| Separate the identity resolution from financial correction | Prepare and route the evidence for checkpoint 4. | Approve the decision described in “Separate the identity resolution from financial correction.” | Retain the source and destination result for checkpoint 4. |
Example pilot board
Use small numbers for the first review
Qualify the duplicate signal before changing either record
Start with the rule that raised the alert. Matching names, addresses, telephone numbers, bank accounts, email addresses, birth dates, government identifiers, or emergency contacts carry different confidence and risk. Shared households and recycled contact details can create false matches, while spelling changes and entity transfers can hide true ones. Record the compared fields and their sources without placing full sensitive values in a general queue. An alert should open a restricted review, not automatically select a surviving record.
Check worker ID, employing entity, employment periods, assignment, location, manager, payroll group, tax profile, and rehire links. Ask whether both records can legitimately be active. A person may hold concurrent roles or move between entities without either record being erroneous. If identity evidence conflicts, stop downstream edits. The support team may assemble a comparison, but the designated identity and HR owners decide whether the records relate to the same worker and which history must remain separately preserved.
Stabilize payroll without destroying evidence
Prevent unsupervised merges, deletions, status closures, bank changes, tax-profile replacement, or balance transfers while the review is open. Identify the next payroll cutoff and the runs in which each record appears. Payroll owners can decide whether to hold a transaction, continue an established record, or use another controlled path. A coordinator should not pick the record that looks newer or has cleaner fields, because that choice can redirect pay or alter statutory reporting.
Take a read-only snapshot of relevant identifiers, status, period totals, deductions, direct-deposit destination reference, and integration responses. Keep the snapshot in the approved restricted location. Record which automated jobs may create another change before cutoff. If payroll proceeds, document the owner’s instruction and later reconciliation requirement. The goal is to keep employees paid correctly without erasing the event chain needed to repair the source and every destination.
Trace creation events and downstream consumption
Follow each record backward through recruiting, onboarding, HRIS entry, imports, vendor feeds, acquisitions, entity transfers, and manual corrections. Determine whether a failed rehire link, delayed integration, changed name, or duplicate onboarding packet produced the condition. Then map where each identifier traveled: timekeeping, payroll, benefits, retirement, learning, access, directories, finance, and regulatory files. A source correction is incomplete if another destination still treats the duplicate as active.
A returning employee with a new ID and an old active record in another entity illustrates why chronology matters. The old record may represent a legitimate prior employment history, an active concurrent role, or an unclosed transfer. Preserve start and end dates, entity ownership, and approved transfer evidence. Ask one bounded identity question at a time. Do not rewrite dates or statuses to force the records into a simpler pattern before the qualified owner decides what occurred.
Separate the identity resolution from financial correction
Once owners determine the relationship, create a correction plan by destination and period. Reconcile hours, gross-to-net pay, deductions, taxes, benefits, retirement contributions, leave balances, costing, general-ledger output, and employee statements. Some items may require reversal and reissue; others may remain historically attached to an inactive identifier. Keep owner approval for each consequential step and retain the original values beside corrected values.
Close only when payroll control totals match, required destinations acknowledge the approved state, access is appropriate, and the employee-facing records are understandable. Notify the employee through approved wording if statements or identifiers change. Review why prevention failed—rehire matching, entity handoff, import control, or manual entry—and test the repair. The reader outcome is a duplicate review that protects identity and pay instead of trading a tidy database for an unreconstructable payroll history.
Copy-ready scripts
Make the stop points easy to say
Payroll hold question"Two records require identity review before the next cutoff. Please specify the controlled payroll path; no merge, deletion, or bank change has been made."
Resolution handoff"The authorized identity decision is recorded. Please reconcile the listed periods and destinations while preserving both original histories."
Launch path
A five-step HR outsourcing workflow
- 01
Qualify the duplicate signal before changing either record
Start with the rule that raised the alert.
- 02
Stabilize payroll without destroying evidence
Prevent unsupervised merges, deletions, status closures, bank changes, tax-profile replacement, or balance transfers while the review is open.
- 03
Trace creation events and downstream consumption
Follow each record backward through recruiting, onboarding, HRIS entry, imports, vendor feeds, acquisitions, entity transfers, and manual corrections.
- 04
Separate the identity resolution from financial correction
Once owners determine the relationship, create a correction plan by destination and period.
Buyer FAQ
HR outsourcing questions
Does a matching bank account prove a duplicate?
No. It is a sensitive signal requiring review, not a conclusive identity decision.
Should the older record be deleted?
Usually not. Owners must preserve required history and decide how inactive or corrected records remain linked.
Sources
Source notes
- U.S. Department of Labor RecordkeepingOfficial federal overview of employer wage and hour recordkeeping responsibilities.
- NIST Privacy FrameworkOfficial framework for accountable, purpose-based handling of personal data.