The OECD Treaty Relief and Compliance TRACE …...withholding tax refunds should be paid The sixth...

TRACE XML SchemaUser Guide

For more information:

[email protected]

@OECDtax

www.oecd.org/tax

The OECD Treaty Relief and ComplianceEnhancement (TRACE) initiative hasdeveloped the Authorised Intermediary (AI)system. This standardised system allows theclaiming of withholding tax relief at sourceon portfolio investments. It removes theadministrative barriers that affect the abilityof portfolio investors to effectively claim thereduced rates of withholding tax to whichthey are entitled pursuant to tax treaties or todomestic law of the country of investment. Itminimises administrative costs for allstakeholders and enhances the ability of bothsource and residence countries to ensureproper compliance with tax obligations.

This document contains the structure of theTRACE XML Schema, as well as a User Guide, asapproved by the Committee on Fiscal Affairsin February 2020. It provides guidance on thestandardised electronic format to be used forreporting TRACE-related information byfinancial institutions to tax administrationsand for the exchange of information betweentax administrations. It is intended tocomplement the TRACE ImplementationPackage, which sets out the procedures,forms and agreements to be put in place tooperationalise the TRACE AI system.

Trace XML Schema: User Guide

This document, as well as any data and any map included herein, are without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.

Please cite this publication as: OECD (2020), Trace XML Schema: User Guide, OECD, Paris. www.oecd.org/tax/forum-on-tax-administration/trace-xml-schema-user-guide.htm

Photo credits: Cover © klss – Shutterstock.com

© OECD 2020

The use of this work, whether digital or print, is governed by the Terms and Conditions to be found at www.oecd.org/termsandconditions

This document was approved by the Committee on Fiscal Affairs on 18 February 2020 and prepared for publication by the OECD secretariat

http://www.oecd.org/termsandconditions

www.oecd.org/tax/forum-on-tax-administration/trace-xml-schema-user-guide.htm

TRACE XML SCHEMA: USER GUIDE © OECD 2020

TABLE OF CONTENTS – 3

Table of contents

TRACE XML User Guide (v1.1) � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 5Introduction � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 5How is the content of the TRACE Implementation Package reflected in the TRACE XML Schema and User Guide? � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 6What is the function of the requirement field of a data element? � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 7

TRACE XML Schema information � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 9I� Message Header � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 9II� PersonParty_Type � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 11

IIa� ResCountryCode� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 12IIb� TIN Type� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 12IIc� NamePerson_Type� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 13IId� Address_Type � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 14IIe� Nationality � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 16IIf� BirthInfo � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 16

III� OrganisationParty_Type � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 17IIIa� ResCountryCode � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 17IIIb� Entity IN (OrganisationIN_Type) � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 18IIIc� Organisation Name � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 18IIId� Entity Legal Type � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 18IIIe� Place of incorporation � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 19

IV� TRACE Body � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 19IVa� AI � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 20IVb� Group AI � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 20IVc� CI � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 21IVd� Group AI CI� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 22IVe� Report Account Holders� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 22IVe� Report Account Holders – Investor � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 23IVe� Report Account Holders – Investor – InvestorID (InvestorID_Type) � � � � � � � � � � � � � � � � � � � 23IVe� Report Account Holders – Investor – Payment � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 24Trace Basic Payment (TracePaymentBasic_Type) � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 25Trace Basic Payment – Withholding tax rate � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 28Trace Basic Payment – Adjustment � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 28Trace Basic Payment – Adjustment – Amount (TraceAdjustment_Type)� � � � � � � � � � � � � � � � � � � � 29IVe� Report Account Holders – OtherAI � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 29

V� Summary (CorrectableEndYearSummary_Type) � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 30V� Summary – ACP (Information regarding Aggregate Covered Payments) � � � � � � � � � � � � � � � � � 31V� Summary – ACP – GrossACP (Gross Amount of Covered Payments) � � � � � � � � � � � � � � � � � � � 32V� Summary – ACP – WHT (Aggregate Tax Withheld) � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 33V� Summary – TotalAdjust � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 33V� Summary – TotalAdjust – Refund � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 34V� Summary – TotalAdjust – Refund – Account (AccountInfo_Type) � � � � � � � � � � � � � � � � � � � � � � 35V� Summary – TotalAdjust – Refund – Account – Account Number (AccountNumber_Type) � � � 35


4 – TABLE OF CONTENTS

VI� Schema version � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 36VII� Corrections � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 36

Introduction � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 36Technical Guidance � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 37MessageSpec, Corrections and Cancellations � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 39

TRACE correction examples � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 40

Appendix A. TRACE XML Schema v1.1 diagrams � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 47

Appendix B. Glossary of namespaces � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � 68


TRACE XML USER GUIDE – 5

TRACE XML User Guide (v1.1)

Introduction

Pursuant to Section VII of the Procedures regarding the Operation of a Financial Intermediary as an Authorised Intermediary (the “Procedures”), the Authorised Intermediary is required to report the following information to the Source Country:

a� detailed information regarding Reportable Payments paid directly or through one or more Contractual Intermediaries, to its Account Holders that are Investors as well as those that are Authorised Intermediaries, during the calendar year;

b� a Year-End Summary of Covered Payments�

The forms for such reporting are set out in Annex 1 to the Procedures (the “Forms”)� Pursuant to Section VII(C) of the Procedures the Authorised Intermediary may file such reports electronically using the format developed for these purposes by the OECD�

Once the information described in a) above is received by the Source Country, it is expected that the Source Country will provide it to the government of the Investor’s residence country through automatic exchange of information programs�

The TRACE XML schema is the electronic format to be used by Authorised Intermediaries for complying with the above reporting requirement to the Source Country and by Source Countries to exchange investor specific information received from Authorised Intermediaries with the countries of residence of the Investors�

This User Guide explains the information required to be included in each TRACE data element to be reported in the TRACE XML Schema� It also contains guidance on how to make corrections of data items within a file that can be processed automatically�

The TRACE User Guide is divided in the following sections:

i� Message Header with the sender, recipient, message type, reporting period

ii� Identification of Individuals (PersonParty_Type)

iii� Identification of Entities (OrganisationParty_Type)

iv� TRACE Body

v� Year-End Summary

vi� Schema version

vii� Corrections


6 – TRACE XML USER GUIDE

Appendix A to the TRACE User Guide shows a diagrammatic representation of the TRACE XML Schema with all its elements� The numbers next to the headings are the corresponding section numbers in the User Guide text�

Appendix B to the TRACE User Guide contains a Glossary of namespaces for the TRACE XML Schema�

How is the content of the TRACE Implementation Package reflected in the TRACE XML Schema and User Guide?

As set out in the introduction, the relevant rules governing reporting under TRACE and the items to be reported are contained in the Procedures, as well as in the forms set out in Annex 1 to the Procedures� The TRACE XML Schema and the User Guide reflect the content of both the Procedures and the forms�

In the first section of the TRACE User Guide (Message Header), explanations are provided in relation to the Message Header elements of the TRACE XML Schema� In the Message Header section of the TRACE XML Schema, information is provided in relation to the distinct features of the message that is being sent� These features include information on the sender, the recipient of the message, the year to which the message relates, the time the message was sent and the whether the message is a new, corrected or revised version�

The second and third sections of the TRACE User Guide contain a type for both individuals (section II) and entities (section III) capturing all TRACE-relevant data elements� These include identification (including the name, date and place of birth, TIN, legal form, etc�), tax residency and addresses elements� As both the PersonParty_Type (for individuals) and the OrganisationParty_Type (for entities) are used on several locations within the TRACE XML Schema, these types are described prior to the TRACE Body Section� The structure of both types reflects the content of the forms of Appendix 1 of the Procedures and is closely aligned to the corresponding types in the CRS XML Schema (the Schema for reporting and exchange of information in accordance with the Standard for Automatic Exchange of Financial Account Information)�

The fourth section of the TRACE User Guide, corresponding to the TRACE Body element in the TRACE XML Schema, contains guidance on all Account Holder-specific reporting information to be reported by the Authorised Intermediary for the reporting period, as foreseen by Section VII of the Procedures� In accordance with the different levels foreseen in the TRACE XML Schema, in a first step, the reporting Authorised Intermediary is identified (AI element)� The information contained in this element corresponds to the corresponding items foreseen in the Forms� Secondly, all Account Holder-related information is contained in the Group AI element� In certain cases, and in line with the Forms, information on Contractual Intermediaries is provided, in case an Account Holder has invested through such Contractual Intermediaries and the Authorised Intermediary has assumed reporting� The TRACE XML Schema provides a distinction between those Account Holders that are Investors and those that are themselves Authorised Intermediaries� For both groups of Account Holders, the TRACE XML Schema allows to provide information on both their identity, according to the types of sections II and III (Individual and Organisation elements), and the Covered Payments they have received, as well as the tax withheld thereon (Payment element)� The content of these elements reflects the captions contained in the relevant forms, in particular forms 10, 11 and 12� Within the Payment element, an Adjustment element is foreseen in order to accommodate subsequent


TRACE XML USER GUIDE – 7

adjustments to the withholding tax applied on Covered Payments, as foreseen by form 12 and Section VI�B� and VI�C� of the Procedures�

The fifth section of the TRACE User Guide describes the Summary element of the TRACE XML Schema, containing the year-end summary of covered payments, as foreseen in form 12� In addition to an overview of the aggregate amount of Covered Payments for which the Authorised Intermediary has ensured reporting, the element contains information on the total amount of subsequent adjustments made by the Authorised Intermediary, as well as on the account of the Authorised Intermediary on which eventual withholding tax refunds should be paid�

The sixth section contains guidance on how corrections, both in relation to incorrect or incomplete Account Holder-related information and regarding adjustments to withholding taxes on Covered Payments, should be handled with the TRACE XML Schema and gives a number of illustrated examples�

What is the function of the requirement field of a data element?

Each data element contains a requirement field indicating the level of scrutiny that the TRACE XML Schema applies to the element� The following requirement levels are foreseen by the TRACE XML Schema, which will be further described below:

• Validation

• Validation (Choice)

• (Optional) Mandatory

• Optional�

Elements having a “Validation” requirement must be completed in all cases� The validation requirement is selected in case the TRACE Implementation Package requires a certain element to be provided for the purpose of reporting under TRACE� The TRACE XML Schema allows validation elements to be automatically checked by the sender in a manner that the message cannot be sent when validation elements are not or incorrectly filled� Similarly the receiver of the message may carry out an automated check and may reject the file� Examples of validation elements include the applied withholding tax rate, the name of the Investor, the legal form of an Entity, etc�

In case the requirement of an element is “Validation (Choice)” in the TRACE XML Schema, the TRACE Implementation Package foresees that a mandatory choice between a number of options� Accordingly, the TRACE XML Schema demands that one of the validation (choice) elements, which are schematically below a validation element, is selected and filled� This is, for instance the case in relation to the (validation) Report Account Holder element, where a choice between Investor and Other Authorised Intermediary is to be made�

Elements that have an “(Optional) Mandatory” requirement reflect instances within the TRACE Implementation Package where an item of information is required to be provided, but only in certain cases� As an example, information on a Contractual Intermediary needs to be provided, if an Account Holder has invested through a Contractual Intermediary, but not in case of a direct investment through the Authorised Intermediary� As the information does not need to be provided in all cases, the validation requirement is not suitable, as failure to provide input to a validation element would prevent the sender from sending the


8 – TRACE XML USER GUIDE

message� Further guidance with respect to the expected content of particular elements of the TRACE XML Schema is provided in the TRACE User Guide�

Elements that have an “Optional” requirement may be filled, in case it is deemed useful by the Authorised Intermediary in order to ensure high quality reporting under TRACE� An example for an optional element is the Type Source Country element, which allow the Authorised Intermediary to provide additional information on the designation of an income type in the Source Country, where deemed useful�


TRACE XML SCHEMA INFORMATION – 9

TRACE XML Schema information

I. Message Header

Information in the message header identifies the Authorised Intermediary that is sending the message� It specifies when the message was created, what period (normally a year) the report is for, and the nature of the report (original, corrected, supplemental, etc�)�

[For use by Source Countries to exchange investors specific information received from AIs with the jurisdiction(s) of residence of such Investors, the instructions outlined in italic and between square brackets in this User Guide are to be followed�]

Element Attribute Size Input Type RequirementSender Validation

The Sender element indicates the sender of the message� As TRACE allows both reporting by an Authorised Intermediary to the Source Country, as well as by the Source Country to the jurisdiction of residence of Investors, a choice between sending by an Authorised Intermediary and by a jurisdiction is provided in this element�

Element Attribute Size Input Type RequirementSendingCompanyAIIN 1 to 200 characters stf:StringMin1Max200_Type Validation (Choice)

In case an Authorised Intermediary is sending a message to the Source Country, it is mandatory that the sending Authorised Intermediary provides its Authorised Intermediary Identification Number in order to allow the receiving Source Country to verify that the message was sent by an Authorised Intermediaries�

[In case of a Source Country sending information to the jurisdiction(s) of residence of Investors, this field is to be left blank�]

Element Attribute Size Input Type RequirementTransmittingCountry 2-character iso:CountryCode_Type Validation (Choice)

This data element identifies the jurisdiction transmitting the message, in case the message is send by a Competent Authority, as opposed to an Authorised Intermediary� This data element uses the 2-character alphabetic country code and country name list1

1� The following disclaimer refers to all uses of the ISO country code list in the CRS schema: For practical reasons, the list is based on the ISO 3166-1 country list which is currently used by banks and other financial institutions, and hence by tax administrations. The use of this list does not imply the expression by the OECD of any opinion whatsoever concerning the legal status of the territories listed. Its content is without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.


10 – TRACE XML SCHEMA INFORMATION

based on the ISO 3166-1 Alpha 2 standard� [In case of transmission by the Source Country Competent Authority to the Competent Authorities of the jurisdiction(s) of residence of Investors, the Source Country code should be entered here�]

Element Attribute Size Input Type RequirementReceivingCountry 2-character iso:CountryCode_Type Validation

This data element identifies the jurisdiction of the tax administration (i�e� the Source Country) that is the intended recipient of the message� This data element uses the 2-character alphabetic country code based on the ISO 3166-1 Alpha 2 standard�

[In case of transmission by the Source Country Competent Authority to the Competent Authorities of the jurisdiction(s) of residence of Investors, the country code of the receiving Competent Authority in the jurisdiction of residence of Investors should be entered here�]

Element Attribute Size Input Type RequirementMessageType trc:MessageType_EnumType Validation

This data element specifies the type of message being sent� The only allowable entry in this field is “TRACE”�

Element Attribute Size Input Type RequirementWarning 1 to 4’000 characters stf:StringMin1Max4000_Type Optional

This data element is a free text field allowing input of specific cautionary instructions about use of the TRACE message content� If the reported data is for a period other than for a full reporting year this information can be given here as narrative e�g� “ten month period”� Similarly, information in relation to file splitting can be indicated here�

Element Attribute Size Input Type RequirementContact 1 to 4’000 characters stf:StringMin1Max4000_Type Optional

This data element is a free text field allowing input of specific contact information for the sender of the message (i�e� the Authorised Intermediary or the Source Country tax authorities in case transmission to the jurisdiction(s) of residence of Investors)�

Element Attribute Size Input Type RequirementMessageRefID 1 to 170 characters stf:StringMin1Max170_Type Validation

This data element is a free text field capturing the sender’s unique message identifier (created by the sender) that identifies the particular message being sent� The identifier allows both the sender and receiver to identify the specific message later if questions or corrections arise�

Element Attribute Size Input Type RequirementMessageTypeIndic trc:TrcMessageTypeIndic_EnumType Validation

This data element allows the sender to define the type of message sent� This element identifies whether data is new or corrected (see Guidance on the Correction Process below)� Messages must contain all new or all corrected/deleted data, not a combination of both�



The possible values are:

• TRACE701 = The message contains new information

• TRACE702 = The message contains corrections/deletions for previously sent information

• TRACE703 = The message advises there is no data to report

• TRACE704 = The message is to void a previous message

Element Attribute Size Input Type RequirementCorrMessageRefID 1 to 170 characters stf:StringMin1Max170_Type Optional

To cancel a complete message, the MessageSpec�CorrMessageRefID can be used only if the AI has obtained agreed prior agreement from the source country or if both exchanging countries have mutually agreed on its use� Otherwise, a correction message should be sent deleting all records of the erroneous message in these instances�

Element Attribute Size Input Type RequirementReportingPeriod xsd:date Validation

This data element identifies the last day of the reporting period (normally a tax year) to which the message relates in YYYY-MM-DD format� For example, if reporting information for Covered Payments made in calendar year 2014, the field would read, “2014-12-31”. If exceptionally the reporting period is not a year then show the length of the reporting period in Warning�

Element Attribute Size Input Type RequirementTimestamp xsd:dateTime Validation

This data element identifies the date and time when the message was compiled� It is anticipated this element will be automatically populated by the host system� The format for use is YYYY-MM-DD’T’hh:mm:ss�nnn� Fractions of seconds may be used (in such a case the milliseconds will be provided in 3 digits, see “�nnn” in the format above)� Examples: 2018-02-15T14:37:40 or 2018-02-15T14:37:40.789 (with milliseconds).

II. PersonParty_Type

The data elements in this section are used for Investors who are Individuals receiving Covered Payments from the Source Country� This complex type is comprised of the following data elements:

Element Attribute Size Input Type RequirementResCountryCode Validation

Element Attribute Size Input Type RequirementTIN 1 to 200 characters trc:TIN_Type (Optional) Mandatory

Element Attribute Size Input Type RequirementName trc:NamePerson_Type Validation



Element Attribute Size Input Type RequirementAddress trc:Address_Type Validation

Element Attribute Size Input Type RequirementNationality 2-character iso:CountryCode_Type Optional

Element Attribute Size Input Type RequirementBirthInfo (Optional) Mandatory

Element Attribute Size Input Type RequirementOtherInfo 1 to 4’000 characters stf:StringMin1Max4000_Type Optional

IIa. ResCountryCode


This data element describes the tax residence country code(s) for the Investor being reported upon and must be present in all data records communicated to the Source Country Competent Authority under TRACE�

Element Attribute Size Input Type RequirementFirst 2-character iso:CountryCode_Type Validation

In line with the Part 2(1) of the Investor Self-Declaration for Individuals contained in the TRACE Implementation Package, the First element should contain the first country of residence for tax purposes provided by the Investor�

Element Attribute Size Input Type RequirementOther 2-character iso:CountryCode_Type Optional

The Other element should contain all other countries of residence provided by the Investor, if any, as provided for by Part 2(2)(b) of the Investor Self-Declaration for Individuals�

