Annexure 2 Standard XML Reporting - Zoll

© FIU Deutschland Last Update: 22-Jan-2018

Annexure 2

Standard XML Reporting -

Instructions and Specifications

- Draft -

© FIU Deutschland Last Update: 22-Jan-2018

Table of Contents

1. Summary ...................................................................................................................................................... 1

2. Conventions used in this document ....................................................................................................... 2

3. Description of XML Nodes ........................................................................................................................ 2

3.1 Node “report” ......................................................................................................................... 2 3.2 Subnode report_indicators ..................................................................................................... 5 3.3 Node transaction ..................................................................................................................... 6 3.4 Node Activity (New in Schema 4.0) ......................................................................................... 9 3.5 Node t_from_my_client ........................................................................................................ 10 3.6 Node t_from .......................................................................................................................... 11 3.7 Node t_to_my_client ............................................................................................................ 13 3.8 Node t_to .............................................................................................................................. 14 3.9 Subnode goods_services ....................................................................................................... 15

4. Description of Common Types Used in the Schema .......................................................................... 17

4.1 Type t_account_my_client .................................................................................................... 17 4.2 Type t_account ...................................................................................................................... 20 4.3 Type t_entity_my_client ....................................................................................................... 22 4.4 Type t_entity ......................................................................................................................... 25 4.5 Type t_person_my_client ..................................................................................................... 26 4.6 Type t_person ....................................................................................................................... 30 4.7 Type t_party .......................................................................................................................... 33 4.8 Type t_address ...................................................................................................................... 35 4.9 Type t_phone ........................................................................................................................ 36 4.10 Type t_foreign_currency ....................................................................................................... 37 4.11 Type t_person_identification ................................................................................................ 38 4.12 Type report_party_type ........................................................................................................ 39

5. Lookup Values........................................................................................................................................... 40

5.1 submission_type ................................................................................................................... 40 5.2 funds_type ............................................................................................................................ 40 5.3 account_type......................................................................................................................... 41 5.4 account_status_type ............................................................................................................. 42 5.5 identifier_type ....................................................................................................................... 42 5.6 conduction_type ................................................................................................................... 42 5.7 trans_item_status ................................................................................................................. 43 5.8 contact_type ......................................................................................................................... 43 5.9 communication_type ............................................................................................................ 44 5.10 legal_form_type .................................................................................................................... 44 5.11 trans_item_type .................................................................................................................... 45 5.12 currency_type ....................................................................................................................... 45 5.13 country_type ......................................................................................................................... 50 5.14 gender_type .......................................................................................................................... 55 5.15 account_person_role_type ................................................................................................... 56 5.16 entity_person_role_type ...................................................................................................... 56 5.17 party_role_type..................................................................................................................... 56 5.18 report_indicator_type ........................................................................................................... 57 5.19 report_type ........................................................................................................................... 59 5.20 rentity_type ........................................................................................................................... 59

© FIU Deutschland Page 1

1. Summary

The purpose of this specifications document is to provide both the reporting entities and reporting persons with the requirements and conditions for creating compatible XML files using the provided XML-Schema for the different supported report types. A report file contains the following information which can be represented in the goAML Client after uploading and verifying the XML file.

Basic information about the report.

Where does the money come from.

Who conducted the transaction.

Where does the money go to.

Was the transaction related to a property transfer

Who reported the transaction(s) (Optional)

What was the reason for the report and which actions have been taken (Optional)

In multi-party transactions, list of all involved parties and their respective roles in the transactions.

An XML report is linked to one Reporting Entity but may contain multiple transactions. An uploaded report can be from ONE report type. This document will provide a reference to the schema, nodes and types as well as the lookup tables for enumeration values. (e.g. Country Codes)


2. Conventions used in this document

The following conventions are used in this document:

Required field Required, 1 to N values

Optional field

Optional sub node Required sub node

Optional, but one of the two nodes should be provided

Integer A 32 bit value

Date time A date and time value in the following format: YYYY-MM-DDTHH:MM:SS

Sequence to sub nodes

3. Description of XML Nodes

3.1 Node “report”

Basic information about Reporting Entity, reporting date and type of report. It can contain multiple transactions.


Figure 1: Overview node “report”


Name Description Type Req.

rentity_id Reporting Entity number defined by FIU

Integer >= 1

Y

rentity_branch Branch of current reporting entity.

255 N

submission_code Type of submission submission_type Y

report_code Type of transaction (STR/CTR)

report_type Y

entity_reference Reference to the report, used by reporting entity

255 Y

fiu_ref_number Optional ref. number to be used as communication channel between the FIU and the Reporting Entity

255 N

submission_date Submission date and time Datetime Y

currency_code_local Local Currency code

currency_type Y

reporting_person Full details of the report’s reporting person

t_person N

location Address reporting Entity / Person (Repurpose of field)

t_address N

reason Facts of the Case (Repurpose of field)

4000 N

action Special Note for the FIU (Repurpose of field)

4000 N

As of schema 4.0, Report could contain either a list of transactions as it was always or a list of involved subjects without the need of a transaction to link them.

transaction Transaction information type transaction Y

Activity Involved subjects and items list linked directly to report.

Y

report_indicators List of indicators for the current reports

indicator 0..many

Table 1: Details node “report”


3.2 Subnode report_indicators

Figure 2: Overview subnode report_indicators


indicator Some classification for the report

25 Y

Table 2: Details subnode report_indicators


3.3 Node transaction

Figure 3: Overview node transaction



transactionnumber Unique transaction number for bank transaction

50 Y

Internal_ref_number Reporting Entity internal transaction reference number

50 N

transaction_location Location 255 N

transaction_description

Designated Use (Repurpose of field)

4000 N

date_transaction Date and time of the transaction

DateTime Y

teller Not in use 20 N

authorized Not in use 20 N

late_deposit and date_posting are both optional but when setting date_posting, late_deposit becomes mandatory. 3 possible combinations 1. none of the nodes is set 2. only late_deposit is set 3. late_deposit AND date_posting are set

late_deposit Announced Transaction (Repurpose of field)

Boolean Y/N

date_posting Announced Transaction Date (Repurpose of field)

DateTime N

value_date DateTime N

