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. Check current rules with a qualified professional before applying them to an individual file.

An 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 identifier, the register, the legal deadline). The common part is written once and applied everywhere. 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 cross-checks that matter in the UK, France and Germany.

Why does one standard break down across subsidiaries?

Most shared service centres inherit as many validation habits as they have subsidiaries. The French team checks the registration receipt, the German team checks the tax and social security numbers, the UK team checks the right to work result, and each treats anything else as optional. When files move to a central team, the reviewers apply whichever habit they learned first, and two identical files get different decisions depending on who opens them.

The typical 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 document or register that supplies the value. If the core says "the identifier on the tax document must match payroll master data", the annex says that in Germany this is the Steuer-ID and in the UK it is the National Insurance number.

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 human 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 and the order of given names count as a mismatch. "Müller" against "Mueller" is the same person in a German passport and a Dutch payslip; a rule that rejects it will bury reviewers in false alarms.

What does each country add? UK, France and Germany

Each market has its own official mechanism, and each proves something narrow. None of them proves that a document is genuine; they prove that an entitlement or a registration exists, or that a number is the one assigned to a person.

United Kingdom: right to work

In the UK, an employer must check the applicant's right to work and keep a copy. GOV.UK says to confirm that documents are genuine and unchanged, that they belong to the person, that photos and dates of birth match, and to record the date of the check. For non-British and non-Irish citizens the online check uses a share code. Copies are kept for the length of employment plus 2 years.

The legal incentive is the civil penalty regime: under section 15 of the Immigration, Asylum and Nationality Act 2006, an employer who employs someone without the right to work can be fined unless it carried out the prescribed checks. The share code result proves the Home Office's record of entitlement on the day of the check. It does not replace comparison #1 (name) and #3 (expiry against the contract).

France: DPAE and registre unique du personnel

French law requires a named declaration to the social protection bodies before hiring: article L1221-10 of the Code du travail provides that an employee can only be hired after the employer has made this declaration (the DPAE). Employers also keep the registre unique du personnel, and article D1221-23 lists entries that include nationality, date of birth, job, qualification, entry and exit dates and, for foreign workers, the type and number of the document that serves as a work authorisation.

This gives the shared service two concrete comparisons. The start date on the contract must agree with the DPAE receipt (check #4) and with the entry date in the register. The permit type and number on the residence document must agree with the register entry (check #3 extended). A register is an internal record: it shows what the employer wrote down, not that the permit is valid.

Germany: Sozialversicherungsnummer and Steuer-ID

Germany uses two different numbers and a file should never confuse them. The Steuer-ID is, according to the Bundeszentralamt für Steuern, an eleven-digit number assigned permanently to one person; it does not change after a move, a name change or a change of marital status. The Sozialversicherungsnummer is assigned by the pension insurance and, as the AOK explains for employers, must be stated in every social security notification so the notification can be matched to the person; if it is missing, the employer queries the pension insurance.

For comparison #5, the Steuer-ID on the tax document is matched with payroll master data, and the Sozialversicherungsnummer on the insurance document is matched with the notification. Statutory insurers describe the number as embedding the holder's date of birth, which makes it a natural partner for comparison #2: a date of birth that disagrees with the number's own date segment is a data entry error to investigate, not a reason to reject the person.

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, not a legal requirement. A UK-style right to work copy is not required in Germany, but the permit expiry comparison is useful in all countries and costs nothing.

"Who is allowed to see the documents in another country?" This is a data protection question, not a workflow one. Under the GDPR, Regulation (EU) 2016/679, a central team in another country receives personal data under the controller's instructions, so the transfer basis and access roles must be set before the first file moves. In the UK, the ICO provides the equivalent guidance.

"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.

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 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: identifier, register, 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 certificates 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, right to work, 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 documents 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 identifier and register.

Does a register or share code lookup prove a document is genuine?

No. A share code result shows the Home Office record of entitlement, and a registration receipt shows a declaration was made. Neither confirms that the paper or image you hold is authentic, so they complement the field comparisons rather than replace them.

How long should the validation evidence be kept?

Follow the local rule: in the UK, right to work copies are kept for the employment plus 2 years according to GOV.UK. Other countries set their own periods in the annex, and the GDPR requires storage limitation for EU entities.

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.