Standard Reporting Instructions and Specifications for
XML Reports (CTR/EFT/IFT Reports)
UNODC Version 4.0.2
FIU-SL Version 1.1.10
Last Update: 04-June-2021
This document is a composite of UNODC documentation on goAML (version 4.0.2) and modifications made
by the Financial Intelligence Unit of Sri Lanka (FIU)
.
.
Version number = [schema changes by the UNODC] [element level changes by the FIU] [minor changes
by the FIU]
UNODC
Rev.
FIU-SL
Rev.
4.0.2
1.0.0
Date
Author
June 20, 2019
Kosala Harshadewa
Description
First amendment to the UNODC general XML
schema documentation, customizing it to the
requirements of the FIU-SL.
Provided more clarifications where necessary,
and restructured the numbering format.
Provided details on the elements which are
mandatory for certain report types (business
rule validation).
Converted following optional fields in the
schema to mandatory elements, as per the
CDD Rule requirements:
• “transaction” element:
“internal_ref_number”, “transaction_location”,
“transaction_description”, “value_date”
• “t_account_my_client” element:
“institution_name”, “branch”,
“currency_code”, “personal_account_type”,
“status_code”
• “t_account” element
“institution_name”
• “t_entity_my_client” element
“incorporation_legal_form”,
incorporation_number, “business”, phones”,
“addresses”, “incorporation_country_code”,
“director_id”
• “t_person_my_client”
“birthdate”, “addresses”, “nationality1”,
“residence”, “occupation”, identification”
1.0.0
June 24, 2019
Kosala Harshadewa
• “account_name” field in “t_account” element
was made mandatory, to identify the account
with the account holder
• Included following Conduction Type codes:
AZ – Interest payment
BA – Tax payment
1.0.0
July 01, 2019
Kosala Harshadewa
• Corrected description for Entity in page 8 for
“director_id” element (type “t_person” for both
my client and not my client)
1.1.0
July 15, 2019
Kosala Harshadewa
• Main objective is to simplify the schema and
limit it for the CTR/EFT/IFT reports only
• Removed following unnecessary elements
from the documentation
June 2021 (2 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
- report_indicators
- activity
- t_party
- report_party_type
• Crossed out several unnecessary
fields/elements in the other elements of the
schema
• Removed “conductor” element from the
“t_from_my_client” and “t_from” elements
1.1.0
July 17, 2019
Kosala Harshadewa
• Amend the description in the summary
sections to restrict the document to
CTR/EFT/IFT reports and to remove
references to the not used elements.
• Made “phone” element optional in the
“t_entity_my_client” element
• Added value “Permanent” to the “Contact
Type” enumerated list and removed “State
owned company” form the “Entity Legal
Form” enumerated list
1.1.0
July 23, 2019
Kosala Harshadewa
• Made “commercial_name” of
“t_entity_my_client” and “t_entity” elements
optional from “not required” state
1.1.0
July 29, 2019
Kosala Harshadewa
• Modified requirement for “director_id”
element in “t_entity_my_client” and “t_entity”
elements to directors and shareholders of
more than 10% share ownership.
1.1.1
August 01,
2019
(First Issue)
Kosala Harshadewa
• Assigned types of unique transaction
numbers for RTGS, SLIPS, CEFTS and
SWIFT transactions in the “transaction”
element.
• Added codes “BB” to “BH” for Conduction
Type lookups list.
• Made “account_name” mandatory in
“t_account_my_client” to be consistent with
“t_account”.
1.1.2
August 06,
2019
Kosala Harshadewa
• Amended description for “director_id”
element in “t_entity_my_client” and “t_entity”
elements to report as per table 9.1
• Added Table 9.1 to map role types to entity
types.
• Added codes “M” and “N” for Entity Person
Role Type lookups list.
1.1.2
August 08,
2019
Kosala Harshadewa
• Amended description for “account_name” in
“t_account_my_client” to include “generic
account” as account name.
1.1.2
September 02,
2019
(Second Issue)
Kosala Harshadewa
• Amended description for “transactionnumber”
in “transaction” element and included Unique
Reference number formula for inter-bank
transactions in the Schedule.
June 2021 (3 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
1.1.3
September 04,
2019
(Third Issue)
Kosala Harshadewa
• Correction for missing SWIFT/RTGS
Transaction Reference Number in second
issue
• Included Transaction Reference Number in
Table 32 (Section 6.1) for SWIFT/RTGS
messages
1.1.4
October 18,
2019
(Fourth Issue)
Kosala Harshadewa
• Amended description for “to_funds_code” in
Table 5 and Table 6 to be in line with
analytical reporting model (funds converted
from one type to another).
• Amended description for
“transaction_location” in Table 2 to make it
applicable only for “Branch” level
transactions.
• Introduced new values for “Funds Type”
(Table 5.2), “Account Type” (Table 5.3) and
“Conduction Type” (Table 5.6) as per the
analytical reporting model.
• Modified codes in tables in Section 5 in
alphabetical order (A,B,C, …) for consistency.
• Introduced new formula to generate unique
reference numbers for the SLIPS transactions
in Table 32 (Section 6.1).
• Minor amendments to the description of some
fields for better clarity.
• Made the “nationality2” field of the
“t_person_my_client” optional from the
previous “do not use” status (Table 7).
• Changed institution type “State Owned
Department” to “Government Institution” and
“State Owned Corporations” to “State Owned
Enterprises” in Section 5.10 Entity Legal
Form Type (Table 26), and amended Table
9.1 accordingly.
• Removed the requirement to report
“signatory” and “t_entity” elements for
“t_account” element.
1.1.5
October 31,
2019
(Fifth Issue)
Kosala Harshadewa
• Corrected description for “Account” under
“Structure of the XML Reports” in Section 1
“Summary”, by removing “t_account” wording.
• Amended description for
“transaction_location” in Table 2 to select
either transacted branch or account
maintained branch.
1.1.6
January 16,
2020
(Sixth Issue)
Kosala Harshadewa
• Most of the crossed-out elements (do not use
elements) in the schema were converted to
optional elements.
• Several fields were converted to “conditional
mandatory” option from “mandatory” or
“optional” condition for validation by business
rules (marked as “C” in field tables).
• SAR report type was removed.
• Allowed reporting of multi-party transactions.
June 2021 (4 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
• Described the options to upload several XML
files to the goAML web, either one by one, or
in a ZIP file.
• Changed codes for Lookups (Section 5) and
value added for virtual currencies. Removed
“Online” and “Mobile” values and added value
“Other” for country codes.
• Introduced transaction reference number
format for cash transactions.
“report” element
• “entity_reference” and “report_indicators”
fields in the “report” element made
mandatory.
“transaction” element
• “internal_ref_number” and “value_date” fields
made optional.
• “transaction_location” filed made conditional
mandatory for in-branch transactions and
credit/debit card transactions.
• Introduced multi-party transaction model to
report special types of transactions such as
credit/debit cards and cheques.
• Table added to illustrate all combinations of
Persons, Accounts, Entities (PAEs) in biparty model.
“t_person_my_client” element
• Introduced new format for “first_name” field to
provide full name (except last name).
• “last_name” field made upper case.
• Removed “middle_name” and “prefix” fields.
• “id_number” field made mandatory and only
for SL persons, and provided format.
• “identification” element made mandatory for
foreign persons with passports, and optional
for SL persons.
“t_person_element”
• Introduced new format for “first_name” field to
provide full name (except last name).
• “last_name” field made upper case.
• Removed “middle_name” and “prefix” fields.
• “id_number” field made mandatory and only
for walk-in SL persons, and provided format.
“t_entity_my_client”/”t_entity”
• “incorporation_number” field made
conditional mandatory for registered entities.
June 2021 (5 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
“t_account_my_client”
• “account_name” field made optional.
• “signatory” element made optional for entity
accounts.
“t_account”
• “account_name” field description changed
and made optional.
“t_address”
• Format for “address” and “town” fields
changed for clarity.
“t_phone”
• “tph_country_prefix” made mandatory.
• Format provided for SL numbers for
“tph_number”.
1.1.7
January 17,
2020
(Seventh Issue)
Kosala Harshadewa
Included description for “t_party” element type,
and provided list for party types.
1.1.8
August 10,
2020
Kosala Harshadewa
• Revised definition for “rentity_id” in “report”
element, and “institution_code” in
“t_account_my_client” and “t_account”
elements for the usage of entity ID assigned
by the goAML system.
• Revised lookup lists for “Funds Type”,
“Conduction Type”, and “Account Type” for
inclusion of new values.
• Provision included to use any transaction
reference as the Unique Reference Number
where format given in Table 34 cannot be
implemented (due to technical limitations).
• Currency List (Lookup List 5.11) and Country
List (Looup List 5.12) were updated for the
latest ISO 4217 and ISO 3166 Alpha-3
Codes.
• City list provided for “city” field in “t_address”
element.
1.1.9
February 17,
2021
Kosala Harshadewa
• Included “director_id” element description for
“t_entity_my_client” elements.
• Removed the usage of “identification”
element in “t_person_my_client” and
“t_person” elements.
• Conditionally mandated “id_number” and
“passport_number” in “t_person_my_client”
based on nationality.
• Conditionally mandated “id_number” (for Sri
Lankan nationals), “passport_number” (for
foreign nationals) and “nationality1” in
“t_person” elements for walk-in third-party
customers.
June 2021 (6 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
1.1.10
June 04, 2021
Kosala Harshadewa
• Content revision in all sections in the
document to be in line with recent minor
changes.
• In item 5 of the “Structure of XML Reports” in
“Summary” section, description of “Account”
element was changed to inform <signatory>
elements are not allowed for corporate
account elements.
• In item 7 of the “Structure of XML Reports” in
“Summary” section, maximum report file size
of 10 MB is given in the description.
• In section 4.1 “t_person_my_client” and
section 4.2 “t_person”, the “id_number” field
was replaced by “ssn” field to report NIC
number.
• In section 4.2 “t_person”, requirement was
made to provide “nationality1” for walk-in
foreign customers.
• In Table 9.1 of section 4.3
“t_entity_my_client”, mandatory reporting
director_id role types are given.
• In section 4.5 “t_account_my_client” and
section 4.6 “t_account”, SWIFT code was
made mandatory if available.
• In section 5.11 “Currencies” lookup list, ACU
(Asia Clearing Unit) and CNH (Chinese
Renminbi) codes were added.
June 2021 (7 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Table of Contents
1.
Summary ....................................................................................................................................... 10
2.
Conventions used in this document ................................................................................................. 13
3.
Description of XML Elements .......................................................................................................... 14
3.1 “report” Element ............................................................................................................................. 14
3.2 “transaction” Element ..................................................................................................................... 16
3.3 “t_from_my_client” Element ........................................................................................................... 21
3.4 “t_from” Element ............................................................................................................................ 22
3.5 “t_to_my_client” Element ............................................................................................................... 24
3.6 “t_to” Element ................................................................................................................................ 25
4.
Description of Common XML Types Used in the Schema ................................................................. 26
4.1 Type “t_person_my_client” ............................................................................................................. 26
4.2 Type “t_person” ............................................................................................................................. 31
4.3 Type “t_entity_my_client” ............................................................................................................... 35
4.4 Type “t_entity” ................................................................................................................................ 41
4.5 Type “t_account_my_client” ........................................................................................................... 43
4.6 Type “t_account” ............................................................................................................................ 47
4.7 Type “t_party” ................................................................................................................................ 50
4.8 Type “t_address” ............................................................................................................................ 52
4.9 Type “t_phone” .............................................................................................................................. 53
4.10 Type “t_foreign_currency” ............................................................................................................ 54
4.11 Type “t_person_identification” ...................................................................................................... 55
4.12 Element “director_id”.................................................................................................................... 56
5.
Lookup Values ............................................................................................................................... 58
5.1 Submission Type ........................................................................................................................... 58
5.2 Funds Type .................................................................................................................................... 58
5.3 Account Type ................................................................................................................................. 59
5.4 Account Status Type ...................................................................................................................... 60
5.5 Identifier Type ................................................................................................................................ 60
5.6 Conduction Type ............................................................................................................................ 61
5.7 Report Code .................................................................................................................................. 61
5.8 Contact Type ................................................................................................................................. 62
5.9 Communication Type ..................................................................................................................... 62
5.10 Entity Legal Form Type ................................................................................................................ 62
5.11 Currencies ................................................................................................................................... 63
June 2021 (8 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5.12 Country Codes ............................................................................................................................. 68
5.13 Account Person Role Type........................................................................................................... 76
5.14 Entity Person Role Type .............................................................................................................. 76
5.15 Gender Type ................................................................................................................................ 77
5.16 Party Type ................................................................................................................................... 77
6.
Annexures ..................................................................................................................................... 78
6.1 Transaction Number ...................................................................................................................... 78
6.2 City List .......................................................................................................................................... 79
June 2021 (9 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
1. Summary
The purpose of this specifications document is to provide the Reporting Institutions (RIs) a detailed
description about the XML Schema which is used for creating compatible XML files for the goAML report
types. The focus of this document is on generating XML files for CTR/EFT/IFT reports, and separate
documents will provide details on how to submit other types of XML reports and web reports in goAML The
Schema file (.xsd file) is the blueprint to create all the XML report files submitted to the FIU through goAML
online reporting system. Currently, following report types are applicable for the RIs:
•
•
•
•
•
Cash Transaction Report (CTR)
Electronic Funds Transfer – Domestic (EFT)
International Funds Transfer (IFT)
Suspicious Transactions Report (STR-A / STR-T)
Additional Information File (AIF-A / AIF-T) – to report follow up additional information relating to a STR,
after reporting the STR.
Detailed explanation about CTR/EFT/IFT report types will be provided in relevant sections of this document.
Separate documents will be provided on how to submit STR reports and AIF reports to goAML (as XML
reports or web reports, selected by RIs).
All the above report types will be XML files generated as per the same goAML Schema. Hence, the basic
structure of all these report types will be similar. However, depending on the type of the report and regulatory
requirements, some elements in the XML file will be mandatory, and some elements will be optional, for each
report type. RIs should ensure that the reports are generated as per the requirements of the schema (valid
syntax) and business rules defined by the FIU (valid content) for that report type.
An XML report contains following information which can be used in the goAML Client (at the FIU) for
analyzing:
•
•
•
•
•
Information about the report (including RI details)
Information about the transactions (many transactions)
Where does the money come “from”
Where does the money go “to”
Details of involved Persons, Accounts and Entities (PAEs)
June 2021 (10 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
RIs can submit the reports to the FIU using goAML online reporting system in two methods:
1. XML Report Uploads (XML Reports)
RIs can develop software systems to generate XML files as per the goAML XML Schema (XSD file),
populating the files with required data from the RI’s data systems (core banking system and other data
management systems). These XML files (XML reports) can then be uploaded through the goAML web
application directly. This approach should be used to submit the reports where the number of transactions
per report is large. Developing such systems to generate XML files is beyond the scope of this document,
and it is the responsibility of the Reporting Institutions to develop such systems if required. The focus of this
document is on generating XML files for CTR/EFT/IFT reports.
2. Web Interface Forms (Web Reports)
If the number of transactions per report is minimum (less than 10 or so), RIs could use the web forms available
in the goAML web application, to manually enter the details for each of the field in the report. This may be the
case for STR reports, where the number of suspicious transactions are very few. Also, for RIs where the
number of CTR/EFT/IFT transaction per report is few, using the web forms may be more appropriate than
developing software applications to generate XML reports. It should be noted that the data entered in to the
web interface forms are automatically converted to an XML file (XML report) by the goAML web application,
and those XML reports are in turn submitted to the goAML client application at the FIU. This document does
not focus on submitting web reports, and a separate document will provide details on how to submit web
reports in goAML.
The RIs should ensure that correct details are submitted to the FIU using either of above methods.
Structure of the XML Reports
1. The report, represented by the <report> element, has some details first to describe the report such as
Reporting Institution ID, branch (which submitted the report), report type, reference numbers for the report
etc.
2. Then the <report> contains a series of <transaction> elements. A “transaction” element has some details
about a single transaction such as transaction references, branch of the transaction, description, date,
mode and amount. A transaction can be either a “Bi-Party” transaction with clear “From” and “To” sides,
or a “Multi-Party” transaction where there are no “From” and “To” sides but only “Parties” related to the
transaction. The parties in the transaction (either in bi-party or multi-party structure) can be clients of the
RI or non-clients.
3. For bi-party transactions, depending on whether the party is a client or not, the details should be reported
using <t_from_my_client>, <t_from>, <t_to_my_client>, and <t_to> elements, as given below:
From Reporting Institution Client
From Non-Client
To Reporting Institution Client
“t_from_my_client” -> “t_to_my_client”
“t_from” -> “t_to_my_client”
To Non-Client
“t_from_my_client” -> “t_to”
“t_from” -> “t_to”
4. For multi-party transactions, depending on whether the related parties are clients or not, details should
be reported using relevant “my client” or “not my client” elements.
June 2021 (11 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5. The parties in goAML reports (bi-party or multi-party transactions) are of three types, namely Person,
Account and Entity.
•
Person
Details of persons related to the transaction are given in this element. There are two types of person
elements. <t_person_my_client> element is used to provide details of persons who are clients of the
RI and <t_person> element is used to provide details of persons who are not clients. The structure of
these two elements are identical, but some fields in the <t_peron_my_client> element are mandatory
while the same fields in <t_person> element are optional. The distinction is based on the fact that RIs
should have more details available for their clients than non-clients. If the person has an account (of
any type) maintained with the Reporting Institution, and he is transacting with the account, he is a
“t_person_my_client”. Otherwise, he is a “t_person”. A walk-in Sri Lankan non-account holder, or an
account holder performing a transaction not relating to his account, is considered as a “t_person” (not
my client), and the NIC number of such Sri Lankan nationals are required to be reported to the goAML,
in addition to first name and last name.
•
Entity
Details of entities (companies, proprietorships, etc.) related to the transaction are given in this
element. <t_entity_my_client> and <t_entity> elements are used for clients and non-clients of the RIs
respectively. <t_entity_my_client> element must have a <director_id> element which is a set of
<t_person> elements, to provide the details of the persons who have a controlling interest for the
entity account. Instructions on the persons who are reportable in the <director_id> element are given
in the respective sections of this document.
•
Account
Details of the accounts related to the transaction are given in this element. <t_account_my_client>
and <t_account> elements are used for accounts of RI and other Institutions respectively.
For personal accounts, <t_account_my_client> element must have <signatory> element(s) to provide
the details of the person(s) which own the account or have the right to use it.
For corporate accounts, <t_account_my_client> element must have one <t_entity> element to
provide the details of the entity which owns the account.
Personal accounts should not have the <t_entity> element and entity (corporate) accounts should not
have <signatory> elements within the <t_account_my_client> elements.
6. If the number of transactions to be reported per reporting period is large, it would not be practical to
manually enter details to the web forms and submit CTR/EFT/IFT reports as web reports. Therefore, RIs
may have to develop software applications to generate those report types and upload them via the goAML
web application as XML reports. On the other hand, if the number of transactions to be reported are low
per reporting period, it will be more practical to submit those reports manually as web reports. For STRs
and AIFs, either web reports or XML reports could be optimal, depending on the number of transactions
to be reported in a single report.
7. Maximum size of an XML report is 10 MB. Accordingly, maximum number of “transaction” elements that
can be included in one CTR/EFT/IFT report is limited to 1000. If the number of transactions for the
reporting period exceeds 1000, RIs should prepare separate XML reports containing 1000 or less
“transactions” in each report and upload the reports to the goAML online system one by one, or put those
XML reports in to a single zip file, and upload that zip file to the goAML online system. Naming formats
for these XML reports and zip files will be provided by the FIU separately.
June 2021 (12 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
It is utmost important that this document is carefully reviewed together by the RI’s Information Technology
(IT) division, Business Operations division and Compliance division, to fully understand the technical and
regulatory requirements given in this document (specially the XML annotations). In case of non-availability of
required information, RIs should develop procedures to obtain the relevant information and include such
information in the XML reports.
2. Conventions used in this document
The following conventions are used in this document:
Required text element
Required text element, can have 1 to N values
Optional text element for all report types
Optional nested element for all report types
Required nested element
One of the two (or more) elements should be provided
Integer
A 32 bit value
Date time
A date and time value in the following format:
YYYY-MM-DDTHH:MM:SS (Example: 2019-02-01T00:00:00)
All timestamps should be Sri Lankan time
Sequence to sub elements (text or nested)
Do not use for any reports
Mandatory (in field tables) Y – Yes, N – No, C – Conditional Mandatory
For the purpose of this document, an element in a goAML XML report can be of two types:
1. Text element – contains only text (including numbers). It does not contain other elements
Example: <rentity_id>9999</rentity_id>
2. Nested element – contains set of other elements
Example:
<phone>
<tph_contact_type>2</tph_contact_type>
<tph_communication_type>L</tph_communication_type>
<tph_number>0112568741</tph_number>
</phone>
June 2021 (13 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
3. Description of XML Elements
3.1 “report” Element
<report> element is the root element of the XML report and it is the highest level nested element. Each XML
report has one <report> element which includes all the sub elements (text and nested) about the report itself,
RI, and transactions. Basic information about RI, reporting date and type of report are given in the <report>
element, and it may contain details of multiple transactions for the period relevant to that report.
For CTR/EFT/IFT reports, there should be a <transaction> nested element to represent each of the threshold
transactions required to be reported. That means, if there are 1000 transactions above the threshold limit for
the reporting period, there should be 1000 <transaction> nested elements within the <report> element.
Figure 1: Overview Element “report”
June 2021 (14 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length/Type
Mandatory
Example
Integer
>= 1
Y
Text
255
N
“Head Office”, “Main
Street Branch”, etc.
rentity_id
Reporting Institution
number given by FIU.
(Refer goAML Web
Manual Version 1.0)
rentity_branch
Name of the branch which
submitted the report
submission_code
Use “E” for all reports
Enumeration
Y
“E”
report_code
Type of report
Enumeration
Y
“CTR”, “EFT” or
“IFT”
entity_reference
Reference given by RI to
the report (for further
communications)
255
Y
fiu_ref_number
Reference given by the
FIU to the report (for
further communications)
255
N
submission_date
Report generated date.
Datetime
Y
“2019-0325T00:00:00”
currency_code_loc
al
Use “LKR” for
CTR/EFT/IFT reports
Type
“Currencytype”
Y
“LKR”
reporting_person
Not required for
CTR/EFT/IFT reports
Type
“t_person_regi
N
stration_in_re
port”
location
Not required for
CTR/EFT/IFT reports
Type
“t_address”
N
reason
Not required for
CTR/EFT/IFT reports
Text
4000
N
action
Not required for
CTR/EFT/IFT reports
Text
4000
N
See 4.8 “t_address”
CTR/EFT/IFT reports should contain a list of transactions with persons, accounts and entities
involve in those transactions.
transaction
Transaction information
activity
Not required for
CTR/EFT/IFT reports
report_indicators
Same as type of report
(this will be different for
STR/SAR/AIF/IRF
reports)
Type
“transaction”
Y
See 3.2
“transaction”
N
Type
“indicator”
Y
“CTR”, “EFT” or
“IFT”
Table 1: Details Element “report”
June 2021 (15 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
3.2 “transaction” Element
<transaction> nested element is the element that encapsulates all the details pertaining to a single transaction
in the report. It is structured to accommodate the complex structure of a banking transaction.
Figure 2: Overview Element “transaction”
June 2021 (16 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
Mandatory
Example
transactionnumber
Unique reference
number to identify a
transaction
50
Y
internal_ref_numbe
r
Reference used by
reporting entity for the
transaction
50
N
transaction_locatio • Mandatory address of
n
the branch when the
“transmode_code” is
“Branch”
• Mandatory name of
the merchant for
credit/debit card
transactions (multiparty)
• Address of the branch
for other transactions
where the transaction
took place (optional).
255
C
transaction_descrip
tion
Description/purpose of
the transaction
4000
Y
“personal loan”
date_transaction
Date of the transaction
DateTime
Y
“2019-03-25T00:00:00”
teller
Do not use for
CTR/EFT/IFT reports
20
N
authorized
Do not use for
CTR/EFT/IFT reports
20
N
late_deposit
Do not use for
CTR/EFT/IFT reports
Boolean
N
date_posting
Do not use for
CTR/EFT/IFT reports
DateTime
N
value_date
Date of the transaction
realized.
DateTime
Y
“2019-03-27T00:00:00”
transmode_code
How the transaction
was conducted
Enumeratio
n
Y
See 5.6 Conduction
Type
transmode_comme
nt
Mandatory description,
if transmode_code is
“Other”
50
C
amount_local
The value of the
transaction in LKR
(maximum two decimal
places)
Decimal
Y
See 6.1 Transaction
Number
“5000000”
Transactions must be either bi-party transactions with clear ‘From’ and ‘To’ sides, or multi-party
transactions with parties (Persons/Accounts/Entities – PAEs) relevant to the transactions.
June 2021 (17 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Bi-Party Transactions
One of the elements <t_from_my_client> or <t_from> should be provided, depending on the
relationship with the PAE in the “from” side. Both CANNOT be present together in a transaction, but
one of them should be present. Refer to “goAML Reporting Model - version 1.10” for bi-party
transaction scenarios.
Name
Description
t_from_my_client
Specifies where the
money came from. If
the source is RI’s
client, then this
element should be
provided
t_from
Length
Mandatory
Example
See 3.3
“t_from_my_client”
Y
(one of them)
Specifies where the
money came from
See 3.4 “t_from”
One of the elements <t_to_my_client> or <t_to> should be provided, depending on the relationship
with the PAE in the “to” side. 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 RI’s
client, then this
element should be
provided
t_to
Specifies where the
money went.
goods_services
Not required for
CTR/EFT/IFT reports
comments
Generic comments
field
See 3.5
“t_to_my_client”
Y
(one of them)
See 3.6 “t_to”
N
4000
N
Multi-Party Transactions
When there is no clear “From” and “To” sides of the transaction, or information is not available to be
reported about the non-customer end of the transaction (either in “From” or “To” side), it should be
reported as a multi-party transaction with the details of the parties relevant to the transaction. Refer
to “goAML Reporting Model - version 1.10” for multi-party transaction scenarios.
party
Describes the involved
party details
(Persons/Accounts/Enti
ties – PAEs)
Type
“t_party”
Y
(if not a biparty
transaction)
See 4.7 “t_party”
Table 2: Details Element “transaction”
June 2021 (18 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Bi-Party Transaction Model
For CTR/EFT/IFT report types with bi-party transactions, there should be a ‘From’ side and ‘To’ side to each
transaction. Both ‘From’ and ‘To’ sides are further divided as ‘my client’ and ‘not my client’, leading in to four
elements, namely, <t_from_my_client>, <t_from>, <t_to_my_client>, and <t_to>.
Bi-party transactions are composed of a source and destination (‘From’ and ‘To’ sides). The source and
destination may be either a Person, an Account or an Entity (PAE). For cash deposits in to accounts, the
source is a person and the destination is an account, i.e. on ‘From’ side there is a person element (either
<t_person_my_client> or <t_person>) and on ‘To’ side there is an account element (either
<t_account_my_client> or <t_account>). For cash withdrawals from accounts, there is an account element
at ‘From’ side and a person element at the ‘To’ side. For money remittance without account transfer (which
is a person to person transaction), there is a person element at the ‘From’ side and person element at the ‘To’
side. The same structure of person to person transactions can be used for any money service type of
transaction without the use of accounts. For account transfers, there are account elements at the ‘From’ side
and ‘To’ side. Same principles apply to Entities as well.
Following table illustrates ALL the possible combinations of PAEs in the bi-party transaction model, and
examples are provided for general cases. A more comprehensive list of transaction scenarios with “From”
and “To” object types are provided in the “goAML Reporting Model” document provided by the FIU.
Source (From)
Destination (To)
Example
t_person_my_client
t_person_my_client
t_person_my_client
t_person
t_person_my_client
t_account_my_client Account holder deposits cash to his account
t_person_my_client
t_account
t_person_my_client
t_entity_my_client
t_person_my_client
t_entity
t_person
t_person_my_client
t_person
t_person
t_person
t_account_my_client Person (not my client) deposits money to an account in
Reporting Institution
t_person
t_account
t_person
t_entity_my_client
t_person
t_entity
t_account_my_client
t_person_my_client
t_account_my_client
t_person
t_account_my_client
t_account_my_client Funds transfer between two accounts within Reporting
Institution
t_account_my_client
t_account
Funds transfer from account of Reporting Institution to an
account of another Institution
t_account_my_client
t_entity_my_client
Authorized person of an entity withdraws money from the
entity’s account in the Reporting Institution
Person (not my client) sends money to person (not my
client) – outward/inward remittance
Person (not my client) sends money to an account of
another Institution
Account holder withdraws cash from his account
June 2021 (19 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Source
Destination
Example
t_account_my_client
t_entity
t_account
t_person_my_client
t_account
t_person
t_account
t_account_my_client Funds receive to an account of the Reporting Institution
from an account of another Institution
t_account
t_account
t_account
t_entity_my_client
t_account
t_entity
t_entity_my_client
t_person_my_client
t_entity_my_client
t_person
t_entity_my_client
t_account_my_client Authorized person of an entity deposits money to the
entity’s account in the Reporting Institution
t_entity_my_client
t_account
t_entity_my_client
t_entity_my_client
t_entity_my_client
t_entity
t_entity
t_person_my_client
t_entity
t_person
t_entity
t_account_my_client Funds receive to an account of the Reporting Institution
from an entity
t_entity
t_account
t_entity
t_entity_my_client
t_entity
t_entity
Person (not my client) receives remittance from abroad
Person (not my client) receives remittance from abroad
Table 2.1: All Combinations of PAEs in Bi-Party Reporting Model
It should be noted that all the above combinations may not be applicable to a single Reporting Institution (RI),
and the RI should only use the combinations applicable for its transactions.
Multi-Party Transaction Model
When there is no clear “From” and “To” sides of the transaction, or information is not available to be reported
about the non-customer end of the transaction (either in “From” or “To” side), bi-party transaction model
cannot be used in the reporting. In such situations, multi-party transaction model with the customer PAE’s
details should be reported in the “party” element.
In the multi-party transaction model, a single transaction can have one or more parties (PAEs) related to the
transaction, without a specific “From” or “To” side. This model is more useful in reporting STRs but for
CTR/EFT/IFT reporting it can also be used. For example, in a credit card transaction, only the details of the
credit card account should be reported as a party (with details of the card holder as the signatory), and the
name of the merchant is reported in the <transaction_location> element. A list of transactions to be reported
as multi-party transactions are given in the “goAML Reporting Model” document.
June 2021 (20 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
3.3 “t_from_my_client” Element
When generating XML reports, if the object (PAE) in the “from” (source) side of the transaction is a client of
the RI, <t_from_my_client> element should be used in a <transaction> element. The details of the client party
will be included in either <from_account>, <from_person> or <from_entity> element located in the
<t_from_my_client> element.
Figure 3: Overview Element “t_from_my_client”
Name
Description
Length
from_funds_code
Type of funds used
in the transaction
Enumeration
from_funds_comment
Mandatory
description, if
“from_funds_code”
is “Other”.
from_foreign_currency
Mandatory
Example
Y
See 5.2 Funds Type
Text
255
C
-
If the “from” side
funds are in foreign
currency, then
specify the foreign
currency details.
Type
“t_foreign_curre
ncy”
N
See 4.10
“t_foreign_currency”
t_conductor
Not required for
CTR/EFT/IFT
reports
Type
“t_person_my_cl
ient”
N
from_account
Element that holds
account information
Type
“t_account_my_c
lient”
Element that holds
person information.
Type
“t_person_my_cl
ient”
from_person
Y
(one of
them only)
See 4.5
“t_account_my_clien
t”
See 4.1
“t_person_my_client
”
June 2021 (21 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
from_entity
Element that holds
entity information.
from_country
Country where
transaction was
initiated.
Type
“t_entity_my_clie
nt”
Enumeration
See 4.3
“t_entity_my_client”
Y
See 5.12 Country
Codes
Table 3: Details Element “t_from_my_client”
Additional Notes
When persons of business places (entities) who are authorized to deal with the entity account are doing
transactions on behalf of the entity, that entity (or the account of the entity, as the case may be) should be
reported for the transaction’s ‘From’ side.
3.4 “t_from” Element
When generating XML reports, if the object (person, account or entity) in the “from” (source) side of the
transaction is NOT a client of the RI, <t_from> element should be used in a “transaction” element. The details
of the party will be included in either <from_account>, <from_person> or <from_entity> element located in
the <t_from> element.
Figure 4: Overview Element “t_from”
June 2021 (22 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
Mandatory
from_funds_code
Type of funds used
in the transaction
Enumeration
Y
See 5.2 Funds
Type
from_funds_comment
Mandatory
description, if
“from_funds_code”
is “Other”.
Text
255
C
-
from_foreign_currency
If the “from” side
funds are in foreign
currency, then
specify the foreign
currency details.
Type
“t_foreign_currenc
y”
N
See 4.10
“t_foreign_currenc
y”
t_conductor
Not required for
CTR/EFT/IFT
reports
Type
“t_person”
N
from_account
Element that holds
account information
Type “t_account”
from_person
Element that holds
person information.
Type
“t_person”
from_entity
Element that holds
entity information.
Type “t_entity”
from_country
Country where
transaction was
initiated.
Enumeration
Example
See 4.6
“t_account”
Y
(one of
them)
Y
See 4.2 “t_person”
See 4.4 “t_entity”
See 5.12 Country
Codes
Table 4: Details Element “t_from”
Additional Notes
When persons of business places (entities) who are authorized to deal with the entity account are doing
transactions on behalf of the entity, that entity (or the account of the entity, as the case may be) should be
reported for the transaction’s ‘From’ side.
June 2021 (23 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
3.5 “t_to_my_client” Element
When generating XML reports, if the object (PAE) in the “to” (destination) side of the transaction is a client of
the RI, <t_to_my_client> element should be used in a <transaction> element. The details of the client party
will be included in either <to_account>, <to_person> or <to_entity> element located in the <t_to_my_client>
element.
Figure 5: Overview Element “t_to_my_client”
Name
Description
Length
to_funds_code
Type of funds used in
the transaction.
to_funds_comment
Mandatory
Example
Enumeration
Y
See 5.2 Funds
Type
Mandatory
description, if
“to_funds_code” is
“Other”.
Text
255
C
-
to_foreign_currency
If the “to” side funds
are in foreign
currency, then
specify the foreign
currency details.
Type
“t_foreign_currency”
N
See 4.10
“t_foreign_curr
ency”
to_account
Element that holds
account information
Type
“t_account_my_clien
t”
to_person
Element that holds
person information
Type
“t_person_my_client
”
to_entity
Element that holds
entity information.
Type
“t_entity_my_client”
to_country
Receiving country of
the transaction
Enumeration
See 4.5
“t_account_my
_client”
Y
(one of
them)
See 4.1
“t_person_my
_client”
See 4.3
“t_entity_my_c
lient”
Y
See 5.12
Country
Codes
Table 5: Details Element “t_to_my_client”
June 2021 (24 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
3.6 “t_to” Element
When generating XML reports, if the object (PAE) in the “to” (destination) side of the transaction is NOT a
client of the RI, <t_to> element should be used in a <transaction> element. The details of the party will be
included in either <to_account>, <to_person> or <to_entity> element located in the <t_to> element.
Figure 6: Overview Element “t_to”
Name
Description
Length
to_funds_code
Type of funds used in
the transaction.
to_funds_comment
Mandatory
Example
Enumeration
Y
See 5.2
Funds Type
Mandatory description,
if “to_funds_code” is
“Other”.
Text
255
C
-
to_foreign_currency
If the “to” side funds are
in foreign currency, then
specify the foreign
currency details.
Type
“t_foreign_currenc
y”
N
See 4.10
“t_foreign_cu
rrency”
to_account
Element that holds
account information
Type “t_account”
to_person
Element that holds
person information
Type “t_person”
to_entity
Element that holds
entity information.
Type “t_entity”
to_country
Receiving country of the
transaction
Enumeration
Y
(one of
them)
Y
See 4.6
“t_account”
See 4.2
“t_person”
See 4.4
“t_entity”
See 5.12
Country
Codes
Table 6: Details Element “t_to”
June 2021 (25 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4. Description of Common XML Types Used in the Schema
XML types define data structures for the XML elements of that type. XML types are not elements, and there
could be unlimited number of XML elements with different names of same type. When an XML element is
created as a certain type, that element inherits the structure defined in the XML type.
goAML XML Schema defines number of XML types, which are used by XML elements that actually hold data
in the report.
4.1 Type “t_person_my_client”
“t_person_my_client” XML type is for the XML elements which provide details about the persons relating to a
transaction, who are customers of the RI. Therefore, RIs should have more details about the person obtained
via the Customer Due Diligence (CDD), hence more fields in this type are mandatory.
June 2021 (26 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Figure 7: Overview Type “t_person_my_client”
June 2021 (27 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
Mandatory
Example
gender
Gender
Enumerati
on
N
See 5.15
Gender Type
title
Title
Text
30
N
“Dr.”
Only surname / last name of the person should be given in the “last_name” field, and all other
parts of the name should be given in the “first_name” field.
first_name
All parts of the name,
except the last name.
If length exceeds 100
characters, provide
first 99 characters +
“_”
Text
100
Y
< 100 chars:
“Karunaratne
Mudiyanselage
Saman”
middle_name
Do not use for
CTR/EFT/IFT reports
Text
100
N
prefix
Do not use for
CTR/EFT/IFT reports
Text
100
N
last_name
Last part of the name
(in upper case)
Text
100
Y
“PERERA”
birthdate
Birth date
DateTime
Y
1953-0125T00:00:00
birth_place
Not required for
CTR/EFT/IFT reports
Text
255
N
mothers_name
Do not use for
CTR/EFT/IFT reports
Text
100
N
alias
Not required for
CTR/EFT/IFT reports
Text
100
N
ssn
• Mandatory NIC
number for Sri
Lankan nationals
• For old NICs, the
format is 9 digits (0-9)
plus ‘X’ or ‘V’ (upper
case) without any
other characters or
spaces
• For new NICs, the
format is 12 digits
only (0-9) without any
Text
25
C
> 100 chars:
“Don Hewa ...
(more names)
Mudiyanselage
Sama_”
Old NIC:
950920970V
New NIC:
199509209700
June 2021 (28 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
other characters or
spaces
passport_number • Mandatory Passport
number for foreign
nationals
• Alpha-numeric
characters without
spaces
Text
25
C
passport_country
Do not use for
CTR/EFT/IFT reports
Text
25
N
id_ number
Additional ID
numbers (postal ID,
GN certificate, etc.)
Text
25
N
nationality1
• Country of Nationality
• "Nationality" in
LankaFin
Enumeratio
n
Y
See 5.12
Country Codes
nationality2
If the customer has
more than one
citizenship, report the
second nationality
Enumeratio
n
N
See 5.12
Country Codes
nationality3
If the customer has
more than two
citizenships, report
the third nationality
Enumeratio
n
N
See 5.12
Country Codes
Country of residence
Enumeratio
n
Y
See 5.12
Country Codes
residence
phones
• A Holder element for
1..many “phone”
elements
• “Tel” in LankaFin
phone
Element for providing
phone details
addresses
address
email
N
Type
“t_phone”
• A Holder element for
1..many “address”
elements
• "AddressLines",
"ReceiverAddress"
and "SenderAddress"
in LankaFin
Element for providing
address details
• Email address
• "Email" in LankaFin
N1234567
N
See 4.9
“t_phone”
Y
Type
“t_address
”
Y
Type
“email_ad
dress”
N
See 4.8
“t_address”
June 2021 (29 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
• Occupation
• "BusinessType",
"ReceiverBusiness"
and
"SenderBusiness" in
LankaFin
Text
255
Y
employer_name
Not required for
CTR/EFT/IFT reports
Text
255
N
employer_addres
s_id
Not required for
CTR/EFT/IFT reports
Type
“t_address
”
N
See 4.8
“t_address”
employer_phone
_id
Not required for
CTR/EFT/IFT reports
Type
“t_phone”
N
See 4.9
“t_phone”
identification
Do not use for
CTR/EFT/IFT reports
Type
“t_person
_identifica
tion”
N
deceased
Not required for
CTR/EFT/IFT reports
Boolean
N
deceased_date
Not required for
CTR/EFT/IFT reports
Date
N
tax_number
Not required for
CTR/EFT/IFT reports
Text
100
N
tax_reg_numebr
Not required for
CTR/EFT/IFT reports
Text
100
N
source_of_wealth
Not required for
CTR/EFT/IFT reports
Text
255
N
• Generic comments
field, to provide any
additional information
• If first names are
longer than 100
characters, provide
full name in this field
4000
N
occupation
Comments
International
Standard
Classification of
Occupations
(ISCO) or Sri
Lanka’s
Standard
Classification of
Occupations
(SLSCO)
Table 7: Details Type “t_person_my_client”
June 2021 (30 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.2 Type “t_person”
“t_person” XML type is for the XML elements which provide details about the persons relating to a transaction,
who are NOT customers of the RIs. This element has the same structure of the “t_person_my_client” type,
but only the limited fields are mandatory. However, RIs should submit every detail regarding the person, if
available.
If the person has an account (of any type) maintained with the RIs, and he is transacting with the account, he
is a “t_person_my_client”. Otherwise, he is a “t_person”. Currently, a walk-in non-account holder, or an
account holder performing a transaction not relating to his account, is considered as a “t_person” (not my
client).
June 2021 (31 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Figure 8: Overview Type “t_person”
June 2021 (32 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
Mandatory
Example
gender
Gender
Enumerati
on
N
See 5.15
Gender Type
title
Title
Text
30
N
“Dr.”
Only surname / last name of the person should be given in the “last_name” field, and all other
parts of the name should be given in the “first_name” field.
first_name
All parts of the name,
except the last name.
If length exceeds 100
characters, provide
first 99 characters +
“_”
Text
100
Y
< 100 chars:
“Karunaratne
Mudiyanselage
Saman”
middle_name
Do not use for
CTR/EFT/IFT reports
Text
100
N
prefix
Do not use for
CTR/EFT/IFT reports
Text
100
N
last_name
Last name
(in upper case)
Text
100
Y
“PERERA”
birthdate
Birth date
DateTime
N
1953-0125T00:00:00
birth_place
Not required for
CTR/EFT/IFT reports
Text
255
N
mothers_name
Do not use for
CTR/EFT/IFT reports
Text
100
N
alias
Not required for
CTR/EFT/IFT reports
Text
100
N
ssn
• Mandatory NIC for
walk-in Sri Lankan
nationals
• For old NICs, the
format is 9 digits (0-9)
plus ‘X’ or ‘V’ (upper
case) without any
other characters or
spaces
• For new NICs, the
format is 12 digits
only (0-9) without any
Text
25
C
> 100 chars:
“Don Hewa
(more names)
Mudiyanselage
Sama_”
Old NIC:
950920970V
New NIC:
199509209700
June 2021 (33 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
other characters or
spaces
passport_number • Mandatory Passport
number for walk-in
foreign nationals
• Alpha-numeric
characters without
spaces
Text
25
C
passport_country
Do not use for
CTR/EFT/IFT reports
Text
25
N
id_ number
Additional ID numbers
(postal ID, GN
certificate, etc.)
Text
25
N
phones
A Holder element for
1..many “phone”
elements
phone
Element for providing
phone details
addresses
A Holder element for
1..many “address”
elements
address
Element for providing
address details
Type
“t_address
”
N
See 4.8
“t_address”
nationality1
• Country of Nationality
for walk-in foreign
customers
• "Nationality" in
LankaFin
Enumeratio
n
C
See 5.12
Country Codes
nationality2
If the customer has
more than one
citizenship, report the
second nationality
Enumeratio
n
N
nationality3
If the customer has
more than two
citizenships, report
the third nationality
Enumeratio
n
N
residence
Country of residence
Enumeratio
n
N
See 5.12
Country Codes
email
Email address
Type
“email_ad
dress”
occupation
Occupation
N
International
Standard
Classification of
Occupations
N1234567
N
Type
“t_phone”
N
See 4.9
“t_phone”
N
Text
255
June 2021 (34 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
(ISCO) or Sri
Lanka’s
Standard
Classification of
Occupations
(SLSCO)
employer_name
Not required for
CTR/EFT/IFT reports
Text
255
N
employer_addres
s_id
Not required for
CTR/EFT/IFT reports
Type
“t_addres”
N
See 4.8
“t_address”
employer_phone
_id
Not required for
CTR/EFT/IFT reports
Type
“t_phone”
N
See 4.9
“t_phone”
identification
Do not use for
CTR/EFT/IFT reports
Type
“t_person
_identifica
tion
N
deceased
Not required for
CTR/EFT/IFT reports
Boolean
N
deceased_date
Not required for
CTR/EFT/IFT reports
Date
N
tax_number
Not required for
CTR/EFT/IFT reports
Text
100
N
tax_reg_numebr
Not required for
CTR/EFT/IFT reports
Text
100
N
source_of_wealth
Not required for
CTR/EFT/IFT reports
Text
255
N
• Generic comments
field, to provide any
additional information
• If first names are
longer than 100
characters, provide
full name in this field
Text
4000
N
comments
Table 8: Details Type “t_person”
4.3 Type “t_entity_my_client”
“t_entity_my_client” XML type is for the XML elements which provide details about the entities relating to a
transaction, who are customers of the RIs. Therefore, RIs should have more details about the entity obtained
via the Customer Due Diligence (CDD), hence more fields in this type are mandatory. The entity could be
related to the transaction via an authorized person doing the transaction, or via the corporate account of the
entity as part of the transaction (online transaction).
June 2021 (35 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Figure 9: Overview Type “t_entity_my_client”
June 2021 (36 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
name
Name of entity
Text
255
Y
commercial_name
Commercial name of the
entity, if different from
the registered name
Text
255
N
Type
“legal_form_t
ype”
Y
See 5.10 Entity
Legal Form
Type
Text
50
C
PV1234
(instead of
pv 1234)
Text
255
Y
International
Standard
Industrial
Classification
of All Economic
Activities (ISIC)
or Sri Lanka
Standard
Industrial
Classification
(SLSIC)
incorporation_legal_fo • The legal form of the
rm
entity
• "CusType" in LankaFin
incorporation_number
Mandatory Business
Registration Number of
the registered entities
(All caps without
spaces)
business
• Business type of the
entity
• "BusinessType",
"SenderBusiness" and
"ReceiverBusiness" in
LankaFin
• General descriptions
are not allowed
phones
• A Holder element for
1..many “phones”
elements
• "Tel" in LankaFin
phone
Element for providing
phone details
addresses
address
email
Length
• Email address
• "Email" in LankaFin
Example
N
Type
“t_phone”
• A Holder element for
1..many “address”
elements
• "AddressLines",
"ReceiverAddress" and
"SenderAddress" in
LankaFin
Element for providing
address details
Mandatory
N
See 4.9
“t_phone”
Y
Type
“t_address”
Y
Text
255
N
url
Not required for
CTR/EFT/IFT reports
Text
255
N
incorporation_state
Not required for
CTR/EFT/IFT reports
Text
255
N
See 4.8
“t_address”
June 2021 (37 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
incorporation_country
_code
Entity incorporated
country
Enumeration
Y
See 5.12
Country Codes
director_id
• A holder element for
1..many entity
controlling persons
Type
“t_person”
Y
See 4.12
“director_id”
role
• Role of the person
given in “director_id”
• Report as per table 9.1
Enumeration
Y
See 5.14 Entity
Person Role
Type
Date
N
Boolean
N
incorporation_date
Incorporation
registration date
business_closed
Boolean to indicate if
the company is closed
down
date_business_closed
If entity is closed date of
business closure
Date
N
tax_number
The entity tax number
Tax
100
N
tax_reg_number
Registration number of
the entity by the Tax
auth.
Tax
100
N
comments
Generic comments field
Text
4000
N
Table 9: Details Type “t_entity_my_client”
June 2021 (38 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Entity Type
(section 5.10)
Role Type as
applicable
Mandatory
to Report
Description
(section 5.14)
Sole Proprietorship
Owner
Yes
Partnership
Partner
Yes
Private Limited
Company
Chairperson
No
Head of the board
Director
Yes
Director
CEO/MD
No
Applicable for other similar positions as well
(such as GM)
Shareholder
No
More than 10% share ownership
Chairperson
No
Head of the board
Director
Yes
Director
CEO/MD
No
Applicable for other similar positions as well
(such as GM)
Shareholder
No
More than 10% share ownership
Chairperson
No
Head of the board
Director
Yes
Director
CEO/MD
No
Applicable for other similar positions as well
(such as GM)
Shareholder
No
More than 10% share ownership
Government Institutions
Head of Institution
No
Head of the Institution
State Owned
Enterprises
Chairperson
No
Head of the board
Director
Yes
Director
CEO/MD
No
Applicable for other similar positions as well
(such as GM)
Shareholder
No
More than 10% share ownership
Chairperson
Yes
Head of the board
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Trustee/
Yes
Public Limited
Company
Unlimited Company
Foundation/Other legal
arrangements
Trust
Co-Trustee
Settler
Yes
June 2021 (39 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
NGO
Club
Society
Charity
Association
Offshore/Overseas
Company
Chairperson
Yes
Head of the NGO
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Chairperson
Yes
Head of the NGO
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Chairperson
Yes
Head of the NGO
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Chairperson
Yes
Head of the NGO
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Chairperson
Yes
Head of the NGO
Director
Yes
Director
CEO/MD
Yes
Applicable for other similar positions as well
(such as GM)
Chairperson
No
Head of the board
Director
Yes
Director
CEO/MD
No
Applicable for other similar positions as well
(such as GM)
Shareholder
No
More than 10% share ownership
Table 9.1: Entity types and relevant Role types to be used in field “director_id” in elements in “t_entity_my_client” and “t_entity”
June 2021 (40 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.4 Type “t_entity”
“t_entity” XML type is for the XML elements which provide details about the entities relating to a transaction,
who are NOT customers of the RIs. This element has the same structure of the “t_entity_my_client” type, but
only limited fields are mandatory. However, RIs should submit every detail regarding the entity, if available.
The entity could be related to the transaction via an authorized person doing the transaction, or via the
corporate account of the entity which is part of the transaction (online transaction).
Figure 10: Overview Type “t_entity”
June 2021 (41 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
name
Name of entity
Text
255
Y
commercial_name
Commercial name of the
entity, if different from
the registered name
Text
255
N
Type
“legal_form_t
ype”
N
See 5.10 Entity
Legal Form
Type
Business Registration
Number of the
registered entities (All
caps without spaces)
Text
50
N
PV1234
(instead of
pv 1234)
business
• Business type of the
entity
• "BusinessType",
"SenderBusiness" and
"ReceiverBusiness" in
LankaFin
• General descriptions
are not allowed
Text
255
N
International
Standard
Industrial
Classification
of All Economic
Activities (ISIC)
or Sri Lanka
Standard
Industrial
Classification
(SLSIC)
phones
• A Holder element for
1..many “phones”
elements
• "Tel" in LankaFin
phone
Element for providing
phone details
incorporation_legal_fo • The legal form of the
rm
entity
• "CusType" in LankaFin
incorporation_number
addresses
address
email
Length
• Email address
• "Email" in LankaFin
Example
N
Type
“t_phone”
• A Holder element for
1..many “address”
elements
• "AddressLines",
"ReceiverAddress" and
"SenderAddress" in
LankaFin
Element for providing
address details
Mandatory
N
See 4.9
“t_phone”
N
Type
“t_address”
N
Text
255
N
url
Not required for
CTR/EFT/IFT reports
Text
255
N
incorporation_state
Not required for
CTR/EFT/IFT reports
Text
255
N
See 4.8
“t_address”
June 2021 (42 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
incorporation_country
_code
Entity incorporated
country
Enumeration
N
See 5.12
Country Codes
director_id
• A holder element for
1..many entity owners
Type
“t_person”
N
See 4.12
“director_id”
Role
• Role of the person
given in “director_id”
• Report as per table 9.1
Enumeration
N
See 5.14 Entity
Person Role
Type
Date
N
Boolean
N
incorporation_date
Incorporation
registration date
business_closed
Boolean to indicate if
the company is closed
down
date_business_closed
If entity is closed date of
business closure
Date
N
tax_number
The entity tax number
Tax
100
N
tax_reg_number
Registration number of
the entity by the Tax
auth.
Tax
100
N
comments
Generic comments field
Text
4000
N
Table 10: Details Type “t_entity”
4.5 Type “t_account_my_client”
“t_account_my_client” XML type is for the XML elements which provide details about the accounts relating to
a transaction, which are held by the RIs. Therefore, RIs should have more details about the account, and the
persons and entities associated with the account, obtained via the Customer Due Diligence (CDD). Hence
more fields in this type are mandatory.
In terms of reporting structure, an account should have persons OR entities associated to it in <signatory>
element OR <t_entity> element respectively. For personal accounts, details of the account holding persons
should be given in <t_person> elements in <signatory> element and for entity accounts, details of the entities
owning the account should be given in <t_entity> element (only one entity for one account).
June 2021 (43 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Figure 11: Overview Type “t_account_my_client”
June 2021 (44 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
instituation_name
The name of the
account holding entity
Text
255
• Given by FIU. (Refer
goAML Web Manual
Version 1.0)
• Provide only if the RI
does not have a
SWIFT code
Text
50
• SWIFT code
according to ISO
9362
• Mandatory if RI has
a SWIFT code
Text
11
C
Do not use for
CTR/EFT/IFT reports
Boolean
N
institution_code
swift
non_bank_instituti
on
Length
Mandatory
Example
Y
C
branch
• Branch code or
name where the
account is held
• "BranchName" in
LankaFin
Text
255
Y
account
• Account number
• "AccNumber" in
LankaFin
Text
50
Y
currency_code
• Currency of the
account
• "CurCode" in
LankaFin
Enumeratio
n
Y
See 5.11 Currencies
“Isuru Udana”, “Diriya
Wanitha”
account_name
Name of the account
given by account
holding entity
Text
255
N
iban
IBAN number of the
account
34
N
client_number
CIF number of the
account
30
N
Enumeratio
n
Y
See 5.3 Account Type
Type
“t_entity_m
y_client”
C
See 4.3
“t_entity_my_client”
personal_account • Account Type
_type
• "AccType" in
LankaFin
t_entity
• Mandatory for entity
accounts
• Holder element for
one
“t_entity_my_client”
element to provide
June 2021 (45 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
details of the entity
owning the account
• Mandatory for
personal accounts
• Holder element for
1..many
“t_person_my_client”
elements to provide
details of the
persons associated
with the account
signatory
is_primary Identifies the primary
account holder. Only
one signatory should
be marked as
“is_primary”.
t_person
Element to provide
details of the
persons associated
with the account
role Role of the person
associated with the
account
C
Boolean
C
Type
“t_person_
my_client”
C
See 4.1
“t_person_my_client”
Type
“account_p
erson_role
_type”
C
See 5.13 Account
Person Role Type
opened
Opening date of the
account
DateTime
N
closed
Closing date of the
account (if closed)
DateTime
N
balance
Do not use for
CTR/EFT/IFT reports
Decimal
N
date_balance
Not required for
CTR/EFT/IFT reports
Date
N
status_code
• Account status when
transaction was
initiated
• "AccStatus" in
LankaFin
Enumeratio
n
Y
beneficiary
Ultimate beneficiary
of the account
50
N
beneficiary_comm
ent
Any special remark
on the beneficiary
255
N
comments
Generic comments
elements
4000
N
See 5.4 Account
Status Type
Table 11: Details Type “t_account_my_client”
June 2021 (46 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.6 Type “t_account”
“t_account” XML type is for the XML elements which provide details about the accounts relating to a
transaction, which are NOT held by the RIs. This element has the same structure of the “t_account_my_client”
type, but only limited fields are mandatory. However, RIs should submit every detail regarding the account, if
available.
Figure 12: Overview Type “t_account”
June 2021 (47 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
instituation_name
The name of the
account holding entity
Text
255
• Given by FIU. (Refer
goAML Web Manual
Version 1.0)
• Provide only if the RI
does not have a
SWIFT code
Text
50
• SWIFT code
according to ISO
9362
• Mandatory if RI has
a SWIFT code
Text
11
C
Do not use for
CTR/EFT/IFT reports
Boolean
N
institution_code
swift
non_bank_instituti
on
Length
Mandatory
Example
Y
C
branch
• Branch code or
name where the
account is held
• "BranchName" in
LankaFin
Text
255
N
account
• Account number
• "AccNumber" in
LankaFin
Text
50
Y
currency_code
• Currency of the
account
• "CurCode" in
LankaFin
Enumeratio
n
N
See 5.11 Currencies
“Isuru Udana”, “Diriya
Wanitha”
account_name
Name of the account
given by account
holding entity
Text
255
N
iban
IBAN number of the
account
34
N
client_number
CIF number of the
account
30
N
Enumeratio
n
N
See 5.3 Account Type
Type
“t_entity”
N
See 4.4 “t_entity”
personal_account • Account Type
_type
• "AccType" in
LankaFin
t_entity
Holder element for
one “t_entity” element
to provide details of
the entity owning the
account
signatory
Holder element for
1..many “t_person”
N
June 2021 (48 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
elements to provide
details of the persons
associated with the
account
is_primary Identifies the primary
account holder. Only
one signatory may be
marked as
“is_primary”.
t_person
Element to provide
details of the
persons associated
with the account
role Role of the person
associated with the
account
Boolean
N
Type
“t_person”
C
See 4.2 “t_person”
Type
“account_p
erson_role
_type”
N
See 5.13 Account
Person Role Type
opened
Opening date of the
account
DateTime
N
closed
Closing date of the
account (if closed)
DateTime
N
balance
Do not use for
CTR/EFT/IFT reports
Decimal
N
date_balance
Not required for
CTR/EFT/IFT reports
Date
N
status_code
• Account status when
transaction was
initiated
• "AccStatus" in
LankaFin
Enumeratio
n
N
beneficiary
Ultimate beneficiary
of the account
50
N
beneficiary_comm
ent
Any special remark
on the beneficiary
255
N
comments
Generic comments
elements
4000
N
See 5.4 Account
Status Type
Table 12: Details Type “t_account”
June 2021 (49 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.7 Type “t_party”
“t_party” XML type is for “party” XML elements in multi-party transactions, where the details of PAEs involved
in the transaction can be reported with the transaction, without from/to direction. A multi-party transaction can
have 1 to many PAEs in the “involved_parties” element within the “transaction” element, which is a collection
of “party” elements of “t_party” type. Each “party” element can have one Person, Account, or Entity element
(my clients or not my clients), and their role in the transaction should be reported within the “party” element.
Figure 13: Overview Type “t_party”
June 2021 (50 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
role
Role of the PAE in
the transactions
person
Mandatory
Example
Enumeration
Y
See 5.16 Party Type
Involved person
Type “t_person”
person_my_client
Involved person
(my client)
Type
“t_person_my_client”
Y
(one of
them)
account
Involved account
Type “t_account”
account_my_client
Involved account
(my client)
Type
“t_account_my_client”
entity
Involved entity
Type “t_entity”
entity_my_client
Involved entity
(my client)
Type
“t_entity_my_client”
funds_code
Type of funds
used in
transaction
Enumeration
Y
funds_comment
Mandatory
description, if
<funds_code> is
“Other”.
255
C
foreign_currency
If the transaction
is conducted in
foreign currency,
then specify the
foreign currency
details.
Type
“t_foreign_currency”
N
See 4.10
“t_foreign_currency”
country
Country of the
transaction
Enumeration
Y
See 5.12 Country
Codes
significance
The significance
of the subject in
the transaction
Integer
N
0-10
(0 = lowest, 10 =
highest)
comments
Generic
comments
4000
N
See 4.2 “t_person”
See 4.1
“t_person_my_client”
See 4.6 “t_account”
See 4.5
“t_account_my_client”
See 4.4 “t_entity”
See 4.3
“t_entity_my_client”
See 5.2 Funds Type
Table 13: Details Type “t_party”
June 2021 (51 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.8 Type “t_address”
“t_address” XML type is for XML elements which provide address details of persons and entities.
Figure 14: Overview Type “t_address”
Name
Description
Length
Mandatory
address_type
The contact type of the
address
Enumeration
Y
address
If the characters
exceed 100, provide
first 99 characters + “_”
Text
100
Y
town
If the characters of the
address exceed 100,
provide the part from
character 100 onwards
Text
255
N
city
• Relevant District in
Sri Lanka.
• For foreign cities,
provide the word
“Foreign” if the city is
not available to the
RI.
Text
255
Y
zip
Zip Code
10
N
country_code
Country of the address
Enumeration
Y
State
State (for foreign
addresses)
Text
255
N
comments
Generic comments
Text
4000
N
Example
See 5.8
Contact Type
See 6.2
City List
See 5.12
Country
Codes
Table 14: Details Type “t_address
June 2021 (52 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.9 Type “t_phone”
“t_phone” XML type is for XML elements which provide telephone details of persons and entities.
Figure 15: Overview Type “t_phone”
Name
Description
Length
Mandatory
Example
tph_contact_type
The contact type
of the Phone
Enumeratio
n
Y
See 5.8
Contact Type
tph_communication_type
The
communication
type of the Phone
Enumeratio
n
Y
See 5.9
Communication
Type
tph_country_prefix
Country code
Text
4
Y
94
tph_number
• Phone number
(numbers only)
• For local
numbers, length
should be 10
with the leading
zero
Text
50
Y
0112457896
tph_extension
Don’t use
Text
10
N
comments
Generic
comments
Text
4000
N
Table 15: Details Type “t_phone”
June 2021 (53 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.10 Type “t_foreign_currency”
“t_foreign_currency” XML type is for XML elements which provide details of foreign currencies used in the
transaction.
Figure 16: Overview Type “t_foreign_currency”
Name
Description
Length
Mandatory
foreign_currency_code
Currency Code
according to ISO 4217
Enumeration
Y
foreign_amount
Transaction amount in
foreign currency
(maximum 2 decimal
places)
Decimal
Y
foreign_exchange_rate
Use “1”
Decimal
Y
Example
See 5.11
Currencies
Table 16: Details Type “t_foreign_currency”
June 2021 (54 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.11 Type “t_person_identification”
“t_person_identification” XML type is for XML elements which provide details of identification of person.
Figure 17: Overview Type “t_person_identification”
Name
Description
Length
Mandatory
type
ID type
Enumeration
Y
number
number of the identification
document, without spaces
Text
255
Y
issue_date
Identification document issue
date
DateTime
N
expiry_date
Identification document
expiry date
DateTime
N
issued_by
Name of Authority issued the
document
Text
255
N
issue_country
Country where the document
was issued
Enumeration
Y
comments
Generic comments field
Text
4000
N
Example
See 5.5 Identifier
Type
See 5.12 Country
Codes
Table 17: Details Type “t_person_identification”
June 2021 (55 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
4.12 Element “director_id”
“director_id” XML element is for XML elements which provide details of entity controlling persons of
“t_entity_my_client” elements.
Figure 18: Overview Element “director_id”
June 2021 (56 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Name
Description
Length
first_name
All parts of the name, except
the last name. If length
exceeds 100 characters,
provide first 99 characters +
“_”
Text
100
Mandatory
Y
Example
< 100 chars:
“Karunaratne
Mudiyanselage
Saman”
> 100 chars:
“Don Hewa ...
Mudiyanselage
Sama_”
last_name
Text
100
Y
“PERERA”
• Mandatory NIC number for
Sri Lankan nationals
• For old NICs, the format is 9
digits (0-9) plus ‘X’ or ‘V’
(upper case) without any
other characters or spaces
• For new NICs, the format is
12 digits only (0-9) without
any other characters or
spaces
Text
25
C
Old NIC:
950920970V
passport_number • Mandatory Passport number
for foreign nationals
• Alpha-numeric characters
without spaces
Text
25
C
N1234567
id_ number
Last name
(in upper case)
New NIC:
199509209700
nationality1
• Country of Nationality
• "Nationality" in LankaFin
Enumeration
Y
See 5.12 Country
Codes
role
• Role of the person given in
“director_id”
• Report as per table 9.1
Enumeration
Y
See 5.14 Entity
Person Role Type
Table 18: Details Element “director_id”
June 2021 (57 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5. Lookup Values
Lookup values are the enumerations (lists) used in certain XML elements, to provide data in the report. If an
XML element’s data type is Enumeration, it means the values which can be used in that XML element are
confined to the values in relevant enumeration (list) defined in the Schema.
5.1 Submission Type
Report submission type
Code
Description
E
Electronically
M
Manually
-
Unknown
Table 19: Submission Type
5.2 Funds Type
Type of funds used in the transaction
Code
Description
CASH
Cash
ELEC
Electronic
MOBL
Mobile
CRDT
Credit
VRTL
Virtual currency
CHEQ
Cheque
BDRF
Bank draft
BGUR
Bank guarantee
PROM
Promissory note
INBL
Inward Bill
OUBL
Outward Bill
TCHQ
Traveler’s cheque
STOC
Stocks
LOAN
Loan
LOCR
Letter of credit
FCTR
Factor
GVSE
Government securities
SHAR
Shares
CDEB
Corporate Debt
June 2021 (58 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
TAX
Tax
BKCG
Bank charges
LSNG
Leasing
PWNG
Pawning
INTS
Interest
MRGN
Margin
OTH
Other
-
Unknown
Table 20: Funds Type
5.3 Account Type
General type of account
Code
Description
CRNT
Current
SAVG
Savings
TRDP
Term deposit
CODP
Certificate of deposit
LOAN
Loan
LEAS
Leasing
PAWN
Pawning
MORT
Mortgage
TRDG
Trading
TRST
Trust
SDBX
Safe deposit box
MOBW
Mobile wallet
ELCW
Electronic wallet
DIGW
Digital wallet
INPL
Insurance policy - Life
INPG
Insurance policy - General
DEBT
Debts
EQTY
Equities
CRCD
Credit card
INVS
Investment
MGTD
Margin trading
FCTR
Factoring
June 2021 (59 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
OTH
Other
-
Unknown
Table 21: Account type
5.4 Account Status Type
Status of the account at the time of transaction
Code
Description
ACTV
Active
CLSD
Closed
CLBC
Closed by customer
CLRE
Closed by reporting entity
DRMT
Dormant
INAC
Inactive
FRZN
Frozen/Suspended
OTH
Other
-
Unknown
Table 22: Account status type
5.5 Identifier Type
Person identifier document type
Code
Description
BCER
Birth certificate
DL
Driver's license
NIC
National Identity Card
PPT
Passport
PID
Postal ID
TID
Temporary ID
OTH
Other
-
Unknown
Table 23: Identifier Type
June 2021 (60 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5.6 Conduction Type
The channel via the transaction was conducted.
Code
Description
BRCH
Branch
ATM
ATM/CDM
INTR
Internet/Web portal
TLBN
Telebanking
MOAP
Mobile app
AGNT
Agent/Broker
STOR
Standing order
POS
POS
IPG
IPG
SMS
SMS/USSD
EMAL
Email
LETR
Letter/Post
BKOF
Back office
MBWL
Mobile wallet
OTH
Other
-
Unknown
Table 24: Conduction Type
5.7 Report Code
Code
Description
CTR
Cash Transaction Report (CTR)
EFT
Electronic Funds Transfer (EFT)
IFT
International Funds Transfer (IFT)
STR
Suspicious Transaction Report (STR)
Not applicable for this document
AIF
Additional Information File (AIF)
IRF
Information Response File (IRF)
Depending on the number of
transactions to be submitted, XML
upload or web upload should be used
Table 25: Report Code
June 2021 (61 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5.8 Contact Type
Contact type of the telephone and address
Code
Description
PRVT
Private
BUSN
Business
CORS
Correspondent
PERM
Permanent
OTH
Other
-
Unknown
Table 26: Contact Type
5.9 Communication Type
Communication type of the telephone and address
Code
Description
FAX
Fax
LNPH
Landline Phone
MOPH
Mobile Phone
PAGR
Pager
STPH
Satellite Phone
OTH
Other
-
Unknown
Table 27: Communication Type
5.10 Entity Legal Form Type
Legal form of the entity
Code
Description
SOLE
Sole Proprietorship
PTNR
Partnership
PVTL
Private Limited Company
PUBL
Public Limited Company
UNLT
Unlimited Company
June 2021 (62 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
GOVT
Government Institution
STAT
State Owned Enterprises
FNDT
Foundation/Other legal arrangements
TRST
Trust
NGO
NGO
CLUB
Club
SOCT
Society
CHTY
Charity
ASOC
Association
OFSH
Offshore/Overseas Company
OTH
Other
-
Unknown
Table 28: Legal Form Type
5.11 Currencies
World Currencies (and their abbreviations) listed by ISO 4217
Code
Currency
ACU
Asia Clearing Unit
XUA
ADB Unit of Account
AFN
Afghani
DZD
Algerian Dinar
ARS
Argentine Peso
AMD
Armenian Dram
AWG
Aruban Florin
AUD
Australian Dollar
AZN
Azerbaijan Manat
BSD
Bahamian Dollar
BHD
Bahraini Dinar
THB
Baht
PAB
Balboa
BBD
Barbados Dollar
BYN
Belarusian Ruble
BZD
Belize Dollar
BMD
Bermudian Dollar
June 2021 (63 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
VES
Bolívar Soberano
BOB
Boliviano
XBA
Bond Markets Unit European Composite Unit (EURCO)
XBB
Bond Markets Unit European Monetary Unit (E.M.U.-6)
XBD
Bond Markets Unit European Unit of Account 17 (E.U.A.-17)
XBC
Bond Markets Unit European Unit of Account 9 (E.U.A.-9)
BRL
Brazilian Real
BND
Brunei Dollar
BGN
Bulgarian Lev
BIF
Burundi Franc
CVE
Cabo Verde Escudo
CAD
Canadian Dollar
KYD
Cayman Islands Dollar
XOF
CFA Franc BCEAO
XAF
CFA Franc BEAC
XPF
CFP Franc
CLP
Chilean Peso
CNH
Chinese Renminbi
XTS
Codes specifically reserved for testing purposes
COP
Colombian Peso
KMF
Comorian Franc
CDF
Congolese Franc
BAM
Convertible Mark
NIO
Cordoba Oro
CRC
Costa Rican Colon
CUP
Cuban Peso
CZK
Czech Koruna
GMD
Dalasi
DKK
Danish Krone
MKD
Denar
DJF
Djibouti Franc
STN
Dobra
DOP
Dominican Peso
VND
Dong
XCD
East Caribbean Dollar
EGP
Egyptian Pound
June 2021 (64 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
SVC
El Salvador Colon
ETB
Ethiopian Birr
EUR
Euro
FKP
Falkland Islands Pound
FJD
Fiji Dollar
HUF
Forint
GHS
Ghana Cedi
GIP
Gibraltar Pound
XAU
Gold
HTG
Gourde
PYG
Guarani
GNF
Guinean Franc
GYD
Guyana Dollar
HKD
Hong Kong Dollar
UAH
Hryvnia
ISK
Iceland Krona
INR
Indian Rupee
IRR
Iranian Rial
IQD
Iraqi Dinar
JMD
Jamaican Dollar
JOD
Jordanian Dinar
KES
Kenyan Shilling
PGK
Kina
HRK
Kuna
KWD
Kuwaiti Dinar
AOA
Kwanza
MMK
Kyat
LAK
Lao Kip
GEL
Lari
LBP
Lebanese Pound
ALL
Lek
HNL
Lempira
SLL
Leone
LRD
Liberian Dollar
LYD
Libyan Dinar
SZL
Lilangeni
June 2021 (65 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
LSL
Loti
MGA
Malagasy Ariary
MWK
Malawi Kwacha
MYR
Malaysian Ringgit
MUR
Mauritius Rupee
MXN
Mexican Peso
MXV
Mexican Unidad de Inversion (UDI)
MDL
Moldovan Leu
MAD
Moroccan Dirham
MZN
Mozambique Metical
BOV
Mvdol
NGN
Naira
ERN
Nakfa
NAD
Namibia Dollar
NPR
Nepalese Rupee
ANG
Netherlands Antillean Guilder
ILS
New Israeli Sheqel
TWD
New Taiwan Dollar
NZD
New Zealand Dollar
BTN
Ngultrum
KPW
North Korean Won
NOK
Norwegian Krone
MRU
Ouguiya
TOP
Pa’anga
PKR
Pakistan Rupee
XPD
Palladium
MOP
Pataca
CUC
Peso Convertible
UYU
Peso Uruguayo
PHP
Philippine Peso
XPT
Platinum
GBP
Pound Sterling
BWP
Pula
QAR
Qatari Rial
GTQ
Quetzal
ZAR
Rand
June 2021 (66 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
OMR
Rial Omani
KHR
Riel
RON
Romanian Leu
MVR
Rufiyaa
IDR
Rupiah
RUB
Russian Ruble
RWF
Rwanda Franc
SHP
Saint Helena Pound
SAR
Saudi Riyal
XDR
SDR (Special Drawing Right)
RSD
Serbian Dinar
SCR
Seychelles Rupee
XAG
Silver
SGD
Singapore Dollar
PEN
Sol
SBD
Solomon Islands Dollar
KGS
Som
SOS
Somali Shilling
TJS
Somoni
SSP
South Sudanese Pound
LKR
Sri Lanka Rupee
XSU
Sucre
SDG
Sudanese Pound
SRD
Surinam Dollar
SEK
Swedish Krona
CHF
Swiss Franc
SYP
Syrian Pound
BDT
Taka
WST
Tala
TZS
Tanzanian Shilling
KZT
Tenge
XXX
The codes assigned for transactions where no currency is involved
TTD
Trinidad and Tobago Dollar
MNT
Tugrik
TND
Tunisian Dinar
TRY
Turkish Lira
June 2021 (67 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
TMT
Turkmenistan New Manat
AED
UAE Dirham
UGX
Uganda Shilling
CLF
Unidad de Fomento
COU
Unidad de Valor Real
UYW
Unidad Previsional
UYI
Uruguay Peso en Unidades Indexadas (UI)
USD
US Dollar
USN
US Dollar (Next day)
UZS
Uzbekistan Sum
VUV
Vatu
CHE
WIR Euro
CHW
WIR Franc
KRW
Won
YER
Yemeni Rial
JPY
Yen
CNY
Yuan Renminbi
ZMW
Zambian Kwacha
ZWL
Zimbabwe Dollar
PLN
Zloty
Table 29: Currency Codes
5.12 Country Codes
This list states the country names (official short names in English) in alphabetical order as given in ISO
3166-alpha-3 code elements.
Code
Contry
AFG
Afghanistan
ALB
Albania
DZA
Algeria
ASM
American Samoa
AND
Andorra
AGO
Angola
AIA
Anguilla
ATA
Antarctica
June 2021 (68 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
ATG
Antigua and Barbuda
ARG
Argentina
ARM
Armenia
ABW
Aruba
AUS
Australia
AUT
Austria
AZE
Azerbaijan
BHS
Bahamas (the)
BHR
Bahrain
BGD
Bangladesh
BRB
Barbados
BLR
Belarus
BEL
Belgium
BLZ
Belize
BEN
Benin
BMU
Bermuda
BTN
Bhutan
BOL
Bolivia (Plurinational State of)
BES
Bonaire, Sint Eustatius and Saba
BIH
Bosnia and Herzegovina
BWA
Botswana
BVT
Bouvet Island
BRA
Brazil
IOT
British Indian Ocean Territory (the)
BRN
Brunei Darussalam
BGR
Bulgaria
BFA
Burkina Faso
BDI
Burundi
CPV
Cabo Verde
KHM
Cambodia
CMR
Cameroon
CAN
Canada
CYM
Cayman Islands (the)
CAF
Central African Republic (the)
TCD
Chad
CHL
Chile
June 2021 (69 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
CHN
China
CXR
Christmas Island
CCK
Cocos (Keeling) Islands (the)
COL
Colombia
COM
Comoros (the)
COD
Congo (the Democratic Republic of the)
COG
Congo (the)
COK
Cook Islands (the)
CRI
Costa Rica
HRV
Croatia
CUB
Cuba
CUW
Curaçao
CYP
Cyprus
CZE
Czechia
CIV
Côte d'Ivoire
DNK
Denmark
DJI
Djibouti
DMA
Dominica
DOM
Dominican Republic (the)
ECU
Ecuador
EGY
Egypt
SLV
El Salvador
GNQ
Equatorial Guinea
ERI
Eritrea
EST
Estonia
SWZ
Eswatini
ETH
Ethiopia
FLK
Falkland Islands (the) [Malvinas]
FRO
Faroe Islands (the)
FJI
Fiji
FIN
Finland
FRA
France
GUF
French Guiana
PYF
French Polynesia
ATF
French Southern Territories (the)
GAB
Gabon
June 2021 (70 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
GMB
Gambia (the)
GEO
Georgia
DEU
Germany
GHA
Ghana
GIB
Gibraltar
GRC
Greece
GRL
Greenland
GRD
Grenada
GLP
Guadeloupe
GUM
Guam
GTM
Guatemala
GGY
Guernsey
GIN
Guinea
GNB
Guinea-Bissau
GUY
Guyana
HTI
Haiti
HMD
Heard Island and McDonald Islands
VAT
Holy See (the)
HND
Honduras
HKG
Hong Kong
HUN
Hungary
ISL
Iceland
IND
India
IDN
Indonesia
IRN
Iran (Islamic Republic of)
IRQ
Iraq
IRL
Ireland
IMN
Isle of Man
ISR
Israel
ITA
Italy
JAM
Jamaica
JPN
Japan
JEY
Jersey
JOR
Jordan
KAZ
Kazakhstan
KEN
Kenya
June 2021 (71 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
KIR
Kiribati
PRK
Korea (the Democratic People's Republic of)
KOR
Korea (the Republic of)
KWT
Kuwait
KGZ
Kyrgyzstan
LAO
Lao People's Democratic Republic (the)
LVA
Latvia
LBN
Lebanon
LSO
Lesotho
LBR
Liberia
LBY
Libya
LIE
Liechtenstein
LTU
Lithuania
LUX
Luxembourg
MAC
Macao
MDG
Madagascar
MWI
Malawi
MYS
Malaysia
MDV
Maldives
MLI
Mali
MLT
Malta
MHL
Marshall Islands (the)
MTQ
Martinique
MRT
Mauritania
MUS
Mauritius
MYT
Mayotte
MEX
Mexico
FSM
Micronesia (Federated States of)
MDA
Moldova (the Republic of)
MCO
Monaco
MNG
Mongolia
MNE
Montenegro
MSR
Montserrat
MAR
Morocco
MOZ
Mozambique
MMR
Myanmar
June 2021 (72 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
NAM
Namibia
NRU
Nauru
NPL
Nepal
NLD
Netherlands (the)
NCL
New Caledonia
NZL
New Zealand
NIC
Nicaragua
NER
Niger (the)
NGA
Nigeria
NIU
Niue
NFK
Norfolk Island
MKD
North Macedonia
MNP
Northern Mariana Islands (the)
NOR
Norway
OMN
Oman
PAK
Pakistan
PLW
Palau
PSE
Palestine, State of
PAN
Panama
PNG
Papua New Guinea
PRY
Paraguay
PER
Peru
PHL
Philippines (the)
PCN
Pitcairn
POL
Poland
PRT
Portugal
PRI
Puerto Rico
QAT
Qatar
ROU
Romania
RUS
Russian Federation (the)
RWA
Rwanda
REU
Réunion
BLM
Saint Barthélemy
SHN
Saint Helena, Ascension and Tristan da Cunha
KNA
Saint Kitts and Nevis
June 2021 (73 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
LCA
Saint Lucia
MAF
Saint Martin (French part)
SPM
Saint Pierre and Miquelon
VCT
Saint Vincent and the Grenadines
WSM
Samoa
SMR
San Marino
STP
Sao Tome and Principe
SAU
Saudi Arabia
SEN
Senegal
SRB
Serbia
SYC
Seychelles
SLE
Sierra Leone
SGP
Singapore
SXM
Sint Maarten (Dutch part)
SVK
Slovakia
SVN
Slovenia
SLB
Solomon Islands
SOM
Somalia
ZAF
South Africa
SGS
South Georgia and the South Sandwich Islands
SSD
South Sudan
ESP
Spain
LKA
Sri Lanka
SDN
Sudan (the)
SUR
Suriname
SJM
Svalbard and Jan Mayen
SWE
Sweden
CHE
Switzerland
SYR
Syrian Arab Republic (the)
TWN
Taiwan (Province of China)
TJK
Tajikistan
TZA
Tanzania, the United Republic of
THA
Thailand
TLS
Timor-Leste
TGO
Togo
TKL
Tokelau
June 2021 (74 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
TON
Tonga
TTO
Trinidad and Tobago
TUN
Tunisia
TUR
Turkey
TKM
Turkmenistan
TCA
Turks and Caicos Islands (the)
TUV
Tuvalu
UGA
Uganda
UKR
Ukraine
ARE
United Arab Emirates (the)
GBR
United Kingdom of Great Britain and Northern Ireland (the)
UMI
United States Minor Outlying Islands (the)
USA
United States of America (the)
URY
Uruguay
UZB
Uzbekistan
VUT
Vanuatu
VEN
Venezuela (Bolivarian Republic of)
VNM
Viet Nam
VGB
Virgin Islands (British)
VIR
Virgin Islands (U.S.)
WLF
Wallis and Futuna
ESH
Western Sahara*
YEM
Yemen
ZMB
Zambia
ZWE
Zimbabwe
ALA
Åland Islands
Table 30: Country Codes
June 2021 (75 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5.13 Account Person Role Type
Relationship of a person to an account.
Code
Description
ACHLD
Account Holder
SIGNT
Signatory
BENEF
Beneficiary
LGGUD
Legal guardian
PWRAT
Power of attorney
NOMIN
Nominee
OTH
Other
-
Unknown
Table 31: Type “account_person_role_type”
5.14 Entity Person Role Type
Relationship of an entity to an account
Value
Description
DRCT
Director
BMEM
Board Member
CEO
CEO/MD
CSEC
Company Secretary
BENE
Beneficiary
SHLD
Shareholder
UBO
Ultimate Beneficial Owner
TRST
Trustee/Co-Trustee
SETL
Settler
CHPE
Chairperson
SECT
Secretary
TRSR
Treasurer
OWNR
Owner
PRNR
Partner
HOIN
Head of Institution
OTH
Other
-
Unknown
Table 32: Type “entity_person_role_type”
June 2021 (76 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
5.15 Gender Type
Value
Description
M
Male
F
Female
O
Other
-
Unknown
Table 33: Gender Type
5.16 Party Type
Value
Description
PYEE
Payee
PYER
Payer
BENF
Beneficiary
OTH
Other
-
Unknown
Table 34: Gender Type
June 2021 (77 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
6. Annexures
6.1 Transaction Number
Transaction
Type
CEFTS
Unique Reference
Description
[STAN + RRN + Local
Transaction Date +
Local Transaction Time]
Unique Reference should be created by concatenating the
values of STAN, RRN, Date and Time fields in the CEFTS
message relating to the particular transaction without any
spaces in the same order.
STAN = Field 11
RRN = Field 37
Local Transaction Date
= Field 13
Local Transaction Time
= Field 12
CITS
(cleared
cheques)
Unique Identification
(UI) Number of the
cheque image
25 digit number used as the file name of the cheque image.
SLIPS
Destination Bank No. +
Destination A/C No. +
Originating Bank No. +
Originating Account No.
+ Value Date
(YYMMDD) + Amount
Field Length:
Destination Bank No.: n 4
Destination A/C No.: n 12
Originating Bank No.: n 4
Originating Account No.: n 12
Value Date (YYMMDD): n 6
Amount: n 12
Example:
Destination Bank No: 7056, Destination A/C No: 145261,
Originating Bank No: 30, Originating Account No: 80012005,
Value Date: 2020 Jan 16, Amount: Rs. 5,550,750.00
transactionnumber:
70560000001452610030000080012005200116000555075000
(Add preceding zeros to fill the maximum character count for
each field)
Note:
Suppose, three SLIPS transactions occur for the same
destination and originating accounts, on the same day, for same
amounts; then the first digit of the “Amount” field needs to be an
incrementing number based of the order of the transactions.
June 2021 (78 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Considering the above example, three transactionnumbers
would be;
70560000001452610030000080012005200116000555075000
70560000001452610030000080012005200116100555075000
70560000001452610030000080012005200116200555075000
SWIFT /
RTGS
Transaction Reference
Number in the message
Internal
Transactions
Internal Transaction
Reference Number
Cash
Transactions
Institution Code
(“rentity_id”) + Date
Stamp (DDMMYY) +
Internal Reference
Number
Field 20 in the SWIFT/RTGS message
7031050319123456CT
Table 35: Transaction Number
Note: In instances where the unique reference number cannot be constructed as per the format given in Table
34 (due to technical limitations), any transaction reference which can be used by the RIs to uniquely identify
the transaction can be used as the unique reference number.
6.2 City List
City Code
Ampara
Anuradhapura
Badulla
Batticaloa
Colombo
Galle
Gampaha
Hambantota
Jaffna
Kalutara
Kandy
Kegalle
Kilinochchi
Kurunegala
Mannar
June 2021 (79 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)
Matale
Matara
Moneragala
Mullaitivu
Nuwara Eliya
Polonnaruwa
Puttalam
Ratnapura
Trincomalee
Vavuniya
FOREIGN
Table 36: City List
Note: Use the relevant District as given in the above table for the address. For foreign addresses, use the
constant “FOREIGN” for the city.
June 2021 (80 of 80)
Standard Reporting Instructions and Specifications for XML Reports (CTR/EFT/IFT Reports)