goAML reports that pass on the first upload.
goAML Reporter turns your core-banking transactions into validated goAML XML for the Financial Reporting Centre, across all four report types: CTR, STR, SAR and STAR.
The demo runs entirely in your browser. No data leaves your machine.
<?xml version="1.0" encoding="UTF-8"?> <report> <rentity_id>1234</rentity_id> <report_code>STR</report_code> <currency_code_local>KES</currency_code_local> <transaction> <transactionnumber>TXN-88213</transactionnumber> <amount_local>980000.00</amount_local> <!-- t_from_my_client · t_to … --> </transaction> </report>
goAML is a compliance obligation. It shouldn't be a data-entry job.
Under POCAMLA, every reporting institution in Kenya files reports to the FRC through goAML. In most institutions that still means copying data from the core banking system into a web form or a hand-edited XML file, and hoping it validates.
Rejected uploads
One wrong party structure, a missing ID, or a date in the wrong format and the whole report bounces. Each retry eats into your reporting window.
Hours per report
A single STR with a dozen transactions can take a morning to key in. Your MLRO ends up doing data entry, not investigation.
No audit trail
When the regulator or internal audit asks what was filed, when, and from which source data, the answer lives in someone's Downloads folder.
From flagged transactions to FRC-ready XML in four steps.
Connect
Pull customers, accounts and transactions from your core banking system, monitoring alerts, or a CSV export.
Map
Each transaction is mapped to the right goAML structure: my-client vs. external party, person vs. entity vs. account.
Validate
Check against goAML rules and common FRC rejection causes before upload, with every issue pointing to a row and field.
File
Generate the XML, upload it, and keep a versioned record of what was filed, by whom, and from which data.
All four report types, one pipeline.
Cash Transaction Report
Cash transactions at or above the USD 15,000 threshold, batched and filed without re-keying.
Suspicious Transaction Report
Flagged transactions with both sides of every transfer mapped: your client, the counterparty, the channel.
Suspicious Activity Report
Activity-based reports built around the people and entities involved, with significance and reasons.
Suspicious Transaction & Activity Report
Combined reports for cases that need both the transactions and the wider activity behind them.
What you get
- All four goAML report types: CTR, STR, SAR and STAR
- Configurable lookup tables (channels, funds types, indicators) matched to your FRC version
- Maker–checker review before any report is generated
- Runs on your infrastructure: on-premise or in your own cloud tenancy
Built for how Kenyan institutions work
- Kenyan ID, passport, KRA PIN and +254 phone formats handled out of the box
- M-Pesa, PesaLink, RTGS, EFT and cash channels modelled correctly
- Core-agnostic: reads from database views, APIs or CSV exports, so it sits alongside whatever core you already run
- Implemented by engineers who have shipped goAML reporting in a licensed Kenyan institution
Built for every FRC reporting institution.
- Commercial banks
- Microfinance banks
- Deposit-taking SACCOs
- Money remittance providers
- Payment service providers
- Forex bureaus
- Digital credit providers
- Mortgage finance institutions
See it with your own data.
We'll take an anonymised export from your system and show you the goAML XML it produces, with every validation issue flagged. Thirty minutes, no commitment.