transmode_code How the transaction was conducted

conduction_type Y

transmode_comment Not in use 50 N

amount_local The value of the transaction in local currency

Decimal Y

Transaction could be either a bi-party transaction with clear From and To sides, or a multi-party transaction with unlimited list of subjects (Persons, Accounts and Entities) where each has a role in the transaction rather than a clear from or to side.

Bi-Party Transaction

One of the nodes t_from_my_client or t_from should be provided. Both CANNOT be present together in a transaction, but one of them should be present.

t_from_my_client Specifies where the money came from. If the source is reporting bank’s client, then this node should be provided

Subnode

Y (one of them)

t_from Specifies where the money came from

Subnode

One of the nodes t_to_my_client or t_to should be provided. Both CANNOT be present together in a transaction, but one of them should be present.

t_to_my_client Specifies where the money went. If the destination is reporting bank’s client, then this node should be provided

Subnode Y

(one of them)


t_to Specifies where the money went.

Subnode

Multi-Party Transaction

This is a new node in schema 3.0. It covers transactions with multi-party involvement covering non-banking transactions. Car dealers for example can report such transactions where more than one subject bought/sold a car, while the car dealer is not reported as part of the transaction but only as the reporting entity. If the transaction is reported in this way, then at least one “Party” node should be reported.

party Describes the involved party details

t_party Y

goods_services Goods (Repurpose of field)

subnode N

comments Generic comments field 4000 N

Table 3: Details node transaction


3.4 Node Activity (New in Schema 4.0)

A new feature of schema 4.0. Reports can now include an activity node to represent an event where a list of subjects and goods are related directly to the report without the need of a transaction.

Figure 4: Overview node activity


report_parties Represents a collection of involved subjects an involved subject with its details

Y

report_party Represents a single involved subject with its details. At least one party should be included.

report_party_type Y

goods_service Goods (Repurpose of field)

t_trans_item N

Table 4: Details node transaction


3.5 Node t_from_my_client

This node should be provided if the source side of the transaction is a client of the reporting bank. As on schema 4.0, entity could be a direct party in bi-party transactions

Figure 5: Overview node t_from_my_client


from_funds_code Type of funds used in initiating transaction

funds_type Y

from_funds_comment Not in use 255 N

from_foreign_currency

If the transaction is conducted in foreign currency, then specify the foreign currency details.

t_foreign_currency N

t_conductor The person performing the transaction.

t_person_my_client N

from_account Subnode that holds account information

t_account_my_client

Y (one of them)

from_person Subnode that holds “from person” information.

t_person_my_client

from_entity Subnode that holds “from enUOtity” information.

t_entity_my_client

from_country Country where transaction was initiated.

country_type Y

Table 5: Details node t_from_my_client


3.6 Node t_from

Source of the transaction. Can be either a person, an account or an entity. In case of a person source, as per Schema 3.0, the conductor could be different from the source person. As per schema 4.0, the entity could be a direct party in bi-party transactions

Figure 6: Overview node t_from

Note: Bi-directional transactions are composed of a source and destination. The source and destination may be either a person, an account or an entity (As per schema 4.0). For account deposits, the source is a person and the destination is an account i.e. on t_from side we will have from_person and on the t_to side we will have t_to_account. For account withdrawals, we will have from_account at the t_from side and to_person at the t_to side. For money remittances, we will have person to person transactions i.e. from_person at the t_from side and to_person at the t_to side. The same structure of person to person transactions can be used for any money service type of transaction. For account transfers, we will have account to account transactions i.e., from_account at the t_from side and to_account at the t_to side.



from_funds_code Type of funds used in initiating transaction

funds_type Y

from_funds_comment Not in use 255 N

from_foreign_currency



t_conductor The person performing the transaction.

t_person N

from_account Subnode that holds account information

t_account

Y (one of them)

from_person Subnode that holds “from person” information.

t_person

from_entity Subnode that holds “from entity” information.

t_entity

from_country Country where transaction was initiated.

country_type

Table 6: Details node t_from


3.7 Node t_to_my_client

This node should be provided if the destination side of the transaction is a client of the reporting bank.

Figure 7: Overview node t_to_my_client


to_funds_code Disposition of funds funds_type Y

to_funds_comment Not in use 255 N

to_foreign_currency If the transaction is conducted in foreign currency, then specify the foreign currency details.

t_foreign_currency

N

to_account Subnode that holds account information

t_account_my_client

Y (one of them)

to_person Subnode that holds person information

t_person_my_client

to_entity Subnode that holds “to entity” information.

t_entity_my_client

to_country Target country of the transaction

country_type Y

Table 7: Details node t_to_my_client


3.8 Node t_to

Information about the transaction disposition(s) - i.e. where the money went. t_to can either point to a person or to an account.

Figure 8: Overview node t_to


to_funds_code Disposition of funds funds_type Y

to_funds_comment Description, if funds_code is “O” (Other) or policy number.

255 N

to_foreign_currency If the transaction is conducted in foreign currency, then specify the foreign currency details.

t_foreign_currency

N

to_account Subnode that holds account information

t_account

Y (one

of them)

to_person Subnode that holds person information

t_person

to_entity Subnode that holds “to entity” information.

t_entity

to_country Target country of the transaction

country_type Y

Table 8: Details node t_to


3.9 Subnode goods_services

Figure 9: Overview subnode goods_services



item_type Lookup code describes the item type

trans_item_type Y

item_make Item Maker 255 N

description Text 4000 N

previously_registered_to Name of previous owner

500 N

presently_registered_to Name of current owner

500 N

estimated_value Estimated value of the property – Used Currency is the one specified in node from_currency

Decimal N

status_code Account status when transaction was initiated

trans_item_status N

status_comments Comments 500 N

disposed_value effective value for property transfer – Used Currency is the one specified in node from_currency

Decimal N

currency_code used to report service conducted in foreign currency

currency_type N

size Size of the property – in unit specified in node size_uom

Decimal N

size_uom Unit of measurement (Repurpose of Field)

250 N

address Address of the property

t_address N

registration_date Official registration date

DateTime N

registration_number Official registration number

500 N

Identification_number Any number that can identify the item

255 N

comments

Additional comments 4000 N

Table 9: Details subnode goods_services


