Ireland Commercial Rates Bill Extraction to Excel

The starting point for Ireland commercial rates bill extraction is straightforward: the bill is built from Rateable Valuation (RV) x Annual Rate on Valuation (ARV), then adjusted for any reliefs or credits that affect the net amount due. Tailte Eireann sets the valuation basis. The local authority sets the ARV through its budget process and issues the bill. For a finance team, that means the real job is not learning one formula. It is turning a stack of council bills into one schedule that preserves the valuation basis, the authority-specific rate, and the adjustments that explain the final payable figure.

That is why a portfolio view matters. A business with sites in Dublin City, Fingal, Waterford, Galway, and Leitrim can receive bills with different layouts, different account references, different relief lines, and different year-to-year changes, even though finance still needs one clean file for reconciliation and forecasting. The useful output is a standard spreadsheet with columns for authority, property reference, RV, ARV, gross rates, relief or credit, net liability, billing period, and the reason the figure moved from last year. Once those fields are consistent, the portfolio can be filtered, tied back to source documents, and rolled into budget or month-end packs without rekeying every council PDF by hand.

What belongs in the bill calculation, and which institution owns each part

The cleanest way to read an Irish commercial rates bill is to split it into three layers. Tailte Eireann owns the valuation layer: the rateable basis for the property and the revaluation process that can change that basis over time. The local authority owns the billing layer: the ARV it adopts through the budget, the bill it issues, and the collection process attached to that bill. The finance team owns the control layer: making sure both parts are captured in a schedule that explains the amount due and any live uncertainty around it.

According to Department of Housing guidance on local government finance and commercial rates, local authorities levy commercial rates using valuation lists prepared by Tailte Eireann, and each authority sets its Annual Rate on Valuation through the annual budget process. That is the institutional split the schedule needs to preserve. If a bill increased, finance should be able to see whether the driver was a new ARV, a changed valuation basis, a relief movement, or an occupancy change, rather than treating the whole figure as one opaque number.

In practice, the calculation should be stored as a short gross-to-net bridge. Start with RV and ARV. Record the gross liability they produce. Then record any separate relief, credit, or vacancy adjustment that changes the net payable amount on the bill. This matters because a valuation dispute is not the same thing as a billing adjustment. A property can have a current bill from the council while a separate valuation issue or appeal status still sits with Tailte Eireann and, if escalated, the Valuation Tribunal. If the schedule collapses all of that into one number, the portfolio loses the ability to explain what changed and what is still unresolved.

2026 ARV reference table for all 31 Irish local authorities

Treat ARVs as a maintained control table, not background prose. The figures below are the official published 2026 ARVs for the 31 Irish local authorities. They are useful because finance can check whether each extracted bill is using the current authority value, but they are not a set-and-forget reference. Local authorities revisit ARVs through their annual budget process, so this table should be refreshed after each Q4 budget cycle for the following rating year.

Source note: figures checked on 2026-04-22 against the official 2026 ARV publication. Tailte Eireann's Reval 2027 guidance for Cork City and Cork County confirms that those are the two remaining revaluation areas, with new valuations published in 2027 and effective for rates from 2028.

Local authority	2026 ARV
Carlow County Council	0.2700
Cavan County Council	0.2432
Clare County Council	0.2581
Cork City Council	81.47
Cork County Council	81.27
Donegal County Council	0.2320
Dublin City Council	0.2890
Dun Laoghaire-Rathdown County Council	0.2140
Fingal County Council	0.1868
Galway City Council	0.2369
Galway County Council	0.2400
Kerry County Council	0.2450
Kildare County Council	0.2313
Kilkenny County Council	0.2230
Laois County Council	0.2328
Leitrim County Council	0.2686
Limerick City and County Council	0.2965
Longford County Council	0.2753
Louth County Council	0.2235
Mayo County Council	0.2470
Meath County Council	0.2132
Monaghan County Council	0.2594
Offaly County Council	0.2308
Roscommon County Council	0.2480
Sligo County Council	0.2536
South Dublin County Council	0.2800
Tipperary County Council	0.2232
Waterford City and County Council	0.3082
Westmeath County Council	0.2134
Wexford County Council	0.2530
Wicklow County Council	0.2240

