Background verification, segregation of duties, immutable audit trails, mandatory leave rules and access controls that a banking or securities regulator will accept, alongside everyday payroll and performance.
Complete
Audit trail on people actions
Who changed what, when and with which approval, retained for the period your regulator requires.
100%
Hires with verification status on record
Identity, address, employment, education and criminal record checks tracked to closure per hire.
2 hrs
To assemble an inspection evidence pack
Personnel files, verification status, mandatory leave compliance and access history exported together.
Zero
Uncontrolled access to compensation data
Salary and personal data restricted by role, with every sensitive view recorded.
The reality on the ground
Every conversation with a people team in this sector surfaces the same handful of failures. Here is what they look like and what they cost.
The regulator asks for personnel files, background verification outcomes, mandatory leave compliance and evidence of who had access to what. The answer lives across an email archive, a vendor portal, a leave spreadsheet and the recollection of two people who have been there longest.
Cost of leaving it: Findings that are procedural rather than substantive, and remediation timelines you did not plan for.
The candidate joins on a conditional basis pending verification. The vendor report arrives in three weeks and lands in an inbox. Nobody tracks the discrepancy that was flagged, and eighteen months later the person is in a sensitive role with an open finding against their file.
Cost of leaving it: An unverified employee in a regulated function, which is exactly what an inspection looks for.
Staff in sensitive functions are required to take a continuous block of leave each year so that anything hidden surfaces. Tracking who has and has not complied across hundreds of people, and enforcing it before the year closes, is a manual exercise that slips.
Cost of leaving it: A control that exists on paper and fails in practice, which is worse than not having it.
Salary review runs on a spreadsheet emailed between a handful of leaders. Copies proliferate, one gets forwarded to the wrong person, and there is no record of who saw what. In a regulated firm this is not just embarrassing, it is a control failure.
Cost of leaving it: Data leakage that cannot be traced and a control environment that will not withstand scrutiny.
Capability deep dive
Same platform, sector specific defaults. Each capability below arrives preconfigured, so your team edits rather than builds.
A day in the life
Software only sticks when the person using it saves time on their own work. These are the three roles that make or break adoption here.
Answerable for the control environment when an inspection arrives.
Daily
Reviews open verification discrepancies and access grant approvals awaiting a checker.
Weekly
Checks mandatory leave compliance and escalates anyone at risk of missing the requirement.
Quarterly
Launches the conflict of interest declaration cycle and tracks non response.
On request
Exports the inspection evidence pack in a couple of hours rather than a fortnight.
Runs hiring and people processes inside a tight control framework.
Offer stage
Selects the verification package matched to the role's sensitivity.
Joining
Confirms documents, declarations and access requests are all recorded before day one.
Confirmation
Cannot confirm employment while a verification discrepancy is open, by design.
Review cycle
Runs compensation review inside the platform with maker and checker approval.
Subject to controls that must be easy to comply with.
Onboarding
Completes declarations and uploads documents once, without email attachments.
Annually
Receives a prompt for the required continuous leave block and books it.
Quarterly
Submits trading and conflict declarations in a few minutes.
Any time
Views own payslips, deferred bonus schedule and documents securely.
Compliance and audit
Personnel files
Contracts, identity documents, qualifications and role history complete and retrievable per employee.
Background verification outcomes
Check level status, vendor reports and discrepancy resolution retained per hire.
Mandatory leave compliance
Continuous leave block status per sensitive role reported across the calendar year.
Maker and checker evidence
Dual approval trail on payroll release, compensation change and access grants.
Access and view logs
Record of who viewed or changed sensitive data, retained for your regulatory period.
Declarations register
Conflict of interest, trading and gift declarations per cycle with non response tracking.
End to end workflow
One record per person, from the day they join to the day they leave. No spreadsheet handoffs in between.
Stage 1
Offer
Role sensitivity determines the verification package and approval path before the offer is issued.
Stage 2
Verification
Checks initiated, tracked and closed, with discrepancies blocking confirmation.
Stage 3
Onboarding
Documents, declarations and access grants recorded with dual approval where required.
Stage 4
Operate
Leave, mandatory leave blocks, payroll and declarations run with a full audit trail.
Stage 5
Change
Role, compensation and access changes require maker and checker and leave an immutable record.
Stage 6
Exit
Access revocation, clearance, settlement and retention treatment executed and evidenced.
Integrations and hardware
No rip and replace. HRMione sits alongside the systems and devices already on your floor.
Verification and identity
Finance and treasury
Governance
Rollout plan
A dedicated onboarding lead runs this with you. Nothing here needs your engineering team.
Week one
Records and access model
Employees, roles, reporting lines and the access matrix configured and reviewed with compliance.
Week two
Controls live
Maker and checker rules, verification packages and mandatory leave rules switched on.
Week four
Parallel payroll
One cycle run in parallel with dual approval, reconciled and evidenced.
Day ninety
Audit readiness
Declaration cycle completed, evidence pack dry run performed with internal audit.
Commercial fit
Most regulated firms configure the access model and control gates in week one with compliance present, then migrate payroll at the next monthly boundary.
Typical headcount
Regulated firms from 50 to 3000 employees, including lending, payments, broking, insurance distribution and asset management.
Indicative spend
Priced per active employee per month, billed annually. Control features are part of the platform rather than a compliance upsell.
Modules in the standard bundle
Case study
Situation
An inspection had produced procedural findings on incomplete verification files and unmonitored mandatory leave. Compensation review ran on emailed spreadsheets with no record of who had seen them.
What we did
The access model was rebuilt inside HRMione with view logging, verification packages were tied to role sensitivity with discrepancy gates, and mandatory leave monitoring plus maker and checker approvals were switched on.
Result
The difference is that controls now run by default rather than by reminder. When the inspection came back, we answered with exports instead of explanations.
Straight answers
Can the audit log be altered by an administrator?
No. The log is append only and no user role, including the highest privilege account in your workspace, can edit or remove entries. Exports are available to internal audit directly.
We use a specific background verification vendor. Must we change?
No. HRMione tracks the check lifecycle and outcomes regardless of vendor, including discrepancy resolution. Where a direct connection exists it is used, otherwise status is maintained against the case.
Our approval matrix is complex and amount based. Is that supported?
Yes. Approval paths are configured per action type with thresholds and delegation, and every approval or rejection is recorded with the actor and timestamp.
How is compensation data protected from over broad access?
Compensation visibility is granted by role, not by seniority, and every view of a sensitive field is logged. Managers can be given team management without any salary visibility at all.
What about data retention and erasure obligations?
Retention schedules are configured per record type so regulatory retention takes precedence over an erasure request where the law requires it, and both the request and the decision are recorded.
Software Solutions
FAQ
Keep exploring
Thirty minutes, your own scenarios, a live sandbox already loaded with a workforce that looks like yours.
We use necessary cookies to run the site. With your consent, we also use analytics and marketing cookies to improve the product. Read our Privacy Policy.
