Skip to content
NetWage

Methodology and sources

Rates verified on 3/10/2026 — official sources

One engine, one source of truth

Every figure on the site — the online calculator as well as the pre-computed salary pages — is produced by the same calculation engine (paie-engine) fed by a versioned parameter file (data/params/ie/2026.json). Each parameter carries its official source, verification date and reviewer name; an audit blocks publication if any of these fields is missing or a check is older than twelve months.

Before publication, the engine is cross-checked against the official calculators of the market — Revenue (Revenue Commissioners) — on a truth table of cases, with a tight tolerance.

The verification pipeline

  1. Read on the official source. Every rate is read directly on the reference publication —the official publications of Revenue (Revenue Commissioners) — the exact documents are listed per parameter in the table below. Never a third-party site, never an unflagged year-over-year extrapolation.
  2. Traced parameter. The value is written into the parameter file with its source URL, verification date and reviewer name — the table below is generated straight from that file.
  3. Tested engine. The engine applies the parameters against the independent truth table; any drift beyond tolerance blocks publication.
  4. Cent-level audit. At every site build, an audit replays each salary amount page through the engine and compares the HTML to the cent; a divergence fails the deployment.

When rates change

Payroll parameters move on an annual cycle: the tax authority publishes indexed brackets and contribution thresholds on its own calendar. Where an official 2026 value was not yet published at verification time, the value in force is kept and flagged in the parameter notes — the flag is removed when the official table lands. The date shown at the top of this page is the most recent verification across all parameters.

Calculation scope

Versioning and update cycle

Every parameter set is versioned by tax year and lives in its own file: brackets, caps, deduction amounts and verified dates for 2026 are never mixed with the previous year's values. When an official finance act or a rate notice changes a figure, the corresponding file is updated, re-verified against the source and re-dated — and the pages that depend on it are regenerated in the same build, so a stale number cannot survive a deployment by accident.

The review is not only annual. Each parameter carries a verification date and a reviewer name, and an automated audit flags any source older than twelve months or missing altogether. Between reviews, the contact page is the channel for sourced corrections: a reader who spots an outdated rate with an official reference triggers the same verification workflow as a scheduled review. What changed, when and why is documented in the file itself, so the history of a figure is as inspectable as the figure.

Practically, this means every amount page and every calculator result carries its own trail: the parameter year, the verification date and a link to the methodology describing the model. When you compare two figures — a payslip line and our breakdown, for instance — you can always walk back to the exact rule and source that produced the number.

Official sources (2026)

ParameterSourceVerified on
incomeTaxwww.revenue.ie3/10/2026
uscwww.revenue.ie3/10/2026
prsiwww.revenue.ie3/10/2026

The full parameter detail (values, units, verification notes) is public in the project's data repository.