Five Countries, One Payroll System

Crimson runs people across dozens of legal entities, each with its own rulebook, and payroll had grown up as a patchwork — a legacy HRIS here, a country vendor there, handoffs held together by hand. The job was to pull all of it onto one global payroll platform across five countries: Australia, the UK, Canada, India, and the US.

There’s a small irony I genuinely enjoy in this one. The platform we landed on is the same one I spent two and a half years supporting from the other side of the fence. I’ve sat with the exact tickets an implementation like this tends to generate — so now I get to be the reason they never get written.

Five countries, and one team that still has to make this month’s payroll land while building next year’s. Payroll configuration doesn’t forgive much, either — a lot of the choices, like the tax treatment you bake into a pay type, are set the moment the first run goes out. There’s no refactoring a payslip after the fact.

I started with Australia and treated it as the template for everything after. That meant a pay calendar I checked payday by payday against the live engine — weekends, public holidays, the awkward edge cases included — and a custom pay-type setup that keeps every commission and earning stream separate and taxed correctly. I wrote down the reasoning behind each one, so whoever comes next inherits decisions instead of mysteries. On top of that, an employee help center distilled from the platform’s documentation, and playbooks that turn the Australian build into a kit the UK and Canada can reuse.

Running quietly alongside all of that: India payroll, end to end. Vendor coordination, statutory compliance, and the paise-level reconciliations that turn a frustrated employee back into one who trusts the system again.

Australia is configured, verified, and ready to go, with the next countries lined up behind it on the same playbooks. Every decision that mattered has a written “why” attached to it — which, in payroll, is the whole difference between an implementation and a time bomb someone else has to defuse later.