How to Read and Reconcile a NZ ACC Levy Invoice

A New Zealand ACC levy invoice carries three separately calculated charges per $100 of liable earnings: the Work levy, with a rate set by the business's Classification Unit (which ACC maps from the business's BIC/ANZSIC industry code); the flat Earners' levy, which funds cover for injuries that happen outside work; and the small Working Safer levy, collected by ACC on behalf of MBIE for WorkSafe NZ. Reconciling the invoice means tying ACC's liable-earnings figure back to the employer's payroll, or — for self-employed payers — to the IR3 income IRD shares with ACC, then checking the Classification Unit code is correct and coding the three line-item amounts into the general ledger.

Three groups of practitioners receive a version of this document every year and need to do something concrete with it: SME bookkeepers handling the annual employer invoice for clients, self-employed contractors decoding their personal invoice, and payroll managers reconciling ACC's liable-earnings figure against payroll. ACC's own pages walk the concepts; this article walks the document, with each section calling out the audience whose handling differs.

ACC bills annually. The cover year runs from 1 April to 31 March, which aligns with the standard NZ tax year but may not align with a business's balance date. The invoice is GST-exclusive, so it doesn't sit in the GST return as a standard supplier invoice — a small detail that catches accounting software users who have never coded one before.

Most NZ businesses pay the ACC levy invoice without scrutiny, and most of the time that's a reasonable choice — the figures are largely correct. The reason to walk the document is that two specific things on it routinely repay attention: the Classification Unit code (because a wrong CU silently overcharges or undercharges every year until corrected) and the liable-earnings figure (because reconciling it against payroll occasionally surfaces a payroll-filing error worth fixing at source). The remaining mechanics — the three levies, the timing, the GST treatment, the GL coding — matter because you need to read them once, not because every line is high-stakes every year.

The Three Levies and What Drives Each Rate

All three levies are charged on the same liable-earnings figure. The amounts differ because the rates differ, and each rate has a different driver.

Work levy. Variable rate per $100 of liable earnings, set by the business's Classification Unit. The CU is mapped from the business's BIC/ANZSIC industry code, so the driver is industry risk: a roofing CU pays many multiples of an accounting CU on the same earnings. This is the line item with the most variation between businesses and the most reconciliation surface — both because the rate itself can be wrong if the CU is wrong, and because the earnings figure it's applied to can drift from payroll. For SME bookkeepers and payroll managers reviewing an employer invoice, the Work levy is the line to look at first; for self-employed contractors it's the same line, but the earnings figure underneath it comes from IR3 rather than from payroll (covered in Section 5).

Earners' levy. Flat rate per $100 of liable earnings, paid into the Earners' Account, which funds cover for non-work injuries — injuries at home, at sport, in the car. For the 2026-27 levy year (1 April 2026 to 31 March 2027), the ACC earners' levy is set at $1.75 per $100 of liable earnings (1.75%), per the rate published on Inland Revenue's published ACC earners' levy rates page. That page is the authoritative source for current and prior years' rates, which is worth bookmarking rather than relying on any single article's snapshot — the rate moves between levy years.

Working Safer levy. Small flat rate per $100, also charged on liable earnings. ACC collects it on behalf of MBIE and applies it to WorkSafe NZ's regulator activity. It's small enough that it rarely repays scrutiny on its own; the value of identifying it on the invoice is mostly that you can recognise it for what it is rather than wonder why there's a third line item.

A practical consequence of the shared earnings base: when a bookkeeper's expected number doesn't match the invoice number, the discrepancy almost never sits in two levies independently. Either the rate is off — which is a CU question (Section 3) — or the earnings figure is off, which is a payroll or IR3 reconciliation question (Sections 4 and 5). Knowing which of those two it is narrows the diagnostic immediately.

The Classification Unit Code as the Audit Lever

The Classification Unit appears on the invoice as a four-digit code with a short industry description sitting near the Work levy line. The Work levy amount is calculated by applying the rate attached to that specific CU to the business's liable-earnings figure. Everything about the Work levy flows from this one piece of metadata.

ACC sets the CU based on the business's BIC code — the Business Industry Classification used in NZ, derived from the Australian and New Zealand Standard Industrial Classification (ANZSIC) system Statistics NZ maintains. When a business registers with IRD or updates its activity, the BIC code feeds into ACC's CU assignment. Same activity, same CU, same Work levy rate.

CU misclassification is the most common reconciliation finding actually worth acting on. A CU sitting in a higher-risk band than the work the business actually does charges materially more per $100 of liable earnings every year, silently, until corrected. A CU sitting lower than the actual work understates the business's true exposure and risks correction with backdated levies if ACC reviews. The industries where CU disputes turn up most frequently are construction trades (where sub-codes vary widely between, say, residential carpentry and commercial roofing), agriculture (where activity mix often shifts between seasons), and any business whose actual day-to-day work has drifted from what was originally registered.