4. Description of Common Types Used in the Schema

4.1 Type t_account_my_client

The structure of this type is similar to that of type t_account, with some added restrictions i.e. some nodes which are not mandatory in t_account may be mandatory in t_account_my_client. These restrictions are defined by the local FIU. The logic here is that whenever the involved account or person is the client of the reporting entity, more details may be demanded on the client, and the reporting entity must have the information as part of the adherence to the “Know Your Customer” (KYC) philosophy of compliance.

Figure 10: Overview type t_account_my_client



institution_name The name of the Bank 255 N

institution_code Institution code

50 Y (one

of them)

swift SWIFT code according to ISO 9362

11

non_banking_institution

A flag to cover cases where the account belongs to non-banking institution

Boolean N

branch Branch code or name 255 Y

account IBAN or account number; If SEPA-Account use IBAN, otherwise use account number

50 Y

currency_code Currency the account is kept in

currency_type Y

account_name This is a free text field used to “Label” the account, for example a saving book account with anonymous owner, or an Entity account dedicated to Invoices, etc.

255 Y

iban Not in use 34 N

client_number Not in use 30 Y

personal_account_type

Account Type account_type Y

t_entity Business entity owning the account

t_entity N

signatory Person(s) with access to the account.

Subnode (can repeated to

specify multiple signatories).

Note that the node t_person

is of type t_person_my_cl

ient

Y

is_primary Identifies the primary account holder. Only one signatory may be marked as is_primary. Has to be ‘true’ when node is set.

Boolean (fixed = 1)

N

t_person Subnode holding detailed information about the signatory. Mandatory for signatories in the XML report.

t_person_my_client

Y

role Subnode holding enumeration about the role of current signatory with the account report.

account_person_role_type

N

opened Date account opened DateTime Y

closed Date account closed DateTime N


balance The account balance after the transaction was conducted.

Decimal Y

date_balance A date to specify the date of the reported balance. Application will show balance history

DateTime N


account_status_type

Y

beneficiary Not in use 50 Y

beneficiary_comment

Not in use 255 N

comments Generic comments elements

4000 N

Table 10: Details type t_account_my_client


4.2 Type t_account

Figure 4: Overview type t_account



instituation_name The name of the Bank 255 N

institution_code Institution code issued by FIU

50 Y

(one of them)

swift SWIFT code according to ISO 9362

11

non_banking_institution

A flag to cover cases where the account belongs to non-banking institution

Boolean N

branch Branch code or name 255 N

account IBAN or account number; If SEPA-Account use IBAN, otherwise use account number

50 Y

currency_code Currency the account is kept in

currency_type N

account_name

This is a free text field used to “Label” the account; for example a saving book account with anonymous owner, or an Entity account dedicated to Invoices, etc.

255 N

iban Not in use 34 N

client_number Not in use 30 N

personal_account_type

Account Type account_type N

t_entity Business entity owning the account

type t_entity

N

signatory Person(s) with access to the account.

Subnode (can be repeated to

specify multiple signatories).

Note that the node t_person is of type t_person

N

is_primary Identifies the primary account holder. Only one signatory may be marked as is_primary. Has to be ‘true’ when node is set.

Boolean (fixed = 1)

N

t_person Subnode holding detailed information about the signatory. Mandatory for signatories in the XML report.

t_person Y

role Subnode holding enumeration about the

account_person_role_type

N


role of current signatory with the account report.

closed Date account closed DateTime N

balance The account balance after the transaction was conducted.

Decimal N

date_balance

A date field to specify the date of the reported balance. Application will show balance history

DateTime Y


account_status_type

N

beneficiary Not in use 50 N

beneficiary_comment

Not in use 255 N

comments

Generic comments elements

4000 N

Table 4: Details type t_account

4.3 Type t_entity_my_client

The structure of this type is similar to that of type t_entity, with some added restrictions i.e. some nodes which are not mandatory in t_entity may be mandatory in t_entity_my_client These restrictions are defined by the local FIU.


Figure 5: Overview type t_entity_my_client



name

Name of Entity 255

Y

commercial_name The “traded as” name of the entity

255 N

Incorporation_legal_form The legal form of the entity

legal_form_type N

fincorporation_number The registration number of the entity/"company" in the relevant authority (e.g. Chamber of Commerce)

50 Y

business Business area of the entity

255 Y

phones A Holder node for a 1..many Phones

Y

phone One occurrence of phone node

t_phone Y

addresses A Holder node for a 1..many Addresses

Y

address One occurrence of address node

t_address Y

email Email address email_address (255)

N

url Entity web address 255 N

incorporation_state Name of the State 255 Y

incorporation_country_code Incorporation Country country_type Y

director_id Individuals authorized t_person_my_client

(Subnode can be repeated for

multiple persons)

Y

incorporation_date Incorporation registration date

DateTime N

business_closed Boolean to indicate if the company is closed down

Boolean N

date_business_closed If entity is closed then specify close date if any.

DateTime N

tax_number USt-ID (Repurpose of field)

100 N

tax_registeration_number Corporate purpose (Repurpose of Field)

100 N

comments Generic comments field 4000 N Table 5: Details type t_entity_my_client


4.4 Type t_entity

Figure 6: Overview type t_entity



name Name of Entity 255 Y

commercial_name The “traded as” name of the entity

255 N

incorporation_legal_form The legal form of the entity

legal_form_type

N

incorporation_number the registration number of the entity/"company" in the relevant authority (e.g. Chamber of Commerce)

50 N

business Business area of the entity

255 N


N


t_phone N


N


t_address N


N

url Entity web address 255 N

incorporation_state Name of the State 255 N

incorporation_country_code

Incorporation Country country_type N

director_id Individuals authorized t_person

N

incorporation_date Incorporation registration date

Date N

business_closed Boolean to indicate if the company is closed down

Boolean N

date_business_closed If entity is closed then specify close date if available

Date N


100 N

tax_registeration_number Corporate purpose (Repurpose of Field)

100 N

comments Generic comments field 4000 N Table 6: Details type t_entity

4.5 Type t_person_my_client

The structure of this type is similar to that of type t_person, with some added restrictions i.e. some nodes which are not mandatory in t_person may be mandatory in t_person_my_client These restrictions are defined by the local FIU.


