Home›Use cases›Employee records & changes
◉ 3 examples from practice

Reconciling employee records automatically
Changes that arrive everywhere at once

A change of address rarely affects only one system. It has to be in the employee file, in payroll, often in time tracking and the directory service too. Forget it in one place and differences appear that nobody notices until a certificate goes out wrong.

9 min saved per change to employee records estimated from comparable projects
11 minbefore, per change
2 minafter
1leading system instead of three
The starting point

What employee records
cost in time today.

1

A change is made in one place and forgotten in three others

2

Nobody knows for sure which system holds the current version

3

Contract changes need approvals, and those are chased by email

4

Restructures with an effective date have to be applied by hand

Programmes involved

These are the systems
tied to this area.

All already connected. If yours is missing, we build the integration at no extra cost, on average within three days.

Personio SAP SuccessFactors Workday Sage DATEV P&I LOGA

Is your programme included?

Three examples

Simple, medium
and genuinely complex.

All of them examples from live operation. What gets built is whatever comes up in your work.

SimpleA few steps, ready straight away

Apply a change of address everywhere

TriggerA change in self-service

  1. Check the change
  2. Write it to the HR system
  3. Hand it to payroll

ResultOne entry instead of four, and payroll is right in the next run.

MediumWith conditions and approvals

Contract change with approval

TriggerA manager requests a change

  1. Record the request
  2. Check the budget
  3. Obtain approval
  4. Generate the addendum
  5. Update it in every system

ResultSalary changes run on the four-eyes principle and without a collection list.

ComplexBranches, deadlines, several systems

Restructuring a whole department

TriggerAn organisational change on a set date

  1. Identify who is affected
  2. Work out the new assignment
  3. Rewrite the cost centres
  4. Adjust the reporting lines
  5. Bring access rights into line
  6. Take the effective date into account
  7. Check country-specific reporting duties
  8. Inform the employees
  9. Archive the previous state

ResultForty changes on the same date, in six systems and two countries, with no night shift.

The exceptions

And what about
the special cases?

That is the question most automation projects fail on. With us the exceptions get built in, not left out.

Backdated changes über einen abgeschlossenen Abrechnungsmonat
A move to another legal entity on the same contract
A change of name that affects the email address and certificates

Each of these cases can be mapped in the builder as its own branch, with a condition, an approval and a different route. Without a line of code.

Common questions

What we are asked about employee records
most often.

Which system is the leading one for us then?
You decide, and it can differ field by field. The address can come from the HR system, the cost centre from payroll. The reconciliation runs in whichever direction you set.
What happens with backdated changes?
They are transferred with their effective date. If the change affects a month already paid, the workflow triggers the retrospective calculation in the payroll system instead of overwriting it.
Do we notice when a reconciliation fails?
Yes. We monitor every workflow and get in touch before you notice. You also see every run in the log with a timestamp and a status.
How are restructures with an effective date handled?
As a scheduled workflow with a date. The changes sit ready and are triggered on the day, in every system at once, not one after the other by hand.
The next step

Tell us
what comes up in your work.

30 minutes on your actual programmes. We rebuild your employee records workflow live, not on a made-up company.