goAML XSD Specification ver. 4.2.1 goAML EE Project EE FIC Schema V4.2.1 Specification.pdf ·...

goAML EE Project

Document Name: FCT_120_1_goAML EE FIC Schema v4.2.1 Specification

Version: 4.2.1

Date: 15/04/2016 of 96

financial intelligence centre REPUBLIC OF SOUTH AFRICA


goAML XSD Specification ver. 4.2.1

goAML EE Project

Legal Disclaimer Unless specific written consent is obtained from the Financial Intelligence Centre the information contained in this document may not be shared with any third parties. By reading this document you acknowledge the confidentiality of such and agree to be bound by the copyright that subsists in Financial Intelligence Centre’s intellectual ideas, views and their representation as expressed in this material.

Document Name: FCT120_1_ goAML EE_FIC Schema ver. 4.2.1 Specification

Version Number: 4.2.1

Version Date: 12 April 2016

Prepared for: FIC

Project: goAML EE Project

Contract Number: NA

Item Number: NA



goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



1. Configuration Control

Document History

Revision Date Change Req. No Change Summary

0.01 25 February 2014

N/A Document created

26 February 2014

Updated document with from review comments

0.03 03 March 2014

Added STRB in report type

0.04 25 April 2014

Updated t_person_my_client/title and Gender to be mandatory

0.07 06 Nov 2014 Update field length changing person identifier fields from 255 to 100. Updated the following lookup lists and include annexure for business rules.

1.2.0 19-June-2015

GoAML 4.2 Release Update

1.2.1 12 April 2016

Updated the document with the release notes published on the 7th of July 2015

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



2. Table of Contents

1. Configuration Control ...................................................................................................................................... 2 2. Table of Contents ............................................................................................................................................. 3 3. Financial Intelligence Centre Introduction Notes ............................................................................................ 5 4. Summary .......................................................................................................................................................... 6 5. Schema updates ............................................................................................................................................... 7 6. Conventions used in this document ................................................................................................................. 8 7. Description of XML Nodes ............................................................................................................................. 9 7.1. Node “report” .................................................................................................................... 9

7.2. Subnode report_indicators ............................................................................................... 12

7.3. Node transaction .............................................................................................................. 13

7.4. Node Activity .................................................................................................................. 16

7.5. Node t_from_my_client ................................................................................................... 17

7.6. Node t_from ..................................................................................................................... 19

7.7. Node t_to_my_client ....................................................................................................... 21

7.8. Node t_to ......................................................................................................................... 23

7.9. Subnode goods_services .................................................................................................. 24

7.10. Type t_account_my_client ............................................................................................... 26

7.11. Type t_account ................................................................................................................. 31

7.12. Type t_entity_my_client .................................................................................................. 35

7.13. Type t_entity .................................................................................................................... 38

7.14. Type t_person_my_client ................................................................................................ 40

7.15. Type t_person .................................................................................................................. 45

7.16. t_person_registration_in_report ....................................................................................... 49

7.17. Type t_party ..................................................................................................................... 53

7.18. Type t_address ................................................................................................................. 55

7.19. Type t_phone ................................................................................................................... 56

7.20. Type t_foreign_currency ................................................................................................. 57

7.21. Type t_person_identification ........................................................................................... 58

7.22. Type report_party_type ................................................................................................... 59

8. Lookup Values ................................................................................................................................................60 8.1. Submission type – goAML Enumeration ........................................................................ 60

8.2. Funds type ........................................................................................................................ 60

8.3. Account type .................................................................................................................... 61

8.4. Account status type .......................................................................................................... 61

8.5. Identifier type .................................................................................................................. 62

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.6. Conduction Type ............................................................................................................. 63

8.7. Transaction Item Status ................................................................................................... 64

8.8. Report Code Type ............................................................................................................ 64

8.9. Contact Type .................................................................................................................... 65

8.10. Communication Type ...................................................................................................... 65

8.11. Entity Legal Form Type .................................................................................................. 66

8.12. Transaction Item Type ..................................................................................................... 67

8.13. Currencies ........................................................................................................................ 68

8.14. Country Codes ................................................................................................................. 74

8.15. account_person_role_type ............................................................................................... 82

8.16. entity_person_role_type .................................................................................................. 83

8.17. party_role ......................................................................................................................... 84

8.18. Report indicator ............................................................................................................... 85

9. Annexure ........................................................................................................................................................90 9.1. Business Rules ................................................................................................................. 90

9.1.1. Rules / Guidance on reporting ..................................................................................... 90

9.1.2. Report Level Rules ...................................................................................................... 92

9.1.3. Activity Level Rules .................................................................................................... 93

9.1.4. Transaction Level Rules .............................................................................................. 95

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



3. Financial Intelligence Centre Introduction Notes The Financial Intelligence Centre Act 38 of 2001 (the FIC Act) mandates all accountable

institutions to submit Cash Threshold Reports (CTR). Furthermore the FIC Act mandates

all accountable and reporting institutions to submit Terrorist Property Reports (TPR) and

requires all businesses (which include accountable and reporting institutions) to submit

Suspicious Transaction Reports (STR) to the FIC in terms of section 28; 28A and 29

respectively. The manner of reporting is prescribed by the Regulations to the Act under

section 22. The reporting must be done electronically by means of the FIC’s web-based

portal or a batch reporting method.

The FIC has chosen goAML as its preferred IT platform to handle all its reporting, data

collection, analysis, case management and secure communications required for the FIC’s

daily operational functions and requirements. The goAML system will in future standardise

all report types and also clearly distinguish between activity reports and bi-party (“to” and

“from”) transaction reports, and the batch reporting method will be limited to transaction

reporting which includes the current CTR, TPR and STR reports. The goAML XML Schema

will be utilised by the FIC for all future batch and electronic web-based portal reporting and

will have to be adapted and implemented by all of the Reporting entities that file intelligence

reports with the FIC.

GoAML is an integrated software solution developed and maintained by the United Nations

Office of Drugs and Crime (UNODC) specifically for use by financial intelligence units

(FIUs) internationally and has to date been deployed to twenty one (21) other FIUs. GoAML

is specifically designed to meet the data collection, management, analytical, document

management, workflow and statistical needs of any FIU irrespective of its size. Please refer

to goAML website goAML for further information in relation to the system and related

products and services.

http://goaml.unodc.org/

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



4. 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

(all transactions will be bi-party transactions with a “to” and “from” side). An uploaded

report can be from ONE report type (CTR, TPR or STR) per upload.

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)

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



5. Schema updates

Update Description Rational

Person element changes

Prefix, Alias and Surname length changes. Restrict to capture Alphanumeric characters only

Aligning the field with SA population registration prescribes

Entity Element changes

Name length changes Aligning the fields with company registration prescription

Look up list update Updated the following lookup list

Submission type –

Funds type

Account type

Account status type

Identifier type

Conduction Type

Transaction Item Status

Report Code

Contact Type

Communication Type

Entity Legal Form Type

Transaction Item Type

account_person_role_type

entity_person_role_type

party_role

Report_type

Report indicator

Input received entailed changes to the affected lists

GoAML Release 4.2 goAML Release 4.2 GoAML Solution upgrade

Issue Fixes on version 4.2

Update Birth_Place to string data type.

Update regular expression on Contact Person element to allow spaces.

Refresh screenshot to be visible.

Responding to issues raised

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



6. 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

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7. Description of XML Nodes 7.1. Node “report”

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

Figure 1: Overview node “report”

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Name Description Data Type and Length

Req. Example

rentity_id Assigned AI/RI registration number to the registered AI/RI.

Integer >= 1

Y

1237

rentity_branch Branch of current reporting entity and should refer to the branch were the transaction took place

String 255

N ABC Bank Centurion Branch

submission_code Type of submission. For XML reports submitted electronically select “Electronic”

Enumeration Y See Submission type

report_code Type of report e.g. (CTR/ TPR/ STR…). Batch reporting only applicable to a report containing a transaction

Enumeration Y Report Code

entity_reference Optional reference to the report, used by reporting entity to uniquely identify the specific report

String 255

N CTR Rep 392

fiu_ref_number Optional and to be used as reference number during formal communication between the FIC and the Reporting Entity

String 255

N ABC_BANK_CTR_20100217.

submission_date Submission date and time Datetime Y 2006-03-25T11:55:00

currency_code_local

Local Currency code

Type “Currency-

type”

Y ZAR

reporting_person Full details of the person submitting the report.

Type “t_person_registration_in_

report”

Y Can be forced mandatory in certain report types by using the new goAML feature: “XML Rejection Rules”

Location Describes location of the reporter. Specifying the origination of report i.e. the

Type “t_address”

Y Mandatory: Same as “reporting person”

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

branch which submitted the report.

reason Description on why the report was made. Conditional rule, Refer to Sec 10 for when it is mandatory.

String 4000

N “the reported person matched the UN-Terror list.”

action Describes action related to the report. The actions will include external actions taken and the agency reported to. Must be captured when report is an STR and TPR

String 4000

N Mandatory: Same as “reporting person”. Example would be to state that the account had been closed and the subject reported to FIC

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 See Node transaction

Activity Involved subjects and items list linked directly to report. New in 4.0

Y See 3.3 Node activity

report_indicators List of indicators for the report being submitted

Type “indicator”