Figure 7: Overview type t_person_my_client



gender Gender gender_type Y

title Title 30 Y

first_name First name 100 Y

middle_name Middle name 100 N

prefix Not in use 100 N

last_name Last name 100 Y

Reporting entity should submit birthdates for persons who are their customers.

birthdate

Birth date DateTime Y

birth_place Place of birth

255 N

mothers_name Birth name 100 N

alias Alias Name, Known as, ..etc

100 N

ssn Marital status (Repurpose of field)

25 N

passport_number No. of passport 25 N

passport_country Passport issue country (Can be reported only when there is a passport number)

25 N

id_ number Not in use 25 N


Y


t_phone Y


Y


t_address Y

nationality1 Nationality (1) country_type Y

nationality2 Nationality (2) country_type N

nationality3 Country of Birth (Repurpose of field)

country_type N

residence Country of residence country_type Y


N

occupation Occupation 255 Y

employer_name Employer’s name 255 N

employer_address_id Employer’s address t_address N

employer_phone_id Employer’s phone t_phone N


identification Subnode(s) for identification documents

t_person_identification

(This subnode can be repeated

to specify multiple

identification documents)

Y

deceased A Boolean to indicated if person has passed away

Boolean N

deceased_date If deceased, then RE can report deceased date if known as well

DateTime N


100 N

tax_reg_number Tax Office (Repurpose of field)

100 N

source_of_wealth Free text description of the person source of wealth

255 N

comments Generic comments field

4000 N

Table 7: Details type t_person_my_client


4.6 Type t_person

Figure 8: Overview type t_person



gender Gender gender_type

N

title Title 30 N

first_name First name 100 Y

middle_name Middle name 100 N

prefix Prefix name 100 N

last_name Last name 100 Y

birthdate

Birth date DateTime N

birth_place Place of birth 255 N

mothers_name Birth name 100 N

alias Alias, Known As, ..etc 100 N

ssn Marital status (Repurpose of field)

25 N

passport_number No. of passport 25 N

passport_country Passport issue country (Can be reported only when there is a passport number)

25 N

id_ number Not in use 25 N


N


t_phone N


N


t_address

N

nationality1 Country of Nationality (1)

country_type

N

nationality2 Country of Nationality (2)

country_type

N

nationality3 Country of Birth (Repurpose of field)

country_type

N

residence Country of residence country_type

N

email Email address 255 N

occupation Occupation 255 N

employer_name Employer’s name 255 N

employer_address_id Employer’s address t_address N

employer_phone_id Employer’s phone t_phone N


identification Subnode(s) for identification documents

t_person_identification

(This subnode can be

repeated to specify

multiple identificatio

n documents)

N

deceased A Boolean to indicated if person has passed away

Boolean N

deceased_date If deceased, then RE can report deceased date if known as well

DateTime N


100 N

tax_reg_number Tax Office (Repurpose of field)

100 N

source_of_wealth Free text description of the person source of wealth

255 N

comments Generic comments field

4000 N

Table 8: Details type t_person


4.7 Type t_party

Figure 9: Overview type t_party



role

Subject role in the transaction

party_role_type Y

Subject: One occurrence of the supported subject types must be included.

person

Involved Person t_person Y

person_my_client

Involved Person t_person_my_client Y

account

Involved Account

t_account Y

account_my_client

Involved Account

t_ account_my_client Y

entity

Involved Entity

t_ entity Y

entity_my_client Involved Entity t_ entity_my_client Y

funds_code Type of funds used in initiating transaction

funds_code N

funds_comment Not in use 255 N

foreign_currency



country Country of the transaction

country_type Y

significance Not in use Integer N

comments Generic comments

4000 N

Table 9: Details type t_party


4.8 Type t_address

Figure 10: Overview type t_address


address_type The contact type of the address

contact_type Y

address

Street name and house number

100 Y

town Name of Town/district/.. as part of a City

255 N

city

City 255 Y

zip

Zip Code 10 N

country_code Country country_type Y

state

State 255 N

comments Generic comments 4000 N Table 10: Details type t_address


4.9 Type t_phone

Figure 11: Overview type t_phone


tph_contact_type The contact type of the Phone

contact_type

Y

tph_communication_type The communication type of the Phone

communication_type

Y

tph_country_prefix Country phone code

4 N

tph_number

Phone number 50 Y

tph_extension

Not in use 10 N

comments Generic comments

4000 N

Table 11: Details type t_phone


4.10 Type t_foreign_currency

Figure 12: Overview type t_foreign_currency


foreign_currency_code Currency Code according to ISO 4217

currency_type Y

foreign_amount Transaction amount in foreign currency

Decimal Y

foreign_exchange_rate Exchange rate which has been used for transaction

Decimal Y

Table 12: Details type t_foreign_currency


4.11 Type t_person_identification

Figure 20: Overview type t_person_identification


type Document type identifier_type Y

number ID of the identification document

255 Y

issue_date Identification document issue date

DateTime N

expiry_date Identification document expiry date

DateTime N

issued_by Name of Authority issued the document

255 N

issue_country Country where the document was issued

country_type Y

comments Generic comments field 4000 N Table 20: Type t_person_identification


4.12 Type report_party_type

New type in schema 4.0. Represents an involved subject in a report and its details. Subject can be a Person, an Account or an Entity – one of them can be included per involved party.

Figure 21: Overview type report_party_type


One of the following subject nodes must be included when activity node is used

person Represents an involved person node

t_person Y

account Represents an involved account

t_account Y

entity Represents an involved entity t_entity Y

significance Not in use Integer N

reason Not in use 4000 N

comments Generic comments element 4000 N Table 21: Type report_party_type


5. Lookup Values

As per schema 4.0, all schema lookups are defined as enumerations. goAML application will introduce an option to update the schema automatically with the lookup codes defined by the FIU in the “Lookup Master” screen. Reporting entities will not be able anymore to submit reports with undefined lookup codes. Most of the lookup enumerations mentioned below are defined by FIU Gerrmany.

5.1 submission_type

Value Description

- Not in use

E Electronically

M Not in use Table 13: submission type

5.2 funds_type

