HR Shared Services Document Management: One Standard for Every Subsidiary

This article is provided for information only and is not legal advice. Regulatory references are accurate as of 2 November 2026 and describe US federal rules unless a state is named. Check current federal and state rules with qualified counsel before applying them to an individual file.

A US-headquartered HR shared service centre can run one document validation standard across every subsidiary if it separates what is common (the fields compared, the outcomes, the escalation path) from what is local (the form, the government record, the retention rule). The common part is written once. The local part is a short annex per country, owned by someone who knows that country's rules. This guide shows how to build both, with the US annex written around Form I-9, E-Verify and the tax withholding forms.

Why does one standard break down across subsidiaries?

Most shared service centres inherit as many validation habits as they have entities. The US team completes Form I-9 and reviews the supporting documents, a European team checks a national registration receipt, another checks a tax identifier, and each treats everything else as optional. When files move to a central team, reviewers apply whichever habit they learned first, and two identical files get different decisions depending on who opens them.

The symptoms are easy to recognise:

• the same mismatch (a surname spelt two ways) is accepted in one country and rejected in another;
• nobody records why a file was accepted, so an audit cannot reconstruct the decision;
• a document is "checked" without anyone writing down which field was compared with which other source;
• country rules creep into the global policy until it is a 60-page document nobody reads.

The fix is structural. A standard defines checks, not documents. A document is only the carrier of fields; the check is the comparison.

What belongs in the global core, and what in the country annex?

The core defines the comparison and the outcome; the annex names the local form or government record that supplies the value. If the core says "the identifier on the tax form must match payroll master data", the US annex says that the form is the W-4 and the identifier is the Social Security number, while another country's annex names its own.

Four outcomes are enough for every check: pass, request (ask the employee for a better or missing document), correct (the data entered is wrong, the document is right) and escalate (a person with authority decides). Reviewers who have more than four outcomes invent their own.

Which cross-checks should the core standard contain?

Six comparisons catch most inconsistencies in an onboarding file, and each names a field on one source and the field it must match on another.

A tolerance rule belongs in the core as well. Decide once whether accents, hyphens, suffixes such as "Jr." and the order of given names count as a mismatch. "Müller" against "Mueller" is the same person in a German passport and a US payroll record; a rule that rejects it will bury reviewers in false alarms.

What does the US annex add?

The US annex rests on three federal mechanisms, and each proves something narrow. None of them proves that a document is genuine. Form I-9 records an employer's examination, E-Verify compares entered data with government records, and the W-4 records the employee's withholding choices.

Form I-9: identity and employment authorization

According to USCIS, all US employers must properly complete Form I-9 for every individual they hire, to verify identity and employment authorization. The employee attests to their employment authorization in Section 1 and presents acceptable documents. In Section 2 the employer examines those documents to determine whether they reasonably appear to be genuine and relate to the employee, then records the document information. USCIS states that employers retain the form for three years after the date of hire, or one year after employment ends, whichever is later.

The wording matters for the shared service. "Reasonably appear to be genuine" is a standard of examination, not a forensic test, and the form proves that the examination took place. The cross-checks that follow from it are comparison #1 (the name on the documents against the name on the form and in payroll), #3 (the authorization expiry against the assignment length) and #4 (the dates recorded on the form against the first day worked). The deadline for each section is set out in USCIS guidance; write it into the annex after your counsel confirms the current rule for your case, rather than copying it from a summary.

E-Verify: comparing entered data with government records

E-Verify is an online service that checks information an employer enters from the employee's Form I-9 against records available to the Department of Homeland Security and the Social Security Administration. It is a comparison of data entered with data held by the government. It does not state that the paper or image you hold is authentic, and a mismatch result means the records did not match, not that the person has done anything wrong. The employer's next step on a mismatch is a procedure defined by the E-Verify program; the annex should link to it and name who runs it. Whether a particular subsidiary participates depends on state law and on federal contractor obligations, so the annex should record the answer per entity instead of assuming a single rule.

Form W-4 and the Social Security number

