WRC Inspection Evidence Pack for Irish Construction Payroll

A WRC inspection evidence pack for Irish construction payroll should connect each worker's classification, hours, rates, premia, payslips, timesheets, and CWPS or equivalent contribution proof for the period under review. For construction employers covered by the Sectoral Employment Order, the pack should also show how each week was tested against the rate that applied at the time, including the 1 August rate steps and any apprentice-year movement.

The practical aim is traceability. If a worker-week passes the SEO check, the workbook should show why. If it fails, the reviewer should be able to move from the exception row back to the payslip, timesheet, contract or onboarding evidence, CWPS schedule, and payment record that explain the issue.

That matters because a WRC inspection is not a request for a tidy spreadsheet alone. The WRC says full inspections generally involve about 130 compliance checks, 14 days' written notice, and records for all persons employed in the previous 12 months, including timesheets and payslips or payroll details, according to its guidance on WRC inspection records employers must make available.

For an Irish construction employer, the evidence pack is therefore best treated as a structured index to the documents, not a separate compliance story written after the fact. The workbook can calculate the SEO position, but the employer still owns the legal and payroll judgement: who is in scope, how each worker is classified, which rate floor applies, whether a premium or allowance has been treated correctly, and how any defect should be remediated.

A practical workbook structure is usually enough:

1. Worker classification roster: worker, category, apprentice year or new entrant flag, contract dates, and classification evidence.
2. Per-worker weekly pay computation: work dates, hours type, paid rate, premia, allowances, gross pay, deductions, and payslip or timesheet references.
3. SEO compliance check: applicable SEO floor, paid amount, delta, exception flag, reviewer note, and source-document links.
4. CWPS or equivalent contribution evidence: pension, sick pay, death-in-service, remittance schedule, and payment proof by worker-week.
5. Source-document index: payslips, timesheets, payroll exports, onboarding or contract records, CWPS schedules, CPAS payment evidence, and correction records.

Start with the worker classification roster

The first sheet should be the worker classification roster. Every rate test downstream depends on one question being answered clearly: which SEO category was used for this worker during this period, and what evidence supports that choice?

For a construction SEO review, the roster should identify each in-scope worker as a Craftsperson, Category A Worker, Category B Worker, Apprentice with year, or New Entrant Operative. If someone is treated as outside scope, the reason should be documented rather than left implied. That avoids a weak audit trail where a worker simply disappears from the test because payroll did not map them to a construction category.

The scope logic has two parts. The employer must operate in the construction sector, and the employee's work must fall within one of the classes covered by the SEO. The WRC's construction-sector guidance describes new entrant operatives as workers over 18 entering the sector for the first time for their first two years, Category B workers as skilled general operatives with more than two years in the sector, Category A workers as specified skilled roles such as advanced scaffolding, banks operatives, steel fixers, crane drivers, and heavy machine operators, and craftspersons as qualified trades.

Misclassification is one of the most damaging evidence defects because the payslip can look arithmetically correct while the statutory floor is wrong. A craftsperson tested at a Category A rate, an apprentice held in the wrong year, or a new entrant left in that category beyond the two-year period can make the workbook understate the amount due.

At minimum, the roster should carry the worker name or payroll ID, category, apprentice year where relevant, new entrant start date where relevant, contract or onboarding reference, classification basis, and reviewer notes. The classification basis does not need to become a legal memo, but it should be specific enough for another reviewer to understand why the row was tested against that rate.

Build weekly rows that test hours, rates, and premia

The working sheet should be built at worker-week level, even if payroll is processed fortnightly or monthly. A weekly row gives the reviewer enough detail to test ordinary hours, overtime, Sunday work, public holidays, allowances, and deductions against the right period and the right worker classification.

A useful row includes worker ID, work week, pay period, ordinary hours, overtime hours, Sunday or public-holiday hours, hourly rate paid, premium rate or multiplier, travel time or country money where applicable, gross pay, deductions, and source-document references. The source fields matter as much as the calculation fields. If a row is challenged, the evidence pack should point to the payslip and timesheet that produced it.

