Skip to content

BrightPay and Thesaurus

Integration · Payments and accounting

Automation with BrightPay
and Thesaurus Payroll

We could not find a public API for BrightPay or Thesaurus Payroll Manager. Both talk to Revenue directly for RPNs and payroll submissions, and both import hours from CSV files. The realistic automation sits before and after payroll: clean timesheets in, journals out and payslip questions answered, while a person runs and approves each payroll.

Who makes BrightPay and Thesaurus?

Both products come from the same Irish company. Thesaurus Software Ltd, which trades as Bright Software Group, has made Thesaurus Payroll Manager since 1992 and also makes BrightPay. Both are desktop payroll programs with cloud add-ons. Many Irish accountants run one of them for their clients.

Integration points (checked 19 Nov 2026)
PointBrightPayThesaurus Payroll Manager
Public APIWe could not find public API documentation.We could not find public API documentation.
Hours importCSV import of hourly, daily and periodic pay. Matches on name, PPSN or works number.Import hours from a text or CSV file (Utilities, Import Hours).
Revenue (RPNs, submissions)Direct, with the employer’s ROS digital certificate.Direct, with the employer’s ROS digital certificate.
Accounting journalsBy API to Xero, QuickBooks Online, Sage Business Cloud Accounting and AccountsIQ. CSV for desktop packages.Check with the vendor.
Employee self-serviceBrightPay Connect: payslips, documents, leave requests and an app.Check with the vendor.

How does payroll connect to Revenue?

Since 1 January 2019, under PAYE Modernisation, Irish employers must report pay to Revenue on or before each pay date. Revenue publishes web services for payroll software providers: Lookup RPN, New RPN, Payroll Submission, Check Submission and Check Payroll Run. Software developers register with Revenue for access to a test environment. Requests are signed with a Revenue-issued certificate.

BrightPay and Thesaurus already use these services. Before each pay run, the software retrieves each employee’s Revenue Payroll Notification (RPN), which sets their tax credits and rate band. After the run, it sends the payroll submission. Both steps use the employer’s or agent’s ROS digital certificate. You do not need a separate integration for this, and an agent should not try to build one. See Revenue Online Service for what else can and cannot be automated with Revenue.

What is worth automating around payroll?

The slow, error-prone work sits before and after the payroll run, not inside it.

Payroll jobs and where automation fits
JobAutomate?How
Collect timesheetsYesPull hours from rosters, clock-in apps or forms, check them against rules and build the import CSV. See [staff scheduling](/use-cases/staff-scheduling/).
Flag exceptionsYesList missing hours, overtime above a limit and new starters without a PPSN before the payroll person starts.
Payslip questionsYes, with careAn agent answers "why is my pay lower?" from a payroll summary the employee can already see, after an identity check.
Journals to accountsAlready builtUse the BrightPay journal link to Xero or other packages. See [Xero](/integrations/xero/).
Run payroll and submitNoA person runs, checks and submits. The software sends the submission.
Change tax detailsNoTax credits come from Revenue through the RPN. Nobody should override them by hand without reason.

Before you connect BrightPay and Thesaurus: a checklist.

Checklist

Connecting BrightPay and Thesaurus safely

What should stay manual?

  • The pay run itself. Do not use screen automation (RPA) to click through BrightPay or Thesaurus. A screen change can post wrong figures, and errors reach Revenue on the pay date.
  • Submissions and corrections. Revenue submissions and amendments need a person who understands them.
  • Termination and leave decisions. An agent can collect a leave request in BrightPay Connect, but a manager approves it.
  • Pay disputes. Route them to a person. The agent should only explain what the payslip shows.

Payroll data includes PPSNs, salaries and sometimes sick leave, which can be health data. Keep the agent’s access to the minimum for each job, and keep files in the EU. This is a guide, not tax or legal advice: ask your accountant and data protection adviser. The accountants page covers practices that run payroll for many clients.

How do you build a clean hours file?

The CSV import is the main door into both programs, so the quality of the file decides the quality of the automation. A good import step does these checks before anyone opens the payroll software:

  • Match every row to one employee. BrightPay matches on name, PPSN or works number. Use the works number where you can, because names change and PPSNs are sensitive.
  • Check the pay period. Every row must fall inside the period you are about to run.
  • Check the rate type. Normal, overtime, Sunday and holiday hours must go to the right rate type in the payroll software.
  • Flag outliers. Hours above a set weekly limit, zero hours for a salaried employee, or a new name that payroll does not know.
  • Keep the source. Save the original roster or clock-in export next to the CSV, so anyone can trace a figure back.

This step is ordinary data entry automation with clear rules. It rarely needs a large language model. Use one only for messy inputs, such as handwritten timesheets or free-text notes from managers.

Where does BrightPay Connect help?

BrightPay Connect is the cloud add-on. Employees see payslips and documents, update some of their own details and request leave in a web portal or a free app. Leave requests stay pending until a manager approves them, and BrightPay states that approved leave syncs to the desktop payroll about every 15 minutes.

This removes many payroll questions before an agent is needed. Turn on Connect first. Add an agent only for the questions that remain, such as "why did my tax change this month?", and let it explain using the RPN and payslip lines the employee can already see.

Common questions

Does BrightPay have an API?

We could not find public API documentation for BrightPay on 19 November 2026. BrightPay does send payroll journals by API to Xero, QuickBooks Online, Sage Business Cloud Accounting and AccountsIQ, and it imports hours from CSV. For other links, build the CSV import or ask Bright Software Group directly.

Can an AI agent run our payroll?

It should not. The agent can prepare clean hours, flag exceptions and answer payslip questions. A person should run each payroll, check the totals and let the software send the submission to Revenue. Errors in payroll reach employees and Revenue on the same day, so human review is essential.

Do we need our own Revenue integration for payroll?

No. BrightPay and Thesaurus Payroll Manager already retrieve RPNs and send payroll submissions to Revenue using your ROS digital certificate. Revenue’s web services for payroll are meant for registered software providers. Use your payroll software and automate the steps before and after it.

Can employees ask an agent about their payslip?

Yes, with care. The agent must confirm the employee’s identity and show only that person’s data. It should explain what the payslip already shows, such as tax, USC and PRSI lines, and send pay disputes to a person. Record this processing in your GDPR records.

Sources

Bring us the task.

Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.

Start a project.

Two people on a sofa with laptops, planning a project beside a whiteboard of sticky notes

Book a call or send us a message. We read everything.

tash@neu.ie
Working with teams in Ireland and worldwide.

Get in touch

Free 30-minute AI review.