The workflow rule is simple: preserve the published ARV exactly as the authority dataset presents it. Do not normalize the value on ingestion just because another authority uses a different-looking notation. The Cork figures look different because Cork City and Cork County are still in Reval 2027, while the other 29 authorities are already on the revalued basis. For extraction and reconciliation, the safe control is to store the authority, rating year, and ARV exactly as published, then let the schedule explain the bill in that authority's own context.

Revaluation context	Authorities	What to store in the schedule
Already through revaluation	The 29 authorities outside Cork City and Cork County	Keep the 2026 ARV, rating year, and bill-level RV exactly as issued, then refresh the ARV after the next budget cycle
Reval 2027 in progress	Cork City Council and Cork County Council	Keep the 2026 ARV exactly as published, flag the property as Reval 2027, and store an expected effective year of 2028 for forecast review

---

Build one Irish commercial rates portfolio schedule from mixed council PDFs

The core extraction task is to reduce different council layouts to one stable column set. A practical Irish commercial rates portfolio schedule usually needs these columns: local authority, site or property name, council account reference, Tailte property number if shown, billing period, RV, ARV, gross rates, relief or credit, net liability, occupancy status, appeal or revaluation status, payment status, source file, source page, and a short variance note. Those fields are enough to support both monthly reconciliation and year-end forecasting without overloading the sheet with legal commentary.

That structure works because it keeps two truths at once. It preserves the authority-specific identifiers that make the bill traceable back to the source PDF, and it gives finance a normalized set of columns that can be sorted, filtered, and compared across the portfolio. In practice, one row per property bill is usually the cleanest model. If a single bill covers multiple properties or periods, split that into separate rows only when the document itself separates the liabilities clearly enough for finance to review them later.

It is also worth deciding up front which fields are reference data and which are reconciliation data. Authority name, property reference, Tailte property number, rating year, and bill issue date are reference fields that help the row stay identifiable over time. Gross rates, relief amount, net liability, payment status, and variance note are reconciliation fields that change with each cycle. Keeping those categories separate makes the workbook easier to audit because finance can refresh current-year amounts without losing the identifiers that tie the row back to a specific property and council bill.

A prompt-based extraction workflow is well suited to this kind of recurring document standardisation. Invoice Data Extraction can take a batch of council bills, use a natural-language prompt to pull fields such as authority, property reference, RV, ARV, gross rates, reliefs, and net liability, and return the result as structured XLSX, CSV, or JSON. Because the same workflow can extract finance bills and invoices into a structured spreadsheet, it fits the operational problem here: turning mixed local-authority PDFs into one reusable dataset without redesigning the output every time a council changes its layout. The useful control is not only the exported sheet itself, but also the row-level traceability back to the source file and page when someone in finance needs to verify a figure.

Reconcile year-over-year movements without guessing what changed

Once the bills are in one sheet, the next job is explaining movement. A portfolio schedule should separate RV change, ARV change, relief change, and occupancy change so finance can tell the difference between a structural shift and a temporary adjustment. Without that bridge, a higher net bill just looks like "rates went up," which is not good enough for budget commentary or audit support.

Authority	Prior RV	Current RV	Prior ARV	Current ARV	Gross change	Relief change affecting net	Primary variance driver
Dublin City	18,500	18,500	0.2820	0.2890	EUR 129.50	EUR 0.00	ARV increase only
Fingal	24,000	24,000	0.1796	0.1868	EUR 172.80	EUR 400.00	ARV increase plus expired temporary credit
Waterford	10,900	11,200	0.2978	0.3082	EUR 205.82	EUR 0.00	Mixed RV and ARV movement

Take the same three-site example in row form. The Dublin City site produces EUR 5,346.50 of gross rates in 2026 against EUR 5,217.00 in 2025, so the movement is purely budget-driven. The Fingal site's gross movement is only EUR 172.80, but if a EUR 400 temporary credit fell away at the same time, the net change is materially larger than the formula alone suggests. The Waterford site shows why current and prior RV must sit next to ARV in the sheet: the bill moved because both the valuation basis and the authority rate changed.

