TIPS SEPA Inst Directory Mapping
File Types Supported
| File Name | File Types Supported | File Formats Supported | File Naming Conventions |
|---|---|---|---|
TIPS Directory |
FULL, DELTA |
XML |
TIPSXXXTTTTYYYYMMDD |
| TTTT is the type, i.e. FULL for the full version and DLTA for the delta version. XXX is the currency related to the records included in the directory; YYYYMMDD specifies the year, month and day as of which the TIPS Directory is valid. AWS S3 Ingestion identifies this file when the file name starts with "TIPS". |
Important points to remember:
-
The client implementations should not modify the files names provided by industry sources and ingest the files as received.
-
The initial file processed must be a full file. Subsequently, full and delta files may be processed.
-
IPF currently does not maintain a counter for delta files. It is important for client implementations to ensure files are not processed out of sequence or any intermediate delta files are not skipped before processing subsequent delta files.
Delta File Load Processing
The TIPS Directory provides a record of changes between the current and previous file version. The type of change field has the following possible values:
-
A = Added
-
D = Deleted
-
M = Modified
-
U = Unchanged
Records marked as Unchanged in the delta file do not update the database, as the source records remain the same and do not require any changes. It is important to note that unchanged records are not expected on DELTA files. All other records are updated accordingly.
For FULL files, all existing entries that are not part of the new file will be deleted.
For DELTA files, processing follows predefined flags, considering only the specified entries for (A)ddition, (D)eletion, or (M)odification.
More on how FULL files are processed can be found here
Mapping Definitions
TIPS SEPA Inst Directory Mapping (Direct and Indirect)
Below table provides the mapping as performed from TIPS Directory file into CSM Participants.
| TIPS Directory Property (Source) | CSM Participant Property (Destination) | Comment |
|---|---|---|
- |
csmAgentId |
Constant value: TIPS |
User BIC |
csmParticipantIdentifier |
|
Party BIC |
routingBIC |
|
Type of Change |
- |
Operation performed as per value. (A)dded, (M)odified, (D)elete and (U)nchanged |
Institution Name |
participantName |
|
Participation Type |
participantType |
Value 01 indicates Direct Participant and value 02 indicates Reachable Party |
Valid From |
activeFromDate |
|
Valid To |
activeToDate |
|
Maximum IP_Amount |
participantsLimits |
Example Mapping
Source Record from Industry file
<File fileId = "TIPSEURFULL20230821" xmlns="urn:TIPS:TIPSDirectory" >
AFPNDEB2XXXAFONE PAIEMENT BPCEFRPPXXXBPCEFRPPXXXU2021070599991231010000000000100000.00
PBNKDEFFTIPDEUTSCHE BANK AG-POSTBANK BRANCH (FORMERLY DEUTSCHE POSTBANK AG) DEUTDEFFXXXDEUTDEFFXXXU2021102599991231020999999999999999999
</File>Destination Record - CSM Participant
{
"_id": "DynamicSettings|participant-TIPS-PBNKDEFFTIP",
"payload": {
"csmAgentId": "TIPS",
"csmParticipantIdentifier": "PBNKDEFFTIP",
"participantName": "DEUTSCHE BANK AG-POSTBANK BRANCH",
"routingBIC": "DEUTDEFFXXX",
"participantCountry": "DE",
"activeFromDate": {
"$date": "2008-01-28T00:00:00.000Z"
},
"participantType": "DIRECT"
},
"version": 1,
"status": "ACTIVE",
"processingEntity": "UNKNOWN",
"_class": "com.iconsolutions.ipf.dynamicsettings.repository.ParticipantSettings"
}{
"_id": "DynamicSettings|participant-TIPS-AFPNDEB2XXX",
"payload": {
"csmAgentId": "TIPS",
"csmParticipantIdentifier": "AFPNDEB2XXX",
"participantName": "AFONE PAIEMENT",
"routingBIC": "BPCEFRPPXXX",
"participantCountry": "DE",
"activeFromDate": {
"$date": "2008-01-28T00:00:00.000Z"
},
"participantType": "INDIRECT"
},
"version": 1,
"status": "ACTIVE",
"processingEntity": "UNKNOWN",
"_class": "com.iconsolutions.ipf.dynamicsettings.repository.ParticipantSettings"
}