[In case of reporting by the Competent Authorities of the Source Country to the jurisdictions of residence of Investors, the sorting of the relevant information to be send to the Competent Authority of a jurisdiction of residence of Investors should be carried out on the basis of the residency information provided in this field.]

IIb. TIN Type

Element Attribute Size Input Type RequirementTIN 1 to 200 characters trc:TIN_Type (Optional) Mandatory

This data element identifies the Tax Identification Number (TIN) used by the tax administration in the Investor’s jurisdiction of residence to identify the Investor� The TIN (if available) should be supplied as specified in the TRACE Implementation Package�

Element Attribute Size Input Type RequirementTIN issuedBy 2-character iso:CountryCode_Type (Optional) Mandatory

This attribute identifies the jurisdiction that issued the TIN�



IIc. NamePerson_Type

Element Attribute Size Input Type RequirementNamePerson_Type nameType stf:OECDNameType_EnumType Optional

This data element allows the Authorised Intermediary to report both the name at birth and the name after marriage�

OECDNameType_EnumTypeLike the CRS XML Schema, the TRACE XML schema reuses elements of the STF

schema that was developed by the OECD for exchange of information� It is possible for STF documents to contain several names for the same party� This is a qualifier to indicate the type of a particular name� Such types include nicknames (“nick”), names under which a party does business (“dba” a short name for the entity, or a name that is used for public acquaintance instead of the official business name) etc�


• OECD201 = indiv

• OECD202 = alias

• OECD203 = nick

• OECD204 = aka

• OECD205 = dba

• OECD206 = legal

• OECD207 = atbirth

Element Attribute Size Input Type RequirementPrecedingTitle 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementTitle 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementFirstName 1 to 200 characters stf:StringMin1Max200_Type Validation

This data element is required for TRACE reporting�

Element Attribute Size Input Type RequirementFirstName xnlNameType 1 to 200 characters stf:StringMin1Max200_Type Optional

See the name type explanation at the beginning of this section�

Element Attribute Size Input Type RequirementMiddleName 1 to 200 characters stf:StringMin1Max200_Type Optional

This data element allows for the Individual’s Middle Name� If the reporting Authorised Intermediary holds a Middle Name or initial it may be included here�



Element Attribute Size Input Type RequirementMiddleName xnlNameType 1 to 200 characters stf:StringMin1Max200_Type Optional


Element Attribute Size Input Type RequirementNamePrefix 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementNamePrefix xnlNameType 1 to 200 characters stf:StringMin1Max200_Type Optional


Element Attribute Size Input Type RequirementLastName 1 to 200 characters stf:StringMin1Max200_Type Validation

This data element is required for TRACE reporting� The reporting Authorised Intermediary or tax administration transmitting the message must provide the Investor’s last name� This field can include any prefix or suffix legally used by the Investor�

As the element is a string it is possible to use this for a free format name or two last names although wherever possible the structured first name and last name should be used�

Element Attribute Size Input Type RequirementLastName xnlNameType 1 to 200 characters stf:StringMin1Max200_Type Optional


Element Attribute Size Input Type RequirementGenerationIdentifier 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementSuffix 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementGeneralSuffix 1 to 200 characters stf:StringMin1Max200_Type Optional

IId. Address_TypeThere are two options for Address type in the schema – AddressFix and AddressFree�

AddressFix should be used for all TRACE reporting unless the reporting Authorised Intermediary or tax administration transmitting the message cannot define the various parts of the Investor’s address�

This data element is the permanent residence address e�g� of the individual Investor�

Element Attribute Size Input Type RequirementCountryCode 2-character iso:CountryCode_Type Validation

This data element provides the country code associated with the Investor’s address�

Element Attribute Size Input Type RequirementAddressFree 1 to 4’000 characters stf:StringMin1Max4000_Type Optional



This data element allows input of address information in free text� If the user chooses the option to enter the data required in a less structured way in “AddressFree” all available address details shall be presented as one string of bytes, blank or “/” (slash) or carriage return-line feed used as a delimiter between parts of the address� This option should only be used if the data cannot be presented in the AddressFix format�

NOTE: If the reporting Authorised Intermediary or tax administration transmitting the message selects AddressFix, it will have the option of inputting the full street address of the Investor in the AddressFree element rather than using the related fixed elements� In this case, the city, subentity, and postal code information should still be entered in the appropriate fixed elements�

Element Attribute Size Input Type RequirementAddressType legalAddressType stf:OECDLegalAddressType_EnumType Optional

OECDLegalAddressType_EnumTypeThis is a datatype for an attribute to an address� It serves to indicate the legal character

of that address (residential, business etc�)


• OECD301 = residentialOrBusiness

• OECD302 = residential

• OECD303 = business

• OECD304 = registeredOffice

• OECD305 = unspecified

Element Attribute Size Input Type RequirementStreet 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementBuildingIdentifier 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementSuiteIdentifier 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementFloorIdentifier 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementDistrictName 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementPOB 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementPostCode 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementCity 1 to 200 characters stf:StringMin1Max200_Type Validation



Element Attribute Size Input Type RequirementCountrySubentity 1 to 200 characters stf:StringMin1Max200_Type Optional

The above data elements comprise the AddressFix type� The “City” data element is required for schema validation� The PostCode should always be included where it exists� Information pertaining to the Investor’s street address may be entered here or in the AddressFree data element�

IIe. Nationality

Element Attribute Size Input Type RequirementNationality 2-character iso:CountryCode_Type Optional

This data element is not required for TRACE reporting�

IIf. BirthInfo

Element Attribute Size Input Type RequirementBirthDate xsd:date (Optional) Mandatory

This data element identifies the date of birth of an individual Investor and is to be provided in all instances�

The data format is YYYY-MM-DD�

The three data elements below apply specifically to the place of birth and should be provided, unless the Authorised Intermediary is prohibited by law to collect and/or report such information�

Element Attribute Size Input Type RequirementCity 1 to 200 characters stf:StringMin1Max200_Type (Optional) Mandatory

Element Attribute Size Input Type RequirementCitySubentity 1 to 200 characters stf:StringMin1Max200_Type Optional

Element Attribute Size Input Type RequirementCountryInfo (Optional) Mandatory

This data element gives a choice between a current jurisdiction (identified by 2-character country code) or a former jurisdiction (identified by name)� One or other should be supplied if place of birth is reported, together with City or City and CitySubentity�

Element Attribute Size Input Type RequirementCountryCode 2-character iso:CountryCode_Type Validation (Choice)

Element Attribute Size Input Type RequirementFormerCountryName 1 to 200 characters stf:StringMin1Max200_Type Validation (Choice)



III. OrganisationParty_Type

This complex type identifies the name of an Investor that is an Entity as opposed to an Individual�

It comprises the following data elements:


Element Attribute Size Input Type RequirementIN 1 to 200 characters trc:OrganisationIN_Type (Optional) Mandatory

Element Attribute Size Input Type RequirementName 1 to 200 characters trc:NameOrganisation_Type Validation

Element Attribute Size Input Type RequirementAddress trc:Address_Type Validation

Element Attribute Size Input Type RequirementEntityLegalType trc:OECDLegalType_EnumType Validation

Element Attribute Size Input Type RequirementPlaceIncorporation Validation


IIIa. ResCountryCode


This data element should contain the tax residence country code(s) of the jurisdiction of residence of the Entity being reported upon�

Element Attribute Size Input Type RequirementFirst 2-character iso:CountryCode_Type Validation

In line with the Part 2(1) of the Investor Self-Declaration for Entities contained in the TRACE Implementation Package, the First element should contain the first country of residence for tax purposes provided by the Entity�

Element Attribute Size Input Type RequirementOther 2-character iso:CountryCode_Type Optional

The Other element should contain all other countries of residence provided by the Entity, if any, as provided for by Part 2(2)(b) of the Investor Self-Declaration for Individuals�

[In case of reporting by the Competent Authorities of the Source Country to the jurisdictions of residence of Investors, the sorting of the relevant information to be send to the Competent Authority of a jurisdiction of residence of Investors should be carried out on the basis of the residency information provided in this field.]



IIIb. Entity IN (OrganisationIN_Type)

Element Attribute Size Input Type RequirementIN 1 to 200 characters trc:OrganisationIN_Type (Optional) Mandatory

This data element provides the identification number (IN) used by the tax administration of the jurisdiction of residence of the Entity�

This data element can be repeated if more than one IN is on file�

Element Attribute Size Input Type RequirementIN issuedBy 2-character iso:CountryCode_Type Optional

This attribute describes the jurisdiction that issued the IN� If the issuing jurisdiction is not known then this may be left blank�

Element Attribute Size Input Type RequirementIN INType 1 to 200 characters stf:StringMin1Max200_Type Optional

This attribute defines the type of identification number being sent (e�g� EIN, TIN)�

IIIc. Organisation Name

Element Attribute Size Input Type RequirementName 1 to 200 characters trc:NameOrganisation_Type Validation

This element should contain the full legal name of the Entity, including the domestic designation for the legal form, as indicated in its articles of incorporation or any similar document�

Element Attribute Size Input Type RequirementName nameType stf:OECDNameType_EnumType Optional

IIId. Entity Legal Type

Element Attribute Size Input Type RequirementEntityLegalType trc:OECDLegalType_EnumType Validation

This element is included for the purpose of classifying the Entity in accordance with the OECD codes describing the legal status of entities�

Possible values to be entered in this field are:

• OECD401 = sole proprietorship (1 Person running a business and no legal distinction between the owner and the business)