This is why gross and net should be stored separately. If the Fingal site also lost a temporary credit, or a vacant unit came back into occupation, the net payable could move far more than the gross calculation suggests. A useful rates schedule therefore keeps prior-year RV, current-year RV, prior-year ARV, current-year ARV, gross liability, relief amount, net liability, and a concise variance note in the same row set. If property files also carry indirect-tax support, keep that evidence trail separate from the rates schedule; our guide to Ireland VAT invoice requirements covers what belongs in the VAT record rather than the commercial rates control file.

Track reliefs, vacancies, appeals, and revaluations as separate status fields

The schedule should not stop at the formula. Reliefs and status fields often explain more than the headline RV x ARV calculation does, especially when finance is forecasting the next cycle rather than just paying the current bill. Vacancy relief, SME support measures, or other local credits can reduce the current net amount without changing the underlying gross liability. If those adjustments are stored only as narrative comments, they disappear from year-over-year analysis.

A practical status block usually includes:

• Relief type and relief status: what adjustment is being claimed, whether it is active, and whether it is provisional or confirmed.
• Effective dates: the dates from which a relief, vacancy treatment, or revised liability applies.
• Valuation challenge stage: internal review, Tailte Eireann process, tribunal stage, or later court stage if relevant.
• Revaluation flag: whether the property sits in a completed revaluation area or an active upcoming round such as Reval 2027.
• Expected effective year and last review date: the two fields that make forecasting and audit follow-up easier.

The cleanest approach is to give each moving part its own field. Keep a relief type column, relief status, effective-from date, effective-to date where relevant, relief amount, and a document reference showing what supports the treatment. Do the same for disputes and revaluations. A valuation issue should sit in a separate status column from the billed amount, with notes such as review with Tailte Eireann, appeal to the Valuation Tribunal, or later court stage if relevant. That way the current bill can still be reconciled while the portfolio also shows that the liability may change after the dispute is resolved.

For portfolio control, avoid overwriting old status data when a position changes. If a vacancy relief ends, or a property moves from review with Tailte Eireann to tribunal stage, store the new status with its effective date and retain the prior state in the audit trail or prior-year row. That matters because controllers are often asked not only what the current bill says, but also why the assumption changed between the last forecast and the current one. A schedule that preserves dated status changes answers that question without reopening every source document.

Revaluation status deserves the same treatment. Even when the current bill is correct, a property sitting inside an active or upcoming revaluation cycle carries forecasting risk that should be visible in the schedule. Storing the revaluation round, expected effective year, and last review date helps finance explain why a future rates line may move even before the next bill arrives. The goal is not to turn the spreadsheet into a law textbook. It is to make sure every material driver of net liability has its own auditable field instead of hiding inside one final number.

Avoid UK assumptions and set an annual review calendar for the portfolio

Irish commercial rates should not be modeled with UK business-rates logic. Ireland ties liability to Tailte Eireann's valuation basis and a local-authority ARV, so UK multiplier assumptions do not transfer cleanly. If a cross-jurisdiction team genuinely needs the UK regime, use the separate UK business rates bill extraction workflow rather than importing its mechanics into an Irish schedule.

For the Irish portfolio itself, a short annual control cycle is usually enough:

1. Refresh the ARV reference table after local authority budget rounds and tag the schedule with the rating year.
2. Extract incoming bills into the standard schema with source-file and page traceability.
3. Review valuation, relief, vacancy, and revaluation statuses separately from the billed amount.
4. Update the forecast using the latest gross-to-net bridge rather than only last year's payable figure.

Teams that are cleaning up recurring document workflows often pair this with adjacent finance controls, especially where AP and compliance data is also being standardized. Property teams dealing with multi-unit schemes may also need a defensible method for allocating OMC block insurance by unit interest contribution alongside rates tracking, while cross-border ownership structures may require a clear process for non-resident landlord withholding notifications. If that is on the same roadmap, the Ireland e-invoicing mandate 2028 guide is a useful parallel reference for another Irish document stream that benefits from the same structured-data discipline.