Introduction to Clearing Directory
This section gives an introduction to Clearing Directory.
Clearing Directory Upload
The bank needs to be registered with a clearing to participate in the services it provides. Each clearing releases a clearing directory file or participant bank catalogue that lists the banks participating with the clearing.
The user can identify the participant bank using a Bank Identifier Code (BIC) or National Clearing Code (NCC). Temenos Payment Hub (TPH) can receive the clearing directory file and upload the information to the TPH clearing directory table through an automated process. The received file can be:
- Full file − Lists all the participant banks in the clearing
- Delta file − Contains only the changes from the previous clearing directory release
Each clearing directory file has a different upload API, which maps the information from the directory file to the TPH clearing directory table.
- Existing records that are used for ongoing payment processing co-exist with the newly uploaded records until the purge process happens
If the effective date provided in the file is same or before the date of upload, the API that is uploaded updates the effective date of the records to the next calendar date. This API determines the reachability key based on the configured parameters and stores it in the clearing directory record. This key is used to perform reachability check.
An obsolete record can be deleted from TPH (if configured). The bank user has the flexibility to add new records and view, edit or delete the existing records in the clearing directory table.
If automatic upload of the directory file fails, TPH mark the operation as ‘failed’ and the file is made available in the folder from which it is uploaded. The following clearing directories are loaded to TPH:
Reachability Check
TPH performs reachability check only for outgoing payments. The system performs a validation to check if the beneficiary bank can participate in a specific clearing directly or through an indirect participant.
The reachability API refers to the records stored in the clearing directory table using the reachability key (user configured) to perform reachability check. If a valid record for the BIC or NCC is not found, TPH routes the payment to the Repair queue for user action.
Reachability check is performed in TPH (for every clearing) or Payment Order (for each product), if configured. A participant bank is considered reachable only when a valid record exists in the directory for the specific BIC or NCC for the defined set of parameters.
License Codes
TPH performs clearing directory upload and reachability check for the following clearings:
| Clearing | License Code |
|---|---|
| EISCD UK Clearing Directory (BACS, FPS,CHAPS, CNCC) | CAIEIS |
| HCTINST Directory Upload (Feature) | CAIHCT |
| EQUENS Instant Directory Upload (Feature) | CAINCT |
| SIC Directory Upload (Feature) | CAISIC |
| HKFPS Directory Upload | CAHINS |
| BECS Direct Entry Directory Upload | CAAUST |
| SYGMA Clearing Directory | CASYGM |
| SYSTAC Clearing Directory | CASYTC |
| VIBER Directory Upload | CAIHCT |
| IG2 Directory Upload | CAIHCT |
| RPSSCL | CARPSS |
| SIBTEL | CATNCL |
| SLIPS Directory Upload | CALKCL |
| TIPS Directory Upload | CAITIP |
In this topic