Y See Subnode report_indicat

ors

Table 1: Details node “report”

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.2. Subnode report_indicators

Figure 2: Overview subnode report_indicators


Req. Example

indicator Indicates the type of suspicion or suspected predicate offence or activity.

Type Report_indicator

_type

Y Crime, Terror Financing, etc. (FIC predefined list of codes)

Table 2: Details subnode report_indicators

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.3. Node transaction

Figure 3: Overview node transaction

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Name Description Data Type And Length

Req. Example

transactionnumber Unique transaction number assigned to a transaction

String 50

Y 20084711

Internal_ref_number Reporting Entity internal transaction reference number

String 50

N WU_BRNCH01_0001

transaction_location

The address location where the transaction took place.

String 255

Y Branch 001, Bloemfontein, Free State

transaction_description

The description of the transaction’s purpose.

String 4000

N

date_transaction Date and time of the transaction

DateTime Y 2006-03-25T11:55:00

teller The identification number of the representative of the AI/RI or the employee assisting the customer to perform a transaction.

String 20

N ID88933345

authorized The name of the individual authorising the transaction.

String 20

N ID00033345

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. In SA these are not applicable

late_deposit Late deposit indicator Boolean Y/N True

date_posting Date of posting (if different from date of transaction), applicable to late deposit.

DateTime N 2006-03-24T19:55:00

value_date The date corresponding to the value of the transaction.

DateTime N 2006-03-27T00:00:00

transmode_code Description of how the transaction was conducted.

Enumeration Y See Conduction Type

transmode_comment

Comments relating to the mode of transaction.

String 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. Note: FIC only to allow bi-party transactions for batch reporting purposes

Bi-Party Transaction

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Name Description Data Type And Length

Req. Example

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)

See t_from_my_client

t_from Specifies where the money came from

Subnode See Node t_from

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)

See Node t_to_my_client

t_to Specifies where the money went.

Subnode See Node t_to

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. Note that feature will not be used by FIC for batch reports

party Describes the party details not

to be used

Type “t_party”

Y See Type t_party

Goods_services The goods/services linked to the transaction

subnode N See 3.5 Subnode goods_services

Comments Generic comments field String 4000

N

Table 3: Details node transaction

Involved

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.4. Node Activity

Reports 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. The activities will be only valid when submitted for the following reports S36,SAR,VDR & TPR

Figure 4: Overview node activity

Name Description Data type and Length

Req. Example

report_parties Represents a collection of involved subjects an involved subject with it’s details

Y

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

Type report_party

_type

Y See 4.9 Node report_party_type

goods_service The standard goods_services node available in previous schemas

Type t_trans_item

N -

Table 4: Details node transaction

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.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.2, entity could be a direct party in bi-party transactions

Figure 5: Overview node t_from_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

from_funds_code Type of funds used in initiating transaction

Enumeration Y See Funds type

from_funds_comment Description, if funds_code is “O” (Other), then provide the specifics or comments relating to funds.

String 255

N -

from_foreign_currency

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

Type t_foreign_curr

ency

N See Type t_foreign_currency

t_conductor The person performing the transaction.

Type t_person_my

_client

N See Type t_person_my_client

from_account Subnode that holds account information

Type t_account_m

y_client Y (one

of them only)

See Type t_account_my_client

from_person Subnode that holds “from person” information.

Type t_person_my

_client

See Type t_person_my_client

from_entity New in Schema 4.0

Subnode that holds “from entity” information.

Type t_entity_my_c

lient

See 4.32 Type t_entity_my_client

from_country Country where transaction was initiated.

Enumeration Y See Country Codes

Table 5: Details node t_from_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.6. Node t_from

Source of the transaction. Can be either a person, an account or an entity. As per schema 4.2, 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.2).

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.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req.

Example

from_funds_code Type of funds used in initiating transaction

Enumeration Y See Funds type

from_funds_comment Description, if funds_code is “O” (Other).

String 255

N -

from_foreign_currency


type t_foreign_curr

ency


t_conductor The person performing the transaction.

type t_person

N

See Type t_person

from_account Subnode that holds account information

type “t_account

Y (one

of them)

See Type t_account

from_person Subnode that holds “from person” information.

type “t_person”

See Type t_person

from_entity

Subnode that holds “from entity” information.

type “t_entity” See 4.22 Type t_entity

from_country Country where transaction was initiated.


Table 6: Details node t_from

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.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

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

to_funds_code Disposition of funds Enumeration

Y See Funds type

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

String 255

N -

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

Type t_foreign_cu

rrency


to_account Subnode that holds account information

Type t_account_my_client

Y (one

of them)


to_person Subnode that holds person information

Type t_person_m

y_client


to_entity New in Schema 4.0

Subnode that holds “to entity” information.

Type t_entity_my

_client

See 4.32 Type t_entity_my_client

to_country Target country of the transaction Enumeration

Y See Country Codes

Table 7: Details node t_to_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.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

Name Description Data type and Length

Req. Example

to_funds_code Disposition of funds Enumeration Y See Funds type

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

String 255

N -

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

Type t_foreign_cu

rrency


to_account Subnode that holds account information

Type t_account

Y (one

of them)

See Type t_account

to_person Subnode that holds person information

Type t_person

See Type t_person

to_entity New in Schema 4.0

Subnode that holds “to entity” information.

Type t_entity

See 4.22 Type t_entity

to_country Target country of the transaction


Table 8: Details node t_to

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.9. Subnode goods_services

Figure 9: Overview subnode goods_services

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req.

Example

Item_type Lookup code describes the item type

Type “trans_item_

type”

Y C = Car L = Land

Item_make Item Maker String 255

N, In case of Car for example, BMW

description Text String 4000

Y Apartment building

previously_registered_to Name of previous owner

String 500

N John Smith

presently_registered_to Name of current owner

String 500

N Jane Smith

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

Decimal N 250000.00

status_code Status code Enumeration

N See Transaction Item Status

status_comments Status Comments String 500

N

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

Decimal N 500000.00

Currency_code

used to report service conducted in foreign currency

Enumeration

N See Currencies

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

Decimal N 150

size_uom Unit of measurement

String 250

N Square meters

address Address of the property

Type t_address

N Type t_address

registration_date Official registration date

DateTime N 2001-12-17T09:30:47

registration_number Official registration number

String 500

N Car VIN Number

Identification_number Any number that can identify the item

String 255

N Car Plate Number

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Comments

Additional comments

String 4000

N

Table 9: Details subnode goods_services

7.10. 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.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Figure 10: Overview type t_account_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Institution_name

The name of the Bank String 120 Y

Bank of …

institution_code Institution code is the code issued to AI/RI by FIC

String 50 Y

(one of

the two

must be

presented)

FIC AI/RI0001/2010

swift SWIFT code according to ISO 9362(not to be used)

String 11

ATTBVI

Non_banking_institution

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

Boolean N

Investment company

Branch

Branch code or name String 50 Y

ABX12 or Centurion

Account

Account number String 50

Y 31032027088

currency_code Currency the account is kept in

Enumeration

Y See Currencies

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.

String 120

N Private savings account

iban International Bank Account Number

String 50

N LT601010012345678901

client_number Client number String 50

N 31032027088

personal_account_type

Type of account Enumeration

Y See Account type

t_entity Business entity owning the account

Type t_entity

N See Type t_entity

signatory Person(s) with access to the account.

Subnode (can

repeated to specify multiple

Y -

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

signatories). Note that the node

t_person is of type

t_person_my_client

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

fixed = 1 N

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

type t_person_m

y_client

Y See Type t_person_my_client

role

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

type “account_person_role_

type”

N See 5.15Type t_person_my_client

opened Date account opened DateTime Y 2003-01-25T00:00:00

closed Date account closed DateTime N 2006-03-25T00:00:00

balance The account balance after the transaction was conducted.

Decimal Y 5000.50

date_balance

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

Date Y (Conditional)

status_code Account status when transaction was initiated

Enumeration

Y See Account status type

beneficiary Ultimate beneficiary of the account.( Should be completed where the beneficiary is different from signatory)

String 50

N Ella Machera

beneficiary_comment

Any special remark on the beneficiary

String 255

N

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

comments Generic comments elements

String 4000

N

Table 10: Details type t_account_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.11. Type t_account

Figure 4: Overview type t_account

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Instituation_name

The name of the Institution where the account is held

String 255 Y

Bank of …

institution_code Institution registration number or license number

String 50 Y

(one of

them)

-

Swift SWIFT code according to ISO 9362 for the banking sector.

String 11

ATTBVI

Non_banking_institution

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

Boolean N

Investment company

Branch

Branch code or name

String 50 N

ABX12 or Centurion

Account

Account number String 50

Y 31032027088

currency_code Currency the account is kept in

Enumeration

N See Currencies

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.

String 255

N Private savings account

iban IBAN String 50

N LT601010012345678901

client_number Client number String 50

N 31032027088

personal_account_type

Account Type Enumeration

N See Account type

t_entity Business entity owning the account

Type t_entity

N See Type t_entity

signatory Person(s) with access to the account.

Subnode (can be


N -

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

signatories).

Note that the node

t_person is of type

t_person

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

fixed = 1 N

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

Type t_person

Y See Type t_person

role

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

Type “account_person_role_

type”