For the SEO rate floor, keep the statutory minimum in a separate expected-rate column rather than burying it in a formula no one can inspect. From 1 August 2025 to 31 July 2026, the WRC construction SEO rates list Craftsperson at EUR 23.00 per hour, Category A at EUR 22.32, Category B at EUR 20.71, and New Entrant Operative at EUR 16.74. From 1 August 2026, the corresponding rates are EUR 23.74, EUR 23.03, EUR 21.37, and EUR 17.28.

Apprentices need their own logic because the rate follows a percentage of the craft rate rather than a flat category figure: Year 1 at 33.33%, Year 2 at 50%, Year 3 at 75%, and Year 4 at 90%. The evidence pack should therefore preserve the apprentice year used for the row, the date that year was assessed, and the rate step in force for the work week.

Premiums should not be blended into a single gross-pay figure too early. Overtime, Sunday work, public holidays, unsocial hours, travel time, and country money may each have different evidence behind them. The workbook should keep the hours type, rate, and supporting timesheet or roster reference separate enough that a reviewer can see whether the correct premium was applied and whether the source document supports the hours claimed.

This is where extraction work usually starts. Invoice Data Extraction can help convert batches of payslip PDFs and structured payroll or timesheet documents into Excel, CSV, or JSON rows, which is useful when the period under review contains hundreds or thousands of payslips. The compliance judgement still sits with the employer or adviser: the tool helps prepare the row-level data, while the payroll team tests classification, SEO rates, premia, and exceptions. For the payslip side of the workflow, the same extraction logic is covered in more detail in the guide to extract Irish payslip data to Excel.

Handle rate steps, pay periods, and apprentice anniversaries

Rate logic should attach to the work date, not just the payslip payment date. If a pay period straddles a construction SEO rate change, one payslip may contain work performed under two different rate floors. A workbook that applies one rate to the whole payslip can create a false pass or a false exception.

The two transition points to make explicit are 1 August 2025, when S.I. 620/2024 came into operation, and 1 August 2026, when the next uplift applies. A worker paid weekly from Monday to Sunday will usually be simple to test. A fortnightly, monthly, or manually adjusted payroll period may need the hours split by work date so that pre-step and post-step hours are tested separately.

Apprentice anniversaries need the same treatment. An apprentice can move from one percentage band to another independently of the general SEO uplift, so the workbook should not assume that a worker's apprentice year is static for the whole review period. The row should show the apprentice year at the work date, not just the apprentice year recorded when the evidence pack was prepared.

The fields that make this auditable are straightforward: work date, pay period start and end, rate-effective date, SEO category, apprentice year at the work date, minimum rate expected, paid rate, and delta. If a rate step is handled outside the payroll system through an adjustment or back-payment, the adjustment should be recorded on its own line and linked to the original affected week.

Preserving this logic helps separate real payroll defects from workbook defects. A flagged row might be an underpayment, but it might also be an effective-date error, a pay-period grouping issue, or an apprentice anniversary applied to the wrong week. The evidence pack should make that distinction visible before anyone decides what remediation is needed.

Treat CWPS as its own evidence stream

CWPS or equivalent contribution proof should sit in its own sheet, tied back to the same worker roster and pay periods used for the rate check. It should not be a loose monthly total attached at the end of the file. The purpose is to show that the contribution evidence belongs to the same workers, weeks, and deductions shown in payroll.

For each contribution week, include worker ID, contribution week, pension employer amount, pension employee amount, sick pay employer amount, sick pay employee amount, death-in-service employer and employee amounts, remittance schedule reference, payment evidence, and any adjustment note. If the employer uses an equivalent scheme rather than CWPS, the sheet should still show how the scheme evidence maps to the workers covered by the SEO.

