Compensation, bonus and KPI for thousands of employees across multiple countries

The situation

Compensation is where spreadsheets survive longest, because the rules are genuinely complicated and every country is slightly different. That is also why spreadsheets are worst there: a bonus matrix with regional targets, replicated across countries and edited by several people each cycle, is a structure a spreadsheet can represent but cannot protect.

What was built

One platform holding the employee master and everything computed from it.

• Employee master data as the single source the rest of the system reads from.
• Compensation packages per employee, versioned rather than overwritten.
• A bonus and KPI matrix builder with targets set by region, so a regional rule is expressed once instead of copied.
• Org charts generated from the same data, so the reporting line used for approvals is the one the business actually has.
• Multi-country payroll reporting, with the export shapes each country's process needs.
• Excel import and export throughout — because that is how HR and finance teams genuinely work, and refusing it just moves the spreadsheet somewhere invisible.

Why import/export is not a compromise

A system that forbids spreadsheets does not eliminate them; it drives them underground, where they become the shadow source of truth. Building mass upload and export in from the start keeps the spreadsheet as a working tool and the platform as the record.

What changed

Thousands of employees, several countries and a monthly payroll cycle running on one dataset, with the bonus rules written down as configuration rather than re-implemented in each cycle's file.

Finance processes on the same stack were delivered for a European medical-imaging group. Client names are withheld here by default.