The diagnostic is short. Read the CU description on the invoice, compare it to what the business actually does day-to-day, and check whether the BIC code on file in IRD records still matches that activity. If the description on the invoice doesn't fit the business — or fits something the business stopped doing two years ago — that's the signal to escalate. The mismatch doesn't need to be dramatic to be worth correcting; even one band of difference can be material at scale. Bookkeepers handling construction clients in particular should treat CU review as a routine part of onboarding, alongside the parallel NZ construction payment claims under the Construction Contracts Act discipline that shapes the same clients' invoicing.

The appeal route runs through ACC directly. The business contacts ACC and requests a CU review, providing evidence of actual activities — product lines, services performed, the income mix between activities. ACC can reclassify the CU and adjust future levies. One thing to flag for clients: a successful reclassification doesn't always reverse prior years automatically. Future-year correction is the default; historical recovery, where it happens, usually requires a separate request and supporting evidence. Don't promise a refund of past overcharges — promise the right rate going forward and treat any backward adjustment as a bonus.

Reconciling ACC's Liable Earnings Against Payroll

ACC's liable-earnings figure isn't the same as the gross-earnings figure on a payroll report, and the gap between the two is the second thing on the invoice that routinely repays attention.

The composition difference is the asymmetry that drives most mismatches. ACC's liable earnings is gross earnings adjusted for items ACC excludes — typically redundancy and retirement payments and certain allowances are out, while ordinary wages, holiday pay, and most taxable allowances are in. Payroll-system gross-earnings reports usually include some items ACC excludes. So when payroll says one figure and ACC's invoice shows another, the most likely explanation isn't that one of them is wrong — it's that they're measuring slightly different things.

The diagnostic for an employer-side reconciliation runs in three steps:

1. Pull ACC's liable-earnings figure off the invoice for the cover period.
2. Pull the equivalent payroll-report figure for the same period — and watch the period-cut. ACC's cover year runs 1 April to 31 March. A business on a non-standard balance date has a payroll year-end that doesn't line up, and reconciling against a payroll report cut to the wrong dates produces a phantom mismatch that resolves the moment you align the periods.
3. Compute the difference and walk down the list of common explanations: redundancy or retirement payments paid in the period (ACC excludes; payroll includes), period misalignment between ACC's cover year and the payroll report cut, shareholder-employee earnings handled separately on a personal IR3-derived invoice rather than through company payroll, and timing of leave payouts spanning the period boundary.

Most differences resolve cleanly to one of those four. When the gap doesn't resolve, that's the trigger to contact ACC, because the liable-earnings figure ACC uses is fed by IRD's payroll data — under payday filing, every Employment Information return the employer files flows through to ACC. A genuine, unexplained mismatch usually means a payday-filing error somewhere in the cover year that's worth correcting at source rather than letting the next ACC invoice carry it forward and compound. Correcting an EI return is straightforward; explaining a four-year cumulative drift later is not.

The pragmatic stance for SME bookkeepers and payroll managers: if the reconciliation resolves to known exclusions and a clean period cut, and the residual gap is within tolerance for the business, document the working and move on. The reconciliation exists to surface real outliers, not to chase every dollar to ground.

The Self-Employed Invoice and Shareholder-Employee Mechanics

For self-employed contractors and sole traders the reconciliation runs through IR3, not payroll. IRD shares the schedular and self-employment income figures from the contractor's IR3 with ACC, and ACC builds the personal levy invoice from that income. Three practical implications follow.

The invoice always trails income by a year. The personal invoice arriving this year is built from last year's IR3 income, which is the figure IRD has on file by the time ACC bills. Contractors looking at this year's invoice and comparing it to this year's expected earnings are comparing the wrong two numbers.

Amending an IR3 after assessment triggers a re-invoice. If a contractor revises a prior return — picks up unreported income, claims a deduction they missed, restates schedular income — the change flows through to ACC and a corrected invoice follows. This is the timing trap to flag for any client doing year-end IR3 cleanup: the ACC consequence isn't always immediate, but it does come.

Schedular tax and ACC levies are separate charges on the same income, driven by different mechanisms. A contractor whose payers withhold tax under the IR330C / IR330 process still receives a personal ACC invoice — the schedular withholding covers income tax, not ACC. The two run in parallel. For the broader picture of how schedular income flows through a contractor's tax obligations, see NZ schedular payments and contractor withholding tax; the point for this article is that an ACC invoice arrives independently of any withholding the contractor's payers have already made.

Two cover options sit underneath the invoice, and the choice matters more than the line items suggest.

CoverPlus is the default for self-employed payers. Cover and levies are calculated automatically from prior-year IR3 income, and weekly compensation in a claim is calculated from that same income figure. It's the simpler option and works fine for contractors with stable income that genuinely reflects their financial commitments.

CoverPlus Extra (CPX) lets the contractor specify an agreed cover level — the weekly amount they'd be paid in a claim — independent of IR3 income. Levies are calculated from the agreed cover figure rather than from the IR3 number. CPX suits two cases in particular: contractors with volatile income, where a single strong year shouldn't cap the next year's cover (or a single weak year shouldn't crater it), and contractors whose IR3 income understates their actual financial commitments because of legitimate deductions, retained earnings, or company structures.