The IRS describes Form W-4 as the form an employee completes so that the employer can withhold the correct federal income tax from pay, and advises completing a new one each year and when personal or financial circumstances change. For the shared service, the W-4 is the source for comparison #5: the name and Social Security number on it must match payroll master data and the name on the identity documents. A W-4 that differs from payroll data does not prove misconduct; most mismatches are typing errors or a recent name change. Treat it as a "correct" or "request" outcome before anything else.

State rules and data protection

Employment rules differ by state, and so do privacy rules. California is the clearest example: the California Attorney General notes that the CCPA exemptions for employment-related personal information expired on 31 December 2022, so covered businesses owe notice at collection and respond to rights requests about employee data. The annex should list the state laws that apply to each US site. For the non-US entities in the group, the equivalent regimes sit in their own annexes.

What do forums say about running this across countries?

People who run HR operations for several entities ask the same questions again and again, and the answers shape the standard.

"Do we have to follow the strictest country everywhere?" No. Apply the strictest rule only when it is a comparison rather than a legal requirement. A US-style retained copy of the supporting documents is not required in every country, but the work authorization expiry comparison is useful in all of them and costs nothing.

"Who is allowed to see the documents in another country?" This is a data protection question, not a workflow one. A central team in another country must receive the data under written terms from the entity that collected it, with access limited to the roles that need it. Decide the transfer basis and the access roles before the first file moves.

"What do we do when two documents disagree and the employee is already working?" Users on HR forums often describe a dead end where payroll waits for HR and HR waits for the employee. The standard should state a deadline per outcome, for example five working days for a request, and name who escalates. It should also say that a request goes to every employee in the same way, to avoid treating people differently based on how a name or document looks.

How do you roll the standard out without stopping hiring?

Roll out by check, not by country. Start with the two comparisons that cost the most when they fail, usually the name on the bank account against the employee (#6) and the tax identifier against payroll data (#5). Run them in parallel with the old process for one pay cycle, compare the results, and only then switch the old process off.

A practical sequence:

1. Write the core as a one-page table like the one above.
2. Ask each country to write its annex on a single page: form, government record, deadline, retention period.
3. Run the checks on the last 50 files from each subsidiary to measure how many existing files would have failed.
4. Fix the tolerance rules based on the false alarms.
5. Move to live files, with the reviewer recording the outcome and the reason in the file.

Tools help with the repetitive part. CheckFile reads fields from identity documents, permits, tax forms and bank letters and lines them up for comparison; it supports more than 3,200 document types and OCR in 24 languages across 32 jurisdictions. The comparison result tells the reviewer where to look. It does not state that a document is authentic, and the decision stays with the reviewer. See the HR solution page for how this works in practice, and pricing for volumes.

Related reading

Start with the pillar guide on industry verification. For the contents of a single country's file, see personnel file requirements and cross-checks. For the pay-side checks, see bank details and tax ID validation before first payroll. For credentials, see diploma and right-to-work verification. Data handling is described on the security page.

Frequently Asked Questions

What is HR shared services document management?

It is the central handling of employee documents (identity, work authorization, tax, bank, contract) for several entities by one HR service team. The aim is one set of checks and one record, so a file gets the same decision whichever subsidiary it comes from.

Do all subsidiaries need the same documents?

No. The forms differ by country and role. What should be identical is the list of comparisons and the possible outcomes, with each country annex naming its own form, identifier and government record.

Does E-Verify or a completed Form I-9 prove a document is genuine?

No. Form I-9 records that the employer examined documents that reasonably appear to be genuine, and E-Verify compares entered data with government records. Neither confirms that the paper or image you hold is authentic, so they complement field comparisons rather than replace them.

How long should the validation evidence be kept?

For Form I-9, USCIS says three years after the date of hire or one year after employment ends, whichever is later. Other countries set their own periods in their annexes, and state privacy law may limit how long other employee data is stored.

Where should the shared service start?

With one or two comparisons that fail often, such as bank account holder against employee name. Prove the process on those, then add the remaining checks one at a time.