goAML Reporting Platform
Automate CTR and STR reporting with schema-valid goAML XML generation, pre-submission validation, and regulator-ready audit trails — built for reporting entities across East Africa.
<?xml version="1.0"?> <report> <rentity_id>7042</rentity_id> <report_code>STR</report_code> <submission_date>2026-04-21</submission_date> <transaction> <amount_local>1245000.00</amount_local> <currency>KES</currency> </transaction> </report>
From raw transaction data to a filed report — in four stages.
Connect your core banking, transaction, and customer data sources via secure integration.
Data is mapped to goAML fields and enriched with the entities, accounts, and parties each report needs.
Every report is validated against the live goAML XSD — errors are surfaced with deep links to the field.
Submit to your FIU and keep a tamper-evident audit trail of who filed what, when.
Everything an MLRO needs to file with confidence.
CTR and STR XML produced automatically, conformant to your regulator’s current goAML XSD version.
Catch every schema and business-rule error before the report leaves your building.
Immutable record of every report, amendment, and filing — exportable for examinations.
Cash transaction reports are detected and assembled automatically against jurisdiction thresholds.
Compile suspicious transaction reports with the parties, accounts, and narrative in one place.
Deployed in your own Azure tenancy — your data never shares an instance with anyone else.
Every report type your FIU expects.
Generate and validate the full range of goAML report types from a single platform, each mapped to your regulator's current schema version.
Frequently asked
Does the platform support our regulator’s schema version?
Yes. Each deployment is configured to your FIU’s current goAML XSD, and we maintain it as schema versions change so your reports stay valid.
How is our data isolated?
Every customer runs single-tenant in their own Azure instance. Your transaction and customer data is never co-mingled with another reporting entity.
How long does deployment take?
Typically six to eight weeks from kickoff to your first live submission, depending on the number and complexity of data source integrations.
Can it integrate with our core banking system?
Yes. We connect to core banking, transaction, and customer data sources via secure integration, and map them to the goAML data model.
See goAML reporting on your own data.
Book a demo and we'll walk through a live CTR and STR submission, end to end.
More on goAML Reporting
AML Risk Scoring Engines: How Automated STR Recommendations Work
How AML risk scoring engines reduce false positives from 85% to under 50%, automate STR recommendations, and help compliance officers focus on real threats.
How to Automate AML Reporting in East Africa: A Practical Guide
Learn how East African banks can automate AML reporting, reduce CTR/STR errors, and cut 87+ hours of manual work per month. A practical implementation guide.
goAML XSD v5 XML Generation: The Complete Technical Guide
Complete technical guide to goAML XSD v5.0.2 XML generation — schema structure, mandatory fields, encoding pitfalls, country extensions, and validation pipelines.
Microservices Architecture for AML Platforms: Why It Matters for Banks
Discover how microservices architecture solves the scalability, resilience, and update challenges that cripple monolithic AML systems in East African banks.
goAML Submission Rejected? How to Diagnose and Fix Common Errors
Your goAML XML was rejected by Kenya FRC or another FIU. Here's how to read rejection notices, identify root causes, and fix errors to resubmit successfully.
goAML XML Schema v5.0.2: CTR and STR Mandatory Fields Reference
Complete reference for goAML XSD v5.0.2 mandatory fields for CTR and STR submissions — field names, data types, Kenya localization rules, and validation requirements.