Reporting & Regulatory

File the report, not the paperwork.
SAR generation & regulatory XML exports.

Remitgo prepares a Suspicious Activity Report from an alert for your nominated officer to review and file, and exports regulatory submissions as schema-valid XML, so the effort goes into the decision rather than the paperwork.

SAR
Auto-generated
XML
Schema-valid
Scheduled
Submissions
Q4 2026
Availability

SAR generation

Promote a case to a Suspicious Activity Report pre-filled from the underlying transactions, customer data and alert evidence, so your nominated officer reviews and confirms rather than rekeys.

  • Pre-filled from case data
  • Restricted to nominated officers
  • Nominated-officer sign-off

Regulatory XML exports

Export submissions as schema-valid XML for goAML and other regulator formats, validated before they ever leave the platform.

  • goAML-compatible XML
  • Schema validation pre-export
  • Multiple regulator formats

Scheduled reporting

Configure recurring regulatory and management reports that build and deliver themselves on the cadence each regime requires.

  • Recurring report schedules
  • Per-regime cadence
  • Automatic generation

Submission tracking

Track each filing from draft to submitted to acknowledged, with status and reference numbers held against the originating case.

  • Draft / submitted / acknowledged states
  • Regulator reference capture
  • Filing hidden from the general case view

Data lineage

Every figure in a report traces back to its source transactions and the AML or SmartSanction events that triggered it.

  • Source-transaction traceability
  • AML & SmartSanction event links
  • Reproducible figures

Audit-ready records

Filed reports are stored immutably with the data, versions and user actions behind them, ready to evidence to a supervisor.

  • Immutable filed-report store
  • User action log
  • Exportable evidence pack

API Reference

Integrate in minutes.

Preview of the planned interface - this API is in development and not yet publicly available.

POST/api/v1/reporting/sar/generatePLANNED

Request

{
  "case_id": "case_3391",
  "customer_id": "cust_001",
  "reason_code": "STR",
  "reason_note": "Repeated deposits just under the reporting threshold",
  "transactions": ["txn_8a21f0", "txn_8a2204"],
  "format": "goaml_xml"
}

Response

{
  "report_id": "sar_0099",
  "case_id": "case_3391",
  "status": "draft",
  "visibility": "restricted",
  "visible_to_roles": ["MLRO", "deputy_MLRO"],
  "format": "goaml_xml",
  "schema_valid": true,
  "validation_errors": [],
  "created_at": "2026-07-01T14:29:52Z",
  "submitted_at": null,
  "acknowledged_at": null,
  "download_url": "/api/v1/reporting/sar/sar_0099/export",
  "api_version": "v1"
}

When schema_valid is false, validation_errors carries one entry per problem - { path, code, message } - naming the element that failed and why. It is an empty array on success, never a placeholder entry.

From alert to filing in minutes.

Remitgo launches Q4 2026. Talk to our team about the SAR formats and regulatory schemas your jurisdictions require.