Research brief · Published
Payroll name and Social Security number match review
A review design for testing whether payroll identity data matches Social Security records before tax filings, with a controlled exception and correction path.

Research finding
Build the population from active and terminated employees with payroll in the period.
Methodology
This brief triangulates the headline measure against official Philippine government, regulatory, development, and labor sources. It translates evidence into an operating control and separates context from recommendations.
| Measure | Interpretation |
|---|---|
| Four identity fields tested per employee record. | Context signal for planning, not a promise about an individual worker or provider. |
| 4 source records | Primary source links are listed and numbered below for review. |
Key takeaways
- Build the population from active and terminated employees with payroll in the period.
- Test the name and number against an authoritative source before the filing deadline.
- Separate a formatting difference from an identity mismatch.
- Keep duplicate employee records in the population until they are merged or closed.
- Classify findings by whether a return was rejected or a wage record was misposted.
Question and scope
This review asks whether the employer can evidence that each payroll record carries the correct legal name and Social Security number. The scope covers employees with wages in the review period, including terminated employees who still need a W-2. The design tests identity data and the correction path, not the employee's eligibility to work. Record the review period, the entities covered, and the systems used for verification.
Population and unit
Build the population from the payroll register, the HR master file, and the prior year W-2 list. Include employees who were hired, terminated, or rehired during the period. The unit is one employee identity record. A population built only from active employees will miss a terminated worker whose W-2 was rejected. List the source file and extraction date for each record.
Authoritative employee record
Identify the system of record for the legal name and number. A self-service profile, a paper form, and a tax notice can disagree. Record which source the payroll team treats as authoritative and who can change it. A change made in one system without the others creates a mismatch. Test one record that was updated during the year. Record the last update date for the field.
Verification channels
Use the Social Security Administration's verification service or the agency's published process for the review. Record the date, the response, and the person who checked it. A verification response is evidence of a match at a point in time, not a permanent status. Do not store full numbers in an unprotected working file. Keep the result with the employee record.
Match keys beyond the number
Compare the legal name, the date of birth where available, and the employee identifier. A correct number with a misspelled name can still be rejected. A name change after marriage or a legal order needs a new source document. Test a hyphenated name and a suffix such as Junior. A match on the number alone is not enough for a clean review.
Exception categories
Separate a formatting difference from a true mismatch and a duplicate record. A missing digit, a transposed number, and an extra space have different fixes. A number that belongs to another person is a serious exception. Record the category, the evidence, and the owner for each exception. A generic error label hides the action required. Count each category separately in the report.
Name change handling
Confirm that a legal name change reached payroll before the next tax filing. The employee should provide a new Social Security card or an official document. Update the name in payroll, HR, and the provider system. Keep the source document with the change record. A name change applied to only one system creates a later rejection. Check the provider copy on the same day.
Duplicate identity
Search for employees who appear twice under different identifiers or name spellings. A rehire, a transfer, or a manual entry can create a second record. Compare the number, the name, and the bank destination. Merge or close the duplicate under an approved procedure. A duplicate that receives two W-2s is a finding even when the total pay is correct. Keep both records until the merge is approved.
Tax filing dependency
Check whether an unresolved mismatch will affect the next W-2, 941, or state return. A rejected W-2 can delay the employee's filing and create a penalty. Record the filing deadline and the correction window. Escalate a mismatch that cannot be resolved before the deadline. A late correction is better than no correction, but it still needs an owner. The filing owner should see the exception before the deadline.
Correction path
Define how a corrected W-2 or a revised payroll record is issued. Keep the original form, the correction request, and the new form together. Explain the change to the employee in plain language. Do not overwrite the original file. A correction that only changes the payroll system leaves the tax record wrong. A new form should reference the original in the file.
Provider and new-hire reporting
Check whether the payroll provider or a new-hire reporting vendor uses the same identity data. A mismatch can cause a rejected new-hire report as well as a rejected W-2. Test one provider record against the employer master. Record the correction and the confirmation. A provider that fixes its own copy may not fix the state filing. Confirm the state acknowledgment after the provider fix.
Access and privacy
Restrict access to full Social Security numbers and identity documents. Give support staff a masked value and an internal employee key. Keep the verification result in an approved system, not a shared spreadsheet. Remove temporary files after the correction is confirmed. A privacy lapse is a separate finding from a data mismatch. Review access to the file after the correction is closed.
Recertification cadence
Set a review cadence that matches the payroll and filing calendar. Test new hires before the first payroll, and test the full population before year-end. Rerun the check after a name change, a rehire, or a system migration. Record the date and the reviewer. A one-time cleanup does not prevent the next mismatch. Add the check to the first payroll of each quarter.
Evidence retention
Store the verification result, the exception record, and the correction evidence for the required period. Keep the evidence by employee and tax year. A confirmation that lives only in a portal session is not a record. Label the file with the review date and the source. The retention period should follow the tax and company rules. A reviewer should be able to find the record by employee identifier.
Employee self-service updates
Review how an employee change flows from self-service to payroll and the provider. A name or number update entered in one system can leave the others unchanged. Require a source document and a confirmation before the record is used for a filing. Test one self-service change during the period. Keep the confirmation and the source document with the employee record.
Termination and final form
Confirm that a terminated employee's identity data is checked before the final W-2 is issued. A wrong name or number is harder to correct after the employee leaves. Record the last known contact and the delivery method. Keep the final form and the verification together. Record the delivery method, the date the form was sent, and the confirmation that the employee received it.
Vendor data exchange
Map every file that carries the name and number between HR, payroll, and the provider. A field that is truncated in a fixed-width file can create a false mismatch. Test the file layout after a vendor change. Record the field length and the validation rule. Keep the layout version with the test result so the next vendor change can be compared.
Metric and reporting
Report the number of records tested, the exceptions by category, and the days to correction. A count of mismatches without an age measure hides a backlog. Show the trend by entity and source system. Give the owner a short list of records still open. Include the oldest open exception, its owner, and the next review date so the report leads to a decision rather than a count.
Owner escalation
Name the person who decides a disputed identity record and the backup who covers an absence. A support specialist can prepare the evidence but should not choose the legal name. Record the escalation date and the decision. A record that waits for an unavailable owner misses the filing. The decision should name the source document used and the date the record was corrected.
Sampling
Sample across entities, hire dates, and employment status. Include at least one new hire, one terminated employee, one name change, and one duplicate. Compare the sample with the full population. Record the selection rule so another reviewer can repeat the work. A sample of only clean records cannot show whether the control works. Include one record that was corrected during the period.
Findings and severity
Classify each finding by whether a tax form was rejected, whether wages were misposted, and how many periods are affected. A duplicate record that produced two W-2s is more severe than a formatting difference caught before filing. Tie each finding to an employee, a form, and a named owner. Rank the exposure by the filing deadline. Show the affected tax year beside each finding.
Limitations
The review depends on verification responses and source documents that may be delayed or incomplete. A name can change after the check, and a provider may correct its record without telling the employer. The design measures identity evidence, not legal status or tax liability. State these limits and separate observed mismatches from missing records. A missing response is not proof that the number is wrong.
Conclusion
Use the review to confirm that payroll identity data matches an authoritative source before each filing. Repair the source record, the provider copy, and the tax form together. Rerun the check after a hire, a name change, or a system change. The control is a current identity record, not a year-end scramble. Set the next review date and the event that will force an earlier rerun.
Sources
Prepare an identity match evidence pack
A Philippines-based payroll support specialist can build the employee population, run the verification queue, and prepare the exception list for owner review. The specialist can also maintain the correction log and the source-document index. Your payroll and tax owners still approve any change to an employee identity record or tax form.
Review payroll reporting supportFAQs
Is a name mismatch the same as a wrong number?
No. A misspelled name can often be fixed with a corrected record, while a number that belongs to another person is a serious identity exception. Separate the categories before assigning a correction. Keep the source document for each change. A generic error code hides the action required.
How often should the match be tested?
Test new hires before the first payroll and the full population before year-end. Rerun after a name change, a rehire, or a system migration. Record the date and the reviewer. A one-time cleanup does not prevent the next mismatch.
Can a provider fix the record for us?
The provider can update its copy, but the employer still owns the tax filing and the employee record. Confirm that the correction reached payroll and the state filing. Keep the confirmation. A provider fix that stops at its portal leaves the employer exposed.
For adjacent operating context, see Payroll Preparation and the payroll operations guide library.