File German Suspicious Activity Report (Verdachtsmeldung — goAML XML)

Q: What does the File German Suspicious Activity Report (Verdachtsmeldung — goAML XML) skill do?

Wandeln Sie einen Verdachtsfall in eine Verdachtsmeldung (Suspicious Transaction Report, STR) als goAML-XML für die deutsche FIU (Zentralstelle für Finanztransaktionsuntersuchungen) über das goAML-Portal um — meldende Stelle (rentity_id) und Geldwäschebeauftragter, Transaktionen mit Beträgen in Euro, beteiligte Personen (Geburtsdatum, Staatsangehörigkeit, Ausweis), Konten (IBAN/BIC), Verdachtsindikatoren und Sachverhalt, Ausführungsverbot und unverzügliche Meldung nach § 43 GwG, mit Beispiel

Q: How do I run the File German Suspicious Activity Report (Verdachtsmeldung — goAML XML) skill?

Copy the skill and paste it into your own Claude or ChatGPT, then provide your source data. FinchContext skills run inside your own AI assistant, so your financial data never leaves your control.

Q: Which region does the File German Suspicious Activity Report (Verdachtsmeldung — goAML XML) skill cover?

Germany. It targets the local tax authority / e-invoicing format described on this page.

Skill: Convert a suspicious-activity case into a goAML STR XML

Region: Germany (Deutschland) Category: AML Does: Takes a suspicious-activity case and assembles the Verdachtsmeldung (Suspicious Transaction Report, STR) as the goAML XML report for electronic filing to the German FIU (Zentralstelle für Finanztransaktionsuntersuchungen) via the goAML web portal / Web-Service. Spec: FIU Germany / goAML (UNODC) — STR XML schema (current goAML schema version)

Under the Geldwäschegesetz (GwG), obliged entities (Verpflichtete: banks, insurers, real-estate agents, etc.) must report facts indicating money laundering or terrorist financing without delay. Germany uses the UNODC goAML system; reports are filed as goAML XML (STR / Verdachtsmeldung). Filed per case on suspicion. Element names below follow the goAML form, not a verbatim XSD.

When this applies

An obliged entity under § 2 GwG identifies facts indicating money laundering, terrorist financing, or that assets stem from a predicate offence, and must file a Verdachtsmeldung (§ 43 GwG) to the FIU without delay.
Covers transaction-based reports (with transactions) and activity reports (without a completed transaction); a transaction subject to the report generally must not be executed before the FIU/prosecutor releases it within the statutory waiting period.
Use also for additional-information (Zusatzmeldung) and corrected reports, using the appropriate goAML report type.

Structure (FORM → XML)

report                rentity_id (reporting entity), report code (STR),
                      submission_date, reporting person, reason for suspicion
transaction (per transaction)
   transactionnumber, date, amount_local (EUR), transmode
   t_from / t_to       account or person/entity, funds type, country
involved parties
   account             institution, IBAN/account no., signatory
   person              name, DOB, nationality, ID document, address
   entity              legal name, registration no., address
goods_services        where relevant (e.g. real estate)
report_indicators     suspicion indicators / typologies
reason                free-text narrative of the suspicion and grounds
attachments           supporting documents

Data rules

Identify the reporting entity by its goAML rentity_id and the responsible reporting person; choose the correct report type (STR vs. activity/additional-information).
Parties must be fully identified: persons by name, date of birth, nationality, and ID document; entities by legal name and registration number (Handelsregister); accounts by IBAN/BIC.
Amounts in EUR (amount_local) to two decimals; for foreign currency record original amount and the EUR equivalent; dates in the schema format.
Provide a clear reason/narrative linking facts to the suspicion plus relevant indicators/typologies; attach supporting evidence.
Respect the execution-stop rule: where a transaction is reported, do not execute it before release/expiry of the statutory period; file without delay (unverzüglich).

Worked example (outline)

report: rentity_id 100245, code STR, submission 2026-06-04
reporting person: Geldwäschebeauftragter, Beispiel Bank AG
transaction: number TX-778812, date 2026-06-02, amount_local 48,500.00 EUR
   t_from: account IBAN DE89370400440532013000 (customer Mustermann)
   t_to:   account abroad, country CY, funds wire transfer
person: Max Mustermann, DOB 1984-03-11, nationality DE, ID Personalausweis L01X...
indicators: structuring / unusual cross-border flow inconsistent with profile
reason: rapid pass-through of unexplained funds; narrative attached

Emitted as goAML STR XML and submitted via the goAML portal to the FIU; the reported transaction is held pending release within the statutory period.

Validation checklist

Reporting entity rentity_id and responsible person set; correct report type (STR)
Persons identified (name, DOB, nationality, ID); entities by registration no.; accounts by IBAN/BIC
Transactions with date, amount_local in EUR, funds type, from/to, countries
Suspicion indicators/typologies and a clear narrative reason provided
Supporting documents attached; schema-valid goAML XML
Execution-stop observed for reported transactions; filed without delay
Submitted via the goAML portal/Web-Service to the German FIU

Last updated: 2026-06-04 — confirm the current schema/version, identifiers, rounding, and deadline against current authority (fiu.bund.de / goAML, relevant authority) guidance before use.