Public Sector GuideUpdated June 2026Verified against Revenue guidance

Travel & Subsistence for Local & Regional Government in Ireland

In a county council or local authority, the mileage rate is the easy part — it's the same civil service rate everyone uses. The hard part is defensibility: every officer's claim has to survive internal audit, the Local Government Audit Service, Enhanced Reporting Requirements, and, ultimately, public scrutiny. A travel-and-subsistence process for a public body isn't judged on speed; it's judged on whether any single payment can be traced, justified, and reproduced years later.

This guide is framed entirely around audit-readiness. It covers how rates apply to inter-county and cross-border officer travel, multi-tier approval workflows for public-sector sign-off, the ERR audit trail and ROS export, and record retention, public-audit, and GDPR/data-residency considerations. The Revenue figures referenced are date-stamped: motor rates effective 1 September 2022, domestic subsistence effective 29 January 2025, both verified current as of June 2026.

The Standard Is Defensibility, Not Speed

Private-sector expense systems optimise for convenience. Public bodies optimise for the day someone asks, "show me the evidence." Whether the question comes from internal audit, the Local Government Audit Service, an FOI request, a councillor's query, or a journalist, the answer has to be the same: a complete, time-stamped record that holds up without explanation. Four things have to be true of every claim.

Correct on the rules

The right civil service band and subsistence rate applied to each trip, with the business purpose and the "lesser of" home-or-base distance recorded.

Properly authorised

Approved through the correct chain of sign-off, with segregation of duties so no officer can authorise their own payment.

Reported to Revenue

Captured in the ERR submission to ROS on or before payment, and reconcilable back to the individual claim.

Retained and retrievable

Held for the full retention period in a form that can be produced on request, with personal data handled to GDPR standards.

Inter-County and Cross-Border Officer Travel

Local and regional government work spreads officers across boundaries — regional shared-service centres, joint projects between authorities, site inspections across a county, training and sectoral meetings in Dublin, and cross-border bodies and EU-funded programmes that reach into Northern Ireland and beyond. The rate mechanics are the standard civil service ones; the discipline is recording each trip so the rate is provably correct.

Mileage is cumulative and per officer

Each officer moves through the four progressive distance bands based on their own year-to-date business kilometres, resetting on 1 January. The bands and the "lesser of" rule are identical to every other sector — see the civil service rates guide and how to calculate mileage.

Inter-county day trips and overnights

A long day at a meeting in another county can qualify for day subsistence (€19.25 for 5–10 hours, €46.17 for 10+ hours); an overnight away triggers the domestic overnight rate, subject to the 100 km rule. Full detail is in the overnight subsistence guide.

Cross-border and international travel

Travel into Northern Ireland or the EU for cross-border bodies and funded programmes uses country-specific overnight subsistence rates rather than the domestic figure, while the mileage bands continue to work the same way. See cross-border travel expenses.

The figures move — the page is dated for a reason. Civil service rates change with Budgets, Finance Acts, and Department of Public Expenditure circulars. An audit-ready process always records which rate was in force on the date of travel, so a claim is judged against the rule that actually applied at the time, not today's rate.

Multi-Tier Approval for Public-Sector Sign-Off

In a council, a claim rarely has a single approver. Sign-off runs through a chain shaped by delegated sanction limits, section budgets, and segregation-of-duties rules. The system has to model that chain — and prove it was followed for every payment.

1

Claimant submission

The officer logs the trip, purpose, and distance — ideally at the time, not reconstructed at month-end.

2

Line-manager / supervisor approval

Confirms the travel was necessary and the business purpose is genuine — the first control, and the one auditors test first.

3

Section head / budget holder sanction

Authorises the spend against the correct cost centre, within delegated sanction limits.

4

Finance / payroll processing

Validates rates, processes payment, and ensures the ERR submission is made on or before the payment date.

Segregation of duties, enforced

