Introducing complead. One AI-native platform for financial crime compliance. Read the story
New Ready Integrations available Check the new integrations
By use case

Compliance that keeps up with regulation

Regulatory requirements are turned into workflows; the workflows then generate the evidence; reports, filings, decisions, and approvals are recorded as the work is carried out and become available when a supervisor requests them.

Compliance that keeps up with regulation
What you switch on

Modules active for regulatory compliance

The reporting is the visible aspect, while the case management, covering all the modules, is accessed by both internal and external auditors via the same record.

Why this matters here

The question always asks about a past date.

A supervisor rarely asks whether the control works now. They ask how it worked in March: what data it used, who decided, and why. Most teams can show today and rebuild the past from memory.

Rebuilt

audit packs

Put together after the request, from what people recall.

Undated

parameters

A threshold without a change log can be stated, not defended.

Scattered

filings and evidence

The report is in one system, the reasoning in another and the data in a third.

4 Artifacts requested at audit
1-click To export an evidence pack
5 to 10-year Retention, by jurisdiction
Zero Days spent building packs
Workflow · Four beats

From requirement to regulatory evidence

Scroll to advance
  1. Step 01 An owner on every action

    Alerts, dispositions, reason codes and approvals are recorded as soon as they occur.

  2. Step 02 Parameters with a change log

    Every threshold change is dated, assigned a cause, and made reversible, along with the measured impact.

  3. Step 03 Filings from the case record

    The case provides draft versions of the SAR and STR, and jurisdiction rules apply per entity.

  4. Step 04 Evidence as an export

    Each pack is provided either per entity or per period, including the list of decisions and the approvers.

complead / cases
  • Decisions this month18,204
  • With named owner100%
  • Reason codesstructured
complead / governance / params
  • Changes logged46
  • With rationale46
  • Oldest retained2019
complead / reports
  • Filed this month9
  • Median prep time18 min
  • Rejected0
complead / audit / export
  • Packs generated31
  • Assembly time0 days
  • Retentionto policy
Decide
Govern
File
Evidence
What you answer to

What must stay retrievable, and for how long

The retention rules allow no exceptions. A record that has been archived but is unreadable satisfies none of them.

Read the compliance guides
FIU Filing within the statutory window From detection
Supervisor Risk assessment and its review history Annual
Auditor Decision record per period 5–10 years
Regulator Model and parameter governance Per change
Case study · Payments

An MLRO who stopped preparing for reviews

A quarterly evidence-assembly exercise became an export. The review turned into a reading exercise, and the parameter history answered questions that used to require a meeting.

0 Days assembling packs
46 Parameter changes logged
100% Decisions with an owner
Read the case study
FAQ

Before you ask us

Do you submit filings on our behalf?

No. Drafts are prepared from the case trail, and the approval and submission stay with your team. A named person reviews and signs every report before it is sent, which keeps accountability where the regulations place it.

How do we show how a control worked on a past date?

From the record. List versions, parameter history and decision logs are dated and retrievable per period. A supervisor asking how a control worked in March gets the data it used, who decided and why, rather than an account rebuilt from memory.

How are threshold changes documented?

Each change is dated, given a cause and made reversible, with its measured impact recorded. A threshold with a change log can be defended in an examination; one without it can only be stated.

What is recorded on each action?

Alerts, dispositions, reason codes and approvals, as they happen and with a named owner. The record is written while the work is done, so nothing has to be reconstructed when a request arrives.

How are filings handled across jurisdictions?

Formats and deadlines are handled per entity, while the suspicion process stays single. Each FIU receives the format and timeline it requires, and group compliance still sees one consistent process across entities.

How long does an evidence pack take to produce?

No assembly time, because it is exported rather than built, per entity or per period. The pack includes the list of decisions and their approvers, generated from the record, so nothing in it depends on recall.

How long are records retained?

To your retention policy: five years in most regimes and ten where required. The record stays readable for the full period, because an archived file that cannot be opened satisfies none of the retention rules.

How does reporting connect to casework?

Reports are drafted from the case record, and the case record is shared across every module. Reporting is the visible part; the casework underneath is what makes each report traceable to its evidence.

Can auditors work from the same record?

Yes. Internal and external auditors work from the same case record across every module. They see the evidence your team saw, not an extract prepared for them.

What must stay retrievable, and for how long?

Filings, the risk assessment and its review history, decision records per period, and model and parameter governance. Each runs on its own clock: FIU reports from detection, the risk assessment at least annually, and decision records for five to ten years.

Bring the question your last auditor asked

We will show you where the answer lives, and what the export looks like.

3,000+ Data sources checked
220+ Countries covered
15 min Always real-time data