goAML and Regulatory Filings
How WatchTower helps teams prepare goAML XML exports, capture missing filing metadata, and preserve filing history.
Pre-export checks
Identify missing goAML fields before XML generation and collect only the missing metadata.
Versioned filing history
Preserve each generated report with its reference, report type, officer, status, and download path.
Evidence-safe editing
Let users add filing metadata without changing the source transaction or case evidence.
What this workflow does
WatchTower can generate goAML XML from a case and preserve the filing event so the team can return to the exact report version later.
The workflow is designed for report preparation and internal filing operations. It does not submit directly to a regulator portal; the institution remains responsible for external submission and acceptance tracking.
The filing workflow supports
- readiness checks before XML generation
- missing metadata capture without changing the original transaction evidence
- additional filing context entered by the reporting officer
- reporting officer details needed by the XML
- XML generation and download
- filing register entries with version history and status tracking
WatchTower prepares and records the regulatory XML workflow. It should be described as goAML XML generation and filing management, not direct NFIU or regulator submission.
Missing metadata handling
Some source systems do not send all regulatory metadata needed for a complete XML export. WatchTower checks the case data before export and prompts the user for only the missing filing metadata.
Core transaction facts, such as amount, direction, customer reference, case evidence, and source transaction details, should remain locked because they come from the underlying transaction record.
Examples of user-supplied metadata
- customer date of birth
- customer phone number
- customer ID type and ID number
- ID issue or enrolment date where required
- occupation and source of wealth
- reporting officer phone number
- additional filing context
Filing register
Each generated report should be traceable after export. The regulatory filings register gives compliance teams a place to review generated reports, download XML versions, see who generated them, and track submission status after external validation or portal submission.
Register data can include
- filing reference
- report type such as STR or CTR
- case link
- generated version
- reporting officer
- generated timestamp
- status such as generated, submitted, accepted, or rejected
Useful API areas
Most filing work is operator-led through the WatchTower console. API documentation should cover only customer-facing report export and filing-register operations, while internal provider or admin controls remain private.