* The following list is specified by FIU Germany. Actual codes defined by FIU in “Lookup Master” will be added automatically to the Schema by goAML client application.

Value Description

1 Account

2 Deposit

3 Cash

4 Direct Debit

5 Payment Order

6 Crossed cheque

7 Cheque

8 Bank draft

9 Credit

10 Securities

11 Currency exchange

12 Traveler’s cheque

13 Cash

14 Casino chips

15 Life insurance policy

16 Insurance

17 Real estate

18 Payment Services

19 Purchase

20 Sale

21 Deposit

22 Other

23 Unknown

24 Transfer Table 14: Funds type


5.3 account_type


Value Description

1 Business account

2 Current account

3 Deposit box

4 Single account

5 Deposit account

6 Loan account

7 Credit card account

8 Time Deposit account

9 Private account

10 Internal account

11 Correspondent Account

12 Credit Card

13 Nostro account

14 Collective account

15 Unknown

16 Savings

17 Savings account

18 SWIFT account

19 Clearing account

20 Currency account

21 Securities Deposit

22 Refugee account

23 Other

25 Direct account

26 Savings

27 Time deposit account

28 Escrow account

29 Payment account

30 Interest and Cash account

31 Other account

32 Guarantee/ Surety Credit account

33 Alternate account

34 Basic account Table 15: Account type


5.4 account_status_type


Value Description

1 Active

2 Dormant

3 Inactive

4 impounded

5 Other

6 Unknown Table 16: Account status type

5.5 identifier_type


Value Description

1 ID

2 Passport

3 ID card replacement

4 Passport replacement

5 Electronical proof of identity

6 Qualified electronical signature

7 Notified electronical Identification system

8 Birth Certificate

9 Certificate of appointment

10 Certificate of abandonment of deportation according to § 60a Abs. 4 Residence Law

11 Proof of arrival at destination according to to § 63 of Asylum law

12 Driving license

13 Other

14 Unknown

15 Not in use Table 17: Identifier type

5.6 conduction_type


Value Description

1 Electronic transaction

2 Cash business

3 ATM

4 Account opening

5 Courier

7 Other


8 Unknown

9 Online Banking

10 Virtual payment

11 Personal

12 Telefonic

BMA Not in use Table 25: Conduction Type

5.7 trans_item_status


Value Description

1 Bought

2 Sold

3 Donated

4 Lent

5 Awarded

6 Exchanged

7 Other

8 Unknown Table 26: Transaction Item Status

5.8 contact_type

* The following list is specified by FIU Germany.

Value Description

1 Business

2 Private

3 Other

4 Unknown Table 27: Contact Type


5.9 communication_type

* The following list is specified by FIU Germany. Actual codes defined by FIU in Lookup Master will be added automatically to the Schema by goAML client application.

Value Description

1 Landline phone

2 Mobile phone

3 Fax

4 Other

5 Unknown Table 28: Communication Type

5.10 legal_form_type


Value Description

1 Joint-Stick company

2 Registered cooperative

3 Individual company

4 Registered association

5 Registered trader

6 Private Company

7 Limited liability company

8 Ltd/ Limited partnership

9 Public corporation

10 Limited Partnership

11 Limited Partnership by shares

12 General partnership

13 Entrepreneurial company, limited liability

14 & Partner- partnership company

15 Other german legal form

16 Foreign form

17 Unknown

18 Not applicable

19 Public agency

20 Federal authority

21 Regional authorities

22 Local authority Table 29: Legal Form Type


5.11 trans_item_type


Value Description

1 Motor Vehicle

2 Ship

3 Aircraft

4 Noble metal

5 Jewellery / Watches

6 Gems

7 Property

8 Art / Antiquities

9 Other high quality goods

10 Other Table 30: Transaction Item Type

5.12 currency_type

World Currencies (and their abbreviations) listed by ISO 4217

AED United Arab Emirates Dirham

AFA Afghani

ALL Leek

AMD Dram

ANG Netherlands Antilles Guilder

AOK Kwanza

AON New Kwanza

ARA Austral

ARP Argentinean Peso

ARS Argentinean Nuevo Peso

ATS Schilling (no longer in use)

AUD Australian Dollar

AWG Aruban Guilder

AZM Azerbaijani Manat

BAM Convertible Mark

BBD Barbados Dollar

BDT Taka

BEC Convertible Belgian Franc (no longer in use)

BEF Belgian Franc (also known as Frank - no longer in use)

BEL Financial Belgian Franc (no longer in use)

BGL Lev

BHD Bahraini Dinar

BIF Burundi Franc

BMD Bermudian Dollar

BND Brunei Dollar

BOB Boliviano

BOP Bolivian Peso

BRC Cruzeiro


BRL Real

BRR Cruzeiro Real

BSD Bahamian Dollar

BTN Ngultrum

BUK Replaced by MMK

BWP Pula

BYR Belarussian Rouble

BZD Belize Dollar

CAD Canadian Dollar

CDF Congolese Franc

CDZ New Zaïre

CHF Swiss Franc

CLF Unidades de Fomento

CLP Chilean Peso

CNY Yuan Renminbi

COP Colombian Peso

CRC Costa Rican Colón

CSK Koruna of former Czechoslovakia. Now replaced by CZK (Czech Koruna) and SKK (Slovak Koruna)

CUP Cuban Peso

CVE Escudo Caboverdiano

CYP Cypriot Pound

CZK Czech Koruna

DDM Former East German Mark, DEM subsequently in use

DEM Deutsche Mark (no longer in use)

DJF Djibouti Franc

DKK Danish Krone

DOP Dominican Republic Peso

DZD Algerian Dinar

ECS Sucre (no longer in use)

EEK Kroon

EGP Egyptian Pound

ERN Eritrean Nakfa

ESA Spanish Peseta, Account A (no longer in use)

ESB Spanish Peseta, Account B (no longer in use)

ESP Spanish Peseta (no longer in use)

ETB Ethiopian Birr

EUR Euro

FIM Markka (no longer in use)

FJD Fiji Dollar

FKP Falkland Pound

FRF French Franc (no longer in use)

GBP Pound Sterling (United Kingdom Pound)

GEL Lari

GHC Cedi

GIP Gibraltar Pound

GMD Dalasi