• OECD402 = Corporation

• OECD403 = Government

• OECD404 = International organisation

• OECD405 = Pension Fund

• OECD406 = Charity



• OECD407 = Collective Investment Vehicle

• OECD408 = Partnership (other than a collective investment Vehicle)

• OECD409 = Trust (other than a collective investment vehicle, charity or pension fund)

• OECD410 = Estate

• OECD411 = Other (specify in the “OtherInfo” element)

IIIe. Place of incorporation

Element Attribute Size Input Type RequirementPlaceIncorporation Validation

This data element should contain the jurisdiction in which the Entity was originally incorporated or, in absence of an incorporation, the jurisdiction according to the laws of which the Entity was set up�

Element Attribute Size Input Type RequirementCountryCode 2-character iso:CountryCode_Type Validation (Choice)

Element Attribute Size Input Type RequirementFormerCountryName 1 to 200 characters stf:StringMin1Max200_Type Validation (Choice)

In principle, the information on the jurisdiction of incorporation should be provided by entering the ISO Country Code� The name of a former country may be entered in case the jurisdiction no longer has a valid ISO Country Code�

IV. TRACE Body

Element Attribute Size Input Type RequirementTraceBody trc:TraceBody_Type Optional

The TRACE body type contains all reportable information on Account Holders and their Covered Payments, as well as the withholding tax applied thereon by a particular Authorised Intermediary a given reporting period� The TRACE Body type comprises the AI element, containing information on the identity of the Authorised Intermediary and the Group AI element, which contains all reporting on Covered Payments received in the course of the reporting period by Account Holders of the Authorised Intermediary, as defined by TRACE�

Element Attribute Size Input Type RequirementAI trc:CorrectableTraceAI_Type Validation

The AI element contains information in relation to the identification of an Authorised Intermediary carrying out reporting under TRACE�

Element Attribute Size Input Type RequirementGroupAI Validation

The Group AI element contains all reportable information on Covered Payments received by the Account Holders of the Authorised Intermediary in the course of a reporting period from a particular Source Country�



IVa. AIThe AI element identifies the financial institution that acts as an Authorised Intermediary

under TRACE�

The Authorised Intermediary uses the Authorised Intermediary Identification Number (AIIN) and the OrganisationParty_Type to provide identifying information�

Element Attribute Size Input Type RequirementAI trc:CorrectableTraceAI_Type Validation

Element Attribute Size Input Type RequirementAIIN 1 to 200 characters stf:StringMin1Max200_Type Validation

In this field, the Authorised Intermediary Information Number issued by the Source Country to which reporting occurs under TRACE should be provided�

Element Attribute Size Input Type RequirementID trc:OrganisationParty_Type Validation

For further guidance on the sub elements of this element, please refer to Section III (OrganisationParty_Type) above�

Element Attribute Size Input Type RequirementDocSpec stf:DocSpec_Type Validation

DocSpec identifies the particular record within the TRACE message being transmitted� It allows for identification of records requiring correction (see also guidance on Corrections below)�

IVb. Group AIThe Group AI element contains all reportable information on Account Holders and

their Covered Payments for which the Authorised Intermediary ensures reporting under TRACE� This group is composed of two subcategories� The first subcategories are the direct Account Holders of the Authorised Intermediary�

For the second subcategory, containing Account Holders of Contractual Intermediaries for which the Authorised Intermediary ensures TRACE reporting, further details in relation to the chains of Contractual Intermediaries through which the Account Holders invest need to be provided and a categorisation on the basis of such investment chains needs to be carried out� Steps to be taken in this respect will be outlined hereafter�

Element Attribute Size Input Type RequirementGroupAI Validation

The following two data elements comprise the GroupAI:

Element Attribute Size Input Type RequirementCI trc:CorrectableTraceCI_Type (Optional) Mandatory

The CI element contains the identification information with respect to Contractual Intermediaries for which the Authorised Intermediary is ensuring reporting under TRACE�



A separate GroupAI is to be generated for each distinct combination of Contractual Intermediaries (i�e� for each specific investment chain) through which Account Holders have invested in Securities giving rise to Covered Payments and for which the Authorised Intermediary assumes reporting under TRACE with respect to the relevant Source Country�

For example, in case an Authorised Intermediary has assumed TRACE-reporting for two Contractual Intermediaries, potential variations of the CI element could include

• CI1 being the Contractual Intermediary on top of the chain (i�e� closest to the Investor) and CI2 being the other Contractual Intermediary;

• CI 1 being the sole Contractual Intermediary in the chain;

• CI2 being the Contractual Intermediary on top of the chain and CI1 being the other Contractual Intermediary; and

• CI 2 being the sole Contractual Intermediary in the chain�

Element Attribute Size Input Type RequirementGroupAICI trc:CorrectableReportAccHolder_Type (Optional) Mandatory

The Group AI CI element is repeatable in the TRACE XML Schema in accordance with the number of Account Holders reported on by the Authorised Intermediary that have invested in Securities which have generated Covered Payments in the Source Country through the same investment chain, composed of one or more Contractual Intermediaries, in the course of the reporting period�

IVc. CI

Element Attribute Size Input Type RequirementCI trc:CorrectableTraceCI_Type (Optional) Mandatory

The following two data elements comprise the CI element:

Element Attribute Size Input Type RequirementTopCI trc:OrganisationParty_Type Validation

The TopCI element contains the information on the last Contractual Intermediary in the chain of Contractual Intermediaries� As provided for in the TRACE Implementation Package, the last, investor-facing Contractual Intermediary is specifically identified, as to make clear that it is this Contractual Intermediary that has obtained the required identification and tax residency information from the Account Holders contained in the corresponding Group AI CI�

Element Attribute Size Input Type RequirementOtherCI trc:OrganisationParty_Type Optional (Mandatory)

The OtherCI element contains all other Contractual Intermediaries (if any) of a given combination of Contractual Intermediaries for which the Authorised Intermediary ensures reporting under TRACE, without specifically indicating a hierarchical order between such other Contractual Intermediaries, as this information is not required to be reported under TRACE�




DocSpec identifies the particular record within the TRACE message being transmitted� It allows for identification of records requiring correction (see also guidance on Corrections below)�

IVd. Group AI CI

Element Attribute Size Input Type RequirementGroupAICI trc:CorrectableReportAccountHolder_Type (Optional) Mandatory

The Group AI CI element is composed of all Source Country-specific TRACE reports (ReportAccHold) on Account Holders holding their investment from which Covered Payments are derived through the same set of Contractual Intermediaries, as reflected in the CI element� It contains a DocSpec element for corrections� Corrections can be made under the CorrectableReportAccHold_Type�


DocSpec identifies the particular record within the TRACE message being transmitted� It allows for identification of records requiring correction� See guidance on Corrections and a description of DocSpec Type�

Element Attribute Size Input Type RequirementReportAccHold Validation

This element contains the TRACE reporting on Account Holders of the corresponding Group AI or Group AI CI in relation to their Covered Payments with respect to the relevant Source Country�

IVe. Report Account Holders

Element Attribute Size Input Type RequirementReportAccHold Validation

The ReportAccHold is composed of the following two elements, one of which is to be chosen depending on whether the Account Holder is itself an Authorised Intermediary or not:

Element Attribute Size Input Type RequirementInvestor Validation (Choice)

The Investor element contains Investor-specific reporting under TRACE and contains both identification information, as well as information on Covered Payments received by the Investor and the tax withheld thereon with respect to the Source Country�

Element Attribute Size Input Type RequirementOtherAI Validation (Choice)



The OtherAI element contains the reporting information in relation to Account Holders that are themselves Authorised Intermediaries� In accordance with TRACE such accounts do not require a more detailed level of reporting, as reporting on the Investors of the latter Authorised Intermediary will be ensured by that Authorised Intermediary, being higher up the investment chain�

IVe. Report Account Holders – Investor

Element Attribute Size Input Type RequirementInvestor Validation (Choice)

The Investor element is composed of the following two elements:

Element Attribute Size Input Type RequirementInvestorID trc:InvestorID_Type Validation

The InvestorID element contains the identification information of the Investor required for TRACE reporting�

Element Attribute Size Input Type RequirementPayment trc:TracePaymentInvest_Type Validation

The Payment element contains information in relation to Covered Payments and the tax withheld thereon with respect to the Source Country to which the TRACE report is sent and can be repeated in accordance with the actual number of Covered Payments by the Investor during the relevant reporting period�

IVe. Report Account Holders – Investor – InvestorID (InvestorID_Type)

Element Attribute Size Input Type RequirementInvestorID trc:InvestorID_Type Validation

The InvestorID element contains a choice of either entering information for an Individual, or for an Organisation� Consequently, these elements are shown as Validation (choice) below�

Element Attribute Size Input Type RequirementIndividual trc:PersonParty_Type Validation (choice)

If the Investor reported is a natural person, the identifying information should be entered here�

Element Attribute Size Input Type RequirementOrganisation trc:OrganisationParty_Type Validation (choice)

If the Investor reported is not a natural person, the entity’s identifying information should be entered here�



IVe. Report Account Holders – Investor – Payment

Element Attribute Size Input Type RequirementPayment trc:TracePaymentInvest_Type Validation

The Payment element contains all information related to a particular Covered Payment under TRACE and is therefore repeatable in accordance with the number of Covered Payments received by an Investor during the reporting period� It is composed of the following elements:

Element Attribute Size Input Type RequirementBasic trc:TracePaymentBasic_Type Validation

