The Bookkeeper's & Payroll Bureau Guide to Irish T&S
For a bookkeeper or payroll bureau, travel and subsistence isn't a once-a-year topic — it's a recurring part of every client's pay run, and since ERR it has a hard deadline attached. This guide is written from your seat: how T&S and ERR actually land on your desk, how to get clean data out of clients, how to slot the ERR export into the payroll/ROS workflow, and the common errors worth catching before you file.
T&S and ERR From the Bookkeeper's Seat
You're the one who actually has to make T&S work each cycle: take whatever the client sends, identify the reimbursed travel and subsistence, make sure it's rated correctly, categorise it for ERR, and get it filed to ROS on or before payment. The rules live elsewhere; the workflow lives with you.
That changes what "good" looks like. It isn't just knowing the rates — it's having the data arrive clean, the rates already applied, and the export ready to file inside the pay-run window, every client, every cycle.
Getting Clean Data From Clients
The biggest time-sink isn't filing — it's chasing and fixing data. The fix is to define what you need and push the capture back to the point of travel.
The fields every trip needs
- Date, start and end point, and distance.
- A clear business purpose for the journey.
- Departure/return times where subsistence applies.
- Which vehicle (and whether it's the employee's own or a company car).
How to make it arrive clean
- Have staff log trips at source — ideally from a phone, at the time.
- Apply the rates and rules automatically so the figures are right on arrival.
- Set a cut-off before the pay run, so you review rather than reconstruct.
Fitting ERR Into the Payroll / ROS Workflow
Because ERR is due on or before payment, it has to sit inside the pay run, not after it. A clean sequence keeps it from ever trailing the payment date.
Collect
Trips and expenses captured by the cut-off, with the required fields complete.
Validate
Check the data — purpose present, bands and subsistence correct, no commuting or company-car mileage slipping through.
Categorise
Confirm each amount is reimbursed travel & subsistence (vs small benefit or remote-working allowance).
Export
Generate the categorised, ROS-ready ERR file for the client.
File to ROS — on or before payment
Submit through ROS before the payment is made.
Pay & record
Process the payment and retain the records for the audit trail.
The one rule that drives the order: the ROS submission must be on or before the payment date. If your process files ERR after pay day, fix the sequence — see ERR deadlines.
Common Errors to Catch Before Filing
You're the last review before the data reaches Revenue. These are the recurring mistakes worth a deliberate check on each run.
- A flat mileage rate applied instead of the four progressive bands
- A band crossover missed — still paying Band 2 after the year-to-date total passed into Band 3
- Commuting (home to normal place of work) claimed as business travel
- Subsistence claimed when the distance or duration test isn't met
- The "lesser of" rule not applied on home-start journeys
- Country money mixed with civil service mileage for the same site travel
- Foreign subsistence treated as euro when the rate is in sterling/dollars
- Round-sum or flat "travel allowances" with no underlying journeys
- Missing or vague business purpose on a claim
- Mileage claimed by an employee who drives a company car
- ERR export prepared after the payment date instead of on or before it
Most of these vanish when the data is captured correctly at source: the normal-place-of-work rule, progressive bands, and subsistence tests applied as the client logs, so there's far less to catch by hand.
How Expense.ie Helps Bookkeepers & Bureaus
Clean data, captured at source
Clients log trips with the required fields and the correct rates already applied — so it arrives ready to review, not rebuild.
Rates & rules applied automatically
Progressive bands, the lesser-of rule, and subsistence eligibility handled as expenses are logged — removing most of the errors-to-catch list.
ROS-ready ERR export
A categorised, date-stamped export per client that slots into the pay run, ahead of payment.
One dashboard for every client
Free practitioner access to manage all clients from one place — the multi-client workflow in practice.
Bookkeeper & Payroll FAQ
Related Resources
Clean Data In, ERR Out — On Time
Free practitioner access gives your bureau one dashboard where clients log clean data, rates and rules apply automatically, and a ROS-ready ERR export drops straight into the pay run. Less chasing, fewer errors, no late filings.
Free for practitioners. No per-seat charge to manage your clients.