Skip to content
Reporting

Obligations built into the platform

Licence obligations do not wait for a reporting sprint. We build transaction monitoring, screening and regulatory reports into the platform, with the evidence auditors ask for.

Traceable

Every figure back to its ledger entries

Repeatable

The same report, rebuilt from the same data

Evidenced

Built for the questions auditors ask

What we build

Capabilities in regulatory reporting

Transaction monitoring

Rules and alerts over the ledger itself, so what is monitored is what actually moved.

Screening

Customers and counterparties screened at onboarding and again when anything changes, with every result kept.

Regulatory reports

Reports generated from the same entries as the balances, built to the obligations your licence carries.

Control evidence

Delivered inside the client's certified control environment, with the evidence produced as part of the build rather than assembled before the audit.

Where this applies

In the UK and EU

In the UK and EU the obligations are the Money Laundering Regulations and JMLSG guidance, suspicious activity reports to the NCA, OFSI and EU sanctions screening, the FCA's financial crime returns, safeguarding reconciliation for EMIs and payment institutions, DORA and the operational resilience rules. The names differ from the Australian ones we have built to. The evidence trail an auditor asks for is the same: every figure back to its ledger entries, every screening result kept, every rule change dated.

How we work

The delivery path

01

Start from the obligation

Licence conditions and the regulator's guidance are read before the data model, so the report shapes what gets recorded.

02

Report from the ledger

No side spreadsheet and no second copy of the truth. Every figure is a query over the same entries as the balances.

03

Rehearse the audit

Walk the evidence trail before the auditor does, from the report back to the transaction.

04

Keep it current

Obligations change. Rules and reports live in version control, so every change is reviewed, tested and dated.

Built to
Australian regulators: AUSTRAC AML/CTF · APRA CPS 234

The licensed platforms we have worked on are in Australia and answer to its financial regulators: AUSTRAC, for money laundering and terrorism financing (the AML/CTF regime), and APRA, for information security (CPS 234). Broadly, AUSTRAC is where the UK Money Laundering Regulations and JMLSG guidance sit, and CPS 234 where DORA and the FCA and PRA operational resilience rules sit.

  • Transaction monitoring and screening
  • Regulatory reports generated from the ledger
  • Delivered inside the client's certified control environment
PythonTypeScriptAWS serverlessEvent sourcingNext.js

Bring us your regulatory reporting problem

Ninety minutes with the engineers who would do the work, on one problem you name: a transaction monitoring rule, a screening check, a regulatory report.