N See 5.15Type t_person_my_client

closed Date account closed DateTime N 2006-03-25T00:00:00

balance The account balance after the transaction was conducted.

Decimal N 5000.50

date_balance

A date field to specify the date of the reported balance.

DateTime N 1753-01-01T00:00:00

status_code Account status when transaction was initiated

Enumeration

N See Account status type

beneficiary Ultimate beneficiary of the account

String 50

N Ella Machera

beneficiary_comment

Any special remark on the beneficiary

String 255

N

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

comments

Generic comments elements

String 4000

N

Table 4: Details type t_account

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.12. 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

Figure 5: Overview type t_entity_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Name

Name of Entity String 120

Y DoeComp 231

Commercial_name The trading name used by the entity

String 120

Y DoeComp

Incorporation_legal_form

The type of business the entity is involved in.

Type “legal_form

_type”

Y See 5.11 CC, PTY (Ltd)

incorporation_number

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

String 50

Y 2014/123456/23

Business Business area of the entity, only mandatory when STR. Refer to Section 10.

String 50

N Free text describing business e.g. IT Services,Imports, Export etc.

Phones

A Holder node for a or many Phones(When selected one of the elements has to be captured)

Y

Phone One occurrence of phone node

Type “t_phone”

Y See Type t_phone

Addresses

A Holder node for a 1 or many Addresses

Y

Address One occurrence of address node


Y Type t_address

Email

Email address email_address (255)

N [email protected]

url Entity web address

String 255

N www.entity.com

incorporation_state Name of the Province where the entity is located

String 255

N -

mailto:[email protected]

http://www.entity.com/

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

incorporation_country_code

Country, will default to SA and must be chaged with different input

Enumeration

Y See Country Codes

director_id This node has in 4.0 a new optional element “role” to describe the role of the subject in the entity from type entity_person_role_type

The details of the entity’s director(s)

type t_person_m

y_client (Subnode

can be repeated for

multiple persons)

Y See Type t_person_my_client

incorporation_date

Incorporation registration date

DateTime N 1753-01-01T00:00:00

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 1753-01-01T00:00:00

tax_number

The entity tax number

String 100

N

tax_registration_number

Registration number of the entity by the Tax auth.

String 100

N

Comments

Generic comments field

String 4000

N

Table 5: Details type t_entity_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.13. Type t_entity

Figure 6: Overview type t_entity

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Name Name of Entity String 120

Y DoeComp 231

Commercial_name The trading name used by the entity.

String 120

N DoeComp

Incorporation_legal_form

The type of business the entity is involved in.

Type “legal_form_

type”

N CC, PTY (Ltd),

incorporation_number

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

String 50

N 2014/12346/23

Business Business area of the entity

String 50

N Text describing business e.g. IT Services,Imp, Exp etc.

Phones

A Holder node for a 1..many Phones

N


Type “t_phone”

N See Type t_phone

Addresses

A Holder node for a 1..many Addresses

N



N Type t_address

Email

Email address email_address

(255)

N [email protected]

url Entity web address String 255

N www.entity.com

incorporation_state Name of the State/ Province

String 255

N -

incorporation_country_code

Country, will default to SA and must be chaged with different input

Enumeration

N See Country Codes

director_id This node has in 4.0 a new optional element “role” to describe the role of the subject in

Individuals authorized

type t_person

N See Type t_person


http://www.entity.com/

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

the entity from type entity_person_role_type

incorporation_date

Incorporation registration date

DateTime N 1753-01-01T00:00:00

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

DateTime N 1753-01-01T00:00:00

tax_number

The entity tax number

String 100

N

tax_registration_number

The registration number of the entity by the Tax authorities

String 100

N

comments

Comments relating to the entity involved.

String 4000

N

Table 6: Details type t_entity

7.14. 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

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Figure 7: Overview type t_person_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

gender The individual’s Gender

Enumeration

Y M or F

Title Title String 30

Y Dr.

first_name The individual’s First name.

String 100

Y Elyas

middle_name The individual’s Middle name.

String 100

N Peter

prefix The individual’s Prefix name.

String 50

N Van, Von,…

last_name The individual’s Last name.

String 120

Y Machera

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

birthdate

The individual’s date of birth.

DateTime Y 1753-01-01T00:00:00

Birth_place

The individual’s place of birth

String 255

N Vienna

mothers_name The individual’s maiden name.

String 120

N Smith

Alias Alias Name, Known as, etc.

String 50

N Ella Mac

SSN

Individual’s South African identification number to be placed in this field. South African citizens are required to provide the RSA-ID number.

Numeric 13

N 7802084568089

passport_number

Mandatory when nationality is not South African. Individual’s Passport Number or Foreign ID Number or Permit Number, Refugee Number or Residence Number.

String 50

N P33127856

passport_country

Mandatory when nationality is not South African. Individual’s Issuing country of Passport/ Foreign ID/ Permit/

Type Country_typ

e

N Issuing country to be used as unification rule

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Refugee/ Residence Number (Can be reported only when there is a Passport/ Foreign ID/ Permit/ Refugee/ Residence Number)

id_ number

Used to capture the individual’s South African passport number.

String 50

N P33127856

Phones

A Holder node for one or many Phones

Y


Type “t_phone”

Y See Type t_phone

Addresses

A Holder node for one or many Addresses

Y


Type t_address

Y Type t_address

Nationality1 Individual’s country of nationality

Enumeration

Y See Country Codes

Nationality2

Individual’s second country of Nationality

Enumeration

N See Country Codes

Nationality3

Individual’s third country of nationality

Enumeration

N See Country Codes

residence Individual’s Country of residence

Enumeration

Y See Country Codes

Email

Individual’s Email address

Type email_addr

ess (255)

N [email protected]

Occupation

Individual’s occupation.

String 50

N Financial Analyst

employer_name

Individual’s employer’s name

String 255

N FIU

employer_address_id Individual’s employer’s address

type t_address

N Type t_address

employer_phone_id Individual’s employer’s phone

type t_phone

N See Type t_phone


goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

identification Subnode(s) for identification documents

type t_person_identification

(This subnode can be


identification

documents)

N See Type t_person_identification

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 1753-01-01T00:00:00

tax_number

The person tax number

String 100

N

tax_reg_number

The person tax reg. number by tax auth.

String 100

N

source_of_wealth

Free text description of the person source of wealth

String 255

N

comments

Comments relating to the individual concerned.

String 4000

N

Table 7: Details type t_person_my_client

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.15. Type t_person

Figure 8: Overview type t_person

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example


Enumeration

N M or F


N Dr.


String 100

Y Elyas


String 100

N Peter


String 50

N Van, Von,…


String 120

Y Machera


birthdate


DateTime N 1753-01-01T00:00:00

Birth_place


String 255

N Vienna


String 120

N Smith


String 50

N Ella Mac

SSN


Numeric 13

N 7802084568089

passport_number


String 50

N P33127856

passport_country

Mandatory when nationality is not South African. Individual’s Issuing country of Passport/ Foreign ID/ Permit/

Type Country_typ

e


goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Refugee/ Residence Number (Can be reported only when there is a Passport/ Foreign ID/ Permit/ Refugee/ Residence Number)

id_ number


String 50

N P33127856

Phones


N


Type “t_phone”

N See Type t_phone

Addresses


N


Type t_address

N Type t_address


Enumeration

N See Country Codes

Nationality2


Enumeration

N See Country Codes

Nationality3


Enumeration

N See Country Codes


Enumeration

N See Country Codes

Email


Type email_addr

ess (255)

N [email protected]

Occupation


String 50

N Financial Analyst

employer_name


String 255

N FIU

employer_address_id Individual’s employer’s address

type t_address

N Type t_address

employer_phone_id Individual’s employer’s phone

type t_phone

N See Type t_phone





goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example



identification

documents)

deceased


Boolean N

deceased_date


DateTime N 1753-01-01T00:00:00

tax_number


String 100

N

tax_reg_number


String 100

N

source_of_wealth


String 255

N

comments


String 4000

N

Table 8: Details type t_person

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.16. t_person_registration_in_report

Figure 9: Overview type t_person_registration_in_report

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example


Enumeration N M or F


N Dr.


String 100

Y Elyas


String 100

N Peter


String 50

N Van, Von,…


String 120

Y Machera


birthdate


DateTime Y 1753-01-01T00:00:00

Birth_place


String 255

N Vienna


String 120

N Smith


String 50

N Ella Mac

SSN


String (Digits Only)

13

N 7802084568089

passport_number


String 50

N P33127856

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

passport_country

Mandatory when nationality is not South African. Individual’s Issuing country of Passport/ Foreign ID/ Permit/ Refugee/ Residence Number (Can be reported only when there is a Passport/ Foreign ID/ Permit/ Refugee/ Residence Number)

Type Country_typ

e


id_ number


String 50

N 6207315807083 (13 digit SA ID Number) or P33127856 (Passport/ Foreign ID/ Permit/ Refugee/ Residence Number)

Phones


N


Type “t_phone”

N See Type t_phone

Addresses


N


Type t_address

N Type t_address


Enumeration N See Country Codes

Nationality2



goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

Nationality3





Email


Type email_addre

ss (255)

N [email protected]

Occupation


String 50

N Financial Analyst

employer_name


String 255

N FIU

employer_address_id