GNS Syli (also known as Guinea Franc)


GQE Ekwele

GRD Greek Drachma (no longer in use)

GTQ Quetzal

GWP Guinea-Bissau Peso

GYD Guyana Dollar

HKD Hong Kong Dollar

HNL Lempira

HRD Croatian Dinar

HRK Croatian Kuna

HTG Gourde

HUF Forint

IDR Rupiah

IEP Punt (no longer in use)

ILS Shekel

INR Indian Rupee

IQD Iraqi Dinar

IRR Iranian Rial

ISK Icelandic Króna

ITL Italian Lira (no longer in use)

JMD Jamaican Dollar

JOD Jordanian Dinar

JPY Yen

KES Kenyan Shilling

KGS Kyrgyzstani Som

KHR Riel

KMF Comorian Franc

KPW Democratic People's Republic of Korean Won

KRW Republic of Korean Won

KWD Kuwaiti Dinar

KYD Cayman Islands Dollar

KZT Tenge

LAK Kip

LBP Lebanese Pound

LKR Sri Lankan Rupee

LRD Liberian Dollar

LSL Loti

LSM Maloti

LTL Litas

LUF Luxembourg Franc (no longer in use)

LVL Lats

LYD Libyan Dinar

MAD Moroccan Dirham

MDL Moldavian Leu

MGF Malagasy Franc

MKD Macedonian Dinar

MLF Malian Franc

MMK Kyat

MNT Tugrik


MOP Pataca

MRO Ouguiya

MTL Maltese Lira

MTP Maltese Pound, replaced by Maltese Lira

MUR Mauritius Rupee

MVR Rufiyaa

MWK Malawian Kwacha

MXN Mexican New Peso (replacement for Mexican Peso)

MXP Mexican Peso, replaced by Mexican New Peso

MYR Ringgit (also known as Malaysian Dollar)

MZM Metical

NAD Namibian Dollar

NGN Naira

NIC Córdoba

NLG Dutch Guilder (no longer in use)

NOK Norwegian Krone

NPR Nepalese Rupee

NZD New Zealand Dollar

OMR Omani Rial

PAB Balboa

PEI Inti

PEN New Sol

PES Sol (replaced by New Sol [PEN])

PGK Kina

PHP Philippines Peso

PKR Pakistani Rupee

PLN New Zloty

PLZ Zloty (replaced by New Zloty [PLN])

PTE Portuguese Escudo (no longer in use)

PYG Guarani

QAR Qatari Riyal

ROL Romanian Leu

RSD Serbian Dinar

RUB Russian Federation Rouble (formerly RUR)

RWF Rwandan Franc

SAR Saudi Riyal

SBD Solomon Islands Dollar

SCR Seychelles Rupee

SDD Sudanese Dinar

SDP Sudanese Pound

SEK Swedish Krona

SGD Singapore Dollar

SHP St Helena Pound

SIT Tolar

SKK Slovak Koruna

SLL Leone

SOS Somali Shilling

SRG Surinam Guilder


STD Dobra

SUR Union of Soviet Socialist Republics Rouble

SVC El Salvadorian Colón

SYP Syrian Pound

SZL Lilangeni

THB Baht

TJR Tajik Rouble

TMM Turkmenistani Manat

TND Tunisian Dinar

TOP Pa'anga

TPE Timorian Escudo

TRL Turkish Lira

TTD Trinidad and Tobago Dollar

TWD Taiwan Dollar

TZS Tanzanian Shilling

UAH Hryvna

UAK Karbovanet

UGS Ugandan Shilling

UKP Incorrectly used for GBP

USD United States Dollar

USN United States Dollar (Next day)

USS United States Dollar (Same day)

UYP Uruguayan Peso, replaced by Uruguayan New Peso (UYU)

UYU Uruguayan New Peso

UZS Uzbekistani Som

VEB Bolivar

VND Viet Nam Dông

VUV Vatu

WST Tala

XAF Franc de la Communauté financière africaine

XAU Gold

XBA European Composite Unit

XBB European Monetary Unit

XBC European Unit of Account 9

XBD European Unit of Account 17

XCD East Caribbean Dollar

XDR International Monetary Fund Special Drawing Rights

XEU ECU (not an official currency, replaced by the Euro)

XOF West African Franc

XPF Franc des Comptoirs français du Pacifique

YDD South Yemeni Dinar

YER Yemeni Riyal

YUD Yugoslavian New Dinar (no longer in use)

ZAL Rand (financial)

ZAR Rand

ZMK Zambian Kwacha

ZRZ Replaced by CDZ

ZWD Zimbabwe Dollar


Table 31: Currency Codes

5.13 country_type

This list states the country names (official short names in English) in alphabetical order as given in ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code elements.

Value Description

AD ANDORRA

AE UNITED ARAB EMIRATES

AF AFGHANISTAN

AG ANTIGUA AND BARBUDA

AI ANGUILLA

AL ALBANIA

AM ARMENIA

AN NETHERLANDS ANTILLES

AO ANGOLA

AQ ANTARCTICA

AR ARGENTINA

AS AMERICAN SAMOA

AT AUSTRIA

AU AUSTRALIA

AW ARUBA

AX ÅLAND ISLANDS

AZ AZERBAIJAN

BA BOSNIA AND HERZEGOVINA

BB BARBADOS

BD BANGLADESH

BE BELGIUM

BF BURKINA FASO

BG BULGARIA

BH BAHRAIN

BI BURUNDI

BJ BENIN

BM BERMUDA

BN BRUNEI DARUSSALAM

BO BOLIVIA

BR BRAZIL

BS BAHAMAS

BT BHUTAN

BU BURMA

BV BOUVET ISLAND

BW BOTSWANA

BY BELARUS

BZ BELIZE

CA CANADA

CC COCOS (KEELING) ISLANDS

CD CONGO, THE DEMOCRATIC REPUBLIC OF THE

CF CENTRAL AFRICAN REPUBLIC

CG CONGO


CH SWITZERLAND

CI COTE D'IVOIRE

CK COOK ISLANDS

CL CHILE

CM CAMEROON

CN CHINA

CO COLOMBIA

CR COSTA RICA

CS SERBIA AND MONTENEGRO

