Australian Instant Asset Write-Off Register from Invoices

For FY 2025-26, Australian small businesses with aggregated turnover under $10 million can claim the instant asset write-off on assets costing less than $20,000 each. The threshold runs per asset, not per invoice. The deduction is timed by the date the asset was first used, or installed ready for use, in the business — not the date on the invoice. The register your tax agent expects in return is one row per eligible asset, capturing purchase date, supplier, asset description, GST-exclusive cost, business-use percentage, and that first-use date.

The threshold has moved several times in recent years and may move again. Always cross-check the ATO instant asset write-off page for the figure that applies to the income year you are working in.

If you are a sole trader, an SBE owner, a bookkeeper preparing a client handoff, or an accountant finalising the depreciation schedule, you have probably already decided to claim. The question is the records. You have a folder of supplier invoices — Hubdoc, Dext, the Xero bills attachments, an email folder, sometimes scans of paper — and a fixed deadline. The ATO publishes the eligibility rules; business.gov.au publishes a summary; the advisory firms publish explainers; the spreadsheet sites publish blank templates. None of them bridge the gap between the invoices you have and the populated register your tax agent will load.

That bridge is what this article covers. The instant asset write off register from invoices Australia practitioners actually have to produce — built line by line from supplier invoices, with the per-asset threshold tested per row, the first-use date captured alongside the extraction, and audit evidence attached to every row.

The article does not perform the depreciation calculation; the tax agent does that from the register. It does not adjudicate edge-case eligibility; that is also tax-agent territory. It does not build a parallel small business pool register; pooling is noted where the IAWO threshold is not met, and pointed to the ATO simpler depreciation page. The single deliverable, throughout, is the IAWO register row.

The columns the register actually needs

The ATO does not publish a register template. What it publishes are the four record-keeping requirements behind any capital allowance claim: the tax invoice itself, proof of payment, evidence of when the asset was first used or installed ready for use, and the basis for any business-use percentage less than 100%. Every column on the register either captures one of those pillars directly or feeds the downstream load into the depreciation schedule. Columns that do neither are clutter.

The shape that survives a tax-agent review and an accounting-software import looks like this:

• Purchase Date — the issue date on the tax invoice. Sets the income year for the cost record (though not necessarily for the deduction; first-use does that).
• Supplier Name — the legal entity on the invoice. Where the asset was acquired under recipient-created tax invoices (RCTIs) in Australia, the supplier on the register is still the supplier even though the buyer issued the invoice; some practitioners default to the issuing party and end up with the wrong name on the audit trail.
• Supplier ABN — eleven digits, validated. Most established suppliers carry an ABN on every invoice, but the column matters because a missing or invalid ABN on a payment over $75 GST-exclusive triggers no-ABN withholding on supplier invoices, and the cost recorded on the register has to reflect that withholding adjustment.
• Asset Description — specific enough that the tax agent can classify it for depreciation (effective life category, pool eligibility, private-use assessment). "Tools" is not enough; "Makita 18V impact driver kit, model DTD157" is.
• GST-Exclusive Cost and GST Amount — kept as separate columns. Where the entity is registered for GST, the depreciation base and the threshold test both run on the GST-exclusive figure; the GST amount is a separate input claim. Where the entity is not registered for GST (some sole traders below the $75,000 turnover threshold), the cost recorded is GST-inclusive — the GST is part of the asset's cost base, not a credit.
• Business Use % — the proportion the IAWO claim applies to. A laptop used 80% for business and 20% privately deducts at 80% of cost. The register carries the percentage; the working that supports it sits with the row's evidence (logbook, floor-area calculation, time-use estimate).
• First Use Date — the timing test. Captured separately from purchase date because it does not come from the invoice. The next section covers this in detail.
• Asset Location — where applicable. Vehicles, generators, tools, and equipment that move between sites benefit from a location column; office furniture rarely does. Useful when assets are later disposed of or reassigned.
• Depreciation Method Flag — IAWO, SBE pool, or general depreciation. This is what tells the tax agent which rows go where in the schedule, and it is what survives the export into the fixed-asset module.

Two of the four record-keeping pillars sit as register columns: the tax invoice (referenced by purchase date + supplier + asset description, with the source file linked or filed alongside) and first-use evidence (the date in the column, with the corroborating record attached). The other two — proof of payment and the basis for the business-use percentage — sit as attached evidence rather than register columns. The register is the index; the evidence folder is the substance.

The per-asset rule, the multi-asset invoice, and the second-element trap