Individual’s employer’s address

type t_address

N Type t_address

employer_phone_id

Individual’s employer’s phone

type t_phone

N See Type t_phone





identification documents)


deceased


Boolean N

deceased_date


DateTime N 1753-01-01T00:00:00

tax_number


String 100

N

tax_reg_number


String 100

N


goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

source_of_wealth


String 255

N

comments


String 4000

N

Table9: Details type t_person_registration_in_report

7.17. Type t_party

Figure 9: Overview type t_party

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96




Req. Example

role

Subject role in the transaction

Enumeration

Y Buyer, Seller,..

Subject: The following become mandatory when the node has been selected.

Person

Involved Person Type “t_person”

Y (At minimum,

one must be

provided)

See Type t_person

Person_my_client

Involved Person Type “t_person_my_client”


account

Involved Account Type “t_account”

See Type t_account

account_my_client

Involved Account Type “t_ account_my

_client”


entity

Involved Entity

Type “t_ entity”

See Type t_entity

entity_my_client Involved Entity Type “t_ entity_my_c

lient”

funds_code Type of funds used in initiating transaction

Enumeration

N See Funds type

funds_comment Description, if funds_code is “O” (Other).

String 255

N -

foreign_currency


Type t_foreign_currency


country Country of the transaction

Enumeration

Y See Country Codes

significance

The significance of the subject in the transaction

Integer 10

N 0-10

comments

Comments relating to the party or parties involved.

String 4000

N

Table 9: Details type t_party

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.18. Type t_address

Figure 10: Overview type t_address


Req. Example

Address_type

The contact type of the address

Enumeration Y Private, Postal, Business,.. See Contact Type

Address

Street number and street name

String 100

Y 54 Embankment Road

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

String 255

N Hennopsriver

City

City String 255

Y Centurion

Zip

Zip/Postal Code String 10

N 0157

country_code Country Enumeration Y See Country Codes

State

State/Province String 255

N Gauteng

comments

Comments relating to the address involved.

String 4000

N

Table 10: Details type t_address

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.19. Type t_phone

Figure 11: Overview type t_phone


Req. Example

tph_contact_type

The contact type of the Phone

Enumeration

Y Private, Business,.. See Contact Type

tph_communication_type

The comm.. type of the Phone

Enumeration

Y Landline, mobile ,fax,.. Communication Type

tph_country_prefix Country phone code

String 4

N 0027

tph_number

Area code (when applicable) and Phone number

String 50 Y

0126416000 or 0827597000

tph_extension

Phone’s extension (when applicable)

String 10

N 6000

comments

Comments relating to the phone involved.

String 4000

N

Table 11: Details type t_phone

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.20. Type t_foreign_currency

Figure 12: Overview type t_foreign_currency


Req. Example

foreign_currency_code Currency Code according to ISO 4217

Enumeration Y See Currencies

foreign_amount Transaction amount in foreign currency

Decimal Y 1300.50

foreign_exchange_rate Exchange rate which has been used for transaction

Decimal Y 1.45

Table 12: Details type t_foreign_currency

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.21. Type t_person_identification

Figure 20: Overview type t_person_identification


Req. Example

type Document type Enumeration Y Identifier type

number ID of the identification document

String 50

Y AT08154711

issue_date Identification document issue date

DateTime N 2001-12-17T09:30:47

expiry_date Identification document expiry date

DateTime N 2012-01-01T00:00:00

issued_by

Name of Authority issued the document

String 255

N Department of Home Affairs

issue_country Country where the document was issued

Type country_type

Y See Country Codes

comments Comments relating to the concerned individual’s identification.

String 4000

N

Table 20: Type t_person_identification

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



7.22. 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


Req. Example

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

person Represents an involved person node

t_person type Y (At

minimum, one must

be provided)

account Represents an involved account

t_account type

entity Represents an involved entity

t_entity type

significance The significance of the subject in the report. Scale indicating role of the party(when TPR this is mandatory)

Integer N 0 - 10

reason Why the subject is involved in the current report(when TPR this is mandatory)

String 4000

N

comments Comments relating to the party type involved.

String 4000

N

Table 21: Type report_party_type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8. Lookup Values As per schema 4.2, all schema lookups are defined as enumerations. Reporting entities will not be able anymore to submit reports with undefined lookup codes.

8.1. Submission type – goAML Enumeration

The following is the list defined by the FIC for use.

Value Description

E Electronic

M Manually

- UNKNOWN

Table 13: submission type

8.2. Funds type


Value Description

1 Airtime Vouchers

2 Bank Draft

3 Bonds

4 Cash

5 Cash Paid To Client

6 Cash Via Credit Card

7 Cash Via Debit Card

8 Cash Via Gift Card

9 Cheque

10 Cheque Paid To Client

11 Coins & Kruger Rands

12 Debit Order

13 Money Order

14 Other

15 Stocks

16 Stop Order

17 Travellers Cheque

18 Virtual Currency

19 Vouchers

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

36 Money Transfer

37 Electronic Fund Transfer (local)

38 Electronic Fund Transfer (international inbound)

39 Electronic Fund Transfer (international outbound)

40 Cash (received by AIRI)

41 Cash (paid by AIRI)

43 Money Remittance

- Unknown

Table 14: Funds type

8.3. Account type

The following is the list defined by the FIC for use for use.

Value Description

1 Bond

2 Cheque

3 Current

4 Mortgage

5 Other

6 Recharge

7 Retail

8 Savings

9 Transmission

10 Trust account

12 Client

- Unknown

Table 15: Account type

8.4. Account status type


Value Description

1 Active

2 Closed

3 Dormant

4 Handed over

5 Inactive

6 Over due

7 Paid in full

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

8 Suspended

- Unknown

Table 16: Account status type

8.5. Identifier type


Value Description

1 Crew Member Certificate

2 Departure Permit

3 Diplomatic Passport

4 Document For Travel Purposes

5 Emergency Travel Document

6 Identity Document

7 Joint Travel Document

8 Machine-Readable Passport

9 Official Emergency Travel Document

10 Official Passport

11 Official Travel Document

12 Other

13 Passport

14 Permit

15 Provisional Permit

16 Refugee ID Document

17 Sailor Identity Certificate

18 South African Driver License

19 South African ID Document

20 South African Passport

21 Temporary Permit

22 Travel Document

- Unknown

Table 17: Identifier type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.6. Conduction Type


Value Description

1 ATM

2 Beddabonds

3 Cellphone Banking

4 Courier

5 Credit Card

6 Currency Exchange

7 Debit Card

8 Debit Oder

9 Electronic Fund Transfer

10 In-Branch

11 Internet

12 Mail

13 Money Remittance

14 Retail

15 Stop Order

16 Telephone

17 Virtual

21 Cash

22 Cash (paid by the AI/RI)

23 Cash (received by the AI/RI)

24 Cash Paid To Client

25 Cash Via Credit Card

26 Cash Via Debit Card

27 Cash Via Gift Card

28 Electronic fund transfer (international inbound)

29 Electronic fund transfer (international outbound)

30 Electronic fund transfer (local)

31 Money Order

32 Money Transfer

- Unknown

Table 25: Conduction Type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.7. Transaction Item Status


Value Description

1 Bought

2 Destroyed

3 Donated

4 Exchanged

5 Hire

6 Let

7 Not Disposed

8 Other

9 Sold

- Unknown

Table 26: Transaction Item Status

8.8. Report Code Type

The following is a list of reporting stream defined by the FIC.

Value Description

VDRT Voluntary Disclosure Report-Transaction (VDRT)

VDR Voluntary Disclosure Report (VDR)

TPR Terrorist Property Report (TPR)

STRB Suspicious Transaction Report Batch (STRB)

STR Suspicious Transaction Report (STR)

SAR Suspicious Activity Report (SAR)

S36T Section 36 Report-Transaction (SEC36T)

S36 Section 36 Report (SEC36)

ORI Outgoing Request For Information International (ORI)

ORD Outgoing Request For Information Domestic (ORD)

M Manual

IRI Incoming Request For Information International (IRI)

IRD Incoming Request For Information Domestic (IRD)

EFT Electronic Fund Transfer (EFT)

CTR Cash Threshold Report (CTR)

CCR Cash Conveyance Report (CCR)

CTRA Cash Threshold Report Aggregation (CTRA)

AIFT Additional Information File Transaction

TFAR Terrorist Financing Activity Report (TFAR)

TFTR Terrorist Financing Transaction Report (TFTR)

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

AIF Additional Information File (AIF)

- Unknown

Table 27: Report Code

8.9. Contact Type


Value Description

1 Business

2 Physical

Table 28: Contact Type

8.10. Communication Type


Value Description

1 Business Contact Tel

2 Business Fax

3 Business Mobile

4 Pager

5 Residential Contact Tel

6 Residential Fax

7 Residential Mobile

8 Satellite

9 Unavailable

- Unknown

Table 29: Communication Type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.11. Entity Legal Form Type


Value Description

1 Attorneys

2 Authorised Users Of Exchange

3 Banks

4 Close Corporation (CC)

5 Estate Agents

6 External Company

7 External Company Under Article 21

8 External Company Under Section 21A

9 External Non-Profit Company

10 False Company

11 Foreign Exchange

12 Foreign Legal Entity

