You pay your first employee on a Friday, and Revenue expects the payroll submission logged on or before that same day, with no grace period once the wages leave your account. There is no forgiving window afterwards, and no HR person down the hall to catch what you missed. So the pressure sits entirely with you, on every pay date, all year.
Carry an old RPN across a quarter, or mistype a pay date, and you quietly under-deduct while late-payment interest builds on a bill you assumed the month’s cash had already covered. By the time a Revenue letter lands, a small slip has grown into a year-end shortfall for one of your own staff, plus a reconciliation you have no accountant to hand off. That is real money and real hours, spent unpicking something that took thirty seconds to get wrong.
The way out is not more vigilance or a bigger spreadsheet. It is turning the whole job into one fixed slot each month, wired so the RPN, the filing and the payment fall into place in the right order and the software carries most of the load.
Reviewed 30 July 2026
Table of Contents
- Before Your First Pay Run
- Build Your Monthly Payroll Routine
- What Else Lands in the Pay Run: Pensions, Leave and Expenses
- When the Run Goes Wrong
- Start Your Fixed Monthly Slot This Week
- Frequently Asked Questions
Before Your First Pay Run
Three things have to be settled before a single euro moves: whether you can realistically do this yourself, who actually belongs on the payroll, and what comes off each person’s pay versus what the business carries on top. Get these wrong and every later month inherits the error.
Can You Run Irish Payroll Without an Accountant?
A small Irish employer can run payroll in-house without an accountant, but only by treating it as a fixed repeating compliance routine rather than occasional admin: register, retrieve RPNs, calculate deductions, and file on or before each pay date.
For most micro-employers, the honest answer is yes. The trick is to stop treating each run as fresh admin and start treating it as the same short loop, repeated on a fixed date. Under PAYE Modernisation, you must report pay to Revenue on or before the date each employee is paid, so payroll becomes a real-time job rather than a monthly catch-up. Before any of this, you must register as an employer with Revenue, including where you pay yourself as a limited company director.
Once you register, the cycle is mechanical and identical every period. Retrieve the current RPN for each employee, calculate PAYE, USC and PRSI from it, submit the payroll submission through ROS or ROS-integrated software, release net pay, and diarise the Revenue payment. One rule keeps you compliant through all of it: if no valid RPN exists for someone on the system, stop and request or update it before you finalise their pay.
What makes this feasible is not that the work is easy, but that it never changes. The same five moves, in the same order, on a date you picked once. Before you can run them, though, you need to know who is on the list.
Employee or Contractor: Who Belongs on Payroll
Whether a worker belongs on payroll is a factual test of control, personal service, integration and financial risk, not a labelling choice. Misclassifying an employee as a contractor can leave you liable for unpaid PAYE, PRSI, USC, interest and penalties.
The label on an invoice counts for nothing. Irish guidance sets status from how the work really runs, so ask four questions of each worker in turn. First, control: who decides their hours, place and method of work? Second, personal service: must that person do the job themselves, or can they send a stand-in? Third, integration: are they part of your business, on the team, using your systems and gear? Fourth, financial risk: can they actually make a loss or a profit on the work?
Control by you, a duty of personal service, high integration and no genuine risk point to a contract of service and an employee. Real freedom, a right of substitution and business risk point the other way, to a contract for services. Where the signals are mixed, the deciding factor is often mutuality of obligation, whether you must offer work and they must accept it.
The consequences are not cosmetic. An employee is paid through PAYE with tax, USC and PRSI deducted at source and insured under Class A. A genuine contractor self-assesses and pays Class S. If Revenue later reclassifies the relationship, the bill lands on you: back PAYE, PRSI and USC, plus interest and penalties, and the worker can chase statutory entitlements such as paid leave they were denied. Directors are settled already. Their fees are Schedule E and must run through payroll.
What Gets Deducted from Pay and What Employers Add on Top
Three statutory deductions come off an employee’s gross pay: PAYE income tax, USC and employee PRSI. Employer PRSI sits outside that sum as a separate labour cost, never deducted from the employee’s wages.
The cleanest way to check any pay run is to split it in two. Gross pay is the starting figure for the period, before anything is worked out, so treat it as the anchor everything else refers to. Then sort every other line into one of two columns.
| Line | Comes off the employee’s gross pay | Carried by the business on top |
|---|---|---|
| PAYE income tax | Yes | No |
| Universal Social Charge | Yes | No |
| Employee PRSI | Yes | No |
| Employer PRSI | No | Yes, as a labour on-cost |
| Auto-enrolment (MyFutureFund) | Employee share, from 2026 | Employer share, plus a State top-up |
Take the left column away from gross and you are left with net pay, the figure that actually reaches the bank. Irish payslips are expected to show gross pay and itemise each deduction, which is exactly what lets a non-specialist owner check the run line by line. The right column never appears as a payslip deduction; employer PRSI is something the business pays on top of wages as a separate charge, so cost it as a labour on-cost.
Directors are the exception worth flagging. A proprietary company director is often treated under PRSI Class S rather than the ordinary employee’s Class A, and that class difference can change the employer PRSI outcome on the director’s own pay. So check the class before you assume Class A just because someone draws a salary. Then reconcile the run so gross, deductions, net and employer cost all line up before you submit.
Build Your Monthly Payroll Routine
With the setup settled, the whole job collapses into one recurring appointment. This part builds it: the day you process, the checks you run before approving, the submission itself, and the payment that closes the month.
Set One Payroll Day and Repeat It All Year
Fix one pay date for the whole year, anchor a recurring processing slot just before it, and diarise a Revenue payment day just after it. Paying monthly means you file twelve times, not fifty-two.
Treat monthly payroll as a repeating filing deadline, not bookkeeping you squeeze in when you remember. Folding the RPN request into the same slot removes every chance to forget it, and folding the payment into the same calendar removes the scramble at the other end. The month then has a fixed shape you can see in advance.
Directors sit inside this same slot, not beside it. They follow the same real-time reporting sequence as other employees, so pull their RPN with everyone else’s and report their pay on the same submission. Once the calendar holds the dates, retrieving each RPN and paying Revenue stop being things you have to remember and become steps the slot triggers.
Run the Pre-Approval Audit Before You Click Approve
Software handles the tax arithmetic, the RPN retrieval and the filing. It cannot confirm your inputs were right, which is the one job that stays yours.
A ROS-integrated payroll package does the mechanical heavy lifting. It pulls each Revenue Payroll Notification, applies the current tax credits, rate bands and PRSI class to work out PAYE, USC and employer PRSI, and files the payroll submission to ROS in real time. Bullet, an Irish-built accounting and payroll app for small businesses, is one such tool: it imports the RPN, applies the current Irish rules, builds a compliant payslip and files the submission. What no package can do is tell you the hours were right or the leave was coded, and the employer remains responsible for filing on or before each pay date.
So before you click approve, run a short, repeatable audit against what you see on screen:
- Verify the RPN basis for each employee. Pull a fresh RPN and confirm the PPSN, credits, rate band and the correct PRSI class for their current employment.
- Reconcile gross to net. Check the gross pay elements build correctly, then confirm PAYE, USC, and employee and employer PRSI resolve to a net pay that matches what will actually leave the bank.
- Review variances against the previous typical run, per employee and per deduction type, and confirm a valid reason for any big swing.
The decision rule is blunt: if you cannot explain a variance, do not approve until you have checked the timesheet, contract or RPN behind it. Then store the report pack to support your six-year record retention. Two minutes here is what prevents the quarter-long repair job in the last part of this guide.
File the Submission on or Before the Pay Date
The on-or-before rule is strict. You must report payroll to Revenue on or before the day you actually pay, with no grace period after. Treat the pay date as your hard deadline and work backwards through four steps.
- Finalise and check the pay run, looking at the pay date, salary or hours, and whether PAYE, PRSI and USC read sensibly against last month.
- Generate the PSR and confirm it carries gross pay, PAYE, USC, PRSI, net pay and each person’s employment details.
- Sign in to ROS with your digital certificate and submit, or upload the file if your software only exports one.
- Confirm the Payroll Submission Response shows received before you release net wages.
Because the pay date sets the submission period, an old or corrected run becomes an amended PSR, never a backdated one. Some Irish payroll tools submit to ROS in one step as you finalise, but confirm that behaviour in your own system rather than assuming it. Then issue each person a payslip showing gross pay, deductions and net pay once the submission is final.
Pay Revenue by the 14th, or the 23rd Through ROS
Filing is only half the month. The money follows its own clock, and the two deadlines are the single thing small employers most often merge into one.
| The filing clock | The payment clock | |
|---|---|---|
| What is due | The payroll submission (PSR) | PAYE, PRSI and USC |
| When | On or before the pay date | The 14th of the following month, or the 23rd if you file and pay through ROS |
| Grace period | None | None |
| Lateness triggers | A late-filing exposure against a deadline that has already passed | Late-payment interest, running from the due date until the balance clears |
| Put right by | An amended PSR against the original pay date | Clearing the balance, though interest already accrued still stands |
Early the following month, open the statement of account Revenue builds from your PSRs and check it against your software totals. Correct any underlying PSR before that statement hardens into your statutory return, because the statement inherits whatever the submissions said. If the two do not match, sort out the difference before you schedule any payment.
Then pay by the due date for your filing route. A variable direct debit lets the transfer run once your bank and Revenue details are set up, so the payment clock closes itself while you are doing something else. That is the whole point of the slot: the deadlines are met by the calendar, not by your memory.
What Else Lands in the Pay Run: Pensions, Leave and Expenses
The slot handles the tax. Three other things arrive inside the same run and have to be coded before you approve it: auto-enrolment contributions, statutory leave, and the tax-free payments Revenue wants reported in real time.
Auto-Enrolment Contributions from 2026
From 2026 the payroll assesses eligible employees, deducts their auto-enrolment pension contribution each period, adds the employer contribution as a separate cost, and submits the contribution details alongside the normal pay run.
Treat auto-enrolment as one more check inside the run you already do, not a separate spreadsheet. Before you work anything out, pull the latest Automatic Enrolment Payroll Notifications (AEPNs) that NAERSA sends to payroll, the same way you already pull RPNs from Revenue. The AEPN tells you who is enrolled and which contribution rate applies, so eligibility is confirmed per employee at the start of the run instead of judged by hand.
Work out gross pay first, apply PAYE, USC and PRSI through each RPN, then apply the employee and employer MyFutureFund percentages to the qualifying slice of gross pay. Contributions are subject to an earnings cap on the relevant part of gross pay: above the cap, contribute on the capped portion only; below it, use actual gross pay. The employee share is a deduction, and the employer share is a separate cost the business carries, with a State top-up alongside it.
The submission mirrors your Revenue reporting. Alongside the PSR, payroll builds a NAERSA contribution file for enrolled staff each period. Verify both acknowledgements before you close the run, and reconcile your payroll contribution totals against NAERSA’s confirmed figures so any mismatch shows up straight away rather than at year end. Opt-out and re-enrolment status arrives through later AEPNs, so update each employee as it changes rather than treating enrolment as a one-off switch.
Sick Leave, Annual Leave and Public Holidays
Record each absence and leave type before running payroll, so the software itemises statutory sick pay, annual leave and public holiday pay separately, keeps annual leave accruing during sickness, and coordinates any state Illness Benefit with what you pay.
Just as you check auto-enrolment status each cycle, your absence data has to be clean before the run, not patched afterwards. Annual leave and public holiday entitlements are statutory rights under the Organisation of Working Time Act framework for annual leave and public holidays, so track them apart from ordinary working time and let each land on its own pay line. Merge them and reconciliation turns into guesswork.
Work each absence through the same short sequence before you open the pay run:
- Classify the absence type first as statutory sick leave, annual leave or public holiday entitlement, never a generic “time off” code, then record the dates or hours affected.
- For sickness, capture the certification status and keep annual leave building alongside it, since leave still accrues during certain absences and the balance needs updating.
- Where an absence spans a public holiday, record that entitlement on its own so payroll pays it as a distinct item.
- If Illness Benefit from the Department of Social Protection is in play, note the claim and reconcile it against employer sick pay before you close, checking PRSI insurable weeks so you neither overpay nor understate cover.
Then itemise each category on the payslip and check that no absence has been left half-coded. If a leave record is incomplete, stop the run rather than push a mismatch into ROS.
Enhanced Reporting Requirements: Travel, Vouchers and the Remote-Working Allowance
Under Enhanced Reporting Requirements you report three categories of tax-free payment made directly to employees, in real time. Costs you settle directly with a provider stay outside scope.
The trigger for Enhanced Reporting Requirements is narrow and worth memorising, because it lets you make the call at approval rather than unpicking it later. Revenue lists three categories of tax-free payments you must report on or before the date the benefit is provided, through your payroll software or the ROS ERR facility: travel and subsistence, the remote working daily allowance, and Small Benefit Exemption benefits. If a payment sits in none of those three buckets, it is not an ERR item.
The second test is who receives the value. The reporting hook attaches to money or vouchers that reach the employee directly, so a mileage or subsistence reimbursement paid into someone’s account is in scope, and so is a gift card handed to a named person. Tax-free remote working allowances paid to the employee are reportable too. But employer-provided equipment or broadband, which fall outside the listed ERR categories, generally are not.
Build one habit into every approval. Ask whether the payment is tax-free, which of the three categories it lands in, and whether it goes to the person or to a supplier. A hotel or airline invoice you settle directly usually carries no tax-free amount to the employee, so treat it as out of scope. Capture the category, amount and date at entry, and the reportable items surface cleanly when you assemble each return.
When the Run Goes Wrong
Even a solid routine lets the odd error through. Four go wrong often enough to plan for, and each has a specific repair that costs far less than the drift it prevents.
No RPN Yet, So New Staff Land on Emergency Tax
With no RPN available for a new employee, you must apply emergency tax, deducting income tax and USC at higher rates with restricted credits, until the employment is registered and Revenue issues a valid RPN.
Treat a missing RPN as a registration and sync gap, not a mistake on your side. A new hire can hold a valid PPS number and still have no Revenue Payroll Notification waiting for you. The notification only issues once the specific job is registered and Revenue matches it to that person’s record. Until that link exists, ROS has nothing to hand your payroll, so it falls back to the emergency basis.
To close the gap, check the employee’s PPS number and start date, then register the job. The employee can do this through the myAccount Jobs and Pensions service, or you register it from your own Revenue route so the RPN generates against your employer number.
The pay run also differs from normal PAYE in one clear way. With a valid RPN, deductions follow the tax credits and standard rate cut-off point it carries. Without one, emergency tax applies a stricter default: where the employee has given a PPS number, a limited first-month cut-off applies and the treatment tightens after week four; where no PPS number is given, tax runs at the higher rate with no credits until you supply it.
So register early, and once the RPN issues, check the emergency deductions against the RPN figures and correct the record. Over-deducted tax comes back through the updated notification. The more expensive version of this problem is the opposite one, where an RPN exists but you never picked up the new one.
Fixing a Quarter Run on an Old RPN
When a quarter has been run on a stale RPN, you correct the under-deducted PAYE and USC by amending each affected submission with the right RPN, then staging the recovery across remaining pay runs rather than taking it in one hit.
The fix is narrower than it feels. You work out PAYE and USC on each pay date from the employee’s current Revenue Payroll Notification, so a stale RPN carried across a quarter simply means each submission took too little against the credits and cut-off points that should have applied. This is a reconciliation, not a penalty. The reason it feels alarming is that the shortfall is invisible until you add it up.
Start by pulling the employee’s RPN history in ROS to confirm when the new RPN issued, then list every affected pay period. Load the correct RPN, recalculate each period to get the revised PAYE and USC, and note the shortfall for each one. Now file an amended PSR for each historic pay date, keeping the same employment identifier and original pay date so Revenue ties the fix to the original line item and does not read it as a new payment. File them in date order and confirm a receipt for each.
Those amendments flow through to your statement of account, which then carries the true liability for the quarter. If the amended liability on ROS does not match your recalculated payroll totals, stop and query it before you stage anything. At year-end, reconcile the deducted, submitted and paid figures against the Employment Detail Summary to confirm the shortfall has reached zero.
Why Your ROS Submission Keeps Getting Rejected
Most rejected or mismatched submissions come from an incorrect pay date, invalid or duplicate line items, or an outdated RPN, rather than a system fault.
Before you resubmit the same file, split the problem into two questions. Did it fail at upload, or did it fail at validation? A file that never lands is usually a technical fault, most often a lapsed or wrong ROS digital certificate or a malformed file from your payroll software. A file that lands but comes back with errors is a data problem, and the Payroll Submission Response will name the first record at fault.
For data errors, work the response line by line instead of blindly rerunning it. The most common trigger is the pay date. Under Revenue’s payroll submission rules, the pay date sets the submission period, so a mistyped date quietly pushes the whole run into the wrong statement month. Fix the date first if the reported period looks off. Next, check each named employee against a fresh RPN, since stale tax details on new starters or leavers often throw employee-level errors. Then confirm you are correcting, not duplicating: if the same run was sent twice, ROS may treat the second file as a duplicate rather than an amendment, which is where the previous line item ID matters so you correct only the changed rows.
If the figures are right but the month is wrong, reconcile the run, the response and the statement of account side by side. A payment sitting in the wrong month is almost always a timing mismatch, not a calculation error. Only when the wording stays vague after these checks should you raise it as a genuine ROS technical issue.
What Late Payroll and Late PAYE Really Cost a Small Employer
Late payroll exposes even a small employer to two separate consequences, because Revenue treats submission timing and payment timing as distinct compliance events. Getting one right does nothing for the other.
Walk one month through both clocks and the shape of the exposure becomes obvious.
One pay date, two deadlines
Your pay date is Friday 27 February 2026. The PSR is due that same Friday, and the cash leaves your account that same Friday. You are busy, so you file the submission on Monday 2 March instead. The wages went out on time, the money is all correct, nobody is short. You have still missed a filing deadline that expired three days earlier, and no amount of filing early next month unwinds it. The repair is an amended PSR carrying the original 27 February pay date.
The second clock is still running. The PAYE, PRSI and USC on that February run are due by 14 March, which in 2026 falls on a Saturday, so in practice you are working to the Friday before, or to Monday 23 March if you file and pay through ROS. Miss that and late-payment interest starts accruing from the due date and keeps accruing until the balance clears. Paying in April does not retire the interest that ran through March.
That is the whole trap: a submission logged after the pay date is already late against a deadline that has passed, while the on-or-before rule and the payment due date never converge. Fixing your filing habit does nothing to stop interest already running on an unpaid amount, and paying on time does not undo a submission that landed late.
For a micro-employer, how serious this gets depends on timing, frequency and any arrears left outstanding, not on whether it was a first slip. So treat the two exposures separately. Confirm which pay dates were reported late, confirm which liabilities were paid late, then put the position right promptly and keep the ROS confirmations. A short, self-corrected pattern is a very different conversation with the Collector General than a growing balance left to drift.
Start Your Fixed Monthly Slot This Week
The insight worth carrying out of all this is that the on-or-before rule and the payment due date are two separate clocks, and one recurring monthly slot is what keeps both from slipping.
Start this week by fixing one pay date for the whole year and building your payroll calendar around it, with a processing slot just before that date and a diarised Revenue payment day just after it. Before your next run, fold the RPN request into that same slot and set up a variable direct debit for whichever due date your filing route gives you. Because the calendar already holds the dates, retrieving each RPN and paying Revenue become things the slot triggers rather than things you have to remember.
From your next pay run, work the pre-approval audit before you click approve. Pull a fresh RPN for every employee and director, run the gross-to-net report, and match total net pay to the bank file you are about to send. Catching a stale RPN at that moment is exactly what stops a small monthly shortfall from compounding into a quarter of amended submissions.
Before your first pay run in 2026, add one layer to the same slot: pull the Auto-Enrolment Payroll Notifications from NAERSA alongside your RPNs, and carry the employer contribution on its own line so it never hides inside net pay. Then reconcile every month and close off each year, checking your PSR totals against the statement of account before the direct debit goes, and matching your deducted, submitted and paid figures against the Employment Detail Summary at year-end until the position reads zero.
Run that slot on its fixed date and the outcome takes care of itself. Every PSR filed on or before the pay date, PAYE, PRSI and USC cleared by the due date, no accountant, and no quiet under-deduction waiting for you in December.
Your Next Step
Open your calendar and put three recurring entries in it right now: your processing slot, your pay date, and your Revenue payment day. That is the whole system, and it takes about four minutes to create.
Then make sure the software underneath it is ROS-integrated, so the RPN retrieval and the submission happen inside the run rather than as separate jobs you have to remember. Bullet is one Irish-built option for small employers doing this without an accountant.
Frequently Asked Questions
Is running payroll in-house realistic for a small Irish employer with a handful of staff?
For most employers with one to ten staff, yes, provided you run it as a fixed routine rather than ad-hoc admin. The work is the same short loop every period, and ROS-integrated software does the tax arithmetic. What it cannot do is check your inputs, which is why the pre-approval audit matters more than the calculation.
What do I have to register with Revenue before I can pay my first employee in Ireland?
Register as an employer with Revenue before the first payment, including where you are a limited company director paying yourself. You then need ROS access with a valid digital certificate to file. A Revenue Payroll Notification only issues once the specific employment is registered against your employer number, so register early enough for the RPN to arrive before pay day.
What happens if there is no RPN for a new employee, and how does emergency tax work?
Emergency tax is the fallback ROS uses when it has no notification to hand your payroll. How hard it bites depends on the PPS number: with one, the employee gets a restricted cut-off for the first month that tightens again after four weeks; without one, everything is taxed at the higher rate and no credits apply at all. Registering the employment ends it, and the excess refunds through the new notification.
How do I handle statutory sick leave, annual leave and public holidays in a pay run?
Code each absence before you open the pay run, never afterwards. Give sick leave, annual leave and public holiday entitlement their own codes so payroll can itemise each on the payslip. Annual leave keeps accruing during certified sickness, so update the balance too. If Illness Benefit is in play, reconcile it against employer sick pay before you close the run.