The threshold runs on each asset, not on each invoice. ATO instant asset write-off guidance is explicit on the point: the instant asset write-off applies on a per-asset basis — Australian small businesses can claim it for multiple assets in the same income year as long as the cost of each individual asset is less than the relevant limit. Most of the operational decisions on the register flow from that single rule.

A worked example of the multi-asset invoice. A $30,000 invoice from a single supplier covering a separately-priced laptop, monitor, and printer at $10,000 each produces three eligible register rows. Each row tests against the threshold independently. The fact that the invoice header total exceeds $20,000 is not relevant. Three rows, three IAWO claims.

The inverse case bites the other way. A $25,000 invoice for a single ute produces no IAWO row. The asset costs more than the threshold, and there is no way to split the cost across invented sub-components to bring it under. The threshold either applies to the asset or it does not. The ute goes into the small business pool under simpler depreciation, with the cost recorded on the register and the depreciation method flag set accordingly.

Second-element costs are where borderline assets flip the wrong way. The cost base for IAWO purposes is not just the purchase price on the original invoice. It includes the second element of cost — freight, delivery, installation, and improvements added to the asset. When those costs arrive on a separate invoice from the asset itself, they belong on the asset's register row, not on a row of their own. A $19,500 industrial generator that ships with a $1,200 freight invoice and a $900 install invoice records on the register at $21,600. That asset is over the threshold. It is no longer eligible for IAWO and moves to the pool, even though every individual invoice in its cost base is under $20,000.

The operational consequence is that the register row for an asset frequently references more than one invoice. The audit trail spans the original purchase, any freight or delivery invoice, any install or commissioning invoice, and any subsequent improvement invoice that adds to the asset's cost base. If the row is collapsed back to "the laptop invoice" alone, the second-element costs are missing and the threshold test is wrong.

Where the per-asset judgement is genuinely a judgement call — a desktop tower invoiced at $14,000 with a separately invoiced monitor at $3,000, or a ute at $19,000 with a tray canopy fitted three weeks later at $4,500 — the question of whether the items are separately identifiable assets or one composite asset is tax-agent territory. The register's job is to surface the question, not to adjudicate it. Record both possibilities (separate rows with a flag, or combined row with a note) and let the tax agent decide. Pretending the question does not exist is what produces revisions on the way to lodgement.

The decision pointer for assets that exceed the threshold is the small business pool. Under simpler depreciation, the SBE pool absorbs the asset and depreciates it at pool rates rather than writing off the full cost in the year of first use. The depreciation-method flag column on the IAWO register tells the tax agent which rows are pool-bound; the tax agent's depreciation schedule handles the pool mechanics from there. The ATO simpler depreciation page covers the pool rules for practitioners who need to read further.

Extracting one register row per eligible asset across a year of invoices

If the threshold runs per asset, the extraction has to produce one row per asset. That is the configuration mismatch that makes most general-purpose extraction tools the wrong fit. Defaults across the AP-automation category are invoice-level: one row per invoice, the line items collapsed into a header total. For an IAWO register, that default is upside-down. A multi-asset invoice that produces one register row has lost the per-asset granularity the threshold test depends on.

The extraction step that fits the IAWO register is line-item, with prompt-driven controls that shape the output to the register's columns rather than to the supplier's invoice format. AI-powered supplier invoice extraction configured for one row per line item — with custom column names, a per-row classification step, and fallback hints for fields that move between supplier formats — produces the populated tracking spreadsheet directly from the year's invoice folder, without manual line-item reconciliation in between. The same line-item approach drives parallel AU tax workflows from supplier invoices, including how practitioners extract fuel tax credit claims from fuel invoices for the BAS.

The prompt for the IAWO register names the columns in the shape the register needs and instructs line-item-level output rather than invoice rollup:

"I'm building an IAWO asset register from this year's supplier invoices. Create one row for each line item that represents a separately identifiable asset. Use the column headers: Purchase Date, Supplier, Supplier ABN, Asset Description, GST-Exclusive Cost, GST Amount, Business Use %, First Use Date, Asset Location, Depreciation Method. Format Purchase Date as YYYY-MM-DD. Leave First Use Date blank and add a flag in a notes column where no delivery, install, or commissioning date is visible on the invoice. For the Depreciation Method column, classify each asset based on its individual GST-exclusive cost: under $20,000 mark IAWO, $20,000 or over mark POOL. Skip line items that are consumables, services, or non-capital purchases. Skip any pages that are remittance advice, statements, or email cover sheets."

