Embedded payroll infrastructure — New Zealand BETA
Your platform is expanding into a country with a two-working-day filing clock to Inland Revenue, KiwiSaver on every eligible hire, and the Holidays Act — the most re-litigated leave law in the region. Ledra Pay gives you the government-sourced New Zealand pack behind the same API you already integrated.
What's at stake
The prospect question is always the same — "can you do IRD?" — and the honest answer has parts. These are the three that catch platforms out.
Annual holiday pay is the greater of ordinary weekly pay and average weekly earnings; other leave uses relevant or average daily pay. It's payroll's most remediated calculation in NZ — a pack that models it correctly is the whole point.
Not monthly — every payday. Employers over the $50,000 PAYE-and-ESCT threshold must file electronically. The return (IR348) and the money to Inland Revenue travel on two separate clocks.
The Employment Information return files to Inland Revenue; the PAYE, KiwiSaver, student loan and child support settle to IRD's EMP account by the 20th — or twice a month over the threshold. Miss either and it compounds.
Your pack
A regulation pack means you never handle the IRD chain raw: your integration stays the same API shape you built for Australia, and the New Zealand pack absorbs PAYE, the ACC earners' levy, KiwiSaver with ESCT, student loan repayments and child support, plus the Holidays Act leave framework and the payday-filing outputs.
Calculation correctness sits with an accredited third-party payroll engine; Ledra Pay orchestrates the pay run, evidences every write, and produces the statutory outputs — while you keep payroll approval and the customer relationship. Rules trace to Inland Revenue and Employment New Zealand sources and ship as versioned pack releases, never silent changes.
PAYE, ACC earners' levy, KiwiSaver/ESCT, student loan (SL codes), child support — modelled as NZ payroll professionals know them.
The leave framework that trips up incumbents — ordinary vs. average pay — is in the pack, not left to you to bolt on.
Minimum wage, KiwiSaver default rate and threshold changes ship as pack releases against the 1 April tax year.
We carry calculation correctness; you keep payroll approval. Tax advice stays with your accountant or tax agent — by design.
The honest answer — "can you do NZ IRD?"
This maps one-to-one onto the NZ setup checklist in our guide — the IRD chain of number, employer registration and filing channel. Green is Ledra Pay; grey is you or your accountant today; ochre is the rail we build next with a design partner.
What the pack returns
The pay-run lifecycle runs live — draft, preview, approve, finalise — and finalising commits real per-employee results. Here is the shape of one employee's result and the payday-filing output beside it.
Every pay run produces the same two things: a payslip your customer can stand behind, and the Employment Information (IR348) data Inland Revenue expects — with the ESCT, student loan and child support already resolved.
The figures on the right are illustrative. Live rates — PAYE bands, the ACC earners' levy, the KiwiSaver default, the minimum wage — are maintained in the government-sourced NZ guide and shipped as versioned pack releases.
Illustrative fortnightly figures for a single tax code (M) employee with KiwiSaver at the default rate and no student loan. The production pack handles all tax codes, secondary income, ESCT tiers, SL/child-support, and Holidays Act leave. Not tax advice — confirm with Inland Revenue and your tax agent.
{
"employment_information": {
"form": "IR348", "pay_period_end": "2026-07-05",
"paye": 448.20, "kiwisaver_ee": 84.00, "kiwisaver_er": 84.00,
"esct": 0.00, "student_loan": 0.00,
"status": "output_file", "file_by": "2 working days"
},
"pay_ird_emp_account": { "due": "the 20th", "channel": "employer bank payment" },
"rail": { "ird_payday_filing": "design_partner_next" }
}
The embeddable component
The New Zealand payslip as a standard web component — drop it into your product, theme it with CSS variables (this one is wearing this page's palette), localise it. The full set — onboarding, employees, leave, pay runs — runs in the component playground →
<ledrapay-payslip-viewer country="NZ"> · sample data, real component, themed inline
The obligations
These are the employer obligations every NZ payroll must serve. Ledra Pay generates the data for all of them — and lodges payday filing directly once the IRD rail is live.
The plan
Same API, New Zealand pack. Run gross-to-net in your sandbox this week, then shadow-run against your incumbent's results before anything goes live.
Calculation · live via Payroll EngineThe full pay-run lifecycle runs live — draft, preview, approve, finalise. Finalising commits real per-employee results and shapes the IR348 Employment Information plus the pay-IRD schedule for your process or your accountant to file.
Output files · availableNew Zealand's filing layer is Inland Revenue's payday-filing gateway — the Return service that files the IR348. We build the direct rail with a design partner whose launch sets the sequence.
Design partner projectThe New Zealand payroll guide
Everything an employer in New Zealand must get right — written from fetched Inland Revenue and Employment NZ sources, verified claim by claim, and maintained as the law moves.
Design partner program
Thirty minutes with our team: gross-to-net end-to-end through the API, the IR348 payday-filing output, and a shadow-run plan against your incumbent's New Zealand payruns.