This element contains all payment and withholding tax information in relation to a Covered Payment under TRACE�

Element Attribute Size Input Type RequirementWhtReliefPart trc:MonAmnt_Type (Optional) Mandatory

In certain instances, Covered Payments received by an Investor due to an investment through a Collective Investment Vehicle may be entitled to a partial withholding tax relief, for instance on the basis of a Mutual Agreement on Collective Investment Vehicles concluded by the Source Country and the country of residence of the Collective Investment Vehicle, models of which are included in the TRACE Implementation Package� In such cases, this field indicates the portion of the Covered Payment that is actually entitled to a reduced rate of withholding tax and is expressed as an amount (rather than a percentage)�

Element Attribute Size Input Type RequirementWhtReliefPart currCode 3 characters iso:currCode_Type Validation

This field specifies the currency in which the proportion of the payment entitled to the reduced rate of withholding tax is denominated� The amount must be accompanied by the appropriate 3 character currency code2 based on the ISO 4217 Alpha 3 standard�

Element Attribute Size Input Type RequirementMethod trc:TraceMethod_EnumType Optional

In case on an investment through a Collective Investment Vehicle, an Authorised Intermediary may be required to determine the portion of a Covered Payment is entitled to a reduced withholding tax rate, for instance on the basis of a Mutual Agreement on Collective Investment Vehicles, as described in relation to the WhtReliefPart element above� In such instances, this field indicates which method has been applied by the Authorised Intermediary for the purpose of determining the portion of the Covered Payment that is entitled to a reduced withholding tax rate� Depending on, inter alia, the type of investment,

2� The following disclaimer refers to all uses of the ISO currency code list in the CRS schema: For practical reasons, the list is based on the ISO 4217 Alpha 3 currency list which is currently used by banks and other financial institutions, and hence by tax administrations. The use of this list does not imply the expression by the OECD of any opinion whatsoever concerning the legal status of the territories listed. Its content is without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.



the identity of the Investor, the relevant withholding tax relief provisions and the content of a potential Mutual Agreement, possible methods to be entered in this field are:

• TRACE601 – Periodic Determinations

• TRACE602 – Sales Restrictions/Investor Restriction

• TRACE603 – Sales Restrictions/Geographic Restriction

• TRACE604 – Sales Restrictions/Preferential Rate Restriction

• TRACE605 – Tracing

Trace Basic Payment (TracePaymentBasic_Type)

Element Attribute Size Input Type RequirementBasic trc:TracePaymentBasic_Type Validation

The TRACE basic payment information provides all information in relation to a particular Covered Payment under TRACE and is composed of the following elements:

Element Attribute Size Input Type RequirementType trc:OECDPaymentType_EnumType Validation

The type of payment indicates how the Covered Payment has been classified for applying the relevant withholding tax rules� The following values are possible:

• OECD501 = Cash Dividends

• OECD502 = Interest

• OECD503 = Capital Gains

• OECD504 = Dividends-in-kind

• OECD505 = Mixed in-kind and cash dividends

• OECD506 = Other income

In case OECD504, OECD505 or OECD506 are selected, further detail on the in-kind dividends or the other income should be provided in the Other Info element�

Element Attribute Size Input Type RequirementTypeSourceCountry 1 to 200 characters stf:StringMin1Max200_Type Optional

Source Country-specific information about with regard to an income type received by the Investor under a Covered Payment, for instance due to the existence of a particular domestic withholding tax regime or classification rule in the Source Country, may be provided by the Authorised Intermediary through this element� In such case, generally the OECD506=Other Income value would be entered in the Type element set out above�

Element Attribute Size Input Type RequirementPaymentDate xsd:date Validation

This element should contain the date on which the Covered Payment was paid to the Investor�



Element Attribute Size Input Type RequirementIssuer 1 to 200 characters stf:StringMin1Max200_Type Validation

This element should contain the full name of the issuer of the security that gave rise to the Covered Payment (e�g� the issuer of the shares for dividends, the issuer of the bonds for interest payments, etc�)�

Element Attribute Size Input Type RequirementSecurity trc:SecurityAccountNumber_Type Validation

This element should indicate the identifying number of the security that gave rise to the Covered Payment� It is composed of:

Element Attribute Size Input Type RequirementISIN 1 to 200 characters trc:ISIN_Type Validation (Choice)

This element should be chosen and completed in case a ISIN number is available to identify the Security�

Element Attribute Size Input Type RequirementOSIN 1 to 200 characters trc:OSIN_Type Validation (Choice)

This element should be chosen and completed in case another identification number is available to identify the Security�

Element Attribute Size Input Type RequirementGross trc:MonAmnt_Type Validation

This element contains the gross amount of the Covered Payment, i�e� before deduction of the applicable withholding tax�

Element Attribute Size Input Type RequirementGross currCode 3 characters iso:currCode_Type Validation

The gross amount must be accompanied by the appropriate 3 character currency code based on the ISO 4217 Alpha 3 standard�

Element Attribute Size Input Type RequirementWhtRate trc:WithholdingTaxRate_Type Validation

This element contains details on the withholding tax rate applied to the gross Covered Payments and the reasons for applying the rate� It follows the withholding tax rate type, which is set out in further detail below�

Element Attribute Size Input Type RequirementWhtAmountAI trc:MonAmnt_Type Optional

This field should contain the amount of tax withheld from the gross Covered Payment, provided the withholding was carried out by the reporting Authorised Intermediary�

In case of a subsequent adjustment (see Adjustment element below) the updated amount should be entered here�



Element Attribute Size Input Type RequirementWhtAmountAI currCode 3 characters iso:currCode_Type Validation

The amount of tax withheld by the Authorised Intermediary must be accompanied by the appropriate 3 character currency code based on the ISO 4217 Alpha 3 standard�

Element Attribute Size Input Type RequirementWhtAmountWA trc:MonAmnt_Type Optional

This field should contain the amount of tax withheld from the gross Covered Payment, provided the withholding was carried out by a withholding agent other than the reporting Authorised Intermediary�

In case of a subsequent adjustment (see Adjustment element below) the updated amount should be entered here�

Element Attribute Size Input Type RequirementWhtAmountWA currCode 3 characters iso:currCode_Type Validation

The amount of tax withheld by the withholding agent must be accompanied by the appropriate 3 character currency code based on the ISO 4217 Alpha 3 standard�

Element Attribute Size Input Type RequirementAdjustment (Optional) Mandatory

The Adjustment element contains any subsequent adjustments that have been made in relation to the tax withheld on a Covered Payment, for instance due to the provision of additional information on the eligibility of the Investor and/or the Covered Payment to a reduced rate�


This field allows the Authorised Intermediary to enter any other information in relation to a Covered Payment in a free-text manner that could not be provided through one of above-mentioned elements� This field should be used when in-kind dividends or other types of income are paid as well as in circumstances specified by Source Countries to ensure accurate reporting under TRACE�

In the context of the payment of either fully in-kind or mixed in-kind and cash dividends, the WHT Rate and WHT Amount fields should contain the actual rate applied and the actual amount withheld with respect to the dividends� In case of a pure in-kind dividend, the WHT Amount would generally be zero, unless the AI has another sources (such as a cash account) from which it can withhold the amount� In case of a mixed in-kind and cash dividend, this amount would typically be the cash withheld on the cash component of the dividend to cover the withholding tax due on the overall in-kind and cash dividend payment�

In these instances, the Other Info element should contain the following further information:

• In case of an in-kind dividend payment, information on the form of the in-kind dividend (shares in the issuer, shares in another company, other form of in-kind payment), including, where appropriate, the ISIN/OSIN of the shares paid-in kind, the amount of shares, as well as its issuer; and



• In addition, in case of a mixed dividend payment, details on the split between the gross value of the in-kind dividend and the cash dividend�

Trace Basic Payment – Withholding tax rate

Element Attribute Size Input Type RequirementWhtRate trc:WithholdingTaxRate_Type Validation

The WHT Rate element contains details on the withholding tax rate applied to the gross Covered Payments and the reasons for applying the rate� It is composed of:

Element Attribute Size Input Type RequirementRate trc:TaxRate_Type Validation

This element contains the withholding tax rate applied to the gross Covered Payments� The withholding tax rate has to be entered as decimal number with a total of four digits, two before and two after the decimal point�

In case of a subsequent adjustment of the withholding tax rate (see Adjustment element below), the new, corrected withholding tax rate should be entered in this element�

Element Attribute Size Input Type RequirementRateReason stf:StringMin1Max200_Type Validation

The rate reason element contains detail on the type of withholding tax relief that is applied� The value should start with the word “TRACE”, followed by the country code of the Source Country, then the word “TREATY” or “DOM” depending on whether relief is applied based on a treaty or on domestic law of the source country, then a unique numeric identifier as specified by the source country to distinguish between the various types of domestic law or treaty relief, where applicable� For instance the value used to specify that a specific type of domestic law relief is applied

e�g� TRACEFIDOM123

This code indicates that a specific type (“123”) of domestic law relief (“DOM”) is applied in Source Country Finland (“FI”)�

Trace Basic Payment – Adjustment

Element Attribute Size Input Type RequirementAdjustment (Optional) Mandatory

The Adjustment element contains information on any subsequent adjustments to the withholding tax applied on a Covered Payment and is composed of the following elements:

Element Attribute Size Input Type RequirementOldWhtRate trc:TaxRate_Type Validation

The Old Wht Rate element contains information about the withholding tax rate that was applied to the Covered Payment prior to the adjustment� The new, correct withholding tax rate should be entered in the Wht Rate field in the TRACE Basic Payment type�



