Prepare an NZ FBT Return from Supplier Invoices (IR420)

To prepare an NZ FBT return from supplier invoices, start by identifying invoices and related records that show benefits provided to employees, then classify each benefit by FBT category, track employee-level values and contributions, and roll the reviewed taxable values into the IR420 workflow. The working paper should preserve the supplier, document date, invoice number, recipient, benefit description, GST-inclusive value, allocation basis, de minimis status, taxable value, source file, and page reference.

That is the part most high-level FBT guidance leaves out. Inland Revenue explains the regime, forms, rates, and filing mechanics. Accounting-firm explainers usually summarise motor vehicles, gifts, low-interest loans, and other benefit types. But the person preparing the return still has to deal with the AP folder: venue invoices, restaurant receipts, gift-card purchases, fuel and repair bills, staff allocation notes, logbooks, insurance invoices, and payroll contribution records.

An IR420-ready workpaper is therefore not a dump of invoice totals. It is a reviewed bridge between source documents and tax categories. One row might begin as a supplier invoice for a staff event, but the final working paper needs to show which part was a staff benefit, which part related to clients, who received the benefit, whether an employee contribution reduced the taxable value, and where the reviewer can find the evidence.

For quarterly FBT return preparation in New Zealand, the practical sequence is:

1. Collect the quarter's supplier invoices, receipts, allocation registers, vehicle records, and contribution evidence.
2. Extract the source fields that are visible on those documents.
3. Add the judgement fields that are not visible on the invoice, such as recipient, purpose, FBT category, exemption status, and reviewer note.
4. Review the taxable values by benefit type before transferring totals into the IR420 or myIR workflow.

The same discipline also helps annual IR421 preparation. The return period changes, but the source-document problem is similar: messy financial documents need to become structured evidence that an accountant, bookkeeper, or finance manager can inspect without reopening every PDF from scratch.

Build the source-document pack before you classify benefits

Supplier invoices are the starting point, not the whole evidence file. A useful FBT pack usually combines AP documents with allocation notes from managers, employee contribution records from payroll or journals, and vehicle evidence held outside the invoice system.

IRD's FBT record-keeping requirements say the records an employer must keep depend on the benefit type, all FBT records must be retained for at least seven years after the relevant income year, and unclassified benefit and gift-card records should include the employee name, transaction date, benefit description, recipient contribution, and market price or purchase cost. That is why an FBT workpaper needs source references, not just category totals.

For a quarter, the pack might include:

• Restaurant, catering, venue, and event invoices.
• Gift-card, voucher, hamper, prize, and staff reward invoices.
• Vehicle purchase, lease, fuel, repair, registration, and insurance invoices.
• Insurance, superannuation, sickness, accident, or death benefit fund contribution records.
• Staff allocation registers showing who received what and when.
• Logbooks, private-use restrictions, unavailable-day evidence, and employee contribution records.

The extraction columns should separate what came from the document from what the preparer decided. Supplier name, invoice number, invoice date, line description, GST-inclusive amount, source file, and page reference are document fields. Recipient, pooled or attributed status, FBT category, de minimis treatment, private-use days, and review comments are workpaper fields. Keeping that distinction visible helps a reviewer see which facts are evidenced by source documents and which decisions need tax judgement.

GST evidence sits in the pack, but it should not take over the FBT analysis. When a supplier invoice is being used to support GST-inclusive values or input tax treatment, the preparer may need to check the NZ taxable supply information requirements. If the same AP evidence is also feeding the GST return, keep that reconciliation in a separate NZ GST101A supplier-invoice workpaper. The FBT question is different: whether the spend created a fringe benefit, who received it, and how it should be valued for the return.

Separate staff benefits from entertainment and client costs

A restaurant or venue invoice does not tell you the FBT treatment by itself. The supplier might be the same, and the total might be paid from the same AP batch, but the tax treatment depends on who benefited and why the cost was incurred.

