Coverage · EU + APAC + US
You're a platform with customers in more countries than your payroll can serve. Ledra Pay gives you thirteen countries of certified regulation packs behind one API — and in Australia, the full stack from calculation to statutory filing — so expansion is a config flag, not a build program.
What's at stake
Each new country is a multi-quarter payroll build with a permanent statutory-maintenance tail. Your roadmap fills with tax tables instead of product.
Per-employee fees to local providers solve coverage but surrender margin, control, and auditability — and your customer experience ends at their black box.
Calculation without statutory submission is half the job. Most "global" payroll APIs quietly stop before STP, RTI, or DSN — leaving the filing risk with you.
Your guide
We know what it's like to look at a country list and see only compliance burden — to want the market without wanting to become a payroll company to get it. That's the exact problem Ledra Pay exists to absorb.
Behind the API sits real statutory machinery: every pack is written in its country's native statutory register — Entgeltabrechnung, Nómina, Bedrijfsvoorheffing — verified by integration tests against real statutory logic, and updated annually as versioned releases. And we'll always tell you plainly what's certified, what's beta, and what's still in build.
The plan
Pick your countries, attach versioned regulation packs to your tenants. The API shape is identical in every jurisdiction — one integration, thirteen markets.
One API, every countryShadow runs diff our results line-by-line against your incumbent provider on real payrun data — zero production risk before you trust us with a single payslip.
Proof before commitmentAustralia's calculate-pay-file stack is the template. As a design partner, your country list decides which statutory submission rail we build next.
You set the orderThe template — Australia
Australia is where the payroll engine and the statutory submission rail meet: gross-to-net with awards and super, payment artefacts, and Single Touch Payroll to the ATO. Every other country grows into this shape.
PAYG withholding, Medicare levy, STSL, 12% super guarantee, Modern Award interpretation, payroll tax by state, leave and termination calculations.
BETACompliant payslips, ABA bank files, and SuperStream contribution batches generated at finalisation. Your platform executes disbursement.
BETASTP Phase 2 pay events lodged to the ATO over SBR — disaggregated gross, income streams, tax treatments — with receipts in the evidence chain.
RAIL IN BUILD · SANDBOX SIM LIVEAUSTRALIA IS CURRENTLY THE ONLY COUNTRY WITH A SUBMISSION RAIL. EVERY OTHER PACK RETURNS STATUTORY OUTPUTS FOR FILING THROUGH YOUR LOCAL PROCESS.
The honest part
Each government gateway is its own certified, country-specific channel: SBR for Australian STP, HMRC for UK RTI, Inland Revenue payday filing in NZ, DSN in France. Nobody gets these for free — and this is where the industry's coverage claims quietly fall apart.
Our approach: build rails one country at a time, in the open. Until a country has its rail, the pack returns statutory output files — correctly structured RTI, DSN, or declaration data — and your local process files them. The day a rail certifies, filing becomes one API call: POST /pay-runs/{id}/lodge. No re-integration.
This ladder is step three of the plan. Design partners set the order.
Step one in detail
Payroll · full stack
Payroll
Payroll
Entgeltabrechnung · demo page →
Salaire
Loonheffing
Bedrijfsvoorheffing
Lohnabrechnung
Lohnabrechnung
Nómina
Vencimento
Retenue
Payroll
All packs are in beta. Components reflect what local payroll professionals actually call these things — not a translated feature list — verified by integration tests against real statutory logic and updated annually as versioned releases.
Operating across countries
Multi-country employers get unified views without your platform stitching results together: employer cost summaries, statutory totals, and cross-entity comparisons as consolidation queries.
Employee and timesheet data flows in from the systems your customers already run; results flow out to accounting. No CSV ceremony required.
Two ways this goes
Design partner program
Australia is the template. NZ payday filing and UK RTI are queued. If your customers are somewhere else, that's a conversation worth having this week.