Element Attribute Size Input Type RequirementAmount trc:TraceAdjustment_Type Validation

The Amount element indicates the amount of the adjustment that has been carried out and is further detailed below�

Trace Basic Payment – Adjustment – Amount (TraceAdjustment_Type)

Element Attribute Size Input Type RequirementAmount trc:TraceAdjustment_Type Validation

The Amount element is composed of an increase and a refund element, one of which is to be chosen in each case, depending on whether additional withholding tax is to be paid or refunded in relation to the Covered Payment�

Element Attribute Size Input Type RequirementIncrease trc:MonAmnt_Type Validation (Choice)

The Increase element contains the amount of additional withholding tax to be paid to the Source Country in relation to the Covered Payment�

Element Attribute Size Input Type RequirementIncrease currCode 3 characters iso:currCode_Type Validation

All amounts must be accompanied by the appropriate 3 character currency code based on the ISO 4217 Alpha 3 standard�

Element Attribute Size Input Type RequirementRefund trc:MonAmnt_Type Validation (Choice)

The Refund element contains the amount of withholding tax to be refunded by the Source Country in relation to the Covered Payment�

Element Attribute Size Input Type RequirementRefund currCode 3 characters iso:currCode_Type Validation


IVe. Report Account Holders – OtherAI

Element Attribute Size Input Type RequirementOtherAI Validation (Choice)

The OtherAI is element, in case selected, is composed of:

Element Attribute Size Input Type RequirementAI trc:TraceAI_Type Validation

This element contains the identification information for the purpose of identifying the other Authorised Intermediary that maintains an account with the reporting Authorised Intermediary and is subject to reporting� For further guidance, please refer to the AI section above�



Element Attribute Size Input Type RequirementPayment trc:TracePaymentBasic_Type Validation

This element contains the payment-related information of the other Authorised Intermediary that maintains and account with the reporting Authorised Intermediary and is subject to reporting under TRACE� It follows the TRACE Basic Payment type described above�

V. Summary (CorrectableEndYearSummary_Type)

Element Attribute Size Input Type RequirementSummary trc:CorrectableEndYearSummary_Type Optional

The Summary element is a non-repeatable element that provides a consolidated overview of all Covered Payments, and the withholding tax applied thereon, reported by a particular Authorised Intermediary in relation to a particular Source Country in the course of the relevant reporting period� It corresponds to Sections VI�B� and VI�C, as well as Section VII of the Procedures, as well as to the content of form 12 in Annex 1, in particular parts 2 and 3 of the form�

In case an Authorised Intermediary is required to make subsequent changes to the Summary element, in particular in case the amount of Total Adjustments, as set out below, needs to be corrected, the Authorised Intermediary should provide the Source Country with an updated and corrected version of the Summary in each instance�

The Summary element is composed of:


DocSpec identifies the particular repord within the TRACE message being transmitted� It allows for identification of repords requiring correction (see also guidance on Corrections below)�

Element Attribute Size Input Type RequirementAI trc:TraceAI_Type Validation

The AI element recapitulates the identification information in of the Authorised Intermediary described above�

Element Attribute Size Input Type RequirementACP Validation

The ACP element contains information regarding the Aggregate Covered Payments reported by the Authorised Intermediary in the relevant reporting period received by its Investors and the Investors of Contractual Intermediaries from the Source Country� The element is further detailed below�

Element Attribute Size Input Type RequirementTotalAdjust (Optional) Mandatory



The TotalAdjust element provides information on the aggregate amount of adjustments to the withholding tax applied to Covered Payments from the Source Country paid to Investors for which the Authorised Intermediary ensures TRACE reporting that have been made in the course of the reporting period�


In this free text field any further information in relation to the consolidated year-end reporting that appears relevant to the proper functioning of TRACE may be entered� This field should only be used in exceptional circumstances and if no other element is available to report the information in a structured manner�

V. Summary – ACP (Information regarding Aggregate Covered Payments)

Element Attribute Size Input Type RequirementACP Validation

The ACP element provides an aggregate view of the Covered Payments reported by the Authorised Intermediary with respect to a Source Country and is composed of:

Element Attribute Size Input Type RequirementGrossACP Validation

The GrossACP element contains the consolidated gross amount of Covered Payments reported by the Authorised Intermediary with respect to the Source Country for the reporting period�

Element Attribute Size Input Type RequirementWHT Validation

The WHT element contains the consolidated amount of tax withheld by the Authorised Intermediary with respect to Covered Payments received by Investors from the Source Country in the course of the reporting period�

Element Attribute Size Input Type RequirementExchangeRate trc:MonAmnt_Type (Optional) Mandatory

The ExchangeRate element should contain the year-end exchange rate applied by the Authorised Intermediary for converting payments received by Investors in non-Source Country currencies into the currency of the Source Country� As payments may have been received in several foreign currencies, this element can be repeated as adequate�

Element Attribute Size Input Type RequirementExchangeRate currCode 3 characters iso:currCode_Type Validation




V. Summary – ACP – GrossACP (Gross Amount of Covered Payments)

Element Attribute Size Input Type RequirementGrossACP Validation

The GrossACP element is composed of the following items:

Element Attribute Size Input Type RequirementGross trc:MonAmnt_Type Validation

The Gross element should contain the total gross amount of Covered Payments for which the Authorised Intermediary ensures reporting from the Source Country in the course of the reporting period�

Element Attribute Size Input Type RequirementGross currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementGrossAI trc:MonAmnt_Type Validation

The GrossAI element should contain the total gross amount of Covered Payments paid, directly or indirectly through one or more Contractual Intermediaries, to Authorised Intermediaries in the course of the reporting period�

Element Attribute Size Input Type RequirementGrossAI currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementReducApplied trc:MonAmnt_Type Validation

The ReducApplied element contains the gross amount of Covered Payments for which the Authorised Intermediary ensures reporting that are not captured in the GrossAI element, on which a reduction of or exemption from withholding tax in the Source Country was applied by the Authorised Intermediary�

Element Attribute Size Input Type RequirementReducApplied currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementGrossOther trc:MonAmnt_Type Validation

The GrossOther element contains the gross amount of Covered Payments for which the Authorised Intermediary ensures reporting that are neither captured in the GrossAI element nor in the ReducApplied element� Accordingly, the amount in the GrossOther



element should correspond to the amount in the GrossACP element, less the amounts of the GrossAI and the ReducApplied elements�

Element Attribute Size Input Type RequirementGrossOther currCode 3 characters iso:currCode_Type Validation


V. Summary – ACP – WHT (Aggregate Tax Withheld)

Element Attribute Size Input Type RequirementWHT Validation

The WHT element provides an aggregate overview of the withholding tax withheld by an Authorised Intermediary with respect to Covered Payments received from the Source Country by Investors for which the Authorised Intermediary ensures reporting� It is composed of the following items:

Element Attribute Size Input Type RequirementByAI trc:MonAmnt_Type Validation

The ByAI element contains the aggregate amount of tax withheld by the Authorised Intermediary on Covered Payments from the Source Country to Investors for which the Authorised Intermediary ensures TRACE reporting�

Element Attribute Size Input Type RequirementByAI currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementByOtherAI trc:MonAmnt_Type Validation

The ByOtherAI element contains the aggregate amount of tax withheld by the other Authorised Intermediaries, acting as withholding agent, on Covered Payments from the Source Country to Investors for which the Authorised Intermediary ensures TRACE reporting�

Element Attribute Size Input Type RequirementByOtherAI currCode 3 characters iso:currCode_Type Validation


V. Summary – TotalAdjust

Element Attribute Size Input Type RequirementTotalAdjust (Optional) Mandatory



The TotalAdjust element contains the total sum of all adjustments to the tax withheld on Covered Payments received from the Source Country that were made subsequent to the end of the reporting period� It should be updated as required and, in such case, a corrected version of the Summary should be provided to the Source Country�

The TotalAdjust element consists of:

Element Attribute Size Input Type RequirementIncrease trc:MonAmnt_Type Validation (Choice)

The Increase element indicates that the Authorised Intermediary has to pay an additional amount of withholding tax to the Source Country, after aggregating all adjustments made�

Element Attribute Size Input Type RequirementIncrease currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementRefund Validation (Choice)

The Refund element indicates that the Authorised Intermediary is entitled to receive a refund of withholding tax from the Source Country, after aggregating all adjustments made

V. Summary – TotalAdjust – Refund

Element Attribute Size Input Type RequirementRefund Validation (Choice)

In case the Authorised Intermediary is entitled to a refund of withholding tax of the Source Country after aggregating all adjustments, the following information is to be provided in the Refund element:

Element Attribute Size Input Type RequirementAmount trc:MonAmnt_Type Validation

The Amount element indicates the amount of withholding tax that is to be refunded by the Source Country�

Element Attribute Size Input Type RequirementAmount currCode 3 characters iso:currCode_Type Validation


Element Attribute Size Input Type RequirementAccount trc:AccountInfo_Type Validation

The Account element contains information on the bank account details of the Authorised Intermediary to which the refund is to be made�



V. Summary – TotalAdjust – Refund – Account (AccountInfo_Type)

Element Attribute Size Input Type RequirementAccount trc:AccountInfo_Type Validation

The Account element is composed of the following elements:

Element Attribute Size Input Type RequirementBank trc:OrganisationParty_Type Validation