13 Gambling - Bookmakers, Casinos Or Totes

14 Inc. (Inc.)

15 Investment Advisors Or Intermediaries

16 Issuers Of Traveller Cheques And Money Orders

17 Ithala

18 Kruger Rand Dealers

19 Limited By Guarantee (Limited By Guarantee)

20 Limited Registration

21 Long-Term Insurers

22 Money Lenders Against Securities

23 Money Remitters

24 Motor Vehicle Dealers

25 Mutual Banks

26 Non Profit Company (NPC)

27 Non-Profit Organisation (NPO)

28 Other Legal Entity

29 Partnership (PAR)

30 Postbank

31 Primary Cooperative (Primary Co-Operative Limited)

32 Private

33 Private Company (Pty) Ltd

34 Proprietary (Pty. Ltd. Registration)

35 Public

36 Public Company (Ltd)

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

37 Secondary Cooperative (Secondary Co-Operative Limited)

38 Shell Company

39 Sole Proprietor

40 State Owned Company (SOC Ltd)

41 Statutory Body

42 Tertiary Cooperative (Tertiary Co-Operative Limited)

43 Trading As (T/A)

44 Transvaal Ordinance

45 Trust

46 Trust Companies

47 Unit Trusts (Collective Investment Scheme Managers)

48 Unlimited (Unlimited)

- Unknown

Table 30: Legal Form Type

8.12. Transaction Item Type


Value Description

1 Antique (Qualifier)

2 Assets In RSA (Immovable)

3 Assets In RSA (Movable)

4 Assets Outside The RSA (Immovable)

5 Assets Outside The RSA (Movable)

6 Boat

7 Caravan (Mobile Home)

8 Coins

9 Electrical Equipment

10 Fire-Arms

11 Fixed Property

12 Furniture/Antique

13 Jet Ski

14 Jewellery

15 Kruger Rands

16 Livestock

17 Machinery

18 Other

19 Paintings (Art)

20 Property

21 Stock

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

22 Timeshare

23 Vehicles

- Unknown

Table 31: Transaction Item Type

8.13. Currencies

World Currencies (and their abbreviations) listed by ISO 4217

Value Description

AFN Afghan Afghani

AFA Afghani

DZD Algerian Dinar

ADF Andorran Franc (1:1 Peg To The French Franc)

ADP Andorran Peseta ENG

AOA Angolan Kwanza

AOR Angolan Kwanza Readjustado

ARL Argentine Peso Ley

ARS Argentinean Nuevo Peso

ARP Argentinean Peso

AWG Aruban Guilder

ARA Austral

AUD Australian Dollar

AZM Azerbaijani Manat

AZN Azerbaijani Manat

BSD Bahamian Dollar

BHD Bahraini Dinar

THB Baht

PAB Balboa

BBD Barbados Dollar

BYR Belarussian Rouble

BEF Belgian Franc (Also Known As Frank - No Longer In Use)

BZD Belize Dollar

BMD Bermudian Dollar

VEB Bolivar

BOV Bolivian Mvdol (Funds Code)

BOP Bolivian Peso

BOB Boliviano

BRN Brazilian Cruzado Novo

BRE Brazilian Cruzeiro

BRB Brazilian Cruzeiro Novo

BND Brunei Dollar

BGN Bulgarian Lev

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

BIF Burundi Franc

CAD Canadian Dollar

KYD Cayman Islands Dollar

GHC Cedi

CLP Chilean Peso

XTS Code Reserved For Testing Purposes

COP Colombian Peso

KMF Comorian Franc

CDF Congolese Franc

BEC Convertible Belgian Franc (No Longer In Use)

BAM Convertible Mark

NIC Córdoba

NIO Cordoba Oro

CRC Costa Rican Colón

HRD Croatian Dinar

HRK Croatian Kuna

BRC Cruzeiro

BRR Cruzeiro Real

CUC Cuban Convertible Peso

CUP Cuban Peso

CYP Cypriot Pound

CZK Czech Koruna

GMD Dalasi

DKK Danish Krone

KPW Democratic People's Republic Of Korean Won

DEM Deutsche Mark (No Longer In Use)

DJF Djibouti Franc

STD Dobra

DOP Dominican Republic Peso

AMD Dram

NLG Dutch Guilder (No Longer In Use)

XCD East Caribbean Dollar

XEU ECU (Not An Official Currency, Replaced By The Euro)

ECV Ecuador Unidad De Valor Constante (Funds Code) (Discontinued)

EGP Egyptian Pound

GQE Ekwele

SVC El Salvadorian Colón

ERN Eritrean Nakfa

CVE Escudo Caboverdiano

ETB Ethiopian Birr

EUR Euro (Replacement Name For The ECU)

XBA European Composite Unit

XBB European Monetary Unit

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

XBD European Unit Of Account 17

XBC European Unit Of Account 9

FKP Falkland Pound

FJD Fiji Dollar

BEL Financial Belgian Franc (No Longer In Use)

HUF Forint

DDM Former East German Mark, DEM Subsequently In Use

XAF Franc De La Communauté Financière Africaine

XPF Franc Des Comptoirs Français Du Pacifique

FRF French Franc (No Longer In Use)

GHS Ghanaian Cedi

GIP Gibraltar Pound

XAU Gold

XFO Gold Franc (Special Settlement Currency)

HTG Gourde

GRD Greek Drachma (No Longer In Use)

PYG Guarani

GWP Guinea-Bissau Peso

GNF Guinean Franc

GNE Guinean Syli

GYD Guyana Dollar

HKD Hong Kong Dollar

UAH Hryvna

ISK Icelandic Króna

ISJ Icelandic Old Krona

UKP Incorrectly Used For GBP

INR Indian Rupee

XDR International Monetary Fund Special Drawing Rights

PEI Inti

IRR Iranian Rial

IQD Iraqi Dinar

ILP Israeli Lira

ILR Israeli Shekel

ITL Italian Lira (No Longer In Use)

JMD Jamaican Dollar

JOD Jordanian Dinar

UAK Karbovanet

KES Kenyan Shilling

PGK Kina

LAK Kip

CSK Koruna Of Former Czechoslovakia.

EEK Kroon

KWD Kuwaiti Dinar

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

AOK Kwanza

MMK Kyat

KGS Kyrgyzstani Som

LAJ Lao Kip

GEL Lari

LVL Lats

LBP Lebanese Pound

ALL Lek

HNL Lempira

SLL Leone

BGL Lev

LRD Liberian Dollar

LYD Libyan Dinar

SZL Lilangeni

LTL Litas

LSL Loti

LUF Luxembourg Franc (No Longer In Use)

MKD Macedonian Dinar

MGA Malagasy Ariary

MGF Malagasy Franc

MWK Malawian Kwacha

MVQ Maldive Rupee

MLF Malian Franc

LSM Maloti

MTL Maltese Lira

MTP Maltese Pound, Replaced By Maltese Lira

FIM Markka (No Longer In Use)

MUR Mauritius Rupee

MZM Metical

MXN Mexican New Peso (Replacement For Mexican Peso)

MXP Mexican Peso, Replaced By Mexican New Peso

MXV Mexican Unidad De Inversion (UDI) (Funds Code)

MDL Moldavian Leu

MCF Monegasque Franc (Currency Union With FRF)

MAD Moroccan Dirham

MAF Moroccan Franc

MZN Mozambican Metical

NGN Naira

NAD Namibian Dollar

NPR Nepalese Rupee

ANG Netherlands Antilles Guilder

AON New Kwanza

PEN New Sol

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

CDZ New Zaïre

NZD New Zealand Dollar

PLN New Zloty

NFD Newfoundland Dollar

BTN Ngultrum

XXX No Currency

NOK Norwegian Krone

MKN Old Macedonian Denar A/93

OMR Omani Rial

MRO Ouguiya

TOP Pa'anga

PKR Pakistani Rupee

XPD Palladium (One Troy Ounce)

MOP Pataca

PEH Peruvian Sol

PHP Philippines Peso

XPT Platinum (One Troy Ounce)

PTE Portuguese Escudo (No Longer In Use)

GBP Pound Sterling (United Kingdom Pound)

BWP Pula

IEP Punt (No Longer In Use)

QAR Qatari Riyal

GTQ Quetzal

ZAR Rand

ZAL Rand (Financial)

BRL Real

ZRZ Replaced By CDZ

BUK Replaced By MMK

KRW Republic Of Korean Won

ZWC Rhodesian Dollar

KHR Riel

MYR Ringgit (Also Known As Malaysian Dollar)

ROL Romanian Leu

RON Romanian New Leu

MVR Rufiyaa

IDR Rupiah

RUB Russian Federation Rouble (Formerly RUR)

RUR Russian Rouble A/97

RWF Rwandan Franc

SML San Marinese Lira (Currency Union With ITL And VAL)

SAR Saudi Riyal

ATS Schilling (No Longer In Use)

CSD Serbian Dinar

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

RSD Serbian Dinar

SCR Seychelles Rupee

ILS Shekel

XAG Silver (One Troy Ounce)

SGD Singapore Dollar

SKK Slovak Koruna

PES Sol (Replaced By New Sol [PEN])

SBD Solomon Islands Dollar

SOS Somali Shilling

YDD South Yemeni Dinar

ESP Spanish Peseta (No Longer In Use)