No officer can approve their own claim, and the approver of a section head's travel sits above them in the chain. This separation is a standard audit test — it should be structural, not a matter of trust.

Every step time-stamped

Who submitted, who approved at each tier, and exactly when — captured automatically. An approval chain you can only describe is not an approval chain you can evidence.

ERR Audit Trail and ROS Export for Public Bodies

Enhanced Reporting Requirements apply to public bodies in full. Since 1 January 2024, reimbursed travel and subsistence — alongside the remote working daily allowance and small benefits — must be reported to Revenue through ROS on or before the date of payment. For a public body paying officer claims continuously, ERR is an ongoing operational reporting obligation, and the audit trail it produces is part of the body's defensibility.

What a defensible ERR trail looks like

  • Each reimbursed payment categorised correctly (travel and subsistence vs other reportable benefits) before the pay run.
  • A date-stamped ROS submission that reconciles line-by-line back to the individual claims behind it.
  • Submission timing demonstrably on or before payment, not retrofitted afterwards.
  • The full chain — claim, approval, rate, payment, ERR submission — retrievable for any single officer payment.

For the mechanics and deadlines, see our ERR compliance guide and ERR reporting deadlines.

The risk is loss of tax-free treatment. If reimbursed T&S can't be tied to a timely, correct ERR submission, Revenue can treat the payment as taxable — exposing the body to PAYE, USC, and employer PRSI on amounts that should have been tax-free. For a public body, that's both a financial cost and a governance finding.

Record Retention, Public Audit, and GDPR

Six years — and often longer

Revenue requires employers to keep records for six years after the end of the tax year to which they relate, available for inspection on request. Public bodies usually layer additional retention obligations on top — records-management policies, the Local Government Audit Service, and National Archives requirements — so the working retention period is frequently longer than the Revenue minimum.

Retrievable, not just stored

Retention only counts if a specific claim from several years ago can actually be produced — the trip, the approval chain, the rate applied, the payment, and the ERR submission — quickly and completely. Archived boxes and dead spreadsheets fail this test; a structured, queryable record passes it.

GDPR and data residency

Officer names, home addresses, journey patterns, and bank details are personal data. As data controller, the body should confirm where its processor stores and processes that data, keep it within the EU/EEA (or transfer it lawfully), and hold a GDPR Article 28 data processing agreement. A travel-expense platform belongs in your Data Protection Impact Assessment.

Procurement due diligence

Treat the system as you would any processor: ask for the data processing agreement, data-residency details, security posture, and access controls up front. These questions belong in the evaluation, not after go-live — and a vendor that can answer them cleanly is itself a signal of audit-readiness.

This guide outlines the considerations rather than legal advice. Confirm specific retention schedules, data-residency terms, and processing arrangements with your own records-management, data-protection, and legal functions, and document them in your DPIA and data processing agreement.

How Expense.ie Supports Public Bodies

A complete, time-stamped audit trail

Every claim records the trip, business purpose, rate applied, approval at each tier, payment, and ERR submission — so any single officer payment can be traced end to end on request.

Multi-tier approval with segregation of duties

Model your sign-off chain — claimant, line manager, budget holder, finance — with no self-approval, every step captured automatically.

Correct rates, ERR-ready exports

Progressive bands and subsistence applied automatically per officer, with categorised, date-stamped ERR files ready to upload to ROS for every pay cycle.

Built for retention and GDPR review

Structured, retrievable records for the full retention period, with data processing and residency terms available for your DPIA and procurement review. Outsourced finance functions can use the accountant dashboard to manage it on a body's behalf.

Public Sector FAQ

Related Resources

Audit-Ready Travel & Subsistence for Public Bodies

Expense.ie gives councils and local authorities a complete, time-stamped audit trail — multi-tier approval, correct civil service rates, ERR/ROS exports, and structured retention — built to survive public scrutiny. Start a free trial, or talk to us about a deployment.

Used by Irish public-sector and semi-state teams. No long contracts.