Design partner
Test the rule against the actual records
Compliance Audit
- 100%
- population tested instead of a sample
- Daily
- assurance cadence instead of annual
- Read-only
- access to every connected system
Every layer above this one is about knowing and planning. This one answers the only question an inspector really asks: can you show me?
The problem
What this module exists to fix
Assurance is a sample, once a year
Internal audit tests 25 vouchers out of four million transactions. It is the best available option today, and it is a statistical fig leaf.
The gap between policy and practice is invisible
You can have a perfect SOP, a mapped control and a signed attestation, and still be non-compliant in the data. Nothing in the traditional stack looks there.
New rules mean new bespoke testing
Every new notification triggers a fresh data-extraction and analysis project, built from scratch, discarded afterwards.
Capabilities
What it does
Read-only system connectors
Certified read-only connectors for ERP, payroll and HRMS, plant historians, e-way bill and GST data, and core banking or lending systems. Regulens never writes to a system of record.
Obligations compiled into tests
An obligation with a trigger, threshold and deadline becomes an executable rule expressed against your data model, with the provision cited in the test definition.
Continuous control monitoring
Tests run on schedule or on event across the full population — not a sample — with exceptions raised into a triage workflow.
New-rule readiness testing
Point the platform at a newly notified rule and ask whether your current operations would satisfy it. Get a population-level answer with the failing records identified.
Exception management
Exceptions are triaged, assigned, dispositioned and closed with rationale, feeding both remediation and control redesign.
Immutable evidence trail
Every test run, result, exception and disposition is written to an append-only, cryptographically verifiable log suitable for inspector and audit inspection.
How it works
Step by step
- 01
Connect
Read-only connectivity is established with your data and security teams, scoped to the minimum fields required.
- 02
Map
Your data model is mapped to the platform canonical model once; tests are then written against the canonical layer.
- 03
Compile
Obligations are translated into executable tests with human review and approval before activation.
- 04
Run
Tests execute continuously across the full population, with results versioned by run.
- 05
Prove
Results, exceptions and dispositions form an evidence chain from the source provision to the individual record.
Questions
The things people actually ask
Including the ones where the answer is a limitation.
- Does Regulens hold our transaction data?
- It depends on the deployment you choose. In the customer-hosted deployment, the execution engine runs inside your environment and only results and metadata leave it. In the Regulens-hosted deployment, data is processed within India under contractual and technical controls set out in the DPA. Most design partners choose customer-hosted.
- Can it write to our systems?
- No. All connectors are read-only by design and certified as such. Remediation actions are raised as tickets in your workflow tooling for a human to action.
- How do we join the design partner programme?
- We are working with a small cohort through 2026 with general availability targeted for 2027. Design partners commit engineering and compliance time and get significant influence over the module and commercial terms. Get in touch through the contact form.
See Compliance Audit against your own footprint
A two-week scoped pilot on your real entities and jurisdictions. You compare the output against what your team found in the same period.