Local Clearing
Local Clearing
Local Clearing
User Guide
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Table of Contents
Overview.................................................................................................................................................. 3
Setup ....................................................................................................................................................... 4
FT.LOCAL.CLEARING ........................................................................................................................ 4
Clearing System Information ............................................................................................................ 6
Funds Transfer fields........................................................................................................................ 6
General processing rules ................................................................................................................. 8
Sort Codes ....................................................................................................................................... 9
Defining Local Transaction Codes ................................................................................................. 10
Additional set up requirements .......................................................................................................... 12
ACCOUNT ...................................................................................................................................... 12
FT.TXN.TYPE.CONDITION ........................................................................................................... 12
Interfaces ............................................................................................................................................... 13
FT.TAPE.PARAMS ............................................................................................................................ 13
Running Clearing - FT.TAPES ........................................................................................................... 15
Processes for Incoming tapes ........................................................................................................ 15
Processes for Outgoing tapes ........................................................................................................ 15
Tracking tape processing ............................................................................................................... 16
Generic Accounting Interface ............................................................................................................ 16
File Layout - AC.ENTRY.PARAM .................................................................................................. 17
Error Management ......................................................................................................................... 19
Accounting Options - AC.ENTRY.PARAM ..................................................................................... 20
Entry Reporting - AC.INWARD.ENTRY ......................................................................................... 22
Deal/Transaction Processing ................................................................................................................ 24
Running the Interface ..................................................................................................................... 24
Running GAI in Batch Mode ........................................................................................................... 26
AC.ENTRY.PARAM DATA.ITEM details........................................................................................ 29
Overview
Local Clearing is a suite of applications in the FUNDS.TRANSFER module, which allow T24 to
interface with local clearing requirements with minimal amendment.
These applications define:
Setup
FT.LOCAL.CLEARING
This is the top-level application in Local Clearing. A record of id SYSTEM must be present to allow
local clearing transactions to be used in FUNDS.TRANSFER.
Information defined here includes:
• Which clearing system is being used for T24 payments.
• Which Funds Transfer transaction types are allowed for clearing, and their characteristics.
• Bank’s own processing details for each branch - sort code, Nostro details etc.
• Customer no. for clearing - all Delivery messages for this customer will be diverted to Clearing.
• PTT (Post office clearing) processing details.
• Local reference information, where required by a specific clearing system.
• Field lengths.
• No of multivalues.
Sort Codes
All sort codes processed via Local Clearing will be checked against the records set up on
BC.SORT.CODE.
If the sort code 123 is used on the TELLER, FUNDS.TRANSFER or DATA.CAPTURE application
then the value date will be defaulted from the VALUE.DATE.PRD field to be the processing date + 5
working days.
FT.TXN.TYPE.CONDITION
This application is used to define all FUNDS.TRANSFER transactions, not just Local Clearing. A
description of how it works is in the chapter FUNDS.TRANSFER in this User guide.
There are three FUNDS.TRANSFER transaction types which are used exclusively by Local Clearing:
BC Outgoing Payments
BI Incoming Payments
BD Incoming Direct Debits
Clearing transactions will use the transaction codes and descriptions, date, charge and commission
defaults set up in these records.
Variations of these transactions can be defined, for example BCAA, BCAS etc.
Interfaces
FT.TAPE.PARAMS
This file contains details of the tape files to be used for sending or receiving information from the local
clearing system.
Much of the information entered here describes the technical processing of incoming and outgoing
tapes - commands for tape loading, routines to call etc.
Also defined are retention of reports, retention of downloaded data and validation to prevent duplicate
processing.
• An ASCII file.
• Of fixed length.
• With CRLF line separators, each line of the file representing a separate record.
• Each record may be one of the following types: HEADER records, containing control information
(up to 9 allowed), TRAILER record containing control information, and DATA records containing
entry details. Each record type should be identified by a sequence of characters in the record.
The source record should be copied to the directory FT.IN.TAPE with the Id XXX.WORK, where XXX
is the name of the AC.ENTRY.PARAM record.
The elements comprising each record should be defined in the application AC.ENTRY.PARAM,
containing the starting position and length within the record. Each item may be identified as mandatory,
and may be validated by a defined validation routine. Standard system (IN2) validation routines may
be defined or customised routines. Each entry processed is also written to a working file,
AC.INWARD.ENTRY, the location of the extracted data in this file can also be specified.
As a minimum to successfully create accounting entries, the following elements must be supplied:
• Amount.
• It also recommended that the currency code is supplied for additional verification against the
account currency.
It is possible to define Local Reference fields in either STMT.ENTRY or CATEG.ENTRY as data
items (Value of DATA.ITEM specified as LOCAL.REF-NAME where NAME corresponds to a local
reference field name defined on the STANDARD.SELECTION table for STMT.ENTRY or
CATEG.ENTRY. The data values should pass any validation defined in the local reference validation
tables before they will be accepted. Multi-valued Local Reference field values should be separated by
the character ~ in the input.
Error Management
The processing performs certain validation to maintain the integrity of the T24 accounting database.
Where a header / trailer are supplied, the following elements will be validated:
CONTROL.DATE - This must match the T24 system date in order to be processed.
CONTROL.TOTAL - This must match the number of DATA records supplied in the file.
Entry validation, which will cause the entry not to be processed includes:
• Account currency code does not match the currency of the entry.
Where an account number or PL category is not found, the entry will be posted to a suspense account.
Optionally a FUNDS.TRANSFER record (type AC) will be created with status HLD, to allow correction
of the incorrect entry after the file has been processed.
Overrides encountered when processing entries (e.g. unauthorised overdraft, posting restriction) may
either be:
• Automatically approved.
• Suspensed automatically.
• Balance by currency netting debit and credit entries, irrespective of value date.
• Balance by value date, currency irrespective of sign, netting debits and credits.
Balancing entries may be raised to either a nominated account per currency, or to an internal account
of a defined category and department. The balancing (contra) entries will use definable debit and
credit transaction codes, together with an additional narrative.
In the case of P&L entries, an additional option will allow these entries to be treated as local currency
or not when raising balancing entries. If P&L entries are balanced by currency account entries,
position updates will result, whereas if treated as local currency there is no currency position.
The interface entries can be identified as interface entries by a separate SYSTEM.ID on the entry,
which is defined in AC.INWARD.ENTRY, field SYSTEM.ID.
Deal/Transaction Processing
Running the Interface
The interface will be invoked from the FT.TAPES application. In order to do this a record must be
defined for the interface in the application FT.TAPE.PARAMS.
The local routine to create the incoming file should be defined as the LOAD.CMD, or alternatively the
UNIX command required to copy the interface file or tape. When FT.TAPES is run with the action
LOAD, the interface file should be written to the directory FT.IN.TAPE, with the name XXXX.WORK,
where XXXX is the name of the FT.TAPE.PARAMS and AC.ENTRY.PARAM record. This will then
be copied to a file XXXX.NNNN in FT.IN.TAPE directory where NNNN is a sequence number allocated
to the file.
• The LOAD.ROUTINE AC.LOAD.INWARD.FILE should be defined. This will return information
concerning the incoming file, which will be stored in the FT.TAPE.REFERENCE / FT.TAPE.HIST
files for information. See APPENDIX.1 for DATA.ITEMs used for this extraction. Any other items
defined for Header and Trailer records may be viewed in ADD.INFO.
• The UPDATE.ROUTINE should be defined as AC.INWARD.FILE, the generic incoming interface
routine.
• The ENQ.PURGE.ROUTINE should be defined as AC.INWARD.ENTRY.PURGE.
• The VERIFICATION field should be set to YES to allow the interface to be run in extract only
mode, for examination of the file contents.
1. “V”erify FT.TAPES using the action LOAD for the interface to create the interface file.
2. “V”erify FT.TAPES using the action UPDATE to create accounting entries from the incoming
interface file. If required FT.TAPES should be run with the action VERIFY to update only the extract
file AC.INWARD.ENTRY. This option is recommended particularly when defining the interface layout
initially in the application AC.ENTRY.PARAM, to ensure that the correct structure has been defined.
Enter external accounting entries before the calculation of interest and charges
In BATCH mode the interface will fail with a FATAL.ERROR and result in the batch stopping. This could
be in the case of file integrity (control date / total differences), or the interface file not being present. If
an error is encountered and the batch should continue, the DATA definition of the records to process
should be suffixed with the value “*NOFATAL”.
To enter external accounting entries after the calculation of interest and charges on accounts, the
batch job EB.GENERIC.ACCT in the BATCH record SYSTEM.END.OF.DAY3 can be used.
Enter external accounting entries after the calculation of interest and charges