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

An HR shared service centre that supports Australian entities alongside other countries can run one document validation standard if it separates what is common (the fields compared, the outcomes, the escalation path) from what is local (the identifier, the official check, the deadline). The common part is written once. The Australian part is a one-page annex owned by someone who knows the Australian rules. This guide builds both halves and shows where the Australian mechanisms, VEVO, the Tax File Number declaration and the Privacy Act 1988, fit into the cross-checks.

Why does one standard break down across subsidiaries?

Most shared service centres inherit as many validation habits as they have subsidiaries. The Sydney team checks visa work conditions, the London team checks a share code result, the Paris team checks a hiring declaration receipt, and each treats everything else as optional. When files move to a central team, each reviewer applies the habit they learned first. Two near-identical files get different decisions depending on who opens them.

The symptoms are easy to spot:

• 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 marked "checked" without anyone writing down which field was compared with which other source;
• local rules accumulate in the global policy until it is a 60-page document nobody opens.

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

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

The core defines the comparison and the outcome; the annex names the Australian document or official check that supplies the value. If the core says "the tax identifier on the declaration must match payroll master data", the Australian annex says that this is the Tax File Number (TFN).

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 given more than four outcomes will 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 an Australian payslip; a rule that rejects it buries reviewers in false alarms.

What does Australia add?

Australia's mechanisms each prove something narrow, and none of them proves that a document is genuine. They show an entitlement on a government record, a declaration lodged for tax purposes, or the obligations that attach to personal information.

Work entitlement: VEVO

The Department of Home Affairs offers the free Visa Entitlement Verification Online (VEVO) service. According to its employer guidance, employers should check a potential employee's visa work conditions through VEVO and must obtain the visa holder's permission first. Hiring someone without a valid visa, or against their visa conditions, is against the law.

Two limits matter for the standard. First, per the Home Affairs VEVO page and overview, VEVO covers only the visa that is currently in effect; for example, a person on a bridging visa while a substantive visa is still running needs a careful manual look. Second, VEVO shows the department's record of entitlement and conditions on the day of the check. It does not tell you that the passport the person showed you is genuine, so comparison #1 (name) and #3 (expiry and conditions against the contract) still apply. Keep the result and the date with the file.

Tax and super: the TFN declaration

For tax, a new employee completes a tax file number declaration. ATO guidance describes the timing: if the employee does not give you a valid declaration within 14 days of starting, you must complete one with the details you have and send it to the ATO. If the employee has applied for a TFN, they have 28 days to provide it, and withholding at the top rate plus Medicare applies if it is still missing. A TFN you receive must also go to the employee's super fund, and for a new employee the ATO asks for this more than 14 days before the first super contribution.

For a shared service, this gives three concrete comparisons. The TFN on the declaration must match payroll master data (#5). The name and date of birth on the declaration must match the identity document (#1 and #2). The employee's super fund details must be those the employee supplied, not those inherited from a previous entity. A TFN declaration is the employee's statement to their employer and the ATO; it is not an ATO confirmation that the number is valid and belongs to that person, so a mismatch is a reason to ask, not to accuse.

Personal information: the Privacy Act 1988 and the APPs

An HR shared service handles passports, visa records and tax numbers, so privacy law governs the workflow, not only the HR policy. The Office of the Australian Information Commissioner describes the 13 Australian Privacy Principles as the cornerstone of the Privacy Act 1988 framework, covering collection, use and disclosure, governance, integrity and correction, and access. They apply to any organisation or agency the Act covers. If a central team in another country opens the Australian entity's files, check how the Act's cross-border disclosure rules apply before the first file moves, and ask counsel to confirm whether the employee records exemption affects your position, because that is a legal question this guide does not settle.

What do forums say about running this across countries?

People who run HR operations for several entities ask the same questions repeatedly, 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 UK-style right to work copy is not an Australian requirement, but comparing the visa expiry with 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. Access roles, the purpose of access and the disclosure basis must be set before the first file moves. Under the GDPR, Regulation (EU) 2016/679, European entities have their own rules, so the annexes will differ.

"What do we do when two documents disagree and the employee has already started?" Users on HR forums often describe a dead end in which 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. For the TFN, the ATO's own 14-day and 28-day windows are a natural anchor.

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 account holder against the employee (#6) and the TFN against payroll data (#5). Run them in parallel with the old process for one pay cycle, compare 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, Australia included, to write its annex on a single page: identifier, official check, deadline, retention period.
3. Run the checks on the last 50 files from each entity to see 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, visa records, 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 entitlement, 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 official check. In Australia those are the TFN and VEVO.

Does a VEVO result prove a document is genuine?

No. VEVO shows the Department of Home Affairs record of the visa currently in effect and its conditions, with the visa holder's permission. It does not confirm that the passport or image you hold is authentic, so it complements the field comparisons rather than replacing them.

What happens if an employee does not provide a TFN?

According to the ATO, if no valid declaration arrives within 14 days of starting, the employer completes one with the details it has and sends it to the ATO. If the employee has applied for a TFN they have 28 days, after which withholding at the top rate plus Medicare applies.

Where should the shared service start?

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