goAML and Regulatory Filings

Configure the positive numeric reporting entity ID registered in the destination goAML portal. This is not the organization name, the portal username, or the reporting officer’s name. A structurally valid XML file can still be rejected if that ID does not belong to the submitting account.

Admin and Risk Lead users can save or change the organization’s reporting entity ID and officer first name, last name, and phone number through settings or the export workflow. Saved details are reused for future exports.

For paired worksheets, explicitly select whether the sender or receiver is the reporting customer. Imported identity and contact data remain associated with their respective parties. Supplied filing metadata is prefilled; complete only missing or invalid information.

Readiness checks can require complete bank account and phone details even when a transaction was valid for monitoring. Monitoring acceptance and filing readiness are different checks.

Corporate STR and CTR XML can represent a company owner and authorized signatories. The reporting customer side must be identified. Corporate client accounts require company details, reportable account and client numbers, institution code, account type and status codes, account opening date, post-transaction balance, and complete authorized signatories.

Signatories require their own name, date of birth, contact and identification details, occupation, source of wealth, nationality, residence, and identification issuing country. Do not infer these from company or transaction descriptions. Corporate PEP export remains unsupported.

XML generation is not certification or regulator acceptance. Validate with the current destination schema and portal requirements before submission.

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.

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.

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.

Most filing work happens through the WatchTower console. The API areas below cover report export and the filing register.