Comparison between goAML schema 4.0 vs goAML schema 3.1

Activity

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

Parent Node / Element / Diagram
report_party / A new type to describe the involved parties in a report activity. The party could be a person, an account or an entity. In addition, the type includes a numeric significance field and two description fields: reason and comments. /
Person / Alias
Any alias of the person, known as … /
Passport_number + passport_country
This element should be used to report the main passport number and the issuing country. Having it here will allow goAML to use passport information as part of the unification keys during integration. Passport_country can be reported only if passport_number is provided. /
id_number
Additional identification keys can be used as part of the unification keys. So in total goAML will allow the FIU to set its unification rules based on 3 identification numbers: SSN, passport number and an additional number. /
Deceased + date_deceased
A new boolean flag to indicate if the subject is deceased and (if the date is known) to be reported as “date_deceased”. /
Tax_number
The person tax number
Tax_reg_number
The person tax reg. number by tax authorities.
Comments
Generic comments field /
Person / Source_of_wealth
Free text description of the person source of wealth /
Account / role
A new element to specify the actual relationship of the subject to the account: like Beneficiary, Co-Holder, Primary Holder, Joint holder, ..,etc. The list is controlled by a dedicated enumeration list driven from the matching lookup table. /
Date_balance
A date field to specify the date of the reported balance. Application will show balance history. /
Comments
New generic comments field /
Entity / Role
A new optional element “role” element was added to director_id node to allow reporting entities to specify the exact role of the reported person in the entity(directorships, shareholdings, beneficial, trustee, accountant, signatory, etc. ). The values are controlled by a dedicated enumeration list driven from the matching lookup table. /
Commercial_name
The “traded as” name of the entity /
Incorporation_number
The element length was extended to 50 chars. /
Incorporation_date
Incorporation registration date /
Business_closed + date_business_closed
Boolean to indicate if the company is closed down and if true to specify the date it closed down, if available. /
Tax_number
The entity tax number
Tax_reg_number
The entity tax reg. number by tax authorities.
Comments
Generic comments field /
t_transaction / From_entity
Entity can now be a direct party on bi-party transaction both as source party as well as destination party
To_entity
Entity can now be a direct party on bi-party transaction both as source party as well as destination party /

Comments
Generic comments field /
t_party / role
The type of the Role element is an enumeration field now /
significance
A new optional element to show a numeric scale of the current party significance in the report ( 0 – 10) /
comments
New generic comments element /
t_address / Town
Name of Town/district/.. as part of a City /
comments
New generic comments element /
t_phone / comments
New generic comments element /

Lookups

Two major changes were done for lookups in this version:

·  Several “lookup like”, free text fields in the schema were previously handled inside the application as lookups, but caused problems due to size limitations. Those elements will no longer be handled as lookups, but as simple free text fields as they are reported in the schema. The list contains following elements:

o  City

o  State

o  Person Occupation

o  Entity Business

o  Transaction Item maker

o  Person Identifier Issuer.

·  All actual lookups in the schema have been restricted as enumerations instead of flexible A-Za-z0-9, 5 chars elements. The advantage of this change is that the system will enforce the mapping between lookups definition in goAML client application and the Schema. Reporting entities will not be able anymore, to submit a transaction with account type “K” for example, where the relevant lookup table contains “A”, “B” and “C” only. However, taking inot account the complexity of maintaining the sync between the lookup tables and the Schema, we decided to introduce such functionality in the next release. goAML users just need to click a button in “Lookup Master” screen in order to sync the lookup tables with the matching schema enumerations.

/ Page 8 of 8 /