The line items on the invoice itself look identical between CoverPlus and CoverPlus Extra. The difference lives in the underlying earnings figure used and what a claim would actually pay out. Worth raising with any self-employed client whose IR3 income looks materially different from how much they'd need to live on if they couldn't work for six months.

Shareholder-employees of close companies sit in a hybrid that catches bookkeepers who weren't expecting it. A close-company shareholder-employee can receive both a PAYE component, billed through the company's payroll-based ACC invoice, and a non-PAYE company-derived component, billed through a personal IR3-derived invoice for the same person. The two invoices aren't duplicates — they cover different parts of the same person's earnings. Bookkeepers handling close-company clients should expect the pair, reconcile them as a pair, and code them through the right ledgers (the company-side invoice into the company books, the personal invoice onto the shareholder-employee's IR3).

Cover Year, Instalments, and GST Treatment

ACC's cover year runs 1 April to 31 March, which aligns with the standard NZ tax year for businesses on a 31 March balance date. A business on a non-standard balance date — a 30 June farming year, say, or a 31 December subsidiary aligned to an offshore parent — sees its cover year and its accounting year diverge. The cover year on the invoice is the period the levies pay for, not the period in which the earnings were taxable.

Instalment plans are available on larger invoices. The invoice itself shows an instalment status when one is active, and the instalment payments are still levies, not interest-bearing finance — there's no separate finance-cost component to split out, and the GL treatment is the same as a single payment. Interest can apply on overdue amounts, so a contractor or business expecting cash-flow tightness around the due date is better off setting up an instalment plan before the due date than missing it and accruing interest after the fact.

Deductibility timing follows standard expense rules. For businesses on the accruals basis, the levy is deductible in the period it relates to — the cover year — regardless of when the cash actually moves. For self-employed contractors filing IR3, the levy belongs on the IR3 expense schedule in the year it relates to. Cash-basis taxpayers recognise on payment. The instalment-plan question doesn't change deductibility on the accruals basis; the full levy is still deductible in the cover year, and instalments are just the cash-side schedule.

The GST treatment is the small detail worth getting right at the coding stage. ACC levy invoices are GST-exclusive: the levies themselves are not subject to GST, and there is no GST input claim against an ACC invoice. Coding the invoice as a standard-rated supplier invoice in accounting software produces a phantom input claim that has to be reversed later, so the right move at entry is to code the line as zero-rated or exempt according to the conventions of the software in use. The broader rules for what counts as a tax invoice and what documentation a registered person needs on file are covered in the NZ taxable supply information requirements — the ACC invoice itself sits outside that GST framework but still belongs in the documentation set for the period.

GL Coding and the Fields to Extract for the Books

The chart-of-accounts choice for ACC levies isn't a question with one right answer; it depends on how visible the line needs to be in the year-end accounts and what other regulatory charges sit alongside it. Four common options:

• A dedicated ACC levies expense account. Best where the levy is material enough to track on its own line, and where comparing year-on-year movement is useful — a CU reclassification, a payroll change, or a CoverPlus-to-CPX switch all show up cleanly here.
• Rolled into Insurance. Mechanically simple if the chart of accounts is consolidated and ACC sits alongside other policy-style charges. The trade-off is reduced visibility of ACC movement specifically, which matters when the next year's invoice changes and a controller asks why.
• Rolled into Compliance or Statutory levies. Fits charts that already group regulatory charges together — appropriate for businesses with multiple levy lines on the books, such as commodity levies in agriculture or industry-specific statutory contributions.
• For self-employed contractors filing IR3, the personal levy goes onto the IR3 expense schedule under self-employment expenses. The narration matters more than the line classification — a clear "ACC personal levies — [year]" entry survives later review better than a generic "compliance" line.

The concrete extractable-fields list — the answer to "what goes on the bookkeeping spreadsheet" — is short and stable across years and across the three audiences the article serves:

• Invoice number
• Period (cover year start and end dates)
• CU code and description
• Liable income / earnings figure
• Work levy amount
• Earners' levy amount
• Working Safer levy amount
• Total
• Due date
• Instalment status (and instalment amounts where applicable)

A bookkeeper handling one ACC invoice a year per client can re-key those ten fields in a couple of minutes and move on. The calculus changes at scale: a firm with dozens or hundreds of clients receiving ACC invoices each levy cycle, or an in-house team handling ACC alongside other annual tax-compliance documents, ends up with a re-keying job large enough to think about automated extraction of structured fields from regulatory PDF invoices as a financial-document automation problem in the same category as payroll-document and tax-compliance-document extraction. The interaction model is a single prompt naming the fields to pull — invoice number, period, CU code, liable earnings, the three levy amounts, total, due date, instalment status — applied to a batch of ACC PDFs and producing one Excel row per invoice. Practitioner-level context (one row per invoice, dates standardised, amounts as native Excel numbers rather than text) sits in the same prompt; the field list above is the spec.