If only ethical business could be a competitive advantage.
It can. It just takes longer to show up on a spreadsheet than most people have patience for.
Payroll carries an odd kind of weight. Run it perfectly 12 times a year, and nobody sends you a thank you card, but get it wrong once, and you’ve affected someone’s rent, their childcare payment, their weekly shop, their faith in the employer who hired them. The stakes sit with people who had no say in which software you chose.
That’s why ethics in payroll technology can’t live on a website page. It has to live in the product itself.
Trust is fragile, and payroll is where it breaks first
Think about what data a bureau actually holds. Names, addresses, dates of birth, National Insurance numbers, bank details, salary, sick leave, court orders, pension opt-outs. It’s one of the richest personal data sets any business will ever touch, and it updates every month.
Now think about how much of that data moves through systems the bureau didn’t build and can’t fully inspect.
Clients aren’t paranoid when they ask hard questions about your platform. They’re doing their job. A payroll partner sits inside the most sensitive corner of their operation, and they’re accountable for what happens there, whether or not they picked the code.
So the question isn’t whether your provider says the right things; it’s whether they actually do the right thing … even when nobody’s watching.
Ethics as a design constraint
At Luna, we treat ethics the way we treat performance or accessibility. It’s a constraint we design against, and it shapes decisions before the first line of code gets written.
Four commitments underpin what we do
We show our workings
Every meaningful action in Luna leaves a trail. Who changed the pay rate, when, from what to what, and who approved it. Audit isn’t a module you buy or a report you request. It should be the default, because a system that can’t explain itself can’t be trusted with someone’s wages.
We collect less
Privacy by design gets quoted a lot and practised rarely. In practice it means we ask a boring question at the start of every feature – “what’s the least data we need to make this work?” This means fewer fields, tighter retention, and clearer purposes, plus data you never collected is data you can never lose.
We name the owner
Controller, processor, sub-processor – these words matter enormously when something goes wrong, and they’re worth being clear about long before that day arrives. Our sub-processor list is published. Our roles are written down. If you want to know exactly where your clients’ data sits and who touches it, you can find out in an afternoon.
We build for everyone who has to use it
Payroll software doesn’t get to pick its users. If someone works for your client, they need their payslip, and their ability to get it shouldn’t depend on their eyesight, their motor control or whether they use a mouse.
Everybody gets paid, so everybody has to be able to use it
Accessibility is one of those things that sounds like a compliance chore until you picture the person on the other end of it. A warehouse worker using a screen reader. Someone with a tremor trying to hit a small button. A colleague whose colour vision means your carefully chosen status badges all look the same.
They still need to check their pay, so we built in accessibility testing from the outset.
Every component in the Luna front end lives in an isolated workbench where it gets rendered on its own and audited automatically against the WCAG 2.1 A and AA rule set. Contrast ratios, focus order, labelling, keyboard reachability, ARIA correctness. The checks run against the rendered page in a real browser rather than against the source code, because what matters is what actually reaches the screen.
Failures break the build, and a component with an accessibility violation doesn’t quietly ship and wait for someone to complain about it 6 months later. It stops in CI, gets fixed, and moves on.
Our developers can also simulate different types of vision impairment while they’re building, which turns accessibility from a review-stage argument into something you notice while the component is still clay.
Automated tooling of this kind, however, can never be 100%. In reality, it catches around half of the accessibility issues in a typical interface. The rest needs human judgement and real assistive technology. We treat the automated layer as the floor we refuse to go below, and we keep the manual review on top of it.
It’s a small example of the general principle. Ethics shows up in engineering decisions that nobody outside the team will ever see, but that is exactly why they’re worth making.
Where incentives actually get tested
Values statements are easy to write; the test comes when there are commercial pinch points.
Could a payroll platform monetise aggregated pay data? Technically, yes. Should it? No, and the fact that it’s technically possible is precisely why the answer needs to be written down somewhere binding.
Could a platform make exports awkward so clients find it painful to leave? Plenty do. We build for portability instead, because a client who stays by choice is worth more than a client who stays by friction.
Could pricing be structured so the interesting costs only surface at renewal? Also common. We’d rather have the difficult conversation on day 1 than the resentful one on day 400.
None of these positions is heroic; they’re just the version of the business we’d want to buy from.
The commercial case
Ethics that only survive when they’re free aren’t ethics. But it’s fair to point out that this approach actually earns its keep.
Bureaus win tenders on due diligence. When a prospect’s IT or compliance team starts asking about ISO certification, data residency, breach notification timelines and sub-processors, you either have answers ready, or you spend three weeks scrambling for them. Sitting on a platform built for scrutiny turns that questionnaire from a threat into a differentiator.
Retention improves too. Clients leave payroll providers over errors and surprises. A system with real auditability catches errors earlier and explains them faster, which means fewer of the conversations that can end relationships.
Plus, it changes who wants to work with you. Partners, integrators and potential clients will all be doing their own diligence now, and being the option that holds up under this scrutiny is worth something.
Trusted technology – the basis for Luna
Great technology is powerful, but trusted technology is priceless. At Luna, trust compounds in a way that features never do. Every clean audit, every clear answer, every month where the numbers are right and provable adds to something a competitor can’t ship in a release note.
That’s the belief we have with Luna – build the version that stands up to scrutiny, and let the scrutiny do the selling.
Want to see how Luna handles auditability, permissions and data retention? Book a demo and ask us the awkward questions. We prefer them.