Extract Australian Council Rates Notices to a Spreadsheet

Every Australian council rates notice carries the same structural core: a rateable property identifier (council assessment number, address, lot and plan), a property valuation, the valuation method that produced it, the rate-in-the-dollar applied, the resulting general rate, fixed and variable service charges (typically waste, sewer, stormwater, sometimes library or environmental management depending on council), a state-government levy where one applies, the total payable, and the instalment options. That common core is where the consistency ends. Format varies across the country's 537 local government areas, three valuation methods (Site Value, Capital Improved Value, Net Annual Value) are in active use depending on state and council choice, and the state-government levy line differs by state — Victoria's notices carry a prominent levy line where Western Australia's typically do not.

To extract Australian council rates notice data into a working spreadsheet across a multi-property portfolio, the schema needs to handle that variation by column, not by hoping the notices align. The audience for this is concrete: residential investors holding two or more rental properties across one or more LGAs, residential property managers running rates on behalf of multiple landlords, commercial property managers handling outgoings recharge under net leases, and accountants pulling together rental schedules at tax time, often alongside PropertyMe, PropertyTree and Console owner statement spreadsheet work. Most of them face notices from several councils each year. Many face notices from more than one state. The consolidated dataset has to support three distinct downstream workflows from one extraction pass: ATO deduction substantiation at 30 June, settlement apportionment when a property changes hands, and commercial tenant recharge under the state-by-state Retail Leases Acts.

The starting point is the field-mapping table — the spreadsheet schema that sits underneath every section that follows.

Column	What it captures
AssessmentNumber	The council's primary identifier for the rateable property
PropertyAddress	Full street address as printed on the notice
LotPlan	Lot and plan or lot and DP, where shown
Council	Issuing council name (LGA)
State	NSW / VIC / QLD / SA / WA / TAS / NT / ACT
RatingYearStart / RatingYearEnd	Period the assessment covers, typically 1 July to 30 June
ValuationMethod	Site Value / Capital Improved Value / Net Annual Value / Gross Rental Value / Unimproved Value
ValuationAmount	The valuation figure used in the rate calculation
RateInTheDollar	Cents in the dollar applied to the valuation, where shown
LineType	General / Differential / Targeted / Service / Levy
LineDescription	What the line is (e.g. General Rate, Domestic Waste Management Service, ESVF, Coastal Protection Levy)
LineAmount	Amount for that line
TotalPayable	Total annual liability per the notice
InstalmentNumber	1 to 4 for quarterly instalments, or a flag for lump-sum
InstalmentDueDate	Date that instalment falls due
InstalmentAmount	Amount of that instalment

One row per extracted line item, with notice-level identifiers (assessment number, property address, council, rating-year dates, total payable) repeated on each row. That denormalised shape is what supports portfolio queries by line type, by council, by state, and by rating year without re-extraction.

The rest of this guide walks the dimensions that vary across the portfolio: the three valuation methods and which state defaults to which, the state-government levy overlays with the current Victorian regime as the most important freshness item, the format variation across the major capital-city councils, the rate line types and instalment columns that complete the schema, the linkage from the consolidated dataset back to the three downstream uses, and three honest extraction routes covering manual entry, per-LGA portal export, and batch multi-LGA processing.

Three valuation methods that shape the rate calculation

Three valuation bases sit underneath Australian council rates, and which one applies depends on the state and, in some states, the council's choice within the options the relevant Local Government Act allows. Site Value (SV) is the unimproved value of the land alone — what the parcel would be worth with no buildings, fixtures, or landscaping on it. Capital Improved Value (CIV) is the total market value of the property including all improvements. Net Annual Value (NAV) is a notional annual rental yield the property could command, used in some jurisdictions particularly for non-residential property; Gross Rental Value (GRV) is the related rental-based measure used predominantly in Western Australia. The terminology shifts across legislation — NSW uses "Land Value" for what is structurally the unimproved figure, the NT and ACT use "Unimproved Capital Value" — but the three concepts (land only, land plus improvements, rental yield) are the bases in active use across the country.

The state-by-state default looks roughly like this:

State	Default valuation basis
Victoria	Capital Improved Value, set under the Valuation of Land Act 1960
New South Wales	Land Value (the unimproved capital value), Valuation of Land Act 1916
Queensland	Site Value for most residential property, with Statutory Value variants under the Land Valuation Act 2010
South Australia	Council choice between Site Value, Capital Value, or Annual Value, Local Government Act 1999
Western Australia	Gross Rental Value for urban property, Unimproved Value for rural
Tasmania	Council choice between Capital Value, Assessed Annual Value, or Land Value
Northern Territory	Unimproved Capital Value
ACT	Unimproved Value as the predominant basis

The practical extraction point is the column-design point most cross-LGA spreadsheets miss: a portfolio dataset must carry ValuationMethod and ValuationAmount as separate columns, because the bases are not directly comparable. A $4,200 rates bill against an $850,000 CIV in Melbourne and a $4,200 rates bill against a $620,000 Land Value in Sydney are not telling the same story about rates burden. A RateInTheDollar figure means nothing without the method that produced its valuation, and a year-on-year comparison across the portfolio falls apart silently if one council switches its valuation cycle and another doesn't.

The mechanism itself is straightforward once the columns are in place. The council sets a rate-in-the-dollar — cents in the dollar of the property's valuation — and multiplies it by the valuation to produce the general rate component. Where the council uses differential rates, different categories of property (residential, commercial-industrial, vacant land, primary production) are assigned different rates-in-the-dollar, so a capital improved value rate in dollar calculation produces materially different general-rate figures for the same valuation depending on category. The differential category itself belongs in the spreadsheet as part of LineDescription.

Two regulatory mechanics also leave traces in the dataset. Rate caps — NSW's IPART-set rate peg, Victoria's Fair Go Rates System, equivalents in other states — constrain year-on-year increases to council general-rate revenue, which means the rate-in-the-dollar typically moves inversely to revaluations to keep aggregate revenue within the cap. A multi-year portfolio dataset shows this directly: when the valuation jumps after a revaluation, the rate-in-the-dollar drops, and the general rate moves by less than the valuation movement alone would suggest. Revaluation cycles also differ by state — NSW councils receive Land Values from the Valuer General every three years for rating purposes, Victorian councils have moved to annual revaluations for many properties, and other states sit somewhere in between. Year-over-year notice comparisons across a portfolio will show different valuation amounts even where the property hasn't changed, and the rating year context is what makes those comparisons coherent.

State-government levy overlays and the ESVF transition

The most important state-government levy item to get right at extraction is Victoria's, because it changed names and structure in 2025. From 1 July 2025, the Emergency Services and Volunteers Fund collected via council rates replaced the Fire Services Property Levy in Victoria. Victorian council rates notices issued from that date carry the ESVF as a distinct line; older notices in a portfolio's archive will still show "FSPL". For year-on-year extraction across a Victorian portfolio, treat ESVF as the successor regime to FSPL on the same line in the rates notice — not as a new charge on top of an existing one. Otherwise the year-on-year comparison double-counts what is structurally one continuing levy under a renamed regime. The Victorian State Revenue Office is the authoritative source on the transition and the current ESVF rates by property classification.

The rest of the state-by-state regime sits on a different shape:

• New South Wales — the Emergency Services Levy is funded through a combination of council contributions, an insurance industry contribution, and a state government contribution. Some NSW council notices show an emergency-services-related line where the council is recovering its contribution; many do not. Treat the NSW situation as state-funded with council contribution rather than a clean per-notice line item. The NSW Emergency Services Levy ESL council rates picture has been an active policy area, and the line's presence and label varies enough that the extraction prompt should not assume it appears.
• South Australia — the Emergency Services Levy is collected separately by RevenueSA, not by councils. SA portfolios receive a council rates notice and a separate RevenueSA ESL notice for the same property, both keyed to the same valuation data. The portfolio spreadsheet needs to capture both, with the RevenueSA ESL extracted as its own row keyed to the same AssessmentNumber (or to a property-level identifier where the assessment number on the two notices differs).
• Australian Capital Territory — the ACT levies a Fire and Emergency Services Levy as part of its territory rates regime; because the ACT does not have separate local councils, rates are issued by the territory government rather than by a council, and the FESL rides on the rates notice.
• Northern Territory — emergency-services and waste-related contributions vary by jurisdiction within NT council rates structures; the per-notice line set is not consistent across NT councils.
• Western Australia, Queensland, Tasmania — emergency-services funding is generally state-funded rather than levied through council rates as a distinct line, though Western Australia's Emergency Services Levy was an active topic earlier in the decade and individual council notices should still be checked for any jurisdiction-specific lines.