Extending the prompt for the supplier ABN fallback ("ABN is usually in the footer; if not present in the footer, check the header block") or the supplier name normalisation ("use the legal entity name on the invoice; ignore trading names in headers") closes the gaps that show up across a real year's mixed-format folder.

A real year's invoice folder is heterogeneous. Some invoices are native PDFs from accounting software, some are scanned from paper, some are mobile photos uploaded into the bookkeeping app, some are multi-page PDFs that contain several separate invoices in one file, some are supplier statements that bundle a quarter's worth of invoices together. The extraction approach has to handle the mix without the practitioner pre-sorting and renaming files. Document filtering that recognises and skips the non-relevant pages — remittance advice, statements, email forwards — keeps the register from filling with junk rows.

Consistency across the year is the second-order problem and the one that makes the tax agent's life easier or harder. A register that names the GST-exclusive cost column "Net" on January's rows and "Subtotal" on June's rows will not load cleanly into the fixed-asset module. A register that records the same supplier as "Bunnings" on some rows and "Bunnings Group Limited" on others will not aggregate cleanly for supplier-spend reporting. Saving the prompt to a prompt library and re-running it against each batch of invoices enforces the column shape across re-runs and across the team — a bookkeeper running quarterly catch-ups uses the same prompt the year-end run will use, and the rows are interoperable.

The extraction produces the rows. It does not replace tax-agent judgement on edge cases — the desktop-and-monitor question, the ute-and-canopy question, the asset whose business-use percentage is genuinely unclear. Those rows go to the tax agent with a flag, not with a fabricated answer.

Capturing the first-use date alongside the extraction

The IAWO eligibility test does not run on the date on the invoice. It runs on the date the asset was first used, or installed ready for use, in the business. The invoice carries the purchase or issue date; first-use is a separate fact about the asset, and the practitioner has to capture it.

The consequence shows up at year-end. An asset purchased on 28 June 2026 but not first used until 5 July 2026 is a first-use event for FY 2026-27, not FY 2025-26. The IAWO deduction belongs to the income year of first use. If the register row carries only the purchase date, the tax agent has no way to tell which year the deduction lands in — and an asset claimed in the wrong year is one of the cleaner findings for an ATO desk review.

The practical solution is a dedicated First Use Date column on the register, populated alongside the extraction rather than reconstructed from memory months later. The extraction step can do meaningful work here: when a delivery date, install date, or commissioning date is visible on the invoice — a separately priced "Delivery 12 May" line item, a "Commissioned and ready for use" footer, an attached delivery docket — the extraction surfaces it as a candidate first-use date. When no such reference is visible, the row is flagged as needing manual completion.

The flag is not a defect. It is the cue. The practitioner fills the date from delivery records, install reports, photo metadata, calendar entries, supplier tracking emails, or, where nothing else exists, a contemporaneous note explaining how the date was determined. Capturing the date during extraction — when the invoice is open and the context is fresh — produces a defensible answer; reconstructing it in October from a single line on a register populated in April produces a guess.

The audit-evidence implication matters here. The ATO's published guidance on capital allowance records is explicit on the point: financial records alone — invoices and bank statements — do not usually evidence first use. The corroborating records (delivery dockets, install reports, photos with metadata, commissioning notes, calendar entries showing the asset in use) attach to the register row as evidence of the date. The First Use Date column points to the evidence; the evidence sits in the per-asset folder alongside the invoice.

The rolling-purchase case needs explicit treatment. An asset paid for in stages — a 30% deposit on order, balance on delivery, install three weeks later — carries multiple invoice dates and a separate first-use date that may match none of them. The register records the date the asset was installed ready for use, which is typically the latest of the three: deposit invoice, balance invoice, install completion. A refrigerated van fit-out ordered in April, paid for in May, delivered in late June, and commissioned in early July is a FY 2026-27 first-use event, even though the substantive payments hit FY 2025-26. The register row's First Use Date column carries that distinction; the cost-base columns reflect the full purchase including the install costs from the third invoice.

Building the audit-ready evidence chain behind every row

The four ATO record-keeping requirements behind any capital allowance claim are the tax invoice itself, proof of payment, evidence of the first-use or installed-ready-for-use date, and the basis for any business-use percentage less than 100%. Run them as a per-row check against the populated register before anything goes to the tax agent — the register row is fine on its own; the row plus its evidence chain is what survives preparing invoice records for an ATO audit.

