Pay transparency, from a worker's request to the statutory report
A worker asks for her own pay level and her category's average by sex through your own page, giving her name as Article 7 requires. The two-month reply clock starts the moment the request arrives, and when it's time to report, your payroll file is read and turned into the statutory figures inside the browser it was opened in, never on a server.
What Directive (EU) 2023/970 requires
Directive (EU) 2023/970 — the Pay Transparency Directive — applies to every EU employer, whatever its size. Pay ranges must be disclosed to job applicants, nobody may be asked about their pay history, and a worker can ask for her own pay level and the average pay levels by sex for people doing work of equal value to hers; an employer must answer within two months. Member states had until 7 June 2026 to transpose it into national law.
Larger employers carry a second duty: publishing a gender pay-gap report. Employers with 150 or more workers report first, from June 2027; the 100–149 band follows from 2031, and employers with 250 or more report every year from 2027 onward. A gap of 5% or more in any category, left unaddressed for six months, triggers a joint pay assessment — a process this product does not run.
The load-bearing idea is "category of workers": people doing the same work, or work of equal value, judged against four statutory criteria — skills, effort, responsibility and working conditions — never job title or department. An organisation defines its own categories; the law does not hand them over ready-made.
The deadline
Directive (EU) 2023/970 sets this clock as its own outer limit, counted from the moment a request arrives.
- at most 2 monthsAnswer a pay-information request
Counted from the calendar day the request reaches you through the page you publish.
Two months is the Directive's own limit, not a guarantee of that length — a country's own transposition can set a shorter period, and Klaruna applies it wherever a country pack declares one.
How it works
- A worker asks for her pay information
Through your own page, she gives her name and contact details, as Article 7 requires, and optionally the category of workers she believes she belongs to and the question she wants answered.
- The two-month clock starts
Counted from the day the request arrives. The queue shows every open request with its days remaining, coloured as the deadline nears, and reminders reach the handler automatically as it approaches and again if it's missed.
- Your team answers from a prepared draft
The category-of-workers register already holds the four statutory criteria and the roles assigned to each category, so the reply's answer fields open with editable model wording for her pay level, her category's average by sex and remarks, every exchange recorded.
- The pay-gap calculator runs in the browser
Pick a payroll export, map its columns once, and the browser computes the statutory figures: the mean and median gaps, the variable-pay gaps, bonus proportions, pay quartiles and a figure for each category. The file is read locally and never uploaded.
- Finalise and download the report
Review the figures, confirm there's nothing left outstanding, and download the report as a self-contained page stating its own source file's checksum and the category-set version it was built against.
What's included
Your own request page
A public page for your organisation in Polish or English, carrying your own logo, where a worker gives her name and asks for her pay information.
A queue that shows what is due
Every open request with its days remaining, coloured as it nears the deadline, filterable by status, overdue requests, and the ones assigned to you.
A drafted reply
Article 7's four answer fields — individual pay level, category, average pay by sex, and remarks — start from a prepared draft rather than a blank form.
Automatic reminders
Emails reach the handler as the two-month clock nears its end, and again if it's missed, without anyone having to watch the queue by hand.
A category-of-workers register
Build categories against the four statutory criteria, assign roles one at a time or from a government tool's own file, and keep draft, active and archived versions.
A pay-gap calculator that stays in the browser
Choose a payroll export once; the statutory figures are computed on the HR manager's own machine, and only those aggregate figures, never a named payroll row, are kept.
Report register and download
Every report for the year, finalised with a recorded confirmation, downloadable as a self-contained page carrying its own source-file checksum and a retention statement.
Built for advisors
A payroll bureau or consultancy acting for several clients sees from one screen which of them still owes a report, and opens one client's own screens to work on it at a time.
Data and security
Everything runs in EU data centres: the application, the database, file storage, backups and email delivery.
Each request, and the dialogue around it, is sealed under a key unique to that request. A finalised report's figures are stored encrypted under their own key too, decrypted only to show or download the report.
No server code can reach the payroll file a calculation is run against — a dedicated test fails the product's own build if one ever acquires a path to it — and a category with too few people assigned is never reported on individually, so a report can't be read back into any one person's pay.
Every action on a request — submission, viewing, replies, assignment, closure — is written to an append-only audit trail.
The Polish document templates — pay-range wording for a job ad, a pay-history ban notice, and an internal pay-transparency policy — can be read today in Polish or English; adopting one is not yet open, because the pack has had no independent legal input yet.
Where it applies
The workflow and deadline tracking work in every EU country. Legal templates are available for Poland, with more countries to follow.