This is where extraction has to move below invoice-header level. A mixed event invoice should be reviewed for line descriptions, dates, venue details, GST-inclusive amounts, attendee lists, business purpose notes, and any staff or client allocation. If a meal, gift, or event involved employees and non-employees, the workpaper should not carry the whole invoice total into FBT without separating the parts.

For example, a catering invoice for a client function with staff attending for business purposes is not the same record as a staff-only celebration. A gift basket sent to a client has a different character from a food or drink gift given to an employee. A venue invoice that bundles room hire, meals, drinks, and entertainment may need separate lines or a preparer allocation, especially if the invoice description is too broad.

The working paper should make the classification visible:

• What was supplied.
• Who received or mainly benefited from it.
• Whether the recipient was an employee, a client, or a mixed group.
• What amount was allocated to staff benefits.
• What evidence supports the allocation.
• Whether a reviewer has accepted the split.

The Australian FBT rules have their own meal-entertainment methods, so an Australian meal entertainment FBT receipt workflow is only a useful contrast for New Zealand teams dealing with trans-Tasman policies. For an NZ IR420 workpaper, keep the focus on New Zealand recipient and purpose evidence, and avoid importing the Australian treatment into the classification.

Track gift cards and unclassified benefits by recipient

Gift cards, vouchers, prizes, staff rewards, and subsidised goods create a different extraction problem from ordinary invoice coding. The supplier invoice proves the purchase cost, but it rarely proves which employee received each benefit. For FBT support, the invoice and allocation register need to sit together.

A practical voucher workpaper has two layers. The first layer is the purchase record: supplier, invoice number, date, description, number of cards or vouchers, face value, GST treatment where relevant, and total cost. The second layer is the employee allocation record: employee name, date provided, card or voucher type, value allocated, contribution, source invoice reference, and reviewer note.

That second layer is what makes de minimis tracking possible. For unclassified benefits and gift cards, the current limits include NZD 300 per employee for a quarterly return period, NZD 1,200 per employee for an income-year or annual return period, and NZD 22,500 across employees. Once a relevant limit is exceeded, FBT applies to the full relevant amount rather than only the excess. A single bulk voucher invoice cannot answer that test unless the workpaper links the purchase to recipient-level allocations.

Gift-card treatment has also become easier to get wrong if the preparer relies on old assumptions. Current Inland Revenue guidance distinguishes retailer-specific and general-use cards, and from 16 April 2025 employers can choose to apply FBT rules to all gift cards and vouchers. The working paper should therefore record the card type and treatment chosen, rather than leaving the reviewer to infer it from the supplier name.

The cleanest spreadsheet shape is one row per employee allocation, not one row per supplier invoice. If ten employees each receive a card from a single purchase invoice, the FBT support needs ten allocation rows tied back to the same source invoice. That structure lets the reviewer filter by employee, quarter, annual total, benefit type, and taxable status without reconstructing the distribution history from emails or manager notes.

Treat vehicle benefits as a document pack, not an invoice total

Motor-vehicle FBT is where supplier-invoice extraction helps, but it cannot carry the whole calculation. Vehicle invoices supply evidence of purchase cost, lease cost, fuel, repairs, registration, insurance, and other running costs. The FBT workpaper also needs facts that usually live elsewhere: vehicle make and registration, who had access to the vehicle, whether private use was available, exempt or unavailable days, restrictions communicated to employees, employee contributions, and the valuation basis selected.

For a quarterly return, the current Inland Revenue formula uses private-use days, capped at 90 days, multiplied by the cost price or tax book value basis and the relevant percentage. The current quarterly rates include 5% including GST for original cost price, 9% including GST for tax book value, and 10.35% including GST for tax book value where Investment Boost is relevant. Income-year and annual calculations use a different day base and percentages, so the workpaper should identify the return type before the reviewer applies the method.

The extraction pack should not pretend the fuel invoice total is the taxable value. A repair invoice might help reconcile that the vehicle existed and was in use. A lease invoice may help establish the lessor, vehicle, and period. An insurance invoice may support the vehicle pack. But the taxable value depends on the vehicle benefit rules, not on simply adding running-cost invoices.