Tax invoice. Every row references the source invoice file, with the file linked from the row or filed under a per-asset reference (purchase date + supplier + asset description, or a generated asset ID). For rows where second-element costs sit on a separate invoice — the freight, the install, the improvement — the additional invoices are linked from the same row. The invoice itself meets ATO tax invoice requirements: supplier identity, supplier ABN where applicable, GST breakdown for invoices over $82.50 GST-inclusive, the issue date, a description of what was supplied, and the GST amount. Invoices that do not meet the requirements need follow-up with the supplier before the row is final.

Proof of payment. Each row links to the bank statement line, payment receipt, or accounting-software payment record that settled the invoice; for cash purchases, the supplier-issued receipt is the evidence and the absence of a bank record is worth a note on the row.

First-use evidence. Each row carries the First Use Date in the column and a reference to the corroborating record: the delivery docket signed on receipt, the install report from the contractor, photo metadata showing the asset in operation, a calendar entry blocking out the install day, a commissioning note from the supplier. Rows where the date was filled from memory because nothing else exists carry that note explicitly — "first-use date determined from operator recollection, no contemporaneous record" is a defensible position; a date with no explanation is not.

Business-use percentage basis. Each row with a business-use percentage less than 100% carries a note on how the percentage was determined. A vehicle's percentage comes from a logbook covering at least twelve continuous weeks of typical use. A home-office asset's percentage comes from a floor-area calculation, time-use estimate, or a documented apportionment method. A tool used for both business and personal projects might carry a time-use estimate based on jobs completed. A bare "80%" with no basis is the row most likely to be challenged on review; the note does not have to be elaborate, but it has to exist.

The retention obligation runs five years from the date the relevant return was lodged or the records were prepared, whichever is later. The register and its attached evidence are a single bundle for that purpose — losing the evidence folder strands the rows, so a backup of the per-asset evidence folder held separately from the working accounting file is cheap insurance. The filing pattern that holds up over time is straightforward: the register is the index, and each row's reference (purchase date + supplier + asset description, or a generated asset ID) names a per-asset folder under the FY directory containing the source invoice or invoices, the payment record, the first-use evidence, and the business-use-percentage working.

Handing the register to the tax agent or loading it into your accounting software

The handoff is a single spreadsheet, one row per eligible asset, in the column shape the prior sections established. Filename convention matters more than it sounds — "Smith Trading 2025-26 IAWO Register.xlsx" is what the tax agent's intake system files cleanly; "asset list final final v3.xlsx" is what gets emailed back asking which version is current. Entity name, financial year, and the words "IAWO Register" make the file self-describing for both the agent and any later audit.

The Depreciation Method flag column is what tells the tax agent which rows go where. IAWO rows go to the immediate write-off in the year of first use; POOL rows go to the small business pool under simpler depreciation; rows flagged for general depreciation (assets the SBE has elected to depreciate outside the simpler depreciation rules, or assets acquired before the entity became an SBE) carry their own depreciation calculation. Some tax agents prefer a separate tab per depreciation method rather than a single sheet with a flag column; the column flag supports either format with a quick filter.

For practitioners running their own books, the same register loads into the fixed-asset module of the major Australian accounting platforms with minor column renaming. Xero's fixed asset register accepts an import with purchase date, supplier, description, cost, depreciation start date, and depreciation method as the core columns. MYOB's asset register and QBO's fixed asset module accept the same shape with platform-specific column names. Reckon's asset register sits in the same neighbourhood. The depreciation start date in every case is the first-use date, not the purchase date — a row that loads with the purchase date in the depreciation start column will calculate depreciation from the wrong day. Bookkeepers running client books load the register on the client's behalf; the column shape does not change.

Capital purchases also report on the BAS at G10 (capital purchases) and 1B (GST credits on capital purchases). That is a separate quarterly reporting deliverable from the annual asset register: the register feeds the depreciation schedule, the BAS feeds the GST account. The two should agree on what was bought and when, but they are not the same document and the IAWO register does not collapse into the BAS workpapers. For practitioners preparing your BAS in Xero, the same supplier-invoice extraction step can serve both deliverables when the prompts are configured for each — one prompt for the BAS-side capital purchases summary at G10 / 1B, one prompt for the IAWO register columns at year-end.

Sole traders and SBEs on a 30 June year-end typically run the extraction in May and June, the audit-evidence checks in early July, and the handoff in July through September; bookkeepers work to whatever the tax agent's intake schedule is, which often pulls the deadline forward.