Compliance watch
A hire clears its checks first
Right to work and background checks are tracked at the offer stage, so the start date is only real once the record says it can be.
The workforce
Certified, checked, and answerable for it.
Audit log · payroll
Step-up code, then the payslip09:41
Second signature givenYesterday
A financial services workforce is advisers, analysts and operations staff in roles that carry certifications and conduct obligations, a compliance function that must evidence everything, and support teams handling money and data all day. Background checks precede start dates, training completion must be provable rather than probable, and every process is designed on the assumption that someone will one day ask to see the trail.
Where it breaks
The problems that live in this world.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
Regulated roles need provable records.
Certifications, checks and role requirements per person must be current and demonstrable on demand. A spreadsheet that was accurate in March is not evidence, it is exposure.
Policies must be provably read.
A policy update sent by email is a hope. When the regulator asks who acknowledged the change, a read receipt you never collected cannot be produced retroactively.
Payroll without dual control is a finding.
One person able to change pay data and approve the run is exactly the situation control frameworks exist to prevent, yet it is the default state of most payroll spreadsheets.
Leavers keep access longer than badges.
Building passes get collected on the last day; system access lingers for weeks. In a regulated firm, that gap is not sloppy, it is reportable.
Day to day
Three operational realities, handled.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
01
Attendance and absence with history.
Presence, leave and absence sit on one record with full history. Approvals show team context before a decision, and the calendar carries compliance dates and probation reviews on permission-gated layers.
02
Payroll under real control.
Each run is validated, unusual movement against the last cycle is flagged, and two people must sign off, with a conflict check and a full audit trail before anything pays out.
03
Compliance that produces evidence.
Right to work, DBS and certifications are tracked with daily checks and expiry warnings. Every report run and export is logged, and money-bearing reports sit behind an email one-time-code reveal.
The modules that fit
Take what fits, leave the rest.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
Compliance watch→
Checks and certifications per person, tracked daily with statutory deadlines per jurisdiction.
Payroll→
Dual-control approval, conflict of interest checks and a full audit trail on every run.
Reports→
Every run and export logged, permission scoped, with money-bearing reports behind a step-up reveal.
Connect→
Announcements with acknowledgements and read receipts, so a policy change is provably seen.
Grievance→
Conduct and grievance cases run through a structured, confidential process with a retained history.
Perform→
Goal and review cadence with the evidence gathered as the year happens, not reconstructed.
A working day, connected
How the day actually runs.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
01
A hire clears its checks first
Right to work and background checks are tracked at the offer stage, so the start date is only real once the record says it can be.
02
A certification stays current
The daily check flags a certification 90 days out, the renewal is assigned and tracked, and the record shows an unbroken chain of validity.
03
A policy change goes out and comes back
The announcement targets the affected population and collects acknowledgements, so the compliance file contains who read it and when.
04
The pay run faces dual control
Validation runs first, anomalies are flagged, and dual control completes with conflict of interest checks, every action on the audit trail.
05
An auditor asks a hard question
The answer is a filtered report with its derivation printed on the page, and the fact you ran and exported it is itself logged.
06
A leaver loses access on day zero
Separation queues access revocation across systems immediately, with equipment and final settlement tracked on the same checklist.
Who lives this
The people inside this playbook.
Payroll
A certification stays current
The daily check flags a certification 90 days out, the renewal is assigned and tracked, and the record shows an unbroken chain of validity.
Reports
A policy change goes out and comes back
The announcement targets the affected population and collects acknowledgements, so the compliance file contains who read it and when.
Connect
The pay run faces dual control
Validation runs first, anomalies are flagged, and dual control completes with conflict of interest checks, every action on the audit trail.
Asked before buying
The questions that come up every time.
Is there a real audit trail?
Yes, in several layers: every payroll decision and approval is logged, every report run and export is recorded and readable by tenant admins, and lifecycle events keep their history on the record. Evidence is a designed output, not an afterthought.
How does dual control work on payroll?
Dual control must complete on every run, with conflict of interest checks, after automatic validation and anomaly detection have flagged missing data, duplicates and unusual movement against the prior cycle.
Can we prove staff read a policy update?
Announcements through Connect carry acknowledgements and read receipts with audience targeting, so a critical message produces a record of exactly who saw it.
Who can see compensation data?
Pay visibility is permission scoped, and money-bearing reports sit behind an email one-time-code reveal on top of role permissions, so a signed-in session alone is not enough to open pay data.
Run it on your own organisation.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.