ESA Spanish Peseta, Account A (No Longer In Use)

ESB Spanish Peseta, Account B (No Longer In Use)

LKR Sri Lankan Rupee

SHP St Helena Pound

ECS Sucre (No Longer In Use)

SDD Sudanese Dinar

SDG Sudanese Pound

SDP Sudanese Pound

SRG Surinam Guilder

SRD Surinamese Dollar

SEK Swedish Krona

CHF Swiss Franc

GNS Syli (Also Known As Guinea Franc)

SYP Syrian Pound

TWD Taiwan Dollar

TJR Tajik Rouble

TJS Tajikistani Somoni

BDT Taka

WST Tala

TZS Tanzanian Shilling

KZT Tenge

TPE Timorian Escudo

SIT Tolar

TTD Trinidad And Tobago Dollar

MNT Tugrik

TND Tunisian Dinar

TRL Turkish Lira

TRY Turkish Lira

TMM Turkmenistani Manat

TMT Turkmenistani Manat

UGS Ugandan Shilling

UGX Ugandan Shilling

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

XFU UIC Franc (Special Settlement Currency)

COU Unidad De Valor Real

CLF Unidades De Fomento

SUR Union Of Soviet Socialist Republics Rouble

AED United Arab Emirates Dirham

USD United States Dollar

USN United States Dollar (Next Day)

USS United States Dollar (Same Day)

- UNKNOWN

UYN Uruguay Old Peso

UYU Uruguayan New Peso

UYP Uruguayan Peso, Replaced By Uruguayan New Peso (UYU)

UZS Uzbekistani Som

VAL Vatican Lira (Currency Union With ITL And SML)

VUV Vatu

VEF Venezuelan Bolívar Fuerte

VND Viet Nam Dông

XOF West African Franc

CHW WIR Bank (Complementary Currency)

CHE WIR Bank (Complementary Currency)

YER Yemeni Riyal

JPY Yen

CNY Yuan Renminbi

YUG Yugoslav Dinar

YUM Yugoslav Dinar

YUN Yugoslav Dinar

YUO Yugoslav Dinar

YUR Yugoslav Dinar

YUD Yugoslavian New Dinar (No Longer In Use)

ZRN Zaïrean New Zaïre

ZMK Zambian Kwacha

ZWD Zimbabwe Dollar

ZWL Zimbabwe Dollar

ZWN Zimbabwean Dollar A/08

ZWR Zimbabwean Dollar A/09

PLZ Zloty (Replaced By New Zloty [PLN])

Table 32: Currency Codes

8.14. Country Codes

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.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

AF Afghanistan

OA African Intellectual Property Organization

AP African Regional Industrial Property Organization

AX Åland Islands

AL Albania

DZ Algeria

AS American Samoa

AD Andorra

AO Angola

AI Anguilla

AQ Antarctica_Eng

AG Antigua And Barbuda

AR Argentina

RA Argentina

AM Armenia

AW Aruba

AC Ascension Island

AU Australia

AT Austria

AZ Azerbaijan

BS Bahamas

BH Bahrain

BD Bangladesh

BB Barbados

BY Belarus

BE Belgium

BZ Belize

BX Benelux Trademarks And Designs Office

DY Benin

BJ Benin

BM Bermuda

BT Bhutan

BO Bolivia

RB Bolivia [Cf. Botswana: Identical Code Element]

BQ Bonaire, Saint Eustatius And Saba

BA Bosnia And Herzegovina

BW Botswana

BV Bouvet Island

BR Brazil

IO British Indian Ocean Territory

BN Brunei Darussalam

BG Bulgaria

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

BF Burkina Faso

BU Burma

BI Burundi

KH Cambodia

CM Cameroon

CA Canada

IC Canary Islands

CV Cape Verde

KY Cayman Islands

CF Central African Republic

EA Ceuta, Melilla

TD Chad

CL Chile

CN China

RC China

CX Christmas Island

CP Clipperton Island

CC Cocos (Keeling) Islands

CO Colombia

KM Comoros

CG Congo

CD Congo, The Democratic Republic Of The

CK Cook Islands

CR Costa Rica

CI Cote D'ivoire

HR Croatia

CU Cuba

CW Curaçao

CY Cyprus

CZ Czech Republic

DK Denmark

DG Diego Garcia

DJ Djibouti

DM Dominica

DO Dominican Republic

TP East Timor

EC Ecuador

EG Egypt

SV El Salvador

GQ Equatorial Guinea

ER Eritrea

EW Estonia

EE Estonia

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

ET Ethiopia

EV Eurasian Patent Organization

EP European Patent Organization

EM European Trademark Office

EU European Union

FK Falkland Islands (Malvinas)

FO Faroe Islands

FJ Fiji

FI Finland

SF Finland

FR France

FX France, Metropolitan

GF French Guiana

PF French Polynesia

TF French Southern Territories

GA Gabon

GM Gambia

GE Georgia

DE Germany

GH Ghana

GI Gibraltar

GR Greece

GL Greenland

GD Grenada

WG Grenada

GP Guadeloupe

GU Guam

GT Guatemala

GG Guernsey

GN Guinea

GW Guinea-Bissau

GY Guyana

HT Haiti

RH Haiti

HM Heard Island And Mcdonald Islands

VA Holy See (Vatican City State)

HN Honduras

HK Hong Kong

HU Hungary

IS Iceland

IN India

ID Indonesia

RI Indonesia

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

IB International Bureau Of Wipo

IR Iran, Islamic Republic Of

IQ Iraq

IE Ireland

IM Isle Of Man

IL Israel

IT Italy

JA Jamaica

JM Jamaica

JP Japan

JE Jersey

JO Jordan

KZ Kazakhstan

KE Kenya

KI Kiribati

KP Korea, Democratic People's Republic Of

KR Korea, Republic Of

KS Kosovo

KW Kuwait

KG Kyrgyzstan

LA Lao People's Democratic Republic

LV Latvia

LB Lebanon

RL Lebanon

LS Lesotho

LR Liberia

LF Libya Fezzan

LY Libyan Arab Jamahiriya

LI Liechtenstein

FL Liechtenstein

LT Lithuania

LU Luxembourg

MO Macao

MK Macedonia, The Former Yugoslav Republic Of

MG Madagascar

RM Madagascar

MW Malawi

MY Malaysia

MV Maldives

ML Mali

MT Malta

MH Marshall Islands

MQ Martinique

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

MR Mauritania

MU Mauritius

YT Mayotte

MX Mexico

FM Micronesia, Federated States Of

MD Moldova, Republic Of

MC Monaco

MN Mongolia

ME Montenegro

MS Montserrat

MA Morocco

MZ Mozambique

MM Myanmar

NA Namibia

NR Nauru

NP Nepal

NL Netherlands

AN Netherlands Antilles

NT Neutral Zone

NC New Caledonia

NZ New Zealand

NI Nicaragua

RN Niger

NE Niger

NG Nigeria

NU Niue

NF Norfolk Island

MP Northern Mariana Islands

NO Norway

OM Oman

PK Pakistan

PW Palau

PS Palestinian Territory, Occupied

PA Panama

PG Papua New Guinea

PY Paraguay

GC Patent Office Of The Cooperation Council For The Arab States Of The Gulf (Gcc)

PE Peru

PH Philippines

PI Philippines

RP Philippines

PN Pitcairn

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

PL Poland

PT Portugal

PR Puerto Rico

QA Qatar

RE Reunion

RO Romania

RU Russian Federation

RW Rwanda

BL Saint Barthélemy

SH Saint Helena

KN Saint Kitts And Nevis

LC Saint Lucia

WL Saint Lucia

MF Saint Martin (French Part)

PM Saint Pierre And Miquelon

WV Saint Vincent

VC Saint Vincent And The Grenadines

WS Samoa

SM San Marino

ST Sao Tome And Principe

SA Saudi Arabia

SN Senegal

RS Serbia

CS Serbia And Montenegro

SC Seychelles

SL Sierra Leone

SG Singapore

SX Sint Maarten (Dutch Part)

SK Slovakia

SI Slovenia

SB Solomon Islands

SO Somalia

ZA South Africa

GS South Georgia And The South Sandwich Islands

ES Spain

LK Sri Lanka

SD Sudan

SR Suriname

SJ Svalbard And Jan Mayen

SZ Swaziland

SE Sweden

CH Switzerland

SY Syrian Arab Republic

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

TW Taiwan, Province Of China

TJ Tajikistan

TZ Tanzania, United Republic Of

TH Thailand

TL Timor-Leste

TG Togo

TK Tokelau

TO Tonga

TT Trinidad And Tobago

TA Tristan Da Cunha

TN Tunisia

TR Turkey

TM Turkmenistan

TC Turks And Caicos Islands

TV Tuvalu

UG Uganda

UA Ukraine

EF Union Of Countries Under The European Community Patent Convention

AE United Arab Emirates

GB United Kingdom

UK United Kingdom

US United States

UM United States Minor Outlying Islands

- Unknown

UY Uruguay

SU Ussr

UZ Uzbekistan

VU Vanuatu

YV Venezuela

VE Venezuela

VN Viet Nam

VG Virgin Islands, British

VI Virgin Islands, U.S.

WF Wallis And Futuna

EH Western Sahara

WO World Intellectual Property Organization

YE Yemen

