Home›Use cases›Reporting & metrics
◉ 3 examples from practice

Automating HR reporting
Numbers that are right, with no Excel in between

Bringing metrics together from several systems takes a long time not because the numbers are hard to find, but because each system names them differently and calculates them differently. By the time the report is finished, it is out of date.

3 hrs instead of three days per monthly report estimated from comparable projects
3 daysbefore, per report
3 hrsafter
0rework caused by discrepancies
The starting point

What reporting
costs in time today.

1

Numbers are exported monthly from three systems and merged in Excel

2

Every metric is defined differently, depending on who calculates it

3

The board asks about a position that is two weeks old

4

Staff cost forecasts happen once a year instead of continuously

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 Workday SAP SuccessFactors DATEV Sage Microsoft 365

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

Headcount on the first of the month

TriggerThe first working day of the month

  1. Determine the headcount
  2. Count joiners and leavers
  3. Send the report

ResultThe board gets the number without having to ask for it.

MediumWith conditions and approvals

Turnover and cost per hire

TriggerEnd of quarter

  1. Fetch the data from recruiting
  2. Assign the cost per channel
  3. Offset the leavers
  4. Calculate the metrics
  5. Save the report as a file

ResultMetrics from four systems, without anyone opening Excel.

ComplexBranches, deadlines, several systems

A staff cost forecast for planning

TriggerThe planning round in autumn

  1. Fetch the actual costs per cost centre
  2. Factor in pay rises
  3. Allow for planned joiners and leavers
  4. Convert the currencies
  5. Calculate the scenarios
  6. Show the variance against last year
  7. Hand it to finance

ResultA dependable forecast across every legal entity, even with several currencies.

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.

Metrics across several entities with different charts of accounts
Comparative figures after a restructure
Reports for the works council and the board at different levels of detail

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 reporting
most often.

Where do the numbers come from?
Straight from the connected systems, not from a cache. That makes the report as current as the source.
Can we report metrics across several legal entities?
Yes. Different charts of accounts and field names are translated along the way, so the numbers become comparable.
How often is it reported?
As often as you like, monthly, weekly or on demand. The workflow can also send the report to a distribution list automatically.
Do the works council and the board get the same numbers?
Only if you want them to. Several reports at different levels of detail can be produced from the same data.
The next step

Tell us
what comes up in your work.

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