Luna integrations
One connection. Every system you already run.
Smart data integration
The LunaversalAPI pulls data from HR, time & attendance, rostering, expenses, and pension systems straight into your bureau’s worklog, then connects out to whichever payroll engine you run, whether that’s one system or several. No manual exports, no rebuilt spreadsheets every pay run.
Payroll data shouldn't live in fifteen different exports
Every HR platform formats things differently. Every rostering tool exports its own version of the truth. Bureaus end up stitching it all together by hand, chasing missing hours, and fixing starter and leaver errors after the payroll’s already run.
That’s the gap LunaversalAPI closes.
Two connections, one platform
LunaversalAPI does two jobs.
- Data collection
It pulls data in from the systems your clients run- HR, time and attendance, rostering, expenses, and pensions- and lands it directly in your bureau’s worklog, ready for your team to review and process. - Connection
Then it connects out to whichever payroll engine or engines you run, from Brain Payroll to Sage to BrightPay, sending the processed data across by API where the engine supports it, or by export and import where it doesn’t.
Underneath both directions sits LSPM, the Luna Standard Payroll Model.
Whatever the source system, the data lands in the same structured format before your team ever touches it.
That means one connection point on the way in, and one flexible route out, instead of a new integration project every time a client changes software or you take on a new payroll engine.
Capture
Normalise
Connect out
Built around your payroll engine, not instead of it
Luna doesn’t ask you to change what you run payroll on.
Whether your bureau operates a single payroll engine or several side by side, Brain Payroll, Sage, BrightPay, or others, LunaversalAPI connects out to each one once your team has reviewed and processed the data in the worklog.
How that data reaches the engine depends on what the engine itself supports. Some accept it via API. Others take it through export and import. Either way, it’s your existing engine doing the payroll run, not a replacement for it.
No migration, no re-platforming, no disruption to a payroll process that already works.
Book a walkthrough, and we’ll show you what an integration with your current HR and time & attendance systems actually looks like.
Two directions, one engine underneath
LunaversalAPI works both ways.
It brings data in from the systems your clients run, and it connects out to the payroll engine or engines your bureau processes on.
Data in
- HR & HRIS – Starter, leaver, and contract data, pulled from the systems your clients already use to manage their people, and landed in your bureau’s worklog.
- Time & attendance – Hours, shifts, and overtime, captured automatically instead of chased down every pay run.
- Rostering – Shift patterns and rota changes, brought into the worklog without a manual re-key.
- Expenses & benefits – Claims and benefit entries, added to the same worklog as everything else, ready for your team to check.
- Pensions – Contribution data, kept consistent and audit-ready alongside every other input.
Data out
- Single or multiple payroll engines – Once your team has processed the worklog, LunaversalAPI connects out to each engine via API or export/import, depending on what that engine supports.
Building compliance and trust
When we created Luna, we wanted to improve the experience of payroll bureaus and providers, their clients and their client’s employees.
For bureau teams, the trust in consistent data no matter which systems a client runs means fewer errors and faster client onboarding. This in turn builds client trust.
Each data run through LunaversalAPI is logged and traceable, so you can see exactly what came in, what changed, and what went out.
Which systems does Luna integrate with?
LunaversalAPI works in two directions.
On the way in, it’s built to connect with HR and HRIS platforms, time & attendance and rostering tools, expense and benefits systems, and pension providers, landing that data in your bureau’s worklog.
On the way out, it connects to the payroll engine or engines your bureau runs, including Brain Payroll, Sage, and BrightPay.
Where a direct connection isn’t available, CSV, XLSX, PDF, and export/import routes are supported.
Does Luna have an open API?
Yes. LunaversalAPI is Luna’s connection layer.
It captures data from employer systems into a structured worklog, and separately connects out to whichever payroll engine your bureau processes on, via API or export/import depending on what that engine supports.
Do I need to change my payroll software to use Luna?
No. LunaversalAPI works alongside your existing payroll engine or engines.
There’s no migration of your core payroll system, just a cleaner route for data to reach it, and a single worklog for your team to work from beforehand.
Can Luna work with more than one payroll engine at once?
Yes.
Bureaus running multiple engines, for example Brain Payroll for some clients and Sage or BrightPay for others, can connect each one through LunaversalAPI rather than managing separate processes for each.
Is my data secure?
Yes.
Every connection runs through validated, auditable data flows, built to the same ISO 27001 and ISO 27701 standards.