Re-keyed narratives
The analyst re-types what the case already recorded, and detail is lost.
Platform · Reporting
Regulatory Filings, drafted from the case
Prepare, review and submit SAR, STR and threshold reports in the format your regulator accepts, built from the case evidence you already have.
goAML
Native XML output
0
Re-keying from the case
4-eyes
Sign-off before submission
100%
Submissions logged and retained
Why this matters
The report is where a good investigation goes wrong
The investigation can be sound and the filing still fails: a format the regulator rejects, a narrative re-typed from memory, a deadline missed because approval sat in an inbox. Complead builds the filing from the case record, validates it against the schema, and logs every submission.
Format rejections
A schema mismatch bounces the filing and the clock keeps running.
No submission log
When the regulator asks what was filed and when, there is no clean record.
How it works
Scroll to advance
Four steps, from case to submitted report
-
Step 01
Pull from the case
The filing starts from a case: subject, evidence and timeline are carried across, not re-typed.
-
Step 02
Draft the narrative
A structured narrative is drafted from the case timeline. You edit for tone and add judgement.
-
Step 03
Validate against the schema
The report is checked against the regulator format before it leaves. Errors are shown by field.
-
Step 04
Sign off and submit
A second reviewer signs, and the report is submitted or exported. The submission is logged.
complead / pull
- New SAR from case#8841
- subject and evidencepre-filled
complead / draft
- Narrativedraft
- words240
- editable
- source eventslinked
complead / validate
- goAMLvalidation
- errors0
- warnings2
- ready tosign
complead / submit
- Signed byMLRO
- submitted14:02
- receiptstored
- retained10y
Pull
Draft
Validate
Submit
Capabilities
What the product actually does
From case to filing
Cases arrive from Case Management. The filing is built from that record, nothing re-keyed.
Narrative drafting
The narrative is drafted in the structure your regulator's schema requires, then edited by the analyst.
Schema validation
Checked against goAML and local formats before submission.
Acknowledgment tracking
Every submission returns a regulator reference, captured and logged against the filing.
Format library
goAML XML, FinCEN and local regulator templates maintained for you.
Submission log
Every filing, its version, reviewer and receipt, retained.
Product tour
Three screens your team lives in
The report, in the regulator's format
Subject, evidence and narrative assembled into the schema your regulator accepts, validated before it leaves.
- Pre-filled from the linked case, no re-keying
- Narrative in the required structure
- Field-level help against the target schema
complead / draft
- SAR-2026-0142
- subjectVolkov
- evidence items3
- narrative240w
No filing leaves with an error
Schema validation shows problems by field before you submit, not after the regulator bounces it.
- goAML and local schema checks
- Errors and warnings separated
- One click to jump to the field
complead / validate
- errors0
- warnings2
- addressformat
- daterange
Every submission, on the record
A searchable log of what was filed, when, by whom and with what receipt.
- Filter by period, type or reviewer
- Receipt stored per submission
- Retention shown per record
complead / log
- filed Q138
- accepted36
- pending2
- receiptsattached
Formats
Which formats are supported, and how they stay current
Regulator formats change. Complead maintains the templates and schema versions so your filings do not break when a format updates.
Full format list
goAML
Native XML for UN goAML jurisdictions
FinCEN
SAR and CTR formats for US filing
Local formats
Türkiye MASAK, UK and EU national templates
Versioning
Schema updates tracked, with change notes
Runs on Fusion
Filings close the loop that Fusion opened
A filing starts from a case, and a case starts from a Fusion score. The filed outcome feeds back as a confirmed label, so the engine learns which alerts led to real reports.
This product
Regulatory Filings
SAR, STR, threshold reports, submission log
Feeds into
Fusion engine
Confirmed outcomes, label feedback
You get
One loop
Alert to case to filing to learning
Integration
Create a filing over the API, get the receipt back
Generate a report from a case, validate it, and receive the submission receipt as an event.
// draft a filing from a case
POST /v1/filings "case_id": "8841", "type": "SAR", "format": "goAML"
201 Created · SAR-2026-0142 · draft
// get submission receipts as events
PUT /v1/filings/webhooks "events": ["filing.validated","filing.submitted","filing.accepted"], "url": "https://you.example/filing-events"
FAQ
Before you ask us
Which formats do you support?
goAML XML, FinCEN SAR and CTR, and local templates including Türkiye MASAK, with more added on request.
Do we still write the narrative?
You edit and own it. The draft is built from the case timeline so you start with the facts already in place.
What happens when a format changes?
The template and schema version are maintained for you, with change notes, so filings do not break silently.
Is there a record of what we filed?
Every submission is logged with its version, reviewer and receipt, retained per your policy.
Can we submit directly or only export?
Both, depending on the regime: direct submission where supported, export where the regulator requires it.
Where is our data stored?
You choose the region: EU, UK or Türkiye.
Testimonials
All case studies
What compliance teams say
Complead provides ultimate control via its case management and safelist systems. Automated API operations significantly reduced my team's manual workload.
Using the API we run AML controls automatically and stay compliant, while reducing our team's daily workload.
With Complead we offer fast, easy, secure onboarding. We focus on real risks, not false positives.