Useful vehicle columns include:

• Vehicle registration, make, model, and year.
• Employee or pooled user.
• Source invoice and page reference for purchase, lease, or running costs.
• Cost price, tax book value, or reviewer-provided valuation basis.
• Private-use days, exempt days, and unavailable days.
• Evidence type, such as logbook, restriction letter, manager confirmation, or employee contribution record.
• Calculation method selected by the reviewer.
• Review status and notes.

This keeps the preparer honest about what the documents prove. Invoice extraction can assemble the vehicle evidence pack and remove re-keying, but the FBT method choice and final taxable value still need tax review.

Map the reviewed workpaper into IR420 or IR421

Once the source records have been extracted and reviewed, the workpaper should roll up from line-level support to return-ready totals. This is the point where the preparer stops asking "what does this invoice say?" and starts asking "what taxable value has the reviewer accepted for this benefit category?"

For an IR420 quarterly return, the line-level workpaper should be summarised by benefit type and treatment. Motor vehicles, low-interest loans, subsidised transport, employer contributions, unclassified benefits, and gift cards should not be blended into one total without category support. If IR427 worksheets or an equivalent internal schedule are being used, the workpaper should make it clear which rows support each worksheet total and which source documents sit behind them.

Annual IR421 preparation uses the same discipline over a longer period. Eligibility and filing-frequency choices should be checked against current Inland Revenue rules, including the relevant payroll-related thresholds, but the document workflow remains familiar: extract, classify, allocate, review, and retain the support. A finance team that has kept clean quarterly workpapers will usually have an easier annual pack than a team trying to reconstruct a year of benefits after balance date.

Gross-up, GST on fringe benefits, single rate, alternate rate, and attribution method choices belong in the review and calculation stage. The extraction file should provide the fields those calculations need, not bury them inside untraceable spreadsheet formulas. A reviewer should be able to filter the source rows, inspect the accepted taxable values, and see which method or rate assumption was applied.

There is also a payroll boundary. Employee names, contributions, benefits that are treated through PAYE, and annual remuneration data may need to be reconciled with payroll records. That is adjacent to NZ payday filing data extraction, but it is not the same job. The FBT workpaper supports the fringe-benefit return; payday filing has its own data fields, return cycle, and compliance checks.

Make the extraction workflow repeatable before the next FBT period

FBT preparation becomes less fragile when the extraction task is standardised before the next quarter begins. The prompt or template should ask for the fields the reviewer actually needs, not just the fields that happen to appear in the invoice header.

A useful extraction prompt for IR420 support might ask for one row per invoice line or benefit record, with columns for source file, page number, supplier, invoice number, invoice date, line description, GST-inclusive value, likely benefit type, employee or recipient if shown, allocation note, employee contribution if shown, and review flag. It should also ask the extraction to preserve ambiguous items rather than force a tax category when the document does not contain enough evidence.

Invoice Data Extraction is relevant at that document-preparation stage. Teams can upload mixed PDFs, JPGs, and PNGs, describe the fields they need in a natural-language prompt, and download structured Excel, CSV, or JSON output. The product can extract invoice-level or line-item data and include source file and page references, which is exactly the evidence trail an FBT reviewer needs when checking the workpaper.

That still leaves the tax judgement with the finance team, accountant, or adviser. The extraction output can show that an invoice line says "staff vouchers", that a manager note names five recipients, and that the source is page 2 of a supplier PDF. It should not decide, without review, whether the amount is exempt, taxable, attributed, pooled, or treated through another regime.

For recurring quarters, save the prompt once the reviewer is happy with the column structure. A stable prompt helps the team extract supplier invoice data into structured spreadsheets in the same shape each period, making comparisons and review notes easier to maintain. Keep extracted fields separate from judgement fields, store allocation evidence beside invoice evidence, and review the treatment before filing.