Skip to content

AML and Regulatory Reporting

Documentation status

Last verified: 26 Sep 2026. Readiness uses the single rubric and status vocabulary.

PARTIAL offline support for goAML-style CTR and STR XML generation. This is not a complete regulatory filing product.

Purpose

Help compliance programmes produce goAML-shaped Currency Transaction Report (CTR) and Suspicious Transaction Report (STR) XML from structured inputs — for human review and manual filing processes outside MasteryHive.

Users

Audience Role
Compliance / AML officers Review generated XML before any filing
MasteryHive / partner engineers Run the offline generation library when programme scope includes it
Product / risk stakeholders Understand what is automated vs what remains human

Business problem

FIUs such as Nigeria’s NFIU expect goAML XML for certain report types. Teams need a generation aid that does not pretend to replace compliance review or national submission systems.

Capabilities

Capability Status
CTR XML generation from structured JSON PARTIAL (offline library)
STR XML generation from structured JSON PARTIAL (offline library; requires reason / action)
FTR (Funds Transfer Report) Not in code
Excel → JSON helper PARTIAL — helper output often needs manual correction before XML succeeds
XSD validation against official schema PARTIAL — helper exists; schema file not shipped; not part of a productised path
HTTP product API for generation Not present
Submission to NFIU (or any FIU portal) Not in code

End-to-end workflow (generation only)

flowchart LR
  data[Structured_report_data]
  validate[Validate_model]
  xml[Generate_XML]
  review[Human_review]
  file[External_filing]
  data --> validate --> xml --> review --> file
  1. Prepare a complete report document (CTR or STR) with institution registration fields.
  2. Validate against the library’s report model.
  3. Generate XML to local output.
  4. Human review — compliance owns correctness of subjects, amounts, reasons, and registration data.
  5. Filing — if required, submit through the institution’s approved NFIU / FIU process. MasteryHive does not perform this step.

Inputs

Input Notes
Report JSON Must include reporting entity / person and CTR or STR fields
Optional spreadsheet Can seed JSON via helper; often needs post-processing

Outputs

Output Notes
goAML-shaped XML file For offline use
No filing receipt There is no submission client

Integrations

System Relationship
KYC / KYB product Library lives alongside KYC; not wired as an HTTP route on the KYC API
Fraud Detection May emit escalation labels such as SAR review on investigator reports — not goAML generation or filing
NFIU / FIU portals Outside MasteryHive — institution-owned

Boundary: generating XML vs submitting to NFIU

Generate XML Submit to NFIU
Offline library can produce CTR/STR-shaped XML Not implemented
Operator / engineer runs generation Institution uses its approved filing channel
Defects in helpers may require manual JSON fixes No MasteryHive credentials, portal client, or filing workflow

Any statement that the platform “files goAML reports with NFIU” is not supported by product evidence.

Review responsibilities

Responsibility Owner
Correctness of transaction rows and subjects Institution / compliance
goAML registration identifiers Institution
Choosing CTR vs STR and narrative reason/action Compliance
Running or requesting XML generation Programme-agreed engineering / ops
Filing and acknowledgement with NFIU Institution — not MasteryHive automation

Readiness

Rated with the single readiness rubric. Reasons for each rating are on that page.

Gate Rating
Code NOT MET (an offline XML library exists; no route and no submission path)
Integration Verified NOT MET
Ops Ready NOT MET
Security Approved NOT MET
GA NOT MET

See Product readiness summary.

Limitations

  • FTR is not implemented.
  • Excel helper chain has known defects (missing fields, timestamp formats, organisation mapping). Treat outputs as draft until validated.
  • Fraud sar_review / investigator_review labels are not regulatory reports.
  • No durable regulatory-report case desk is claimed in the AI products.