// Module 11 · Reporting

Regulatory Reporting Reporting.

STR and SAR preparation with goAML-aligned XML export for the Central Bank of Jordan

OPERATIONAL STR · SAR · SUPPORTED goAML · Aligned export
// Overview

Overview

Our Regulatory Reporting module streamlines compliance by automating the preparation of regulatory reports for supervisory authorities.

Structured report types for STR and SAR keep filings accurate and complete. Reports export as goAML-aligned XML for the Central Bank of Jordan's goAML portal, ready for review and submission by your compliance team.

Complete audit trails track every report from creation through export, with the full history retained for regulatory examinations.

// Features

Key Features

Comprehensive reporting capabilities for regulatory compliance

01

Report Templates

Structured report types for STR and SAR with a guided, sectioned editor

02

goAML-Aligned Export

Suspicious activity reports export as goAML-aligned XML for the Central Bank of Jordan (JO-CBJ), ready for portal upload by your team

03

Auto-Population

Automatic population of report fields from case data and customer information

04

Validation Rules

Built-in completeness checks verify required fields and data before a report can be exported

05

Audit Trail

Complete tracking of the report lifecycle from creation through review, approval, and export

06

Four-Eyes Approval

The analyst who drafts a report cannot submit it — maker-checker separation is enforced by the platform's permission model

// Benefits

Key Benefits

01
Faster Report Generation
Reduce report creation time with auto-population from case data and structured report types
02
Improved Accuracy
Built-in completeness checks help produce complete and accurate reports before export
03
Export-Ready Output
Reports export as goAML-aligned XML for Jordan's CBJ portal, eliminating manual re-keying
04
Complete Audit Trail
Full documentation of report history for regulatory examinations
05
Data Sovereignty
Reports are prepared and stored on your own infrastructure — nothing leaves the institution
06
Built for Jordan
Purpose-built for Jordan's goAML programme (Central Bank of Jordan), with goAML-aligned report structures
// Integrations

Integration Points

How Reporting connects with the systems around it — inbound case and customer data, goAML-aligned export files, the platform APIs, and the scheduled jobs that generate the work feeding your reports.

Inputs
  • Case management system
  • Alert management
  • Customer data
  • Transaction records
Outputs
  • goAML-aligned XML export
  • STR / SAR report files
  • Report archive
APIs
  • Reports export API
  • Case management API
  • Client data API
Scheduled Jobs
  • Scenario monitoring runs
  • Daily risk rescoring
  • Periodic rescreening
// KPIs

Performance Metrics

60%
Faster Reporting
Reduction in report generation time
80%
Auto-Populated Fields
Report fields drawn from case data
50%
Time Savings
Reduction in manual effort
100%
Actions Audited
Report actions captured in the audit trail
Illustrative targets
// Next step

Ready to streamline your regulatory reporting?

See how automated report preparation and goAML-aligned export can save your team time

Request a Demo
// FAQs

Frequently Asked Questions

Which regulatory formats are supported?

The platform prepares STR and SAR reports and exports them as goAML-aligned XML for the Central Bank of Jordan (JO-CBJ) — the jurisdiction the platform is built for.

How does the goAML export work?

Reports are generated as goAML-aligned XML and exported for your compliance team to review and upload to the goAML portal.

Can reports be edited after submission?

Reports are edited in draft, with every change captured in the audit trail. Formal amendment versioning of filed reports is on the product roadmap.

How long are reports retained?

Reports are stored in your own database — the platform deploys on-premises — so retention follows your institution's policy on your own infrastructure.

Can the analyst who drafted a report also submit it?

No. Four-eyes approval is enforced — the drafter of an STR/SAR cannot submit their own report; a second authorised reviewer must approve and submit it.

How are report fields populated?

Reports auto-populate from case data — client KYC details, in-window transactions, and the case narrative — and generation is blocked if required data is missing.

// Ready when you are

Ready to Transform Your AML Compliance?

Join leading financial institutions using AML SHIELD to combat financial crime