This element contains further information about the bank where the account of the Authorised Intermediary is maintained to which the withholding tax is to be refunded by the Source Country�

Element Attribute Size Input Type RequirementAccountNumber trc:FIAccountNumber_Type Validation

V. Summary – TotalAdjust – Refund – Account – Account Number (AccountNumber_Type)

Element Attribute Size Input Type RequirementAccountNumber trc:FIAccountNumber_Type Validation

This element contains information on the account maintained by the Authorised Intermediary to which the withholding tax is to be refunded by the Source Country� The element is composed of:

Element Attribute Size Input Type RequirementIBAN 1 to 200 characters trc:IBAN_Type (Optional) Mandatory

This element should be completed if the account of the Authorised Intermediary to which refunds are to be made has an IBAN number�

Element Attribute Size Input Type RequirementOBAN 1 to 200 characters trc:OBAN_Type (Optional) Mandatory

This element should be completed if the account of the Authorised Intermediary to which refunds are to be made has an account number other than an IBAN number�

Element Attribute Size Input Type RequirementBranchCode 1 to 200 characters stf:StringMin1Max200_Type (Optional) Mandatory

In case a branch code or routing number is part of the identifying information for the account of the Authorised Intermediary to which refunds are to be made, such information should be provided in this element�

Element Attribute Size Input Type RequirementSWIFT trc:SWIFT_Type (Optional) Mandatory

In case a SWIFT or BIC Code is part of the identifying information for the account of the Authorised Intermediary to which refunds are to be made, such information should be provided in this element�



VI. Schema version

The version of the schema and the corresponding business rules have a unique version number assigned that usually consists of two numbers separated by a period sign: major and minor version (ex: 1�0)� The version number could also contain a third number (ex: 1�0�1) which indicates that the schema was revised with very minor changes (ex: only new enumerations were added)�

The version is identified by the version attribute on the schema element� The target namespace of the CRS schema contains only the major version�

Element Attribute Size Input Type RequirementTRACE_OECD version 1 to 10 characters stf:StringMin1Max10_Type (Optional) Mandatory

The root element TRACE_OECD version attribute in the XML report file must be set to the value of the schema version� This will identify the schema version that was used to create the report�

For the TRACE schema v1�1, the version attribute must be set to the value “1�1”�

VII. Corrections

IntroductionIn case the reporting Authorised Intermediary becomes aware of inaccurate information,

be it in relation to the identification, tax residency or address information of an Account Holder, or be it relation to Covered Payments and the withholding tax applied thereon, a correction will need to be made� As long as the error is discovered in the course of the year and prior to the end of the reporting period, the input data can be altered on an ongoing basis prior to the generation of the XML file containing the TRACE report at year-end that will be transmitted to the Source Country�

However, in case an error is discovered after year-end, adjustments to part of the TRACE reporting will need to be made, in accordance with the guidance set out in this section�

In order to facilitate a targeted reporting of corrections, the TRACE XML Schema is split into a number of correctable types, allowing correcting specific parts of the TRACE reporting� Such correctable types include the CorrectableReportAccHold_Type, allowing a correction of identification or payment-related information of a specific Account Holder and the CorrectableEndYearSummary_Type, allowing a correction of the year-end summary of the Authorised Intermediary�

In case an adjustment to withholding applied on a Covered Payment needs to be made subsequent to the end of the reporting period, the Payment element of the TRACE XML Schema provides for a specific Adjustment element where such adjustments can be entered� In this respect, reference is made to the corresponding guidance in section IV above� The total amount of all adjustments made to Covered Payment of Account Holders of an Authorised Intermediary is further reflected in the Total Adjustments element within the year-end summary, as described in Section V� Accordingly, in case an Authorised Intermediary proceeds to subsequent adjustments of withholding taxes applied on Covered Payments, both the CorrectableReportAccHolder_Type for each of the Account Holders for



which an adjustment has been made and one updated CorrectableEndYearSummary_Type report, containing a revised information on the Total Adjustments, needs to be submitted�

Technical GuidanceThe section describes how to make automatic corrections by sending a file of corrected

data that can be processed in the same systems as the original data that was received� Reference to corrections also includes deletion of data elements in the following section�

For the Trace XML Schema, the term record refers to the correctable records AI, CI, ReportAccHold and Summary� The correctable records contain a DocSpec element (and a DocRefID), thus allowing for future corrections�

When performing a correction, the whole record will be corrected (with all its sub-elements being resubmitted)�

DocSpec Type


DocSpec identifies the particular record within the TRACE message being transmitted� It allows for identification of records that require correction� DocSpec_Type is comprised of the following elements:

Element Attribute Size Input Type RequirementDocTypeIndic stf:OECDDocTypeIndic_EnumType Validation

This element specifies the type of data being submitted� Allowable entries are:

• OECD0 = Resent Data (only to be used for resending the AI or CI element)

• OECD1 = New Data

• OECD2 = Corrected Data

• OECD3 = Deletion of Data

• OECD10 = Resent Test Data (only to be used for resending the AI or CI element)

• OECD11 = New Test Data

• OECD12 = Corrected Test Data

• OECD13 = Deletion of Test Data

A message can contain either new records (OECD1) or corrections/deletions (OECD2 and OECD3), but cannot contain a mixture of both�

The resend option (OECD 0) can only be used for the AI and/or CI elements�

For the AI element, the resend option (OECD0) can only be used when the CI and/or the ReportAccHold are provided and the AI has already been sent�

For the CI element, the resend option (OECD0) can only be used when the ReportAccHold is provided and the CI has already been sent�



When the ReportAccHold is corrected or deleted, the AI and CI will be resent (OECD0), unless the AI or CI also needs to be corrected or deleted� If the CI was omitted when the ReportAccHold was initially sent, then CI will also be omitted when correcting or deleting the ReportAccHold�

The AI cannot be deleted without deleting all related CI and ReportAccHold (either in same message or in previous messages)�

The CI cannot be deleted without deleting all related ReportAccHold (either in same message or in previous messages)�

OECD10 – OECD13 must only be used during previously agreed-upon testing periods or after a bilateral discussion where both parties agree to testing� This is to help eliminate the possibility that test data could be co-mingled with “live” data�

Element Attribute Size Input Type RequirementDocRefID 1 to 200 characters stf:StringMin1Max200_Type Validation

A unique identifier for this document (i�e� one record and all its children data elements)�A correction (or deletion) must have a new unique DocRefID for future reference�

Element Attribute Size Input Type RequirementCorrDocRefID 1 to 200 characters stf:StringMin1Max200_Type Optional

The CorrDocRefID references the DocRefID of the element to be corrected and/or deleted� It must always refer to the latest reference of the record (DocRefID) that was sent�

In this way, a series of corrections or amendments can be handled as each correction completely replaces the previous version� The TRACE Correction examples below show how this works in practice�

Uniqueness of MessageRefID and DocRefIDIn order to ensure that a message and a record can be identified and corrected, the

MessageRefID and DocRefID must be unique in space and time (i�e� there must be no other message or record in existence that has the same reference identifier)� The same applies to the Authorised Intermediary Identification Number issued by the relevant Source Countries� In that context it is therefore highly recommended that the Authorised Intermediary Identification Number starts with the ISO Country Code issuing the AIIN as to ensure that its uniqueness is warranted�

The MessageRefID identifier can contain whatever information the sender uses to allow identification of the particular record but must start with the sending jurisdiction code (either of the residence jurisdiction of the sending Authorised Intermediary or of the sending tax authority, in case of reporting by the Source Country to the jurisdiction(s) of residence of Investors), then the year to which the data relates, then the receiving jurisdiction code, then Authorised Intermediary Identification Number (if the message is sent by an Authorised Intermediary), then a dash before a unique identifier�

e�g� FR2017CAAiin123-123456789 (for a report by an Authorised Intermediary)

This MessageRefID indicates that France is the country of the sending Authorised Intermediary, the data relates to the year 2017, Canada is the receiving Source Country, the AIIN is “Aiin123” and the unique identifier is “123456789”�

e�g� CA2017BE-99443322 (for reporting by a Source Country to another jurisdiction)



This MessageRefID indicates that Canada is the transmitting Source Country, the data relates to the year 2017, Belgium is the receiving jurisdiction, and the unique identifier is “99443322”�

The DocRefID is used by the reporting Authorised Intermediary (or the Source Country) to identify a unique record and it is composed of the country code of the sending jurisdiction, then the year to which the data relates, then the Authorised Intermediary Identification Number (if the record is sent by an Authorised Intermediary) then a dash followed by a unique identifier�

e�g� FR2017Aiin123-286abc123xyz (for a record by an Authorised Intermediary)

This DocRefID indicates that France is the sending country, the data relates to the year 2017, the AIIN is “Aiin123” and the unique identifier is “286abc123xyz”�

e�g� CA2017-156def222rts (for a record by a Source Country to another jurisdiction)

This DocRefID indicates that Canada is the sending country the data relates to the year 2017 and the unique identifier is “156def222rts”�

MessageSpec, Corrections and CancellationsCorrection messages must have their own unique MessageRefID so they can also be

corrected in the future� There is no equivalent for the DocSpec when it comes to messages as a whole�

To cancel a complete message, the MessageSpec�CorrMessageRefID can be used only with the prior agreement of the Competent Authority of the Source Country or when the exchanging jurisdictions have mutually agreed� Otherwise, a correction message should be sent deleting all records of the erroneous message in these instances�

The following examples show how the DocSpec_Type elements are used to correct one or multiple parts of data previously sent�


