� Introduce a min length Data type for any kind of numeric data with two decimal fraction digits, especially monetary amounts. Structure of the address for a party broken down into its logical parts, recommended for easy matching. The 'City' element is the only required subelement. All of the subelements are simple text - data type 'string'. The user has the option to enter the data about the address of a party either as one long field or to spread the data over up to eight elements or even to use both formats. If the user chooses the option to enter the data required in separate elements, the container element for this will be 'AddressFix'. 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. PLEASE NOTE that the address country code is outside both of these elements. The use of the fixed form is recommended as a rule to allow easy matching. However, the use of the free form is recommended if the sending state cannot reliably identify and distinguish the different parts of the address. The user may want to use both formats e.g. if besides separating the logical parts of the address he also wants to indicate a suitable breakdown into print-lines by delimiters in the free text form. In this case 'AddressFix' has to precede 'AddressFree'. This data type is to be used whenever monetary amounts are to be communicated. Such amounts shall be given including two fractional digits of the main currency unit. The code for the currency in which the value is expressed has to be taken from the ISO codelist 4217 and added in attribute currCode. Name of organisation The user must spread the data about the name of a party over up to six elements. The container element for this will be 'NameFix'. His Excellency,Estate of the Late ... Greeting title. Example: Mr, Dr, Ms, Herr, etc. Can have multiple titles. FirstName of the person Defines the name type of FirstName. Example: Given Name, Forename, Christian Name, Father's Name, etc. In some countries, FirstName could be a Family Name or a SurName. Use this attribute to define the type for this name. Middle name (essential part of the name for many nationalities). Example: Sakthi in "Nivetha Sakthi Shantha". Can have multiple middle names. Defines the name type of Middle Name. Example: First name, middle name, maiden name, father's name, given name, etc. de, van, van de, von, etc. Example: Derick de Clarke Defines the type of name associated with the NamePrefix. For example the type of name is LastName and this prefix is the prefix for this last name. Represents the position of the name in a name string. Can be Given Name, Forename, Christian Name, Surname, Family Name, etc. Use the attribute "NameType" to define what type this name is. In case of a company, this field can be used for the company name. Defines the name type of LastName. Example: Father's name, Family name, Sur Name, Mother's Name, etc. In some countries, LastName could be the given name or first name. Jnr, Thr Third, III Could be compressed initials - PhD, VC, QC Deceased, Retired ... This is the identification number/identification code for the party in question. As the identifier may be not strictly numeric, it is just defined as a string of characters. Attribute 'issuedBy' is required to designate the issuer of the identifier. Country code of issuing country, indicating country of Residence (to taxes and other) This container brings together all data about an organisation as a party. Name and address are required components and each can be present more than once to enable as complete a description as possible. Whenever possible one or more identifiers (TIN etc) should be added as well as a residence country code. Additional data that describes and identifies the party can be given . The code for the legal type according to the OECD codelist must be added. The structures of all of the subelements are defined elsewhere in this schema. Tax Identification number This container brings together all data about a person as a party. Name and address are required components and each can be present more than once to enable as complete a description as possible. Whenever possible one or more identifiers (TIN etc) should be added as well as a residence country code. Additional data that describes and identifies the party can be given. The code for the legal type according to the OECD codelist must be added. The structures of all of the subelements are defined elsewhere in this schema. Message type defines the type of reporting Information in the message header identifies the Financial Institution (FI) or Tax Administration that is sending the message. It specifies when the message was created, what calendar year the report is for, and the nature of the report (original, corrected, supplemental, etc). Free text expressing the restrictions for use of the information this message contains and the legal framework under which it is given All necessary contact information about persons responsible for and involved in the processing of the data transmitted in this message, both legally and technically. Free text as this is not intended for automatic processing. Sender's unique identifier for this message Sender's unique identifier that has to be corrected. Must point to 1 or more previous message The reporting year for which information is transmitted in documents of the current message.