Check goAML reports before you upload them.
goAML Reporter produces goAML XML for the Financial Reporting Centre from a CSV of your transactions, and checks it for common causes of rejection. It covers 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 transaction list to goAML XML in four steps.
Import
Load transactions from a CSV export from your system, or type them in.
Map
Each transaction is mapped to the right goAML structure: my-client vs. external party, person vs. entity vs. account.
Validate
Check for common causes of rejection before upload, with every issue pointing to a row and field.
Download
Generate the XML and download it, ready for you to upload through the FRC's goAML portal.
All four report types, one pipeline.
Cash Transaction Report
Cash transactions at or above the threshold, built from your transaction list.
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 the free validator does
- All four goAML report types: CTR, STR, SAR and STAR
- CSV import with a downloadable template
- Checks that point to the exact row and field
- Runs in your browser, so nothing is uploaded
Built for how Kenyan institutions work
- Kenyan ID length and +254 phone formats checked
- M-Pesa, PesaLink, RTGS, EFT and cash channels modelled correctly
- Cash for the day added up against the CTR threshold
- A first check, not the FRC's official validation: always upload through the goAML portal
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.
Send an anonymised export and we will show you the goAML XML the validator produces, with every issue flagged. If you want it connected to your own systems and approval steps, tell us what you need and we will say plainly what exists today.