CU CUBA

CV CAPE VERDE

CX CHRISTMAS ISLAND

CY CYPRUS

CZ CZECH REPUBLIC

DE GERMANY

DJ DJIBOUTI

DK DENMARK

DM DOMINICA

DO DOMINICAN REPUBLIC

DZ ALGERIA

EC ECUADOR

EE ESTONIA

EG EGYPT

EH WESTERN SAHARA

ER ERITREA

ES SPAIN

ET ETHIOPIA

FI FINLAND

FJ FIJI

FK FALKLAND ISLANDS (MALVINAS)

FM MICRONESIA, FEDERATED STATES OF

FO FAROE ISLANDS

FR FRANCE

GA GABON

GB UNITED KINGDOM

GD GRENADA

GE GEORGIA

GF FRENCH GUIANA

GG GUERNSEY

GH GHANA

GI GIBRALTAR

GL GREENLAND

GM GAMBIA

GN GUINEA

GP GUADELOUPE

GQ EQUATORIAL GUINEA

GR GREECE

GS SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS


GT GUATEMALA

GU GUAM

GW GUINEA-BISSAU

GY GUYANA

HK HONG KONG

HM HEARD ISLAND AND MCDONALD ISLANDS

HN HONDURAS

HR CROATIA

HT HAITI

HU HUNGARY

ID INDONESIA

IE IRELAND

IL ISRAEL

IM ISLE OF MAN

IN INDIA

IO BRITISH INDIAN OCEAN TERRITORY

IQ IRAQ

IR IRAN, ISLAMIC REPUBLIC OF

IS ICELAND

IT ITALY

JE JERSEY

JM JAMAICA

JO JORDAN

JP JAPAN

KE KENYA

KG KYRGYZSTAN

KH CAMBODIA

KI KIRIBATI

KM COMOROS

KN SAINT KITTS AND NEVIS

KP KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF

KR KOREA, REPUBLIC OF

KS KOSOVO

KW KUWAIT

KY CAYMAN ISLANDS

KZ KAZAKHSTAN

LA LAO PEOPLE'S DEMOCRATIC REPUBLIC

LB LEBANON

LC SAINT LUCIA

LI LIECHTENSTEIN

LK SRI LANKA

LR LIBERIA

LS LESOTHO

LT LITHUANIA

LU LUXEMBOURG

LV LATVIA

LY LIBYAN ARAB JAMAHIRIYA

MA MOROCCO


MC MONACO

MD MOLDOVA, REPUBLIC OF

ME MONTENEGRO

MG MADAGASCAR

MH MARSHALL ISLANDS

MK MACEDONIA

ML MALI

MM MYANMAR

MN MONGOLIA

MO MACAO

MP NORTHERN MARIANA ISLANDS

MQ MARTINIQUE

MR MAURITANIA

MS MONTSERRAT

MT MALTA

MU MAURITIUS

MV MALDIVES

MW MALAWI

MX MEXICO

MY MALAYSIA

MZ MOZAMBIQUE

NA NAMIBIA

NC NEW CALEDONIA

NE NIGER

NF NORFOLK ISLAND

NG NIGERIA

NI NICARAGUA

NL NETHERLANDS

NO NORWAY

NP NEPAL

NR NAURU

NU NIUE

NZ NEW ZEALAND

OM OMAN

PA PANAMA

PE PERU

PF FRENCH POLYNESIA

PG PAPUA NEW GUINEA

PH PHILIPPINES

PK PAKISTAN

PL POLAND

PM SAINT PIERRE AND MIQUELON

PN PITCAIRN

PR PUERTO RICO

PS PALESTINIAN TERRITORY, OCCUPIED

PT PORTUGAL

PW PALAU

PY PARAGUAY


QA QATAR

RE REUNION

RO ROMANIA

RS SERBIA

RU RUSSIAN FEDERATION

RW RWANDA

SA SAUDI ARABIA

SB SOLOMON ISLANDS

SC SEYCHELLES

SD SUDAN

SE SWEDEN

SG SINGAPORE

SH SAINT HELENA

SI SLOVENIA

SJ SVALBARD AND JAN MAYEN

SK SLOVAKIA

SL SIERRA LEONE

SM SAN MARINO

SN SENEGAL

SO SOMALIA

SR SURINAME

ST SAO TOME AND PRINCIPE

SV EL SALVADOR

SY SYRIAN ARAB REPUBLIC

SZ SWAZILAND

TC TURKS AND CAICOS ISLANDS

TD CHAD

TF FRENCH SOUTHERN TERRITORIES

TG TOGO

TH THAILAND

TJ TAJIKISTAN

TK TOKELAU

TL TIMOR-LESTE

TM TURKMENISTAN

TN TUNISIA

TO TONGA

TP EAST TIMOR

TR TURKEY

TT TRINIDAD AND TOBAGO

TV TUVALU

TW TAIWAN, PROVINCE OF CHINA

TZ TANZANIA, UNITED REPUBLIC OF

UA UKRAINE

UG UGANDA

UM UNITED STATES MINOR OUTLYING ISLANDS

US UNITED STATES

UY URUGUAY

UZ UZBEKISTAN


VA HOLY SEE (VATICAN CITY STATE)

VC SAINT VINCENT AND THE GRENADINES

VE VENEZUELA

VG VIRGIN ISLANDS, BRITISH

VI VIRGIN ISLANDS, U.S.

VN VIET NAM

VU VANUATU

WF WALLIS AND FUTUNA

WS SAMOA

YE YEMEN

YT MAYOTTE

YU YUGOSLAVIA

ZA SOUTH AFRICA

ZM ZAMBIA

ZR ZAIRE

ZW ZIMBABWE

- Default Table 32: Country Codes

5.14 gender_type

Value Description

- Unknown

F Female

M Male


5.15 account_person_role_type


Value Description

1 Depositor

2 Authorized drawer of an account

3 Owner

4 Other

5 Unknown

5.16 entity_person_role_type


Value Description

1 Manager

2 Procurator

3 Beneficial owner

4 Other registered manager

5 Unknown

5.17 party_role_type

Value Description

1 Beneficiary/Receiver

2 Payee/Sender

3 Other

4 Unknown

5 Employer

9 Doer