YU Yugoslavia

ZR Zaire

ZM Zambia

ZW Zimbabwe

Table 33: Country Codes

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.15. account_person_role_type

* The following list is a suggestion. .

Value Description

1 Account holder

2 Beneficiary

3 Co-account holder

4 Contact person

5 Responsible person

6 Signatory

- Unknown

Table 34: Account Person Role Type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.16. entity_person_role_type

*The following list is a suggestion. .

Value Description

1 Accountant

2 Alternate Director

3 Audit Committee Member

4 Auditor

5 Board Member

6 Both Director/Officer

7 Chairman Of The Board

8 Chief Executive Officer

9 Chief Operation Officer

10 Company Secretary (Natural Person)

11 Compliance Officer

12 Co-Owner

14 Director (Companies And CC)

15 Employee

16 Executor

17 External / Overseas

18 Financial Director

19 Founding Member

20 Incorporator

21 Joint Executor

22 Legal Representative

23 Local Managers

24 Manager

25 Member

26 Money Laundering Reporting Officer

27 Non-Executive Director

28 Non Executive Independent Director

29 Officer

30 Other Trustee

31 Owner

32 Partnership

33 Primary/Secondary Founding Member

34 Representative

35 Representative Trustee

36 Responsible Person

37 Secretary Company/Close Corporation

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



38 Shareholder

39 Signatory

40 Testamentary Trust

41 Trust

42 Trustee

A Director

- Unknown

Table 35: Entity Person Role Type

8.17. party_role


Value Description

XSH Source Primary Person

XSE Source Entity

XS Source Party

XDH Destination Primary Person

XDE Destination Entity

XD Destination Party

XC Conductor

B Beneficiary/Recipient

A Payer/Sender

- Other

Table 36: Party Role Type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



8.18. Report indicator

The following is the list defined by the FIC for use to be used when reporting indicator.

Value Description

- Other

RIND001 Account Accessed Overseas: Account was either issued with a supplementary card, or the primary card is being used by someone other than the account holder to access funds abroad

RIND002 Activity does not match client profile or expected transacting patterns

RIND003 Adverse reports - international

RIND004 Adverse reports on commercial databases

RIND005 Adverse reports on local press

RIND006 Appear on sanction/watch list(s)

RIND007 Arms trafficking

RIND008 Automated rules based account monitoring

RIND009 Cash Conveyance Report (CCR) in terms of Section 30 of the FIC Act 38 of 2001

RIND010

Cash Threshold Report (CTR) in terms of Section 28 of the FIC Act 38 of 2001 when the report contains unrelated transactions whereby each transaction on its own has exceeded the threshold and no aggregation is demonstrated

RIND011 Corruption- General corruption allegations, usually aimed towards the service provider and not the benefactor

RIND012 Corruption/Bribery

RIND013 Counterfeiting and piracy of products

RIND014 Counterfeiting of currency

RIND015 Counterfeit Note: A counterfeit note was discovered, typically at a casino

RIND016 Denomination conversion

RIND017 Drug Mule- Person has previously been convicted or suspected of involvement in drug trafficking

RIND018 Drug trafficking

RIND019 Electronic funds transfer (EFT) in terms of section 31 of the FIC Act 38 of 2001

RIND020 Environmental crime

RIND021 Extortion

RIND022 Filed as a result of a request for info from the South African Reserve Bank

RIND023 Filed as a result of a subpoena received in relation to a fraud investigation/case

RIND024 Filed as a result of a subpoena received in relation to a theft investigation/case

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

RIND025 Forex Related- Persons usually sending large amounts of cash abroad, typically using a forex dealer

RIND026 Forgery

RIND027 Fraud

RIND028 Fraud: Change of Banking Information

RIND029 Fraud: ATM

RIND030 Fraud: Cheque- Cheques are either stolen or altered to reflect new beneficiaries

RIND031 Fraud: General- General indication of fraud, but no specific details as to the type of fraud perpetrated

RIND032

Fraud: Advance Fee- Also known as a 419 scam. Promises of a reward or service in exchange for an upfront fee. Reward or service never materialises. These have included sms notices of lotto winnings, advertising of goods for sale that don't exist, promises of large funds

RIND033

Fraud: Beneficiary Maintenance- A notice (usually in e-mail form) is sent to a company or business, informing them that one of their service providers have changed banking details and all future payments need to be paid into a new bank account. This turns out to be false and payment is

RIND034

Fraud: Credit Application- Fraudulent supporting documentation is provided for access to credit. Not to be confused with KYC fraud, where false or stolen KYC documents are used to open bank accounts for the purpose of hiding the true account transactor‘ s identity

RIND035

Fraud: Deposit Refund- Funds are paid into a service provider’s account, usually by cheque. The service provider is contacted and informed that more was paid into the account, than what was quoted and the extra funds are requested back. Service provider pays the extra funds

RIND036 Fraud: Internet deposit- While the internet is given as the mode used to commit fraud, the specific type of fraud isn't indicated

RIND037 Fraud: KYC- Knowingly or unknowingly, a person's identity is used to open an account for a third party, who then transacts on that account as if it belonged to them

RIND038 Fraud: Phishing- Unauthorised access via the internet, to the victim's bank account. Funds are then stolen and transferred from the victim to the perpetrator.

RIND039

Fraud: Pyramid Scheme- A pyramid scheme involves the payment of an access fee to a wealth building initiative, followed by the recruitment of new investors in order to move up the pyramid. While the sale of products might be involved, the main intention is the recruitment of investors

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

RIND040 Fraud: Speedpoint- Speedpoint machines in stores are used to either put through false transactions, or refund transactions that did not exist

RIND041 Fraud: Tender- Involves the suspicion that tenders were awarded to service providers through collusion, interference or favouritism. Involves a government department

RIND042 Gautrain related payments- Gautrain related payments

RIND043 Hawala

RIND044 Home loan abuse- Home loan accounts which see elevated account activity, usually with the intention of avoiding tax responsibilities

RIND045 Huge cash deposits

RIND046 Human trafficking/smuggling of migrants

RIND047 Illicit arms trafficking

RIND048 Illicit trafficking in stolen and other goods

RIND049 Increased Account Activity- Account monthly turnover shows an increase from previous months

RIND050 Insider trading and market manipulation

RIND051 Involves international Politically Exposed Person (PEP)

RIND052 Involves local Politically Exposed Person (PEP)

RIND053 Kidnapping, illegal restraint, hostage-taking

RIND054

Kite flying- The rapid transfer of funds between accounts, for the purpose of increasing the balance in the involved accounts and thereby allowing access to increased credit facilities, based on a false account turnover

RIND055 Large cash deposit

RIND056 Large cash deposits (multiple cash deposits)

RIND057 Large casino winnings

RIND058 Large cheque deposits

RIND059 Large credit card transfer

RIND060 Large deposit

RIND061 Large electronic funds transfer

RIND062 Large inter account transfers- Could potentially be kite flying, or for tax avoidance purposes

RIND063 Large internet transfers

RIND064 Large Inwards Transfers- Funds are received from abroad into a South African account, without adequate explanation of the source of funds

RIND065 Large Outwards Transfers- Funds are sent abroad from a South African account, without adequate explanation as to the source of funds.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

RIND066

Minor Account Abuse- An account is opened for a minor, but controlled by a third party (usually a parent or guardian). This account is used for business related activity, so as to avoid tax responsibilities

RIND067 Money laundering

RIND068 MoneyGram related

RIND069 M-Pesa related

RIND070 Murder, grievous bodily injury (for profit)

RIND071 Online gambling where internet service provider is situated outside South Africa’s borders

RIND072 Online gambling where internet service provider is situated within South Africa

RIND073 Other

RIND074 Other theft

RIND075 Piracy (does not include counterfeiting)

RIND076

Ponzi Scheme- An investment scheme where payments received are used to pay promised dividends to earlier investors. Not to be confused with a pyramid scheme, where the investors are aware of the structured repayment scheme employed.

RIND077 Proliferation

RIND078 Rapid Disposition of Funds- Funds enter and leave an account in quick succession. Could be done to layer funds, or to avoid tax responsibilities

RIND079 Regular cash deposits

RIND080 Regular casino play

RIND081 Related (by means of business relationships and/or family member) to a Politically Exposed Person (PEP).

RIND082 Relates to Western Union product

RIND083 Report filed as a result of a request for information/subpoena from law enforcement agency

RIND084 Rhino horn/poaching

RIND085 Robbery

RIND086 SARS (including eFiling) payments are either redirected to other bank accounts, or false tax returns are submitted in order to gain access to elevated returns

RIND087 Sexual exploitation/prostitution

RIND088 Smuggling (diamonds, gold, minerals, precious & semi-precious minerals, protected resources)

RIND089 Smurfing

RIND090 Stock theft

RIND091 Structuring

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



Value Description

RIND092 Suspicious Activity Report (SAR) in terms of Section 29 of the FIC Act 38 of 2001

RIND093 Suspicious cash deposit

RIND094 Suspicious Transaction Report (STR) in terms of section 29 of the FIC Act 38 of 2001

RIND095 Tax evasion

RIND096 Terrorism

RIND097 Terrorist Property Report (TPR) in terms of Section 28A of the FIC Act 38 of 2001

RIND098 The diversion or illegal access to government funds by employees

