mapsandschemas
The mapsandschemas directory contains validation framework maps, schemas, and reference data files and maps.
-
xliff.dtd file– Not included as part of the pack, and must be copied from ITX install directory into the mapsandschemas directory.
-
epcl.txt file – contains the latest External Purpose Code List that is used to validate all Customer to PSP messages.
-
eeaSEPACtryCd.txt file - contains the list of countries and territories which are part of the jurisdictional scope of the SEPA Schemes and their ISO country codes.
-
errc.txt file - contains the latest External Reversal Reason Code that is used to validate all Customer to PSP Payment Reversal messages.
-
Validation framework maps - perform validation of the SEPA message by checking for: 1) Basic UNIFI compliance and 2) EPC-mandated usage rules for Credit Transfer and Direct Debit. The main map for the validation framework (sepvalid) resides under the sepa_validation.mms. All of the validation maps reside within this source file, so they can all be built at the same time, by using the Build All option in the Map Designer.
-
ISO 20022 Schemas - All needed schemas are provided for the validation of all the different message types and levels (UNIFI, SEPA, CORE, and AOS). Any new or modified schema must be located here. Also, there is a SEPA generic schema (sepagen.xsd) that contains a list of all messages that are supported by the validation framework maps.
-
sepa_library.mms file – includes additional utility maps to work with the BICPlusIBAN directory.
-
Dependent EPC - All dependent EPC are validated based on the Local Instrument Code.
-
Reference data files and maps - The SEPA component comes with XML templates used by the validation framework for validating BICs, currency code, country code and allowed decimal places for currency amounts information. The SEPA component also contains maps to populate these templates with live data supplied by SWIFT (sepa_library.mms).