Extract Australian Tax Depreciation Schedules to Excel

To convert an Australian tax depreciation schedule to Excel, reduce the quantity surveyor report to the current-year Division 43 capital works claim, Division 40 plant and equipment claim, the depreciation method used, any low-value pool deduction, ownership and rental-use apportionment, and source-page evidence. A good extraction reconciles to the report's annual summary while preserving enough asset-register detail for review, SMSF audit support, and later schedule amendments.

That is the practical job. The QS report may run 30 to 60 pages, with cover notes, property details, annual deduction summaries, capital works schedules, plant and equipment tables, low-value pool lines, and method comparisons. The tax workpaper should not copy the PDF page by page. It should turn the report into a structured worksheet that a tax agent, SMSF accountant, property bookkeeper, or portfolio investor can review and carry into the rental schedule or SMSF annual return.

The main risk is treating extraction as tax advice. A BMT depreciation schedule to spreadsheet workflow, a Washington Brown report conversion, or an MCG, Capital Claims or Duo Tax extraction can organise the data, but the practitioner still decides what is claimable for the client, which method is being used, whether apportionment has been applied correctly, and whether any post-May 2017 second-hand residential plant issue needs review.

For a firm handling more than one property, consistency matters more than faithfully reproducing each provider's layout. The output should let a reviewer compare properties, years, providers and entities without reopening every PDF. The schedule remains the source document. The spreadsheet becomes the working layer that makes the numbers reviewable.

Start with the annual summary, then prove the numbers

Most depreciation schedules give the answer before they give the evidence. The annual summary usually shows the total deduction for each income year, often split between capital works and plant and equipment, and sometimes split again by prime cost and diminishing value. That summary is the fastest place to find the current-year claim, but it should not be the only data extracted.

The summary has to be tied back to the supporting pages. At minimum, capture the property address, ownership details shown in the report, QS provider, report date, schedule version, income year, Div 43 amount, Div 40 amount, low-value pool amount, selected method, and the page number or table reference where each figure appears. Provider metadata matters because an amended schedule, a later inspection, or a replacement report can change which PDF supports the number in the tax file.

The capital works pages usually support the building and structural component of the claim. The plant and equipment asset register supports the asset-level claim, with details such as asset description, effective life, cost, opening adjustable value or written-down value, current-year deduction, and closing value. Low-value pool tables need their own treatment because pooled amounts can be easy to double count if the extraction simply pulls every visible deduction line.

This evidence layer is also consistent with ATO record-keeping expectations. The ATO guidance on depreciating assets in rental properties says taxpayers should keep at least a spreadsheet for rental-property depreciating assets and notes that a quantity surveyor can prepare a report when a rental property is purchased. For a practice file, that means the spreadsheet should show not only the deduction amount, but also where the amount came from.

Mixed-provider PDFs make this discipline more important, not less. A Washington Brown depreciation schedule Excel conversion may label or order the tables differently from a BMT, MCG, Capital Claims or Duo Tax report. The extraction target should be the firm's workpaper schema, with provider-specific wording mapped into standard fields.

Build the Excel schema around tax review, not PDF layout

A useful worksheet starts at the property and income-year level. Core fields should include client or entity, property address, ownership percentage, rental-use percentage, QS provider, report date, schedule version, income year, Div 43 claim, Div 40 claim, depreciation method selected, low-value pool deduction, SMSF notes where relevant, source page, and review flags.

That structure gives the reviewer a file they can sort, filter and reconcile. It also avoids a common mistake: rebuilding each provider's PDF layout in Excel. A firm-wide schema is more useful than separate BMT, Washington Brown, MCG, Capital Claims and Duo Tax templates because the tax work is the same even when the report design changes. The question is whether the worksheet supports return preparation, partner review, client queries and audit evidence.

For SMSF files or audit-heavy property portfolios, add an asset-level tab. Useful per-asset fields include asset description, category, acquisition or installed date where available, original cost, effective life, opening adjustable value or written-down value, current-year deduction, closing written-down value, claimable flag, and pool flag. The asset-level tab should feed the property-level totals, not compete with them.

Keep related property documents in the same workpaper ecosystem, but do not merge their fields into the depreciation schedule table. An SMSF property compliance pack may include the depreciation report alongside leases, loan statements and expense evidence. Australian council rates notice extraction and Australian land tax assessment extraction support different tax and bookkeeping questions. The depreciation schedule should remain the worksheet for non-cash deductions, asset registers and capital works evidence.

Review flags are worth treating as first-class fields. A flag might mark an amended schedule, unclear ownership percentage, missing rental-use apportionment, post-May 2017 second-hand residential plant, a low-value pool line that needs checking, or a method mismatch between the annual summary and asset register. These flags let a preparer separate extracted data from judgement still required.

Treat Div 43, Div 40 and low-value pool lines differently

The extraction should not flatten every depreciation line into one table of amounts. Div 43 capital works and Div 40 plant and equipment answer different tax questions, and the worksheet should preserve that difference.

Div 43 is usually the building and structural allowance. In a QS report it may appear as capital works, building allowance, structural improvements, construction expenditure, or a similar label. The useful extraction fields are property, income year, capital works amount, start date or construction date where shown, rate, source page, and any note that affects the capital works base. The workpaper usually does not need every line of building-cost narrative unless the file is being reviewed in detail.