10 Buyer

11 Vendor

12 Contractor


5.18 report_indicator_type

Value Description

A1000 Money laundering

A1001 Transaction i.c.w. money laundering (FIU approval required, §46 par 1)

A1002 Transaction i.c.w. money laundering (respite not possible, §46, par 2 )

A1003 Transaction i.c.w. money laundering (subsequent finding, §46, par 2 )

A1004 Business connection i.c.w. money laundering

A1005 Brokerage i.c.w. money laundering

A2000 Terrorism financing

A2001 Transaction i.c.w. terrorism financing (FIU approval required, §46, par 1)

A2002 Transaction i.c.w. terrorism financing (respite not possible, §46, par 2)

A2003 Transaction i.c.w. terrorism (subsequent determination)

A2004 Business modell i.c.w. terrorism

A2005 Item of property i.c.w. terrorism

A3000 Other reason

A3001 Violation of disclosure requirement

A3002 Subsequent registration

A3003 Other reason

A4000 Urgent fact

Identified Facts

B1000 Customer-related particularities

B1101 Politically exposed person

B1102 Hit in terrorism sanctions list VO (EG) Nr. 881/2002

B1103 Hit in other sanctions list

B1104 Knowledge of criminal investigation against client

B1105 Client or beneficial owner of the country, without equivalent standards in relation to money laundering prevention

B1201 Presentation of fake / conspicuous personal documents (disguising identity)

B 1202 Irregularities under the Postid procedure

B1203 Refusal of necessary information to identify the customer

B1204 Conspicuous behavior of the customer

B1205 Use of false or conspicuous documents / business documents

B1206 Use of conspicuous addresses (mailboxes, mailbox companies, group addresses)

B1207 Refusal / obscuration of the disclosure of the beneficial owner

B1208 Disguising the disclosure of the beneficial owner by complex / international corporate structure

B1301 Customer profile is unsuitable for business purposes

B1302 Conceivable / incomprehensible economic background of the customer

B1303 Customer has no business-specific knowledge or business background appropriate to the transaction / business relationship

B1304 Customer does not enter into a basic subscriber or a third party

B1305 Customer obviously acts for third parties

B1306 Local not plausible business relationship between customers and obligated parties

B1307 Participation of / in illiquid companies

B1308 Customer who is a non-recognized NGO or NPO

B2000 Transactions/ Business relationships purchased features


B2101 Economically not plausible transaction

B2102 Transaction contradicts the economical background of client

B2103 Transaction contradicts business purpose of client

B2104 Unknown source of fund

B2105 Suspicious purpose

B2106 Implausible use of different / transitory/ omnibus accounts

B2107 Use of anonym payment methods

B2108 Transaction was carried out under great time pressure for non-comprehensible reasons

B2109 Shortly before the transaction is concluded, new parties or agreements are introduced

B2110 Unexpected changes in financing

B2111 Unexplained change of account binding

B2112 Transaction is above or below the announced value

B2113 Processing of payment services outside the usual banking sector

B2114 Transaction obviously does not serve an economically justifiable purpose

B2301 Transactions are made from unusual sources or unsafe countries

B2201 Exchange of cash in / from 500 € banknotes

B2202 High or unusual exchange of cash into other denominations of the same currency

B2203 Other unusual / high cash exchange

B2204 Unusually high cash payments / cash withdrawals

B2205 Variety of cash deposits / disbursements without explanation

B2206 Unusual cash payment in commercial transactions

B2115 Smurfing (splitting and aggregating cash below thresholds)

B2302 Transaction into / off offshore financial center

B2303 Transaction to / from third countries that do not have adequate systems to prevent, detect and combat money laundering and terrorist financing

B2304 Transactions to / from third countries where corruption and other criminal activities are significant

B2305 Transaction to / from countries which, for example, the EU or the UN have imposed sanctions, embargoes or similar measures

B2306 Transactions to / from countries that provide financial or other support for terrorist activities or in which known terrorist organizations are active

B2401 Other facts

Business area

C1001 Abnormalities i.c.w. Credit operations / fiduciary activities

C1002 Abnormalities i.c.w. Securities transactions

C1003 Abnormalities i.c.w. credit transactions

C1004 Abnormalities i.c.w. insurance operations

C1005 Abnormalities i.c.w. Leasing operations

C1006 Abnormalities i.c.w. foreign trade (international trade)

C1007 Abnormalities i.c.w. currency exchange

C1008 Abnormalities i.c.w. prepaid cards

C1009 Abnormalities i.c.w. credit cards

C1010 Abnormalities i.c.w. E-Money

C1011 Abnormalities i.c.w. Cryptograms (e.g., bitcoin)

C1012 Abnormalities i.c.w. cheques


C1013 Abnormalities i.c.w. cheques

C1014 Abnormalities i.c.w. deposit box

C1015 Abnormalities i.c.w. purchase / sale of properties

C1016 Abnormalities i.c.w. purchase / sale of vehicles

C1017 Abnormalities i.c.w. purchase / sale of ships

C1018 Abnormalities i.c.w. purchase / sale of aircrafts

C1019 Abnormalities i.c.w. purchase / sale of precious metals

C1020 Abnormalities i.c.w. purchase / sale of precious gem

C1021 Abnormalities i.c.w. purchase / sale of jewellery and watches

C1022 Abnormalities i.c.w. purchase / sale of art and antiquities

C1023 Abnormalities i.c.w. purchase / sale of high quality goods

C1024 Abnormalities i.c.w. with other business areas

Suspected criminal offenses / money laundering

D1001 Corruption, criminal offenses (eg bribery and corruption)

D1002 Fraud and infidelity

D1004 tax offenses

D100401 social benefit fraud

D1006 Endangering the democratic state (including terrorist financing)

D1019 Other offense

D1020 No criminal offense

5.19 report_type

Value Description

AIA Not in use

AIT Not in use

ANA Not in use

ANT Not in use

EIT

MBA Not in use

MBT Not in use

VMA Report (without transaction)

VMT Report (with transaction)

5.20 rentity_type

Value Description

RE Liable

SH Not in use

FIU Not in use

SUP Not in use

IND Not in use

Annexure 2 Standard XML Reporting - Zoll

Documents