Did the April 2023 NZ GST rule changes affect how wholesale distributors issue invoices?

Yes, though the main effect is flexibility rather than additional burden. From 1 April 2023, the requirement to use the term 'tax invoice' was removed under the Taxation (Annual Rates for 2022-23, Platform Economy, and Remedial Matters) Act 2023. NZ businesses now provide 'taxable supply information' (TSI) rather than a formally labelled tax invoice document. For wholesale B2B transactions above $1,000 — which covers almost all distributor invoices — the required information includes supplier name and GST registration number, recipient name and address where known, date, description of goods, quantity, GST-exclusive price, GST charged, and GST-inclusive total. For a distributor running a custom ERP with compliant invoice generation, the practical impact is that electronically delivered, properly structured invoice documents satisfy the TSI requirement. The paper 'tax invoice' format is no longer the only option.

Can Xero or MYOB Business handle invoicing for a NZ food distributor sending 200+ invoices per day?

For most food distributors at that volume, the answer is no — not without significant manual effort or workarounds. Xero and MYOB Business are designed for businesses creating invoices manually or in small batches. They do not support dispatch-triggered invoice generation (where the invoice is created automatically when goods leave the warehouse), catch-weight lines where the invoice price is derived from confirmed dispatch weights rather than a fixed order price, or automated credit note generation from delivery returns data. Some distributors use bulk CSV imports into these platforms, but this breaks down for catch-weight products and does not scale cleanly past a certain volume. A wholesale distributor sending 150-300 invoices per day from ERP dispatch typically needs ERP-level invoicing rather than SME accounting software invoicing.

How does a wholesale ERP handle invoicing for catch-weight products where the price isn't known at order time?

The ERP triggers invoice generation from the dispatch event, not from the order. When the warehouse picks and weighs catch-weight products — typically fresh or chilled food such as meat, seafood, dairy, or fresh produce — the confirmed weights are recorded against the dispatch. The ERP takes those confirmed weights, applies the customer's per-unit pricing to the actual quantity dispatched, calculates GST, and generates the invoice. The invoice amount reflects what was physically shipped, not what was originally ordered. Customers ordering 5 boxes of salmon fillet may receive boxes totalling slightly different weights than estimated — the invoice reflects the actual dispatched weights. Any system that generates invoices at order time produces an incorrect amount for catch-weight lines.

Does the ERP need to issue a separate credit note for every return, or can credit notes be batched?

Both are possible depending on the distributor's AR model. For large accounts with frequent returns — supermarket or major retail delivery routes where driver returns are processed daily — batching credit notes into one document covering all returns from a delivery or period is common and reduces document volume. For accounts where returns are infrequent and customers want a clean match between original invoice and credit note, one-for-one credit notes are the cleaner approach. The ERP should support both patterns and link each credit note to the original invoice it is reversing, for GST period reconciliation and AR balance accuracy.

← All insights

Automated GST invoicing for NZ wholesale distributors: what changes at scale

6 July 2026 · 7 min read · Zeabyte

A NZ food distributor handling 200 dispatch lines per day — spread across hundreds of trading accounts — cannot produce GST-compliant invoices manually. At that volume, invoicing is a back-office process that must run automatically from the ERP as goods leave the warehouse. The tools that work for an SME with 10–20 invoices a week (Xero, MYOB Business, cloud invoicing apps) were not designed for this workflow or this scale.

This matters practically because the invoicing model in a wholesale ERP is fundamentally different from what SME accounting software provides — not more complex as a matter of preference, but necessarily different because of how wholesale distribution physically works. Understanding where those differences lie is what lets you design the invoicing engine correctly from the start, rather than discovering the gaps after go-live.

What changed with NZ GST invoicing rules in April 2023

From 1 April 2023, New Zealand updated its GST invoicing requirements under the Taxation (Annual Rates for 2022–23, Platform Economy, and Remedial Matters) Act 2023. The requirement to use the words "tax invoice" on documents was removed. Businesses now provide "taxable supply information" (TSI) — which can be in any format and delivered electronically, provided it contains the required fields.

For wholesale B2B transactions, which typically exceed $1,000, the required TSI fields include: the supplier's name and GST registration number, the recipient's name and address (where known), date, description of the goods or services, quantity, GST-exclusive price, GST charged, and GST-inclusive total.

For distributors already running a custom ERP that generates invoice documents with this information, the practical effect is primarily flexibility. Electronic delivery of a properly structured document satisfies the TSI requirement — the formal paper "tax invoice" layout is no longer the only compliant format. What the change does require is that the invoice generation engine correctly populates all required fields for each transaction tier, and that there is a traceable record of delivery: who received the document, by what channel, and when.

Why invoices can't be generated at order time for many wholesale products

For ambient grocery or household goods distributors, the invoice amount can be known at order time — price times quantity, applied to a fixed unit price. For fresh and chilled food distributors (meat, seafood, fresh produce, dairy), this does not hold. The invoice price is based on actual weight, and the actual weight of a case or carton is not confirmed until the warehouse picks and weighs the goods at dispatch.

A customer places an order for five boxes of beef mince. The cases in the chiller do not all weigh the same. The invoice must reflect the confirmed weights of the five boxes that actually leave the building — not the estimated order quantity. Any system that generates the invoice from the order creates an incorrect document that will need to be reversed and reissued once actual dispatch weights are confirmed. At scale, this becomes a significant operational overhead.