The multi-state extraction implication is concrete. State-government levies live in the spreadsheet as LineType = Levy, with LineDescription carrying the specific name — ESVF, ESL, FESL — and the issuing entity captured either in Council (where the council collects on behalf of the state, as in Victoria) or in a separate field for the state revenue office (as for South Australia's RevenueSA-issued ESL). Without that discipline, a portfolio-level pivot treats Victorian ESVF, an NSW emergency-services council contribution, and a RevenueSA ESL as the same line, and the resulting summary obscures the structural differences a multi-state operator needs to see. Where ESVF Victoria council rates extraction sits next to NSW notices in the same dataset, the column shape is what holds the comparison together; the prompt that produces the dataset has to know to look for the levy line in different places on different states' notices.

For portfolios with notices from before 1 July 2025, treat FSPL as the predecessor of ESVF on the same line — useful for time-series analysis on Victorian property, but not a separate concept that needs its own column. A flag indicating the regime in force at the rating-year boundary is enough.

Notice format variation across the major capital-city councils

With 537 LGAs across the country, no two council rates notices look identical. The major-capital-city councils show the conventions a portfolio holder will encounter most often, and their layouts are also influential — smaller councils within each state tend to follow a shape resembling the capital-city council in their state. The snapshot below covers the dimensions that actually affect extraction: which valuation method appears, how the state-government levy is presented, how service charges are segregated, what differential categories are visible, and the typical instalment cadence.

Council	Valuation method on the notice	State levy line	Service-charge segregation	Differential categories	Instalment cadence
City of Sydney	Land Value	Not consistently present as a per-notice line	Domestic Waste Management charge segregated as a separate line	Residential / Business categories with sub-categories visible	Quarterly (Aug, Nov, Feb, May typical)
City of Melbourne	Capital Improved Value	ESVF prominently shown as a distinct line	Smaller fixed service-charge set; waste typically bundled	Residential / Commercial / Industrial / Vacant differentials	Quarterly (Sep, Nov, Feb, May typical)
City of Brisbane	Site Value (rateable value)	Not on the council notice as a state line	Separate water and wastewater charges may appear within or alongside the rates notice depending on the billing arrangement	Residential / Commercial / Multi-residential / Other categories	Quarterly
City of Perth	Gross Rental Value	Not on the council rates notice	Service-charge lines for waste and other levies; ESL handling depends on the year	Residential / Non-residential categories	Often four instalments or annual lump-sum
City of Adelaide	Council-chosen basis (Capital Value or similar under the LG Act 1999)	RevenueSA's ESL is issued separately and does not appear on the council notice	Waste and CWMS-style charges where applicable	Residential / Commercial / Industrial / Vacant categories	Quarterly

The practical extraction point follows directly: a prompt that works cleanly on a Sydney notice will not produce the right line shape on a Melbourne notice, because the levy line, the service-charge segregation, and the differential category presentation differ. Cross-LGA consolidation requires either a prompt that tolerates the variation — looking for the levy line under multiple possible labels, treating Domestic Waste Management as a service line even when other councils bundle it — or a per-state prompt strategy where the extraction runs once per state and the outputs are concatenated. The same problem appears in UK business rates demand notice extraction, where billing-authority-level format variation across England and Wales raises the equivalent multi-jurisdiction extraction question; the answer in both cases is column-stable schema and prompt-level tolerance for line-shape variation, not per-notice manual reconciliation.

Where format variation actually shows up is worth naming concretely so the prompt and the spreadsheet design account for it:

• Line-item count and granularity. A Melbourne notice may itemise five lines (general rate, ESVF, waste, environmental, total). A Sydney notice may itemise differently, with the differential rate label embedded in the general-rate line and a separate Domestic Waste Management charge.
• Where the levy line sits. Victoria places ESVF prominently. South Australia's ESL doesn't appear on the council notice at all. NSW notices are inconsistent.
• Whether utility-style charges are bundled. Queensland councils often run water and wastewater separately, sometimes on the same notice, sometimes separately. NSW segregates Domestic Waste Management.
• Whether the rate-in-the-dollar is printed. Some councils print the cents-in-the-dollar figure prominently; others print only the calculated general rate, leaving the rate-in-the-dollar to be derived from the council's published rate schedule.
• Arrears, credits, and adjustments. Prior-period balances appear differently across councils — sometimes as a distinct line item with its own line type, sometimes folded into the opening balance. The extraction should preserve the distinction so current-year liability isn't misstated by prior-year arrears.

This is the snapshot the SERP cannot supply from any single source. Each council page describes its own format, no regulator publishes a cross-council comparison of notice conventions, and the major rates-comparison sites focus on the rate-in-the-dollar figure rather than how the underlying notice is laid out. To consolidate council rates across LGAs Australia-wide, the format-variation map matters more than any single council's documentation.

Rate line types and instalment columns that complete the schema

The LineType column is what lets a portfolio dataset be queried meaningfully. Five values cover essentially everything that appears on an Australian rates notice:

• General. The council's main rate, calculated as valuation multiplied by rate-in-the-dollar. Typically one line per notice. Where the council prints its general rate as a single figure without the rate-in-the-dollar, the spreadsheet still captures the result; the input figures live in the council's published rate schedule.
• Differential. Where the council applies different cents-in-the-dollar to different property categories — residential versus commercial-industrial versus vacant land versus primary production — the differential category belongs in LineDescription so a portfolio query can filter by category. Differentials are common in larger councils; smaller rural councils often run a flatter schedule. From an extraction perspective, a differential rate is structurally the general rate with an extra label.
• Targeted. Levied on a specific service area or a defined group of properties: coastal protection levies on coastal LGAs, Business Improvement District levies on commercial precincts, special rate areas funding street upgrades or precinct programs. Targeted rates appear only on a subset of properties in a portfolio and easily get lost without their own line type.
• Service. Fixed or variable charges funding specific functions — waste management, sewer, stormwater, library, environmental management. Whether these appear on the rates notice or a separate utility notice varies by council. The Domestic Waste Management charge in NSW is the most consistently-segregated example.
• Levy. State-government levies as covered earlier (ESVF in Victoria, FESL in the ACT, council ESL contributions in NSW where they appear), plus the SA ESL extracted from the separate RevenueSA notice and folded into the same dataset.

The reason to keep these as five distinct values rather than collapsing service charges and levies, or general and differential, is that the downstream uses care about the distinction. ATO substantiation cares whether a charge is council-imposed or a state levy collected on the council's behalf. Settlement apportionment cares whether a charge runs on the council's rating-year cycle or a separate state cycle. Commercial outgoings recovery under retail leases cares whether a charge is a recoverable outgoing under the lease and the relevant Retail Leases Act, which often turns on which body imposed the charge. The line-type discipline is what makes those downstream questions answerable from one extraction pass. Irish commercial rates show a similar general-plus-targeted structure underneath their own terminology — see Irish commercial rates bill extraction for the analogous line-type-and-charge-component breakdown that underpins commercial rates billing in another jurisdiction.

The instalment dimension sits alongside the line types. Most Australian councils offer quarterly instalments aligned to the rating year that runs 1 July to 30 June, with typical due dates falling around September, November, February, and May (the exact dates vary by council). Some councils offer a discount for paying the full annual amount early; the discount affects cash flow but not the deductible expense, which is the rates assessed for the period regardless of when each instalment is paid.

For a quarterly rates instalment tracker Australia-wide, the columns to carry are InstalmentNumber, InstalmentDueDate, and InstalmentAmount. A clean convention works: InstalmentNumber runs 1 to 4 for quarterly, and a single row with InstalmentNumber = 0 (or a separate flag column) records lump-sum payments. Whichever convention a portfolio adopts, consistency across councils matters more than the choice itself. Joined back to the line-type rows, the instalment rows give a payment schedule the portfolio can run cash-flow forecasts off, while the line-type rows give the assessed-liability view the deduction substantiation works from.

Two adjustments deserve dedicated handling. Arrears and credits from prior periods appear on some notices as distinct lines and on others folded into an opening balance. Capture them with a distinct line type or an explicit flag so prior-year liability doesn't get re-counted as current-year expense. The cash-versus-accrual distinction matters for accrual-basis investors and for ATO substantiation: the deductible expense is the rates assessed for the rating year, regardless of when the instalments are paid. The instalment columns track payment timing; the TotalPayable line tracks the assessed liability. When the rating year and the financial year align (1 July to 30 June), the two views collapse into the same number; when a property is sold mid-year or the assessment is revised, they don't, and that's exactly when the per-line, per-instalment schema starts earning its place.

Three downstream uses the consolidated dataset has to feed

A single per-notice, per-line spreadsheet supports all three downstream workflows without re-extraction, as long as the schema covers the columns developed in earlier sections — assessment number, property address, council, state, rating-year dates, valuation method and amount, line type, line description, line amount, total payable, and the instalment columns. The integration is what justifies the column discipline: each downstream use draws on a different subset of those columns, and the council rates notice spreadsheet investor portfolios produce works only when one extraction pass produces the data all three uses need.

ATO deduction substantiation at tax time. Council rates on rental property are deductible against rental income in the year the liability is incurred — the rating-year basis. For ATO substantiation, the relevant data points per property are the council assessment number, the property address, the rating-year start and end dates, and the total payable, with the source notice as the primary record. Per-line extraction is more useful than total-only, because it lets the investor or accountant separately classify the general rate, service charges, and state levies — though all are typically deductible together as council rates expense against the rental property. The line-type discipline matters when a property changes use partway through the year, when only part of a levy is recoverable, or when a service charge sits on the line between rates and a separate utility outgoing. As a council rates investment property deduction tracker, the consolidated spreadsheet substantiates the deduction in the form the ATO and an accountant working a rental schedule both expect — the same per-property, per-period view that supports rental property expense extraction for landlord tax schedules in the US Schedule E equivalent and tax depreciation schedule extraction to Excel for Australian Div 43 and Div 40 workpapers. Council rates are not subject to GST, and rates passed through to tenants under a commercial lease retain that GST treatment; readers needing the full detail should consult the ATO's Rental Properties Guide and TR 97/23 directly rather than treating this article as a GST primer. Where the rateable property is held inside a self-managed super fund, the rates rows feed an additional downstream view — an audit-ready evidence pack covering SMSF rental property rates, levies, and trades invoices — alongside the standard rental schedule.

Settlement adjustment when a property changes hands. When a property sells mid-year, council rates are apportioned between vendor and purchaser based on days held in the rating year. The PEXA settlement statement adjustment lines carry the adjustment line, and the conveyancer typically calculates the apportionment from the rates notice. The columns that support this are RatingYearStart, RatingYearEnd, and TotalPayable, with a derived per-day rate calculation falling out of those three. Settlement-specific columns can be added — SettlementAdjustmentDate and SettlementAdjustmentAmount — when an adjustment is recorded against a property in the portfolio. A settlement adjustment council rates apportionment Australia-wide is mechanical once the rating-year dates and total payable are extracted; the only complication is when the rating year spans a regulatory change (the FSPL-to-ESVF transition is the recent example), which is why the line-type and line-description columns matter for settlements crossing 1 July 2025. The same per-day apportionment pattern shows up in US ALTA settlement statement extraction for property settlements in the US — different document, identical apportionment logic against the consolidated rates dataset.

Commercial tenant recharge under net lease. Commercial leases — particularly net leases and most retail leases under the state-by-state Retail Leases Acts — recharge council rates to tenants. The extraction-then-allocation flow is straightforward: extract the per-property total payable, apportion across tenants by Net Lettable Area or as the lease specifies, and invoice each tenant for their share. The Retail Leases Acts in each state impose audit and disclosure obligations on outgoings statements, and the per-line extraction approach supports the audit trail because each charge component is traceable back to a specific source-notice line. Tenant recharge council rates commercial lease workflows hold up under audit when the spreadsheet carries LineType, LineDescription, and LineAmount per row, with the property identifier as the join key against the tenant register. Where a tenant disputes an outgoing — questioning whether a state levy is recoverable as an outgoing under the lease, or whether a special-rate-area charge falls inside the lease's recoverable scope — the line-type column is what produces the answer in seconds rather than hours.

Body corporate and owners corporation common-property rates earn a brief mention here. Where a body corporate or OC owns rateable land separate from the unit-owners' lots — a common-property-titled parcel, a driveway, an unsubdivided land area — the BC pays those rates, and they sit in a separate row of the portfolio spreadsheet, allocated against the BC entity rather than against an individual lot. The treatment is the same as any other rateable property: per-line extraction, line-type discipline, and the integration back to whichever downstream use applies. Strata levy notices and OC fee notices are separate documents from the rates notice and warrant their own extraction in a portfolio context.

Three routes for moving rates notices into the spreadsheet

Route 1: Manual data entry. For one or two properties in the same state, manual entry into the schema developed earlier is the lowest-friction route. The investor receives a few notices a year, the spreadsheet structure is fixed once and reused, and the time cost per notice is acceptable — usually fifteen to twenty minutes per notice once the schema is in place. Manual entry produces the most defensible audit trail for accountants doing low-volume substantiation, because every figure has been read off the source notice by hand. Where this breaks down is at the multi-LGA boundary, and especially the multi-state boundary: the cognitive cost of remembering each notice's structural quirks (which line is the levy, where the differential category sits, whether utilities are bundled, what label the council uses for what is structurally a service charge) accumulates fast, and accuracy degrades on the third or fourth council in a session.

Route 2: Per-LGA portal CSV export. Most major-capital-city councils, and many smaller councils, offer a ratepayer portal — a logged-in view of the property's current and historical rates notices, with PDF download and in some cases a CSV export of rates and instalment data. Where the portfolio is concentrated in a small number of LGAs and the relevant councils' portals are mature, Route 2 is materially faster than Route 1 for the same accuracy. The limitations are real, though: not every council offers CSV export, the export format differs by council and needs to be normalised into the common schema, historical notices are sometimes only available as PDF, and the export rarely captures the line-by-line structure cleanly — totals and instalment dates come through, line-type classification often doesn't. A portfolio of six properties spread across six councils means six portal logins, six export formats, and six normalisation jobs.

Route 3: Batch multi-LGA notice processing. For portfolios spanning many LGAs, and especially multiple states, batch processing of the source notice PDFs produces the consolidated dataset directly. The input is the notice stack — every rates notice received in the rating year, in whatever PDF format each council issues. The output is the schema developed in the earlier sections, with one row per extracted line item, the council identifier preserved per row, and the line-type discipline applied at extraction. The route handles format heterogeneity at the prompt level rather than the spreadsheet level: the same prompt processes Sydney, Melbourne, Brisbane, Perth, and Adelaide notices and produces the same column shape across the portfolio, which is what makes the multi-LGA rates notice consolidation portfolio actually consolidable rather than five concatenated mini-spreadsheets each in its own format. The same portfolio-management problem appears across the Tasman when teams need NZ council rates invoice extraction for property portfolios rather than an Australian LGA-only dataset. This is where automated council rates notice extraction across your portfolio earns its place — the prompt is written once for the schema the article has built up, the notices are uploaded as a batch, and the spreadsheet returns ready for the three downstream uses covered in the previous section.

Our platform handles this third route as a natural fit. Users upload a stack of rates notice PDFs — up to 6,000 files in a single batch, with single PDFs up to 5,000 pages where a council issues consolidated multi-property notices — and write one natural-language prompt describing the schema: assessment number, property address, council, state, rating-year dates, valuation method and amount, line type and description and amount, total payable, instalment number and due date and amount. The same prompt produces consistent, structured output across every notice in the batch regardless of which council issued it; that cross-council consistency is the differentiator from running notices through a general-purpose AI tool, where the column shape drifts between conversations. Each output row carries a reference to the source file and page number, which is the audit-trail artefact ATO substantiation, settlement adjustment, and retail-leases outgoings audits all expect. Output is delivered as Excel, CSV, or JSON, ready to load into the portfolio's existing spreadsheet workflow or to feed an accounting system.

Route choice follows portfolio shape directly. One or two properties in one state stay on Route 1 indefinitely. A handful of properties in two or three LGAs benefit from Route 2 where the relevant portals support CSV export. Portfolios that cross several LGAs and especially several states are where Route 3 changes the time-and-accuracy trade-off most — the extraction work that scaled poorly in Route 1 becomes a single batch job, and the per-council quirks the portfolio holder used to track in their head become the prompt's responsibility instead.