
Software and Automation ROI. How to Build a Business Case
Build a software or automation business case from measured current-process cost, TCO, scenarios, sensitivity analysis, and explicit stop criteria.
June 7, 2026. That's two months from now. By that date, every EU member state must transpose the Pay Transparency Directive into national law. If you're an HR director or CTO at a company with more than 100 employees, this date should be circled in red.
Most companies think the deadline is 2027. It's not. June 2027 is when companies with 250+ employees must submit their first pay gap report. The directive itself becomes national law in 60 days.
Directive 2023/970 on pay transparency introduces specific technical requirements for payroll and HR systems. These aren't vague principles. They're features your software either has or doesn't.
Start with salary bands. Every job position must have a defined pay range, and applicants have the right to know that range before the interview. A band can no longer live in a spreadsheet on someone's laptop, because your system has to manage it, version it, and publish it.
Then comes gender pay gap reporting, where how often you file depends on headcount. Companies with 250+ employees report annually, and their first report is due June 2027. Companies with 150 to 249 employees report every three years. Companies with 100 to 149 employees have until June 2031, but planning should start now.
The hardest part technically is categorizing "equal work and work of equal value." Your HR system must compare positions using objective, gender-neutral criteria, namely skills, effort, responsibility and working conditions. What gets compared is the substance of the work, not the job title on the contract.
Employees get rights of their own. Any of them can request the average pay for their job category, broken down by gender, and your system must produce that on demand.
If you're running SAP HR, Workday, or a regional payroll provider, you're likely in one of two situations.
Either your vendor is already building a pay transparency reporting module, in which case find out the delivery date and start testing. The module alone won't be enough. You need properly categorized data, and that data won't enter the system on its own.
Or your system doesn't support this reporting and has no plans to. Then you need either a migration or a middleware layer that pulls data from your existing system, processes it, and generates reports in the required format.
Both roads run into the same wall. Data quality decides this. If you don't have clean, structured data on positions, pay components, and employee categories, no software will save you.
The directive requires employers to prove how they determined a specific employee's pay. If a woman in the same position earns less than a man, the company must demonstrate that the difference is based on objective factors (experience, performance, certifications), not gender.
Your HR system must store the history of pay decisions. Who approved a change, on what basis, and when. This isn't just an HR requirement. It's a software requirement, a data model requirement, an audit trail requirement.
If you use or plan to use AI in HR processes (candidate screening, performance evaluation, pay recommendations), you're under dual regulation. The AI Act classifies AI systems in employment as high-risk. The Pay Transparency Directive adds another layer. Any automated pay decisions must be explainable and auditable.
These two regulations will overlap in practice more than most companies realize.
Between June 2026 and June 2027, you have one year. In that year you must map all positions, define salary bands, categorize "equal work," build the data infrastructure for reporting, and test the outputs. One year sounds like plenty. It isn't.
Start with an HR system audit. Not an audit of people or processes (though you'll need that too), but an audit of the software. Can your system generate the reports the directive requires? Does it have the right data model? Is the data clean?
If you answer "I don't know" to any of those, it's time to find out. In two months, the directive becomes law.
Need an HR system audit or help preparing for pay transparency reporting? Get in touch. We can help you assess your payroll software readiness.

Build a software or automation business case from measured current-process cost, TCO, scenarios, sensitivity analysis, and explicit stop criteria.
Your enterprise clients will start sending NIS2 compliance questionnaires. Here's what software companies need to know about security baselines, incident response, and supply chain obligations.
The AI Act applies fully from August 2, 2026. AI used for job ads, CV screening, and candidate scoring falls under high-risk rules. Practical compliance guide.