Div 40 is asset-register work. Plant and equipment rows need the asset description, cost, effective life, method, opening adjustable value or written-down value, current-year deduction, closing value, and claimable status. If the report shows both prime cost and diminishing value columns, those are alternative method outputs for review. They are not amounts to add together.

Low-cost and low-value pool lines need separate identification. If a pooled asset appears in both an asset register and a pool summary, the extraction should mark the pool flag and reconcile the pool deduction to the annual summary. A plain table scrape can pull both the individual line and the pool total, which creates a double-count risk before anyone reaches the tax software.

The post-May 2017 treatment of second-hand residential plant is another reason to separate extraction from judgement. The worksheet can flag assets that appear to be second-hand residential plant, show acquisition or installed dates where available, and preserve the source page. It should not silently decide eligibility.

For a prompt-based workflow, the instruction should name the schema, not ask for a broad summary. In Invoice Data Extraction, a practitioner can upload financial documents and use a natural-language prompt to request structured Excel, CSV or JSON output. For a QS report, the prompt should ask for separate Div 43, Div 40, method comparison, pool indicator, source-page and review-flag fields. The tool structures the schedule; the accountant reviews whether the tax treatment is correct.

Reconcile the extraction before it reaches the tax return

The first reconciliation is method selection. If the annual summary uses diminishing value, the extracted asset rows should not accidentally feed prime cost amounts into the workpaper. If the report shows both methods, the spreadsheet should carry both only as review columns, with a separate selected-method field controlling the claim total.

The second reconciliation is the roll forward. For Div 40 assets, opening adjustable value plus additions or relevant adjustments, less current-year depreciation, should lead to the closing written-down value shown by the schedule. A small difference may be rounding. A large difference may mean the extraction picked up the wrong year, the wrong method column, or a subtotal rather than an asset line.

Capital works need a different check. Review the start date, rate and annual amount for plausibility, then confirm the extracted Div 43 total agrees to the annual summary. This is especially important when the report includes multiple construction periods, renovations or amended capital works bases.

Low-value pool checks should happen before apportionment. Confirm that pooled deductions have not been counted once in the ordinary asset register and again in the pool table. Then check ownership and rental-use percentages. Apportionment should be visible in the worksheet and applied once. It should not be applied once during extraction, again in the workpaper, and a third time in tax software.

Schedule amendments deserve their own evidence fields. When a client sends a revised QS report, tie extracted rows to the provider, report date, schedule version and source page. Without version control, a current-year amendment can be mixed with prior-year figures from the old PDF.

For SMSF property files, the same discipline supports audit evidence as well as return preparation. The depreciation worksheet sits alongside bank records, leases, repairs evidence, valuation material and rental statements. Where the property ledger is maintained through agent statements, PropertyMe, PropertyTree and Console owner statement extraction can support the cash-income and expense side, while the QS schedule supports the non-cash depreciation claim.

When automation is worth it, and when the QS export is enough

Automation is not always the right starting point. If a single-property investor receives a clean Excel or CSV export from the QS provider, and the figures are easy to enter into the rental schedule, a separate extraction workflow may add little value. The original export, checked against the PDF and saved with the client records, may be enough.

Extraction becomes more useful when the work is repeated, inconsistent or review-heavy. A tax practice may receive BMT PDFs for some clients, Washington Brown reports for others, older MCG schedules for long-held properties, and amended reports from smaller providers. A property bookkeeper may need one portfolio worksheet across entities and income years. An SMSF accountant may need asset-level evidence that can stand up in both return preparation and audit support.

In that setting, the value is standardisation. The firm can define one schema for property details, Div 43, Div 40, low-value pool, method, apportionment, source page and review flags, then map every provider's report into that schema. That is where financial document extraction into spreadsheets fits the workflow: received QS PDFs become consistent workpapers rather than one-off manual readings.

Invoice Data Extraction supports that kind of prompt-based conversion by letting users upload financial documents, describe the fields they want, and download structured XLSX, CSV or JSON output. The platform is designed for volume as well as simple jobs, with batches of up to 6,000 mixed-format files and single PDFs up to 5,000 pages. Those are extraction capabilities, not tax conclusions. The review still belongs with the accountant, adviser or property specialist.

The strongest use case is a firm that wants consistent first-pass data before professional review. The weakest use case is a clean, current provider export for one property where the reviewer can already see the necessary figures.

A practical workflow for a firm-wide depreciation workpaper

Start by collecting the QS PDF or provider export with the client file, then confirm the property, entity, provider, report date and schedule version before extracting any figures. If the client has sent more than one schedule, decide which version supports the current workpaper and keep the old version separately for history.

Extract to the firm's schema, not to the PDF's visual order. The first tab should hold the property-level income-year figures: Div 43, Div 40, low-value pool, selected method, ownership percentage, rental-use percentage, source page and review flags. A second tab can hold per-asset Div 40 details for SMSF, audit-heavy or portfolio files.

Reconcile before import. The annual summary should agree to the extracted claim totals. Method columns should be clearly separated. Pool lines should not be double counted. Apportionment should be visible and applied once. Any post-May 2017 second-hand residential plant issue, amended schedule note or unclear ownership detail should remain flagged until a reviewer resolves it.

Store the final Excel file with the QS source document and the tax workpaper, using a name that identifies the client, property, income year and schedule version. For next year's return, versioned and source-linked rows are faster to roll forward than another manual read of a long PDF.