40 – TRACE CORRECTION EXAMPLES

TRACE correction examples

First example: a correction is made in relation to the Gross amount element of a Covered Payment to an Investor� The correction must be made in the Payment field “Gross” (Gross Amount of the Covered Payment)�

The correction file is sent from the Authorised Intermediary established in France to the Competent Authority in the Source Country, i�e� Canada (containing only corrections, not a mix of new and corrected data)�

MessageRefID: FR2017CAAiin123-FranceNationalPart00001

For this Correction, the whole ReportAccHold must be resubmitted with all the Investor information (InvestorID and Payment details)�

ReportAccHold DocTypeIndic: OECD2 Corrected Data

DocRefID: FR2017Aiin123-RAH002A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123-RAH0001 References the DocRefID of the element to be corrected�

When the ReportAccHold is corrected, the AI and CI will be resent (OECD0), if no data needs to be corrected on the AI and CI�

AI OECD0 Resent data DocRefID : FR2017Aiin123-AI001

CI OECD0 Resent data DocRefID : FR2017Aiin123-CI001

The new “Gross Amount of Payment” is 100 euros� Previously, a different amount was sent�

All the ReportAccHold information is also resubmitted (when performing a correction, the whole record is corrected with all its sub-elements)�


TRACE CORRECTION EXAMPLES – 41

Second example: a correction is made regarding multiple information items relating to the Investor, i�e� name, address, issuer of the security� The correction is made with regard to the previous correction (so it must always reference the latest DocRefID)�


All the ReportAccHold Investor information is resubmitted, with the new name, address and issuer information (when performing a correction, the whole record is corrected with all its sub-elements)�


AI OECD0 Resent data DocRefID :FR2017Aiin123-AI001


ReportAccHold DocTypeIndic: OECD2 Corrected Data

DocRefID: FR2017Aiin123- RAH003 A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123- RAH002 Always references the latest DocRefID�



Third example: a correction is made only with respect to the reporting Authorised Intermediary; no ReportAccHold data needs to be corrected� The correction must reference the reporting Authorised Intermediary to be corrected, via its DocRefID�

MessageRefID: FR2017CAAiin123-FranceNationalPart00003�

AI DocTypeIndic: OECD2 Corrected Data

DocRefID: FR2017Aiin123-AI002 A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123-AI001 Always references the latest DocRefID (for the AI in this example)�

Since no data in ReportAccHold or CI needs to be corrected, only the AI element is sent as correction (the CI, ReportAccHold and Summary are omitted)�



Fourth example: a correction is made with respect to the OtherAI element, the payment type must be changed to “Dividend”�


ReportAccHold

DocTypeIndic: OECD2 Corrected Data

DocRefID: FR2017Aiin123- RAH004 A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123- RAH003 References the DocRefID of the element to be corrected�


AI OECD0 Resent data DocRefID : FR2017Aiin123-AI002 Always references the latest DocRefID (for the AI)�


The new payment type is “Dividend”� Previously, the payment type was “Interest”�

All the ReportAccHold information for OtherAI is also resubmitted (when performing a correction, the whole record is corrected with all its sub-elements)�



Fifth example: a correction is made with regard to the CI element, no AI or ReportAccHold data needs to be corrected�


When performing a correction, the whole record will be corrected (with all its sub-elements being resubmitted)� So in the case of a correction of the CI record, the TopCI and all the OtherCI will also be resubmitted with this correction�

AI DocTypeIndic: OECD0 Resent data DocRefID : FR2017Aiin123-AI002 Always references the latest DocRefID (for the AI)�

CI DocTypeIndic: OECD2 Corrected Data DocRefID: FR2017Aiin123-CI002

A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123-CI001 Always references the latest DocRefID (for the CI in this example)�

Since only the CI needs to be corrected, the ReportAccHold and Summary will be omitted� The AI will be resent (OECD0)�



Sixth example: a correction is made with regard to the Summary element, the aggregate tax withheld by the AI must be corrected�


Summary

DocTypeIndic: OECD2 Corrected Data DocRefID: FR2017Aiin123-SUM002 A correction must have a new DocRefID for future reference�

CorrDocRefID: FR2017Aiin123-SUM001 References the DocRefID of the element to be corrected�

The aggregate tax withheld by the AI must be corrected for an amount of 2000 euros�

When performing a correction, the whole record will be corrected (with all its sub-elements being resubmitted)� So all the Summary information is also resubmitted (AI, ACP, TotalAdjust, OtherInfo)�

Since only the Summary needs to be corrected, the AI, CI and ReportAccHold will be omitted�


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 47

Appendix A

TRACE XML Schema v1.1 diagrams


48 – APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS

Message Header [Section I]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 49T

RA

CE

Bod

y R

epor

ting

[Sec

tion

IV]



AI [

Sect

ion

IVa]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 51G

roup

AI [

Sect

ion

IVb]



CI [

Sect

ion

IVc]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 53G

roup

AIC

I [Se

ctio

n IV

d]



Rep

ortA

ccH

old

(Rep

ort A

ccou

nt H

olde

r) [S

ectio

n IV

e]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 55In

vest

or [S

ectio

ns I

I, II

I and

IV

]



Individual/Organisation InvestorID [Sections II and III]



Person Party Type [Section II]

For practical reasons, the ResCountryCode list is based on the ISO 3166-1 country list which is currently used by banks and other financial institutions, and hence by tax administrations. The use of this list does not imply the expression by the OECD of any opinion whatsoever concerning the legal status of the territories listed. Its content is without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.



Person Name Type [Section II]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 59A

ddre

ss T

ype

[All

Sect

ions

]



Org

anis

atio

n Pa

rty

Type

[Sec

tion

III]

For

prac

tical

rea

sons

, the

Res

Cou

ntry

Cod

e lis

t is

bas

ed o

n th

e IS

O 3

166-

1 co

untr

y lis

t whi

ch is

cur

rent

ly u

sed

by b

anks

and

oth

er fi

nanc

ial i

nstit

utio

ns, a

nd h

ence

by

tax

adm

inis

trat

ions

. The

use

of t

his

list d

oes

not i

mpl

y th

e ex

pres

sion

by

the

OEC

D o

f any

op

inio

n w

hats

oeve

r co

ncer

ning

the

lega

l sta

tus

of th

e te

rrito

ries

list

ed. I

ts c

onte

nt is

w

ithou

t pre

judi

ce to

the

stat

us o

f or

sove

reig

nty

over

any

terr

itory

, to

the

delim

itatio

n of

inte

rnat

iona

l fro

ntie

rs a

nd b

ound

arie

s and

to th

e na

me

of a

ny te

rrito

ry, c

ity o

r are

a.


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 61In

vest

or P

aym

ent [

Sect

ion

IV]



TRACE Basic Payment [Section IV]

For practical reasons, the CurrencyCode list is based on the ISO 4217 currency code list which is currently used by banks and other financial institutions, and hence by tax administrations. The use of this list does not imply the expression by the OECD of any opinion whatsoever concerning the legal status of the territories listed. Its content is without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.



Trace Adjustment

For practical reasons, the CurrencyCode list is based on the ISO 4217 currency code list which is currently used by banks and other financial institutions, and hence by tax administrations. The use of this list does not imply the expression by the OECD of any opinion whatsoever concerning the legal status of the territories listed. Its content is without prejudice to the status of or sovereignty over any territory, to the delimitation of international frontiers and boundaries and to the name of any territory, city or area.



Oth

er A

I [Se

ctio

n IV

]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 65Su

mm

ary

[Sec

tion

V]



Sum

mar

y, A

CP

(Agg

rega

te C

over

ed P

aym

ents

) [Se

ctio

n V

]


APPENDIX A� TRACE XML SCHEMA V1�1 DIAGRAMS – 67Su

mm

ary,

Tot

al A

djus

tmen

ts [S

ectio

n V

]


68 – APPENDIX B� GLOSSARY OF NAMESPACES

Appendix B

Glossary of namespaces

TRACE XML Schema Namespaces

Namespace Description Filename

trc TRACE-specific types TraceXML_v1.1.xsd

stf OECD Common types oecdtrctypes_v1.0.1.xsd

iso ISO types (Country & Currency codes) isotrctypes_v1.0.2.xsd

TRACE XML SchemaUser Guide

For more information:

[email protected]

@OECDtax

www.oecd.org/tax

The OECD Treaty Relief and ComplianceEnhancement (TRACE) initiative hasdeveloped the Authorised Intermediary (AI)system. This standardised system allows theclaiming of withholding tax relief at sourceon portfolio investments. It removes theadministrative barriers that affect the abilityof portfolio investors to effectively claim thereduced rates of withholding tax to whichthey are entitled pursuant to tax treaties or todomestic law of the country of investment. Itminimises administrative costs for allstakeholders and enhances the ability of bothsource and residence countries to ensureproper compliance with tax obligations.

This document contains the structure of theTRACE XML Schema, as well as a User Guide, asapproved by the Committee on Fiscal Affairsin February 2020. It provides guidance on thestandardised electronic format to be used forreporting TRACE-related information byfinancial institutions to tax administrationsand for the exchange of information betweentax administrations. It is intended tocomplement the TRACE ImplementationPackage, which sets out the procedures,forms and agreements to be put in place tooperationalise the TRACE AI system.

The OECD Treaty Relief and Compliance TRACE …...withholding tax refunds should be paid The sixth...

Documents

Transcript of The OECD Treaty Relief and Compliance TRACE …...withholding tax refunds should be paid The sixth...