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

A Canadian HR shared service centre can run one document validation standard across every subsidiary and province if it separates what is common (the fields compared, the outcomes, the escalation path) from what is local (the identifier, the official source, the legal deadline). The common part is written once. The local part is a short annex per country, and in Canada often a short annex per province, owned by someone who knows those rules. This guide shows how to build both, with the cross-checks that matter when files carry a Social Insurance Number, a work permit and a bank certificate.

Why does one standard break down across subsidiaries?

Most shared service centres inherit as many validation habits as they have subsidiaries. One entity checks the SIN against payroll, another only collects a void cheque, a third accepts a photo of a permit with no expiry date recorded. 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 entity 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;
• local 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 official source that supplies the value. If the core says "the identifier on the tax or social document must match payroll master data", the Canadian annex says that this identifier is the Social Insurance Number, and the German annex says it is the Steuer-ID.

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. "Françoise Côté" and "Francoise Cote" are the same person on a Quebec driver's licence and a payslip typed in a system without accents; a rule that rejects it will bury reviewers in false alarms.

What does Canada add to the core?

Canada supplies two concrete anchors for the cross-checks, the SIN and the work permit, and each proves something narrow. Neither proves that the paper or image in front of you is genuine. They establish that a number exists for a person and that an entitlement had an end date on a given day.

The Social Insurance Number

Employers must collect the SIN and handle it with care. According to Service Canada's employer guidance on the SIN, an employer should request each new employee's SIN within three days after the day employment begins, and SINs should only be used for income-related information. The same page explains that SINs beginning with a "9" are issued to temporary workers who are neither Canadian citizens nor permanent residents, and that they are valid only until the expiry date of the employee's immigration document.

That gives the shared service three precise comparisons:

• the SIN supplied by the employee against the number in payroll (check #5);
• for a number starting with 9, the expiry date of the SIN against the expiry date of the work permit (check #3);
• the date the SIN was requested against the first day worked (check #4).

The same guidance tells employers to ask to see the immigration document, such as a work or study permit, and check its expiry date, and to verify the new document once Immigration, Refugees and Citizenship Canada (IRCC) decides a renewal. A temporary resident with a pending renewal may have maintained status while IRCC decides, so an expired permit is an escalation, not an automatic stop. The SIN matching a name proves a number was issued; it does not prove who is presenting it.

The tax and payroll side

The Canada Revenue Agency publishes the TD1 personal tax credits return by pay year, with separate versions for 2025 and 2026 pay. For the shared service, the practical point is version control: a TD1 completed for the wrong year or the wrong jurisdiction is a mismatch of its own, and the reviewer should compare the form's year with the pay date before it reaches payroll.

Privacy: PIPEDA and the provincial regimes

Where a UK article would cite the ICO and the UK GDPR, the Canadian annex starts from PIPEDA. The Office of the Privacy Commissioner of Canada states that PIPEDA applies to private-sector organizations across Canada that handle personal information in commercial activity, that it applies to the personal information of employees of federally regulated businesses, and that Alberta, British Columbia and Quebec have provincial laws deemed substantially similar. In Quebec, the private-sector law has been amended by Law 25, so a Quebec subsidiary needs its own annex.

For a multi-country group, the consequence is simple: the privacy basis for moving a Canadian employee's file to a central team differs by province and by whether the employer is federally regulated. Settle that before the first file moves, and list it in the annex.

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. The three-day SIN request is a Canadian rule, but the comparison of permit expiry against the contract end date is useful in every country and costs nothing.

"Who is allowed to see the documents in another country?" This is a privacy question, not a workflow one. For a Canadian file seen by a team abroad, the annex should say which regime applies (PIPEDA or a provincial law) and who has access. Under the GDPR, Regulation (EU) 2016/679, the same exercise applies in reverse for European files handled from Canada.

"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 or province. 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, and each Canadian province where rules differ, to write its annex on a single page: identifier, official source, 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, work 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. Data handling is described on the security page.

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 and permits, see diploma and right-to-work verification.

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 documents differ by country, province and role. What should be identical is the list of comparisons and the possible outcomes, with each annex naming its own identifier and official source.

Does a SIN or permit check prove a document is genuine?

No. A SIN shows that a number was issued, and a permit expiry date shows the end of an entitlement on the document. Neither confirms that the paper or image you hold is authentic, so they complement the field comparisons rather than replace them.

What should we check on a 9-series SIN?

According to Service Canada, a SIN beginning with 9 expires with the employee's immigration document. Compare the SIN expiry date with the permit expiry date, and set a re-check before either date passes.

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.