HR-Glossar

Schatten-Payroll (parallel payroll run)

What a parallel payroll run is, how it secures a change of provider or system and what makes such a run fail.

1. What is Schatten-Payroll (parallel payroll run)?

One point of terminology first, because this term means two different things. In international usage, "shadow payroll" almost always refers to the parallel tax calculation run for assignees working across borders. This entry describes something else: the German payroll practice of running a complete parallel calculation when changing provider or system.

A Schatten-Payroll in that sense is a complete payroll run alongside the real one – with the same data, in the new system or at the new provider, but without paying anything out and without filing any reports. Payments and reports continue to come from the old procedure.

The purpose is a reconciliation. Both runs are compared line by line: gross amounts, tax and contribution deductions, net pay, employer contributions, reporting data. Every deviation is traced to its cause – a master record carried over wrongly, a wage type coded differently, a collective rule interpreted differently, a missing allowance. Only when the results agree, or every remaining difference is explained, does the business move across.

The parallel run is therefore not a test in the sense of a sample but a complete proof: it shows not that the new procedure *can* calculate, but that it calculates the same thing for this business.

2. Origin and development

The parallel run is a pattern from system implementation: a new procedure runs alongside the old one for a time until it has proved itself. In payroll it carries particular weight, because the changeover date allows no indulgence – pay, tax and contributions fall due on fixed dates, and a missed payroll run cannot be made up without employees, the tax office and the health insurance funds noticing.

The changeover is the demonstrably most delicate phase of the cooperation. That is precisely why the parallel run has established itself as the standard approach and not as a special service for particularly large businesses.

3. Core principles and how it works

The same input data, separate systems

Both runs work with the same master and movement data for the payroll month. Only then is a deviation a finding and not merely a difference in what was entered.

Reconciliation at line level

What is compared is not the total but the composition. Two runs can arrive at the same net pay and still be wrong in different ways – where two errors cancel each other out, for instance.

Every difference is explained, not smoothed over

A deviation is traced to its cause and documented. Not every difference is an error in the new system – some uncover an old error, which then has to be decided on its merits.

The old run stays authoritative

Until the hand-over, only the old procedure pays and reports. The parallel run produces no payment, no report and no certificate – otherwise duplicate filings would arise.

No transition without agreement

The changeover date is the result of the reconciliation, not its precondition. A transition by acclamation, because the calendar said so, defeats the purpose of the exercise.

4. Who is Schatten-Payroll (parallel payroll run) relevant for?

- Companies facing a change of provider – for them the parallel run answers why the change need not founder on the risk of a gap in pay. - Companies facing a change of system – even without changing provider, when moving to different payroll software. - HR and finance leaders – they carry responsibility for the changeover date and need a demonstrable reason to release it. - Payroll providers – for them the parallel run is the set-up phase in which knowledge about a new client actually arises.

5. How it differs from related terms

- Parallel run and test payroll – a test payroll checks with invented or selected cases whether a system works. The parallel run calculates the real population. - Parallel run and data migration – the migration brings the data across, the parallel run proves they arrived correctly. Without the second step the first is unverified. - Parallel run and the four-eyes principle – the parallel run is limited to the transition and compares two systems. The four-eyes principle applies permanently afterwards and compares an entry against its source. - Parallel run and a trial month – a trial month moves the risk into live operation. The parallel run keeps it outside.

6. Variants and adaptations

- A single parallel run – one payroll month is calculated in parallel. Usual with a manageable population and no special cases. - A parallel run over several months – several consecutive months. Necessary where one-off payments, fluctuations or collective particularities become visible only over the year. - A partial parallel run – only selected areas run in parallel, a part of the business under a particular collective agreement for instance. Cheaper, but covers less. - A retrospective reconciliation – completed months are recalculated in the new system and checked against the actual payslips. Useful where a genuine parallel run is no longer possible in the time available.

7. Advantages and challenges

Advantages

  • The change is verified before it happens, not afterwards
  • No payroll run is missed, because the old procedure stays authoritative until hand-over
  • Deviations become visible at line level, not first in the annual total
  • The receiving team learns the population on real cases, not on descriptions
  • The changeover date rests on evidence rather than on an assurance
  • Old errors in the previous procedure frequently come to light in the process

Challenges

  • Two complete payroll runs mean double the effort over several months
  • The previous provider has to release data and reports – which is not always smooth
  • Without a binding reconciliation date the parallel run loses its purpose
  • Not every deviation is quickly explained; individual cases can hold up the schedule
  • With a very small population the effort can exceed the benefit

8. Best practices for implementation

Define the reconciliation beforehand

What is compared, and from what size of deviation it is followed up, belongs settled before the first run. Without that, the reconciliation becomes a feeling.

Settle the release of data early

Master data, wage type mapping, year-to-date values and the last payslips come from the previous provider. That hand-over is the most frequent bottleneck and belongs at the beginning, not the end.

Deliberately draw the special cases in

A parallel run covering only the normal case proves little. Attachments, benefits in kind, partial retirement, multiple employment and collective special cases belong expressly in scope.

Tie the transition to the result

The changeover date is released when the reconciliation agrees – not because the calendar says so. That order belongs agreed in writing.

9. Tips for employers and employees

For employers

  • **Start early** – the parallel run needs completed payroll months; starting shortly before the desired date effectively omits the safeguard
  • **Think about the year end** – a change at the start of the year is clean but requires the parallel run to fall in the previous year
  • **Do not argue deviations away** – every unexplained difference otherwise moves into live operation
  • **Name the responsibilities** – the reconciliation needs someone on each side who decides, not only someone who supplies

For employees

  • **Nothing changes for you during the transition** – payment and certificates come from the existing procedure until hand-over
  • **Check the first payslip after the transition** – personal allowances, supplements and recurring deductions above all
  • **Keep your documents** – the previous months' payslips are the measure by which a clean transition shows itself

10. Conclusion

The parallel payroll run moves the risk of a change of provider or system to where it harms nobody: into a run that pays nothing out and reports nothing. It costs double the effort over several months and requires cooperation from the previous provider – in return the changeover date rests on evidence rather than on an assurance. Shortening the parallel run, or limiting it to the normal case, saves precisely where the exercise has its value.

For an international group, one point bears repeating from the top of this entry: what is described here is not the shadow payroll of cross-border assignees. The two are unrelated, and a project plan that conflates them is planning the wrong work. This run is about proving that a new German payroll calculates the same figures as the old one, before anybody is paid from it.

Related terms

Our promise

Software supports. People take responsibility.

Let us talk about your payroll – no strings attached, specific, and with a dedicated contact from day one.

Set up fail-safetrue to detail, e.g. shadow payroll
Four-eyes reviewbefore every approval
Hosted in GermanyISO 27001 · GDPR