This is what makes dispatch-triggered invoicing the correct model for fresh and chilled wholesale. The invoice is a by-product of the dispatch confirmation event — it is generated after weighing, not before. For a deeper look at how catch-weight tracking works in the warehouse and ERP, see our post on catch-weight inventory for NZ food distributors .

How ERP-driven invoice generation works at dispatch

In a correctly designed wholesale ERP, the invoice generation sequence is triggered by the dispatch confirmation event — when goods are confirmed as picked, packed, and allocated to a delivery run. The sequence is:

Dispatch confirmed. The warehouse confirms the dispatch lines: products dispatched, quantities, and confirmed weights for catch-weight items.
Pricing resolved. The ERP applies the customer's pricing from the pricing hierarchy — price level, per-customer overrides, quantity breaks — to the confirmed dispatch quantities. For catch-weight lines, the per-unit rate is applied to the actual dispatched weight.
GST calculated. GST is calculated on the taxable value. Most wholesale food is GST-zero-rated in NZ (fresh fruit and vegetables, meat, fish, poultry, grains, eggs, and a range of other foods are zero-rated under the Goods and Services Tax Act 1985). The ERP needs to know the correct GST treatment for each SKU and apply it consistently.
TSI document generated. The ERP generates the invoice document with all required TSI fields populated — supplier details, recipient details, line items, GST, totals.
Document delivered. The invoice is delivered to the customer's nominated channel: email, EDI (for large retail and supermarket accounts on Foodstuffs Exchange or Woolworths NZ), or posted to the customer's account in the B2B ordering portal.

This entire sequence runs automatically as part of the dispatch workflow. No one manually creates an invoice; the invoicing is embedded in the distribution process. The finance team sees invoices posted to AR as dispatches complete, rather than processing a separate invoicing task.

Credit notes at wholesale scale

Returns, short shipments, and quality claims generate credit notes. At wholesale scale, these are frequent. A chilled delivery driver returns two cartons of product the customer rejected at the door. A batch of fresh produce is short-weighted on arrival. A promotional price was incorrectly applied to an account and needs reversing. Each case requires a credit note against the original invoice, correctly reducing the GST liability for the period.

In a custom ERP, credit notes are generated from the same delivery and returns data that drives the original invoicing. The returns workflow — where the driver or warehouse records what came back, against which delivery — feeds the credit note generation. The ERP links each credit note to the original invoice, adjusts the outstanding AR balance, and delivers the credit note through the same channel as the invoice. The GST is reversed correctly for the period in which the adjustment falls.

What breaks this is when the credit note process is manual — someone in the accounts team issuing credit notes individually in Xero or MYOB after being notified by email from the warehouse or sales team. At low volume, this is manageable. At wholesale scale, manual credit notes create AR reconciliation problems, introduce delays in customer accounts, and create GST period mismatches when credits are processed late.

Four failure modes to design around

The patterns that create invoicing problems at wholesale scale are predictable. Understanding them in advance shapes the design decisions worth making before build begins.

Invoices generated at order time for catch-weight lines. The invoice is wrong as soon as the actual dispatch weights are confirmed. The distributor issues credit notes and replacement invoices for a large portion of their daily dispatch — a process that adds administrative overhead and creates customer AR disputes.
Zero-rating applied inconsistently. In NZ food distribution, standard-rated and zero-rated goods often ship on the same invoice (a mixed delivery of, say, packaged snacks at 15% GST and fresh produce at 0%). An ERP that applies a single GST rate to all lines on an invoice will consistently mis-state the GST position. This creates a compliance liability and, if it runs undetected, can be difficult to unwind retrospectively.
Credit notes processed out of period. When the returns process is manual and slow, credit notes frequently fall in a different GST period from the original invoice. For a distributor filing GST returns monthly, this creates period-by-period GST mismatches that need to be explained to the IRD if audited.
No traceable delivery record for TSI documents. Under the post-2023 TSI rules, the distributor is responsible for ensuring the customer received the taxable supply information. A manual email process with no send confirmation or delivery record creates a gap in that audit trail. An ERP that logs invoice delivery — channel, timestamp, recipient address — provides the evidence trail needed.

What to build in from the start

Wholesale invoicing is not a module to add after the core ERP is live. The invoicing model — dispatch-triggered generation, catch-weight line handling, per-SKU GST treatment, automated credit notes, multi-channel delivery — needs to be defined in the design phase before build starts.

For a custom ERP serving a NZ food distributor, the invoicing design brief should specify: the trigger event (dispatch confirmation vs order confirmation, and why); which product categories carry which GST treatment; how catch-weight dispatch weights flow from the warehouse to the invoice line; how returns and short-shipments trigger credit note generation; and which delivery channels are required (email, EDI, portal, paper, or a mix).

If your distribution business has outgrown what your current accounting software can do for invoicing — or you're scoping a custom ERP and want to understand how invoicing fits into the wider system — talk to us about how Zeabyte has designed invoicing for NZ food distributors and wholesalers.

Learn about Zeabyte's custom ERP work · Integration capabilities · Talk to us

Talk to the team that does this every day

30 minutes, no obligation — we'll look at your systems and tell you exactly what's possible.

Talk to us