RIND099 Theft

RIND100 Theft of explosives

RIND101 Theft of firearms

RIND102 Third party access to account

RIND103 Transactions occurred in contravention of SARB regulations.

RIND104 Transfer of funds between accounts

RIND105 Unexplained account activity

RIND106 Filed as a result of a request for info from a Supervisory Body in terms of the FICA Schedule Item(s)

RIND107 Relates to money remitter product

RIND108 Additional Information File (AIF) in response to Section 32 of FIC Act 38 of 2001

RIND109 Terrorist Financing Activity Report (TFAR) in terms of section 29 of the FIC Act 38 of 2001

RIND110 Terrorist Financing Transaction Report (TFTR) in terms of section 29 of the FIC Act 38 of 2001

RIND111 Cash Threshold Report Aggregation(CTRA) in terms of Section 28 of the FIC Act 38 of 2001 when the report includes aggregated transactions as per FIC regulations

Table 37: Report Indicator Type

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



9. Annexure

9.1. Business Rules

The section below specify business rules that should be incorporated and

implemented by the FIC stakeholders into their builds in order to avoid submitted

reports from being rejected. Please note that these are subject to the review

process and may result in changes or additions.

The rules have been categorised for ease of read into two categories:

o Rules applied at all levels;

o Rules applied at report level;

o Rules applied at activity level; and

o Rules applied at transaction level.

9.1.1. Rules / Guidance on reporting

These are set of rules and guides that are applicable to all reports and how

they should be captured:

No Rule Description

1

All applicable fields must be completed without any special

characters such as ", -, +, =, _,/, \, [, ], {, }, *,#, etc. including

fictitious values.

2

Limit the space in sentences to one (1) space between words where

descriptions and explanations are provided such as in the “Reason

of suspicion” and/or “Action” fields and conform to sentence case

format.

3

XML Batch reporting will be limited to transaction based reports,

which include AIFTs, CTRs, CTRAs, EFTs, STRs, TFTR and

VDRTs.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



No Rule Description

4

Activity reporting will be captured and submitted via the web and

includes SARs, TPRs and VDRs. Activity-based reports refers to

activities where a transaction(s) was/were attempted, unsuccessful,

interrupted, incomplete, corrected, reversed and/or cancelled, etc.

5

Intelligence reports must be captured in line with the prescriptions of

the FIC Act, under no circumstances may one report type be used to

report multiple or other specified reporting obligations (e.g. – CTR

reporting only covers the requirements under Section 28 of the FIC

Act, obligations under Section 29 will have to be captured separately

as an STR or SAR as per the guidelines and prescriptions of the FIC

Act). Each reporting obligation must be reported to the FIC in line

with the prescribed reporting format and XML Schema.

6

All responses in terms of Section 24, 26, 27, 32, 34 and/or 35

respectively of the FIC Act will have to be submitted by means of the

Additional Information File (AIF) in the prescribed format and as per

the guidelines issued by the FIC. Note that pdf documents will only

be accepted when submitting copies of identification documents,

copies of bank opening documents and other applicable Know Your

Customer (KYC) documents respectively.

7

In cases where lookups and/or reference tables are provided for

selection, ONLY values from the applicable lookup or enumeration

list will be accepted, no other data input/values/selection may be

accepted. Please advise the FIC through the established channels if

lookups and/or reference tables need to be expanded and all

approved requests will be implemented accordingly in line with the

FIC’s processes and procedures.

8 Date of Birth (DOB) and Date fields must contain valid dates. Future

dates or default date values will be rejected. All date values must

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



No Rule Description

comply with the format as defined in the XML Schema Definition

(XSD).

9

The values for date field or elements must aligned to the regional

settings (English South Africa) and that user PCs are set-up

accordingly.

10

The South African ID Number(ID) may be used to interpret

information from as stated below and this should subsequently be

captured by the reporting entities:

i. First 6 ID digits= Date Of Birth [yyyymmdd]

ii. 7th ID digit: 0-4 = female, 5-9 = male

iii. 11th ID digit: 0 = South African citizen, 1 = foreigner

9.1.2. Report Level Rules

These are set of rules that are applied at a report level. If these rules are not

adhered to, the XML report will be rejected in its entirety and would be

deemed not to have been successfully submitted.

No Rule Description

1

All intelligence reports have to have an applicable “Report Indicator”

selected, and where applicable, more than one “Report Indicator”

may be provided (minimum of one “Report Indicator” per intelligence

report- excluding the “Unknown” descriptor). Note that this is

applicable for all intelligence report types captured/filled either in

batch and/or via the web-based reporting portal. “Report Indicators”

reference tables will be provided by the FIC and must be used

accordingly (please refer to section 9 of the document for the

values).

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



No Rule Description

2

All STRs/STRBs//SARs, TPRs/TPRTs and VDRs/VDRs respectively

will have a “Reason” and an “Action” field respectively which are free

text descriptions and must be completed as per the prescribed

format (Sentence Case) and as per the guidelines issued by the FIC.

Note that the “Reason” and/or “Action” field should NOT be used to

hold any additional/new client (s) [an account (s), person (s) and/or

entity (ies)] information. All information pertaining to a client, whether

or not “my_client” and/or “client” must be captured in the prescribed

fields. "Reason" and “Action” fields are mandatory for Suspicious

Activity Report (SAR), Suspicious Transaction Report (STR),

Suspicious Transaction Report Batch (STRB), Terrorist Financing

Activity Report (TFAR) and Terrorist Financing Transaction Report

(TFTR).

3

No document attachments may be used to describe the information

that is applicable to the “Reason” and/or “Action” fields respectively-

all information will have to be completed on the report in the

applicable fields.

9.1.3. Activity Level Rules

The section below list rules that are applicable at for non-transaction based

reporting, they are also applicable wherein both an activity and transaction is

involved.

No Rule Description

1

Fields or elements used to hold First_name, middle_name,

third_name and last_name should not include numerics and special

charaters, i.e. -,\?/=+#!$%*~`():;{}|* and should be captured in the

appropriate fields.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



No Rule Description

2

RSA-ID Number must be thirteen (13) digits for SA nationals and

must be captured in the SSN field or element and must be provided

for all South African nationals.

3

Foreign nationals’ Passport Number/ Foreign ID Number/ Permit

Number/ Refugee Number/ Residence Number should be captured

in the Passport Number field or element. For non-South African

nationals included in the report or registration, their identification

number, i.e. Passport Number/ Foreign ID Number/ Permit Number/

Refugee Number/ Residence Number and the issuing country

details must be provided. Note that:

a) “Passport” refers to “Non South- African Identity

Document”

b) “Passport Number” refers to “Foreign Passport/ Foreign

ID/ Permit/ Refugee/ Residence Number”

c) “Passport Country” and “Issuing Country” are used

synonymously.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



9.1.4. Transaction Level Rules

The section below list rules that are applicable at transaction level involved in

reporting.

No Rule Description

1

All intelligence reports should always include at least one selection

i.e. “my_client” (account and/or person and/or entity). The definition

of the term “my_client” is intended to include both South African and

non-South African citizens and/or residents, thus all natural and

legal persons, entities, companies and institutions, and should

furthermore be interpreted against the requirements as set out in

Section 21, 22, 23 and/or 26 respectively of the FIC Act.

2

Reporting entities need to provide all available information in relation

to the “my_client” and/or “client” (account and/or person and/or

entity) fields respectively, and the use of “Unknown” should be

limited to information sets which are not held by the Reporting

entities. Note that the use of “Unknown” may imply subsequent

additional requests for information from the FIC as per the mandate

set out in the FIC Act, and it is recommended that the Reporting

entities provide all available information in as much detail possible

upfront when submitting the report to avoid unnecessary follow up

requests in relation to the submitted reports.

3

An EFT must be across the borders of the Republic of South Africa.

At least one of the parts of an EFT report (“TO” or “FROM”) will have

to list the “Currency Code” for the international

portion/conversion/amount of the transaction.

4

Fields or elements used to hold First_name, middle_name,

third_name and last_name should not include numerics and special

characters, i.e. -,\?/=+#!$%*~`():;{}|* and should be captured in the

appropriate fields.

goAML EE Project


Version: 4.2.1

Date: 15/04/2016 of 96



No Rule Description

5

RSA-ID Number must be thirteen (13) digits for SA nationals and

must be captured in the SSN field or element and must be provided

for all South African nationals.

6

Foreign nationals’ Passport Number/ Foreign ID Number/ Permit

Number/ Refugee Number/ Residence Number should be captured

in the Passport Number field or element. For non-South African

nationals included in the report or registration, their identification

number, i.e. Passport Number/ Foreign ID Number/ Permit Number/

Refugee Number/ Residence Number and the issuing country

details must be provided. Note that:

a) “Passport” refers to “Non South- African Identity Document”

b) “Passport Number” refers to “Foreign Passport/ Foreign ID/

Permit/ Refugee/ Residence Number”

c) “Passport Country” and “Issuing Country” are used

synonymously.

goAML XSD Specification ver. 4.2.1 goAML EE Project EE FIC Schema V4.2.1 Specification.pdf ·...

Documents

Transcript of goAML XSD Specification ver. 4.2.1 goAML EE Project EE FIC Schema V4.2.1 Specification.pdf ·...