The WRC construction SEO figures give the reviewer a useful reference point. From 1 August 2025 to 31 July 2026, weekly pension contributions are EUR 31.87 for the employer and EUR 21.27 for the employee. From 1 August 2026, they rise to EUR 32.89 and EUR 21.95. Sick pay weekly contributions from 1 August 2025 are EUR 2.37 employer and EUR 0.63 employee. Death-in-service contribution is EUR 1.14 employer and EUR 1.14 employee per week.

The reconciliation should run both ways. The payslip deduction should agree to the worker's contribution row, and the contribution row should agree to the remittance schedule and payment proof. Where there is a timing difference, late adjustment, missed week, or corrected remittance, keep the note beside the affected worker-week instead of relying on a separate explanation.

For a deeper remittance workflow, use a dedicated CWPS monthly schedule from construction payslips. In the WRC inspection evidence pack, the CWPS sheet's job is narrower: prove that the pension, sick pay, and death-in-service contribution evidence is complete, worker-specific, and linked to the payroll rows being tested.

Keep the source documents tied to every workbook row

The evidence pack is only as strong as its document references. A calculation row that says a worker passed the SEO rate test is useful; a row that also points to the payslip PDF, timesheet, payroll export, contract or onboarding record, CWPS schedule, payment evidence, and adjustment note is far more defensible.

Use a document reference convention that another person can follow without asking the preparer what a file name means. A practical reference usually combines worker ID, pay period, document type, and version or review note where needed. The exact naming convention matters less than consistency. The reviewer should be able to filter to one worker, open the linked files, and follow the payroll position without reconstructing the folder structure from memory.

This is also the point where raw payroll evidence becomes structured review data. Many firms start with folders of payslip PDFs, timesheet files, payroll exports, CWPS schedules, and payment confirmations. Invoice Data Extraction can help extract payroll and financial document data into structured spreadsheets by turning document batches into Excel, CSV, or JSON outputs that feed the workbook. It does not decide whether a worker is correctly classified, whether a premium is legally due, or whether a defect has been remediated.

The same source-document discipline applies beyond payroll. A construction firm preparing for WRC review may also be tightening project payment controls, contract notices, and accounts workflows. Those records should not be mixed into the payroll evidence pack, but they often sit in the same finance function. The Ireland CCA 2013 payment claim notice workflow is an adjacent control area where document timing and traceability matter in a similar way.

Keep original files intact. If a PDF is renamed, moved, or OCR'd, preserve the source file reference and note the extracted or reviewed version separately. If a back-payment is made after a self-audit, the pack should show the original payslip, the exception row, the correction calculation, and the later payment evidence as a chain rather than replacing the original record with the corrected one.

What to do when the pack shows a defect

A useful evidence pack will sometimes show uncomfortable results. Treat that as a control working, not as a reason to tidy the record after the fact. Each defect should be logged with worker, period, category, calculated floor, paid amount, document references, and the reason the row was flagged.

Separate the defect type before deciding what comes next. A missing timesheet is a document defect. A duplicated payslip row is a data defect. A craftsperson recorded as Category A is a classification question. A worker-week paid below the applicable floor is a rate issue. A missing pension, sick pay, or death-in-service remittance is a contribution issue. Those problems may all appear in the same workbook, but they do not have the same remediation path.

Do not overwrite the original evidence trail to make the pack look clean. Preserve the original record, record the correction or back-payment separately, and link the correction back to the affected worker-week. Where classification, entitlement, limitation periods, worker communication, or remediation strategy is uncertain, get appropriate payroll or legal advice before acting.

WRC guidance says that where breaches are detected at inspection, a breach letter may issue setting out the breach, the grounds for the inspector's determination, and actions required within a specified deadline, usually 21 days, to demonstrate compliance. It also describes possible escalation where an employer does not engage or does not demonstrate compliance.

The operational priority is to know the position before the inspection file is requested. A strong evidence pack lets the employer identify the issue, quantify the exposure, tie the finding to source documents, and decide the next action with advisers while the records are still organised enough to support the decision.