Banking Back-Office Processing Financial Transactions Reference Guide

Copyright  2002, Unisys Corporation. All rights reserved Unisys is a trademark of Unisys Corporation Release 9.000

October 2003 Printed in the UK 3937 0408–930

The names, places, and/or events used in this publication are not intended to correspond to any individual, group, or association existing, living or otherwise. Any similarity or likeness of the names, places and/or events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed Program Product License or Agreement to purchase or lease equipment. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such License or Agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, indirect, special or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. All registered trademarks are acknowledged. Correspondence regarding this publication should be forwarded to Unisys Corporation, Bakers Court, Bakers Road, Uxbridge, Middlesex, UB8 1RG, United Kingdom.

About This Guide This guide describes information on the management of financial transactions as processed by the Unisys Banking Back-Office Processing product.

Scope This guide describes the financial transactions available with the Retail Payments module, together with the associated data entry and interface screens. Examples of the screens are shown.

Audience This guide is intended for personnel who need an understanding of the methods of introducing financial transactions into the Unisys Banking Back-Office Processing product. In particular, it should be used by back-office staff that enter batch transactions manually.

Prerequisites Any person using this guide should be familiar with the user documentation. Users of this guide should have read the Starter's Guide to Retail that provides instruction in the use of the system.

How to Use This Guide This guide should be used as a reference tool when preparing information for back-office data entry. Use the guide in conjunction with a printed copy of your Guide to Setting Up the Retail System and the Core Retail Functions and Inquiries Guide that show the codes and mnemonics that are entered on other screens. Refer to the Core On-Demand Reports Guide for instructions on how to select and run the reports that provide this information.

3937 0408–930

iii

About This Guide

Organisation This guide consists of seven sections and two appendices: Section 1. Introduction This section provides an introduction to the Retail Payments module; it briefly describes the functions provided. Section 2. Processing Financial Transactions This section outlines the main types of financial transaction handled by the system and the basic rules for their processing. Section 3. Front Office Transactions This section describes the financial transactions that are available in the system and can be input by a teller in the front office. These transactions are typically entered into a Retail Delivery System (RDS). The RDS sends information to the system via interface screens. A short description covering the data to be received from the RDS is supplied with each interface screen. The description is accompanied by an illustration of the interface screen and a list of the mandatory fields. Section 4. Back Office Transactions This section describes the batch entry of transactions in the back office. These transactions are typically not entered via an RDS. A short description covering data entry, is supplied with each screen. The description is accompanied by an illustration of the screen and a table listing the mandatory, amendable and recall fields. Section 5. Charges This section describes the different types of charges supported by the system and explains the procedure for setting up charges. Section 6. Accounting Centre and Suspense Accounts This section describes the data entry screen used to create a relationship between an internal account and a specific accounting centre, currency and function combination. A short description covering data entry, is supplied with the screen. The description is accompanied by an illustration of the screen and a table listing the mandatory, amendable and recall fields. Section 7. Definition of Field Names This section provides definitions of the field names on the Financial Transaction screens. The fields are listed alphabetically and details of valid entries are given.

iv

3937 0408–930

About This Guide

Appendix A. Transaction Types This appendix lists the codes that represent each transaction handled by the system. One table of codes is given for each transaction type. Appendix B. Transaction Entries This appendix list the accounting entries that represent transactions handled by the system.

Related Product Information Product Overview (3937 0234) This document describes the capabilities and benefits of the system. It consists of an overview and description of each of the modules and interfaces available. It is intended for use by senior management. Retail Operations Reference Card (3937 0929) This document is a single card that provides a list of screen names and their mnemonics. The list is organised according to the menu structure of the Graphical User Interface. The card also describes how to log on and off, enter data, make inquiries and print reports. Starter’s Guide to Retail (3937 0903) This guide describes how to enter data and make online inquiries. It includes a description and example of commonly used data entry and inquiry screens. It also describes how to add a client and use a workflow with examples. This guide is intended for all new and inexperienced personnel who need to enter data and make inquiries. Guide to Setting Up the Retail System (3937 0879) This guide describes how to set up parameters that govern the operating environment of the system. It describes the procedures for setting up the business and operational tables, blueprint parameters, and setting up usercodes and access security. It should be used by all persons involved in installing, implementing and maintaining the system. Core Retail Functions and Inquiries Guide (3937 0887) This guide describes the kernel functions that are used regularly for the maintenance of information utilised by a number of modules. It describes the procedures for setting up and maintaining data, such as exchange rates. It also describes the interface to standard letters systems and the vault management facilities. It should be used by all users.

3937 0408–930

v

About This Guide

Retail Lending Administration Guide (3937 0390) This guide is only relevant to the retail loans module. It describes how to set up and maintain retail loan product templates. It also details the screens needed to enter an application for a loan and administer any loan granted as a result of an application. The screens used to record details of collateral used to back a loan are also described. An appendix gives the calculations used by retail loans. This guide should be used by personnel involved in loan administration. Retail Clients and Accounts Administration Guide (3937 0895) This guide describes the data entry and inquiry screens associated with setting up and maintaining client details. This guide also describes the set up and maintenance of client accounts, client account templates and automatic payments, such as standing orders. An appendix covers the calculations used by client accounts. This should be used by personnel preparing information for data entry. Arrears Management Administration Guide (3937 0978) This guide describes the data entry screens associated with the Arrears Management functionality. This allows the user to recognise when an account is in arrears, create an arrears case, and manage the arrears case. General Ledger Administration Guide (3937 0457) This guide describes the data entry screens associated with General Ledger transactions. This should be used by personnel preparing information for data entry. Core On-Demand Reports Guide (3937 0853) This guide describes how to run online reports that are relevant to retail and wholesale banking functions. Any options available when producing a report are detailed as well as any specific calculations. Retail On-Demand Reports Guide (3937 0846) This guide describes retail on-demand reports in alphabetical order. Any options available when producing a report are detailed as well as any specific calculations. Overnight Reports Guide (3937 0861) This guide describes how to run offline reports. This includes an overview of overnight processing. Instructions on how to initiate reports are given. This guide should be used by all personnel who need to understand the reports and the overnight process.

vi

3937 0408–930

About This Guide

Data Dictionary (3937 0226) This document provides details of data fields within every dataset on the database. This document should be used by staff preparing the accounting models and writing SQL reports to inquire on the database.

3937 0408–930

vii

About This Guide

viii

3937 0408–930

Contents About This Guide ......................................................................................... Section 1

Introduction Overview ................................................................................... Front Office Transactions ....................................................... Relationship with the RDS ........................................ Passbook Updates ................................................... Security ..................................................................... Back Office Transactions ........................................................ Exchange Rates ....................................................................... Validation of Transactions ...................................................... Back Valued Transactions ...................................................... Charges ..................................................................................... ATM / EFTPOS Management Systems and Payroll .............. Clearings ................................................................................... Internal Accounts ..................................................................... Retail Banking Accounting Entries ........................................

Section 2

1–1 1–2 1–3 1–4 1–4 1–6 1–6 1–7 1–7 1–8 1–8 1–8 1–9 1–10

Processing Financial Transactions Introduction .............................................................................. Retail Transaction Definition (TRDFM) .................................. Cash Transactions ................................................................... Depositing Cheques ................................................................ Clearing Deposited Cheques ................................... Cheque Withdrawals ................................................................ Cheque Withdrawals via Clearing ............................ Cheque Withdrawals via Foreign Banks .................. Payment Orders ....................................................................... Intra Bank Payment Orders ...................................... Domestic Payment Orders ....................................... Foreign Payment Orders .......................................... Bill Payments ............................................................................ Intra Bank Bill Payments .......................................... Domestic and Foreign Bill Payments ....................... Cashiers Cheques .................................................................... Intra Bank Cheques .................................................. Domestic Bank Cheques .......................................... Travellers Cheques ..................................................................

3937 0408–930

iii

2–1 2–2 2–3 2–3 2–3 2–8 2–8 2–8 2–9 2–9 2–9 2–9 2–10 2–10 2–10 2–11 2–11 2–11 2–12

ix

Contents

Section 3

Front Office Transactions Overview of Front Office Transactions ................................. Deposit Transactions ................................................ Withdrawal Transactions .......................................... Transfer Transactions .............................................. Cheque Negotiation Transactions ............................ Cheque Sale Transactions ....................................... Bureau de Change Movement Transactions ............ Retail Transaction Direct Entry Screens ............................... Deposits (TRDEP) .................................................... Withdrawals (TRWDR) ............................................. Transfers and Bill Payments (TRTFR) ..................... Cheque Negotiation (TRCNG) ................................. Cheque Sales (TRCSS) ........................................... Retail Delivery System Screens ............................................. Deposits Interface (TTDEP) ..................................... Loan Drawdown (TTLDD) ........................................ Withdrawals Interface (TTWDR) .............................. Transfers Interface (TTTFR) .................................... Cheque Negotiation Interface (TTCNG) ................... Bureau de Change Movements Interface (TTBDC) ............................................................... Cheque Sales Interface (TTCSS) ............................ Balance Inquiry / Passbook Update Interface (TTBPU) ...............................................................

Section 4

4–1 4–3 4–5 4–7

5–1 5–2 5–2 5–3 5–3 5–3 5–4

Internal Accounts Introduction .............................................................................. Create Internal Accounts ........................................................ Accounting Centre Accounts (BRACA) .................................

x

3–30

Charges Introduction .............................................................................. Item Charge .............................................................................. Turnover Charge ...................................................................... Periodic Charge ....................................................................... Event Based Charges .............................................................. Manual Event Based Charge ................................... Automatic Event Based Charge ...............................

Section 6

3–28 3–29

Back Office Transactions Introduction .............................................................................. Retail Batch Opening (RBTHD) ................................ Batch Transaction Details (RBTDE) ......................... Retail Batch Closure (RBTCL) .................................

Section 5

3–1 3–2 3–2 3–4 3–4 3–5 3–5 3–6 3–7 3–9 3–11 3–14 3–16 3–18 3–19 3–20 3–21 3–23 3–26

6–1 6–2 6–3

3937 0408–930

Contents

Section 7

Definition of Field Names Introduction ..............................................................................

7–1

Appendix A Transaction Types Introduction .............................................................................. Transaction Codes ................................................................... Deposits .................................................................... Withdrawals .............................................................. Bill Payments ............................................................ Cheque Negotiation .................................................. Bureau de Change Movements ................................ Cheque Sales ........................................................... Other Liability Transactions ...................................... Other Asset Transactions ......................................... Transaction Codes for Accounting Models .............. Charges .................................................................... Cross Accounting Centre Transactions ....................

A–1 A–2 A–2 A–4 A–5 A–6 A–6 A–7 A–8 A–9 A–11 A–12 A–13

Appendix B Accounting Entries Demand/Fixed Term Deposits/Savings ................................. Client Triggered ........................................................ Cheque Negotiation .................................................. Cashier’s Cheque Sales ........................................... Travellers Cheque Sales .......................................... System Triggered ..................................................... System Generated .................................................... Loans ........................................................................................ Performing Loan Activities ........................................ Non Performing Loan Activities ................................ After Final Demand Loan Activities .......................... Other ........................................................................................ Bureau De Change ................................................... Retail Cross Accounting Centre Postings ............................ Retail Cross Currency Postings ............................... Retail Cross Currency, Cross Accounting Centre Postings ................................................................

3937 0408–930

B–3 B–3 B–11 B–13 B–15 B–16 B–24 B–29 B–29 B–48 B–57 B–60 B–60 B–62 B–63 B–64

xi

Contents

xii

3937 0408–930

Figures 1–1

Relationship between Urbis and the Retail Delivery System ..................

1–3

2–1 2–2 2–3 2–4 2–5

Retail Transaction Definition ................................................................... Intra Bank Cheque Clearing .................................................................... Domestic Cheque Clearing (Successful) ................................................ Domestic Cheque Clearing (Unsuccessful) ............................................ Foreign Cheque Clearing ........................................................................

2–2 2–4 2–5 2–6 2–7

3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 3–9 3–10 3–11 3–12 3–13

Deposits screen ...................................................................................... Withdrawals screen ................................................................................. Transfers and Bill Payments screen ....................................................... Cheque Negotiation screen .................................................................... Cheque Sales screen .............................................................................. Deposits Interface screen ....................................................................... Loan Drawdown screen .......................................................................... Withdrawals Interface screen .................................................................. Transfers Interface screen ...................................................................... Cheque Negotiation Interface screen ..................................................... Bureau de Change Movements interface screen ................................... Cheque Sales Interface screen .............................................................. Balance Inquiry / Passbook Update interface screen .............................

3–8 3–10 3–13 3–15 3–17 3–19 3–20 3–21 3–23 3–27 3–28 3–29 3–30

4–1 4–2 4–3

Retail Batch Opening screen .................................................................. Batch Transaction Details screen ........................................................... Retail Batch Closure screen ...................................................................

4–4 4–6 4–7

6–1

Accounting Centre Accounts screen .......................................................

6–4

3937 0408–930

xiii

Figures

xiv

3937 0408–930

Tables 1–1

Validation Errors - Effect of Overriding ...................................................

1–4

3–1 3–2

Transfers screen - Mandatory Fields ...................................................... Transfers Interface screen - Mandatory Fields .......................................

3–11 3–22

5–1

Automatic Charges .................................................................................

5–4

7–1

Definition of Field Names ........................................................................

7–1

3937 0408–930

xv

Tables

xvi

3937 0408–930

Section 1 Introduction Overview The Retail Payments module is designed to handle transactions of many types, such as cheque deposits, payment orders and travellers cheque sales. The module provides: •

An interface to capture information from and return information to a Retail Delivery System (RDS). This information is entered by tellers and normally concerns an individual transaction, such as a bill payment or a cashier’s cheque withdrawal

•

Screens to permit the direct entry of front office transactions into the system

•

Screens to permit the rapid manual entry of a large volume of transactions, such as the deposit of a shop’s takings

•

Online inquiry and update of the System database. This database holds the details of your bank’s clients, accounts and products. See the Retail Clients and Accounts Administration Guide and the Retail Lending Administration Guide.

•

Reports for supplying files to clearing and for processing files received from clearing

•

Reports for the overnight processing of transactions from ATM / EFTPOS management systems and payroll

•

System generated financial transactions for Charges and Interest

•

System generated financial transactions for Automatic Payments (standing orders and direct debits)

•

Ability to interface with other channels for transaction processing, including internet banking and telephone banking

The processing of transactions from all sources including system generated transactions and clearing is detailed in Section 2 “Processing Financial Transactions”. Details of the individual reports are given in the Overnight Reports Guide.

3937 0408–930

1–1

Introduction

Front Office Transactions The front office teller facilities that will be provided by the Retail Payments module are grouped into the following categories: •

Deposits

•

Withdrawals

•

Transfers

•

Cheque Negotiation

•

Bureau de Change

•

Cheque Sales

•

Passbook Updates

•

Account Balance Inquiries

Front office transactions can be entered into Urbis using the two following methods: •

Direct entry into Urbis using the Front Office Transaction Screens, described in Section 3

•

Indirect entry into Urbis via a retail delivery system (RDS).

The interface screens that the system provides to capture data for each of the above transactions are not designed to be used directly. Rather they should be accessed via an RDS. The descriptions of the interface screens that you find in this guide provide reference information regarding the data that must be captured by the RDS for delivery to the system.

1–2

3937 0408–930

Introduction

Relationship with the RDS Teller transactions are entered into a Retail Delivery System (RDS). The RDS is an interface to Urbis. Through this interface you can enter transactions and extract information in the form of balance inquiries. This is shown in the following diagram:

Accounting Centre (A)

RDS Server (A)

Central Site Urbis Host

Front Office Teller Functions

Back Office Functions

(B)

Financial Transactions : • Deposits and Withdrawals • Transfers • Cheque Negotiations • Bureau de Change Currency Movements • Cheque Sales • Passbook Printing • Balance Inquiries Examples : • Batch Input (Deposits) • Batch Input (Withdrawals) • Set up of Accounts for Accounting Centre

KEY : (A) Financial Transactions : front office to Urbis (B) Back office functions using direct connection to Urbis Note: Some Accounting Centres may have limited IT capability or operate completely manually

Figure 1–1. Relationship between Urbis and the Retail Delivery System Teller transactions entered into the RDS can be updating or non-updating. Updating transactions are reflected in the Urbis database in real-time when both systems are online. If communication from the RDS to Urbis is unavailable, transactions entered into the RDS are stored until online operation is resumed. When Urbis becomes available, the stored transactions are applied one by one as a series of transactions. It is the responsibility of the RDS to ensure that new online transactions are not processed until all stored transactions are applied. When Urbis is offline, the link from the RDS to the Urbis database is unavailable. This means that account balances and account rules cannot be checked before a transaction is entered. Therefore, the bank must have procedures to control the transactions that take place in these circumstances. If you enter a transaction that would have failed online validation by Urbis but was accepted by the RDS, Urbis forces the transaction to be posted anyway. For example, if the account is permitted to have a debit balance, the system posts the transaction to the account (even if the overdraft limit is exceeded) and the unauthorised overdraft interest rate set for the account is applied automatically. If the account is not permitted to have a debit balance, the system posts the transaction to the relevant accounting centre error suspense account. The RPOSTBRLST Postings to Accounting Centre Accounts report (see the Retail On-Demand Reports Guide) gives details of postings made to the error suspense account.

3937 0408–930

1–3

Introduction

Passbook Updates Urbis controls the transactions that appear in an account’s passbook. The RDS controls the physical printing of the passbook entries. When Urbis successfully processes a teller transaction, it determines whether the account processed is a passbook account. If it is a passbook account, the following processing occurs: •

If the teller has indicated via the RDS that the passbook is available for printing, then Urbis passes details of all the account’s unprinted transactions to the RDS for printing

•

If the teller has indicated via the RDS that the passbook is not available for printing, then Urbis stores details of the new transaction. This transaction together with any other unprinted transactions can be sent to the RDS for printing when the passbook is available

To permit adhoc passbook updating, Urbis supplies a separate facility that the RDS can utilise to obtain any unprinted transaction details when the passbook is presented. To allow for exceptional circumstances, such as print failure, this facility also allows the RDS to obtain transaction details that have already been flagged as printed by Urbis. In this case, the teller must specify that all transactions from a particular date and time are required. When transactions are received from sources other than the RDS, for example internally generated interest settlements or ATM transactions, and are processed against passbook accounts, then Urbis stores details of the transactions. These transactions together with any other unprinted transactions can be sent to the RDS for printing when the passbooks are available.

Security When a transaction is entered into the RDS, it checks that the teller has the authority to perform the transaction. In Urbis, the teller must have the authority to enter financial transactions. The actual transactions that a teller can perform depend on settings in the RDS. If a teller receives a validation error when inputting a transaction, for example ‘Overdraft limit exceeded’, the error can be overridden. Normally it will be the responsibility of the teller’s supervisor to override an error. The person who overrides the error must have an authority level greater than the level of the error message. If a validation error is overridden, the actual processing performed is dependent upon the error. The following table describes the processing that occurs if an error is overridden. Note: The supervisor is unlikely to override several of the errors given in this table. However, if the link between the RDS and Urbis is unavailable and an invalid transaction is accepted, then the transaction will be forced when the link is restored. The table shows how these forced transactions will be processed. Table 1–1. Validation Errors Effect of Overriding

1–4

Problem Item

Error Found

Action If Overridden

Account

Not open or not found, or account only allows credit balances

Post to error suspense account of currency on screen

3937 0408–930

Introduction

Problem Item

Error Found

Action If Overridden

Amount

All zeros entered

Do not process transaction

Book Date

Not found

Use today’s date

Charge Account

Not open or not found

Post to error suspense account of currency on screen

Cross Currency Transaction

Not valid for account

Post to error suspense account of currency on screen

Currency Conversion

Conversion fails

Post to error suspense account of currency on screen

Input Date

Invalid date

Use Book Date

Loan Drawdown and Loan Records

Not found or account not open

Post to error suspense account of currency on screen

Loan Drawdown Amount

Validation fails

Post to error suspense account of currency on screen

Product Master Record

Not found

Post to error suspense account of currency on screen

Screen Currency Code

Not in currency table

Post to error suspense account of ‘unknown’ currency

Screen Currency Code

Single currency transaction but not in account’s currency

Post to error suspense account of currency on screen

System Parameter Record

Problem with system set up (for example invalid status)

Do not process transaction

Teller Sequence

Not entered

Do not process transaction

Transaction

Transaction already processed

Do not process transaction

Transaction Code

Not valid for screen

Set transaction code to n99 (where n is the first digit of the supplied transaction code). Post to error suspense of currency on screen

Transaction Code

Not in table of transaction codes

Set to 1 and post to error suspense of currency on screen

Transaction Code

Transaction code invalid for product

Post to error suspense account of currency on screen

Value Date

Invalid date, or Holiday/Weekend, or Date before last interest settlement date

Post to error suspense account of currency on screen

3937 0408–930

1–5

Introduction

Back Office Transactions The system provides a batch processing facility. This enables you to enter data for: •

Accounting centres that are unable to capture data at a particular time

•

Accounting centres where online equipment is not available

•

Summary transactions for those transactions that include a large amount of data, for example a collection of takings for a shop

Batch transactions are split into three elements: 1.

Opening the batch with a batch header

2.

Entering transaction details

3.

Closing the batch

A batch contains entries for one currency only.

Exchange Rates The exchange rates used for cross currency transactions are held on the Exchange Rates Maintenance (EXCHM) table. The Exchange Rate Group and the Cross Currency Transaction fields are set on the Retail Transaction Definition (TRDFM) screen. If these fields are not indicated, then the transaction uses the Exchange Rate Group set up on the Accounting Centres Maintenance (ACNTM) screen (see the Retail Guide to Setting Up). The exchange rate groups that may be referenced are: COUN - Counter rates CASH - Cash transactions CHEQ - Cheque transactions TCHQ - Travellers cheque transactions OTHR - Other transactions If you enter a cross currency transaction that involves one foreign currency only, the system converts the currency of the transaction to the currency of the related account. If you enter a cross currency transaction that involves two foreign currencies, the system converts the currency of the transaction to base currency first and then to the currency of the related account. The ‘Sell’ rate held on the Exchange Rates Maintenance (EXCHM) table is used for a local to foreign currency conversion and the ‘Buy’ rate is used for a foreign to local conversion.

1–6

3937 0408–930

Introduction

Validation of Transactions When a transaction is entered into the system, it checks that the teller has the authority to perform financial transactions. The system makes other checks as to the validity of the transaction, for example whether there are sufficient funds in an account to support a withdrawal. If a transaction input fails validation, an error message is passed to the RDS. A supervisor can override the error and commit the transaction to the system if the supervisor has a sufficient level of authority (see “Security” later in this section). The validation performed when a debit transaction is received for processing against an account is dependent upon the type of account and the rules set up for the individual client. For example when a debit transaction is submitted against a demand account, the system calculates the available balance by adding the total approved overdraft limit for the account to the value balance and subtracting any held amounts. If the resulting figure is higher than the debit amount, the transaction is accepted. If the debit amount is higher, the transaction is rejected and an error message displayed. At this point the transaction can be resubmitted by a user that has sufficient authority to override the error. If an excessive debit is submitted in this way, the penalty overdraft rate defined for the account is applied automatically. If the system is offline when a withdrawal is made, the system accepts debit transactions that fail validation without user intervention. Such transactions can take an account balance into overdraft or over the authorised overdraft limit. If this occurs, the penalty overdraft rate set for the account is applied automatically. If, however, the account is of a type that cannot have a debit balance, the transaction is redirected to the accounting centre error suspense account. The account is reported on the RPOSTBRLST - Postings to Accounting Centre Accounts report. When sufficient funds are available to rectify the situation, you must debit the client account and credit the accounting centre error suspense account manually.

Back Valued Transactions If an account has interest conditions, transactions can be entered with a value date as far back as the last interest settlement date. If an account does not have interest conditions, you can enter a transaction with a value date as far back as the account’s transaction history is retained.

3937 0408–930

1–7

Introduction

Charges The following types of charges exist in the system: •

Item

•

Turnover

•

Periodic

You can define a charge for every transaction processed by the system. When a transaction that attracts a charge is processed, the charge is applied automatically when the transaction comes to value. The charge will be debited from the client account associated with the transaction unless a charge account has been specified in the account details. You can define charge transactions for charges that are unrelated to a financial transaction. For example, a request for a duplicate statement. A series of transaction codes is dedicated to such charges. See Section 5, “Charges” for further details.

ATM / EFTPOS Management Systems and Payroll Urbis processes batch files received from ATM / EFTPOS management systems and payroll. These files contain the payroll transactions and the transactions performed via ATMs and EFTPOS during the day. Urbis then processes the transactions during overnight processing to update the accounts before the following day’s processing begins.

Clearings The system processes batch files received from clearing centres to withdraw funds from client accounts as a result of cheques, previously issued by the bank’s clients being presented for payment. The system posts the transactions to update the accounts before the following day’s processing begins.

1–8

3937 0408–930

Introduction

Internal Accounts Each accounting centre has a set of internal accounts to support the banks processing, as follows: •

Bureau de Change movements

•

Cashier’s cheque negotiation

•

Cashier’s cheque sales

•

Eurocheque negotiation

•

Travellers cheque negotiation

•

Travellers cheque sales

•

Cheques for collection

•

Foreign currency cheques for collection

•

Payment orders for collection

•

Outgoing payment order collection

•

Domestic standing orders collection

•

Fixed term deposit suspense

•

Error suspense

One account is allocated to each currency and function listed above. With the exception of error suspense accounts, the same account can be used for more than one combination of accounting centre and function, but different accounts must be used for each currency. In addition to the set provided for the system processing, internal accounts my be created and used for manual processing by the bank to support other functions such as, loan drawdowns by cheque withdrawal. Error suspense accounts are used for postings that must be processed but according to the bank’s rules should not be processed without manual intervention. For example, if a client account is not permitted to be in debit but a withdrawal that causes a debit balance is made while the system is offline, then when the transaction is received it is posted to an error suspense account. Further examples of the use of error suspense accounts are shown in Table 1-1. The RPOSTBRLST - Retail Postings to Branch Accounts List report (see the Retail On-Demand Reports Guide) is run on a daily basis for all the error suspense accounts and gives details of all the transaction postings to the accounts. These transactions can be investigated and the appropriate action taken according to the bank’s procedures. Each accounting centre must have an error suspense account for each of the currencies that it uses. An ‘unknown currency’ account must be set up as an error suspense account. This account will be used for those transactions with a currency that is not used by your accounting centre. See Section 6, “Internal Accounts”, for details on set up and processing.

3937 0408–930

1–9

Introduction

Retail Banking Accounting Entries Retail banking client account transactions do not post via the accounting models. The postings that are made depend on rules specified for a product on the Product Transaction Types (PTTRM) screen. Two accounts are specified for every transaction that is permitted for a product: one for the product itself and one for the transaction. For further details on this screen, see the Retail Clients and Accounts Administration Guide. The Product Transaction Types (PTTRM) screen can pick up defaults for both general ledger accounts. The default general ledger account for a transaction code is defined on the Retail Transaction Definition (TRDFM) screen (see Section 2). The default for a product is defined with the product details on the Product Maintenance Screen 1 (PTA1M) for retail banking client accounts and on the Loan Product Maintenance - 2 (PTL2M) screen for retail loan accounts. For further details on this screen, see the Retail Lending Administration Guide. The provision of two general ledger accounts for every combination of product and transaction facilitates double entry book keeping by reflecting an accounts balance (via the product) and the means by which the balance has been updated (via the transaction). For further details on General Ledger updates, see General Ledger Updates to Retail Banking Transactions in the General Ledger Administration Guide. For a complete list of retail accounting entries, see Accounting Entries in Appendix B.

1–10

3937 0408–930

Section 2 Processing Financial Transactions Introduction Urbis is able to handle a wide range of financial transactions. The transaction code determines the financial transaction to be performed, and can be received from: •

An interface that is used to capture information from and return information to a Retail Delivery System (RDS)

•

The direct entry of a front office transaction into the system

•

A program performing overnight processing.

Appendix A “Transaction Types” gives a full list of transaction codes by transaction type. This section outlines the main types of financial transaction handled by the system and the basic rules for their processing. The actual validation rules that are used to determine whether a transaction is successful are largely dependent on the products and accounts that your bank sets up. For example, the Product Transaction Types (PTTRM) screen, described in the Retail Clients and Accounts Administration Guide, is used to specify the transactions that are permitted against a product. Each transaction can be associated with a charge. The charge will be levied automatically when a chargeable transaction is passed for an account.

3937 0408–930

2–1

Processing Financial Transactions

Retail Transaction Definition (TRDFM) The financial transactions processed by the system cover deposits, withdrawals, transfers, cheque negotiation, Bureau de Change movements and cheque sales. Each transaction is represented by a code (a full list of transaction codes is available in Appendix A of this guide). All financial transactions must be defined on the Retail Transaction Definition (TRDFM) screen. This includes transaction charges and event charges. A complete set of financial transaction definitions is included as part of the foundation database installed with the system. However, you must set the ‘Default GL Transaction Account’ to match your general ledger account structure. In addition, manual event charges and arrears charge transactions must be defined (see the Arrears Management Administration Guide and the Retail Clients and Accounts Administration Guide). The Product Transaction Types (PTTRM) screen defines the general ledger accounts that are updated when a transaction is passed for an account. The general ledger account that you specify on the Retail Transaction Definition (TRDFM) screen is a default that can be referenced on that screen. The following figure shows an example of the Retail Transaction Definition screen.

Figure 2–1. Retail Transaction Definition

2–2

3937 0408–930

Processing Financial Transactions

Cash Transactions When cash is deposited, the book, available and value balances of the account receiving the deposit are updated online. If cash is withdrawn via a withdrawal slip, the book, available and value balances of the account being debited are also updated online.

Depositing Cheques When a cheque is deposited, the book balance is updated online but the value and available balances are not updated until the value date of the cheque has been reached. The value date of a cheque deposit depends on the clearing period associated with the bank that issued the cheque. For an RDS transaction, the value date of each cheque deposit transaction must be supplied by the RDS. Note: A deposit that is composed of a mixture of cash and cheques (local currency only) must be entered into the system via two transactions. When a cheque deposit is entered that involves a cheque drawn on your own bank, the cheque details are checked against the Stopped Cheques list. This can be done only if details of the deposited cheque are entered with the transaction.

Clearing Deposited Cheques The processes that the system follows to clear cheques deposited in accounts held at your bank depends on the bank that the cheque is drawn upon. There are three types: •

Intra bank, where the cheque is drawn against an account held at your bank

•

Domestic, where the cheque is drawn against an account held at another bank that is a member of the domestic clearing system

•

Foreign, where the cheque is drawn against an account held at another bank that is not a member of the domestic clearing system

All of the above are covered in the following sections.

3937 0408–930

2–3

Processing Financial Transactions

Intra Bank Cheque Deposits The following diagram shows the processes that the system follows when a client deposits a cheque that is drawn upon your own bank:

Day 1

Online Deposit Cheque

Deposit transaction is posted to the credit account

End-of-Day Processing Withdrawal transaction created against Source of Funds Account

Check available funds in Source of Funds

Check = Pass Debit Source of Funds Account

Check = Fail Charge debited against Source of Funds Account ‘Contra’ deposit transaction and charge posted to the credit account

Day 2

Beginning-of-Day Processing Deposit transaction comes to value against credit account

Deposit transaction comes to value against credit account (amount is cancelled out by ‘contra’ transaction already posted)

Figure 2–2. Intra Bank Cheque Clearing When a client deposits an intra bank cheque, a teller enters a deposit transaction into the system, or the RDS. The book balance of the credit account involved in the transaction is updated online. During overnight processing, the system checks the source of funds account to ensure that the cheque can be paid. If sufficient funds are available, a withdrawal transaction is created to debit the account. For users with an RDS interface, this transaction is in the format accepted by the Withdrawals Interface (TTWDR) screen. Finally, the transaction is brought to value during beginning-of-day processing the following day (i.e. the value balance of the credit account is credited with the cheque amount).

2–4

3937 0408–930

Processing Financial Transactions

If, when the system checks the source of funds account, it finds that the cheque cannot be paid, it does not post a cheque withdrawal transaction to the account. A charge transaction is posted to the source of funds account. An account check fails if insufficient funds are available or the cheque itself has been stopped. A ‘contra’ deposit transaction and a charge transaction are posted to the credit account during end-of-day processing that day. The contra is a negative of the cheque amount. During beginning-of-day processing the next day, the deposit transaction is brought to value as with a successful cheque deposit above but is cancelled out by the previously posted contra transaction. The client’s statement shows that the cheque was returned. If a guaranteed cheque is deposited that would fail an account check for any reason other than it has been stopped, the transaction is force posted. This may cause the account to go into unauthorised overdraft. If the account is not permitted to go into overdraft, the transaction is posted to the error suspense account.

Domestic Bank Cheque Deposits The following diagram shows the system processing when a client deposits a cheque that is drawn upon a bank other than your own that is a member of the domestic clearing system:

Our Bank Deposit Cheque (online)

Send cheque details to domestic clearing (EOD)

Domestic Clearing House Receive cheque and send to drawing bank

Drawing Bank Clear cheque successfully no further action

Our Bank If no reply received from domestic clearing by end of clearing period, credit the credit account

Figure 2–3. Domestic Cheque Clearing (Successful)

3937 0408–930

2–5

Processing Financial Transactions

When a client deposits a cheque drawn upon another domestic bank, a teller enters a deposit transaction. During overnight processing, the cheque details are extracted and sent to the domestic clearing house. The clearing house sends the details on to the bank that issued the cheque. If the issuing bank clears the cheque successfully, it does not need to send a reply to the clearing house. Therefore if you receive no communication regarding the cheque by the time the clearing period has elapsed, the cheque is assumed to have cleared. The deposit transaction is then brought to value and the credit account is credited with the cheque value. If the issuing bank cannot clear a cheque, it sends a rejection message back to the clearing house. This message is then forwarded to your bank. Contra and charge transactions are then posted valued at the same date as the original cheque deposit. This is shown in the following diagram:

Our Bank Deposit Cheque (online)

Send cheque details to domestic clearing (EOD)

Domestic Clearing House Receive cheque and send to drawing bank

Drawing Bank Unable to clear cheque return to clearing

Domestic Clearing House Return to bank

Our Bank Post ‘contra’ amount and charge to the credit account - value date = date of original deposit Cheque deposit and ‘contra’ transaction come to value against the credit a/c during beginning-of-day

Figure 2–4. Domestic Cheque Clearing (Unsuccessful)

2–6

3937 0408–930

Processing Financial Transactions

Note: A rejection notice should be received before the clearing period has elapsed. If it is not, the contra transaction will be back-valued. The back-valuation must be valued prior to any interest settlement event on the account. If interest settlement has occurred since the value date of the cheque, then a contra posting is made to an error suspense account and manual adjustment is required.

Foreign Bank Cheque Deposits The following diagram shows the processes that the system follows when a client deposits a cheque that is drawn upon a bank other than your own that is not a member of the domestic clearing system:

Deposit Cheque

Deposit transaction is posted to Foreign Cheques for Collection account

Clear funds manually with Source of Funds bank

Clearing = Successful

Clearing = Unsuccessful

Manually transfer funds to the credit account

Manually post ‘contra’ transaction to the Foreign Cheques for Collection account Manually post charge to the credit account

Figure 2–5. Foreign Cheque Clearing When a client deposits a cheque drawn upon a bank that is not a member of the domestic clearing system, a teller enters a deposit transaction. This credits the Foreign Cheques for Collection Account. The Foreign Cheques for Collection account is a client account set up by you specifically for this purpose. The foreign cheque must be cleared manually according to the procedure your bank follows for this. When notification is received from the foreign bank that a cheque has cleared successfully, enter a Transfer transaction to move the funds into the beneficiary’s account. As part of the overnight processing all foreign cheque deposit transactions are identified and postings made to the nostro accounts. If you receive notification that a cheque cannot be cleared, you must post a ‘contra’ transaction (reversal) into the Foreign Cheques for Collection account. You should also post a charge to the beneficiary’s account.

3937 0408–930

2–7

Processing Financial Transactions

Cheque Withdrawals When a withdrawal is attempted using a cheque, the withdrawal cannot take place until the value date of the cheque is reached. Direct entry of the cheque withdrawal can be performed on the Cheque Negotiation (TRCNG) screen. For users with an RDS interface, online cheque withdrawals are performed when the RDS sends details to the Cheque Negotiation Interface (TTCNG) screen. If the standard account validation is successful, then the account balances are updated online. If account validation is unsuccessful, then an error is returned.

Cheque Withdrawals via Clearing If cheques drawn on your bank are deposited into accounts held at other domestic banks, then a file containing details of the cheques to be cleared is received from the clearing house. During end-of-day processing the system extracts the cheque details and processes them as domestic cheque withdrawal transactions. If a transaction is rejected, the details are written to a file that is returned to the clearing house. The only action that is taken against the debit account is that a charge is applied automatically.

Cheque Withdrawals via Foreign Banks If a cheque drawn on your bank is deposited into an account held at a foreign bank, then a withdrawal transaction must be raised manually against the client’s account to move funds into the foreign bank’s nostro account. As part of the overnight processing all these withdrawal transactions are identified and postings made to the nostro accounts. If processing is unsuccessful, then the foreign bank cheque must be returned and a charge must be raised manually against the client’s account.

2–8

3937 0408–930

Processing Financial Transactions

Payment Orders Payment orders differ from cheques in that they are always guaranteed since they are paid for before they are issued. As is true for cheques, processing of payment orders differs depending on whether they are intra bank, domestic or foreign.

Intra Bank Payment Orders An intra bank payment order is effectively the transfer of funds between one client account held at the bank and another and it is treated as such by the system. Therefore, on the date of the payment order funds are withdrawn from one account and deposited in the other.

Domestic Payment Orders Processing of a domestic payment order differs depending on whether it is outgoing or incoming. For outgoing payment orders: •

A cash payment is first deposited in the Outgoing Payment Order Collection account. Details of this transaction are then extracted and included in a file that is sent to the clearing house.

•

A payment from a client account (such as a cheque payment) causes a withdrawal transaction to be posted to the paying client’s account. Details of this transaction are then extracted and included in a file that is sent to the clearing house.

When a domestic payment order is received from the clearing house, the value of the payment order is paid into the beneficiary’s client account as a deposit transaction during end-of-day processing. If a client account is not to be used and the payment order is to be cashed, the payment order is paid into the Payment orders for Collection account. When the beneficiary arrives to cash the payment order, you debit the Payment order for Collection account via a withdrawal transaction.

Foreign Payment Orders As is the case for domestic payment orders, processing differs depending on whether the payment order is outgoing or incoming. For outgoing payment orders: •

A cash payment is first deposited in the Outgoing Payment Order Collection account. As part of the overnight processing all outgoing foreign payment orders are identified and postings made to the nostro accounts

•

A payment from a client account (such as a cheque payment) causes a withdrawal transaction to be posted to the paying client’s account. As part of the overnight processing all outgoing foreign payment orders are identified and postings made to the nostro accounts

Details of the foreign payment orders are sent to the foreign bank using the method standard to your bank. When a foreign payment order is received for payment into a client account, you must credit the account using a deposit transaction. If a client account is not to be used and the payment order is to be cashed, you must credit the Payment orders for Collection account when the instruction is received. When the beneficiary arrives to cash the payment order, you debit the Payment orders for Collection account via a withdrawal transaction.

3937 0408–930

2–9

Processing Financial Transactions

Bill Payments Bills paid for either with cash or from a client account are always processed as transfers. For bill payments, the bill reference must be supplied to specify the bill that is being paid.

Intra Bank Bill Payments Intra bank bill payments may be initiated by a cash deposit or a withdrawal from an account held at the bank and a deposit to another account held at the bank. In either case, the bill payment can be set up as a transfer of funds using the RDS to send details, including the appropriate transaction codes, to the Transfers Interface (TTTFR) screen. For direct entry of an Intra Bank Bill Payment, use the Transfers and Bill Payments (TRTFR) screen.

Domestic and Foreign Bill Payments Domestic and Foreign bill payments are managed via collection accounts in a similar way to payment orders. However for outgoing bill payments, the bank identifier, accounting centre and account number of the destination account must be supplied so that they can be included in the file sent to the clearing house or foreign bank.

2–10

3937 0408–930

Processing Financial Transactions

Cashiers Cheques Intra Bank Cheques Cashiers cheques can be sold to a client either using cash or funds from an existing account e.g. where a client wishes to withdraw the closure balance by a cashiers cheque. To sell a cashiers cheque, the RDS interfaces to Urbis via the Cheque Sales Interface (TTCSS) screen using transaction codes 620 (by cash) or 630/631 (by account funds). The system automatically uses the cashiers cheque sales internal account (CCSALE) for the accounting centre of the teller that is defined on the Accounting Centre Accounts (BRACA) screen. Once sold, the cheque may be bought from the client using the Cheque Negotiation Interface (TTCNG) screen either paid in cash (transaction code, 450) or to a client account (452). The system automatically uses the cashiers cheque sales internal account (CCSALE) for the accounting centre of the teller that is defined on the Accounting Centre Accounts (BRACA) screen. When your institution does not use the RDS interface, then the above process can be applied on the Retail Transaction Direct Entry Screens, Cheque Sales (TRCSS), and Cheque Negotiation (TRCNG). Note: You need to issue a cashiers cheque to the cashiers cheque sales internal account (CCSALE) before it can be sold. See Retail Clients and Accounts Administration Guide Section 8 for details.

Domestic Bank Cheques A cashiers cheque from another bank may be deposited to a client’s account by the RDS interfacing to Urbis via the Deposits Interface (TTDEP) screen using transaction code 140. When your institution does not use the RDS interface, then the above process can be applied on the Retail Transaction Direct Entry Screens, Deposits (TRDEP). The 140 transaction is picked up during the overnight run by the report RTEXTRACT - Retail Transaction Extraction, to be sent to clearing (EXTPAYMENT).

3937 0408–930

2–11

Processing Financial Transactions

Travellers Cheques Travellers cheques can be sold to a client either using cash or funds from an existing account. To sell travellers cheques, the RDS interfaces to Urbis via the Cheque Sales Interface (TTCSS) screen using transaction codes 600 (by cash) or 610/611 (by a/c funds). The system automatically uses the travellers cheque sales internal account (TCSALE) for the a/c centre of the teller that is defined on the Accounting Centre Accounts (BRACA) screen. Travellers cheques may be bought from the client using the Cheque Negotiation Interface (TTCNG) screen either paid in cash (transaction code, 440) or to a client account (442). The system automatically uses the travellers cheque negotiation internal account (TCNEGO) for the a/c centre of the teller that is defined on the Accounting Centre Accounts (BRACA) screen. When your institution does not use the RDS interface, then the above processes can be applied on the Retail Transaction Direct Entry Screens, Cheque Sales (TRCSS), and Cheque Negotiation (TRCNG). Note: You need to assign travellers cheques to the teller before they can be sold. See Core Retail Functions and Inquiries Guide Section 3, Vault Management, for details.

2–12

3937 0408–930

Section 3 Front Office Transactions Overview of Front Office Transactions Front office transactions can be entered into Urbis using the two following methods: •

Direct entry into Urbis using the Front Office Transaction Screens

•

Indirect entry in to Urbis via a retail delivery system (RDS). Urbis provides interface screens that capture transaction data transmitted from the RDS. The interface screens are not designed to be accessed directly by users. The tellers enter front office transactions into the RDS operating at an accounting centre. The RDS interfaces to Urbis to send transaction information and receive information from the database. See "Retail Delivery System Screens" for descriptions of the interface screens used.

Each screen is able to handle a number of business transactions. It is the transaction code that determines the business transaction to be entered. Appendix A “Transaction Types” gives a full list of transaction codes by transaction type. The types of transaction processed by Urbis are as follows: •

Deposits

•

Withdrawals

•

Transfers

•

Negotiation of cheques for immediate clearance

•

Bureau de change currency movements

•

Cheque sales

The Product Transaction Types (PTTRM) screen, described in the Retail Clients and Accounts Administration Guide, is used to specify the transactions that are permitted against a product. Each transaction can be associated with a charge. The charge will be levied automatically when a chargeable transaction is passed for an account. For a cross currency transaction that involves one foreign currency, Urbis converts the currency of the transaction to the currency of the destination account. For a cross currency transaction that involves two foreign currencies, Urbis converts the currency of the transaction to base currency first and then to the currency of the destination account. Note: Individual bureau de change transactions are processed by the RDS. Summaries of currency sales and purchases are passed to Urbis.

3937 0408–930

3–1

Front Office Transactions

Deposit Transactions Deposits of the following items are accepted by Urbis: •

Cash – Account Currency – Foreign Currencies

•

Cheques – Intra bank – Domestic – Foreign – Cashier’s

•

Account credit adjustments

•

Payment order deposits (via RDS only)

•

Loan repayment adjustment credits (via RDS only)

•

Loan early payments (via RDS only)

•

Loan payments (the specific processing associated with these deposits is described in Section 1 “Loan Payments” in the Retail Lending Administration Guide) (via RDS only)

Deposit transactions are processed by the Deposits (TRDEP) or the Deposits Interface (TTDEP) screens.

Withdrawal Transactions Withdrawals of the following items are accepted by Urbis: •

Cash – Account Currency – Foreign Currencies

•

Account debit adjustment

•

Deferred Charges

•

Cash advance from a plastic card (via RDS only)

•

Payment order withdrawals (via RDS only)

•

Cashier’s cheque for collection and withdrawal (via RDS only)

•

Loan repayment adjustment debit (via RDS only)

•

Charges unrelated to a financial transaction (via RDS only)

•

Loan drawdown (via RDS only)

Withdrawal transactions are processed by the Withdrawals (TRWDR) and the Withdrawals Interface (TTWDR) screens. Loan drawdowns are processed by the Loan Drawdown Interface (TTLDD) screen.

3–2

3937 0408–930

Front Office Transactions

Notice Periods Notice may be required to withdraw funds from certain types of savings account. If a withdrawal is attempted that fails to meet the notice parameters set for the account, a warning is returned to the RDS. This gives the teller the opportunity to ask the client to verify the transaction. If the client wants to go ahead with the transaction anyway, the teller can override the warning and input the transaction. A penalty is applied to the account during overnight processing. The penalty is calculated according to the selection made in the related product template. After a client gives notice for a withdrawal they can give notice for further withdrawals before the notice period for the first has elapsed. This does not affect the length of the notice period for any of the withdrawals. See the Retail Clients and Accounts Administration Guide for details on notices.

Loan Drawdowns A drawdown on a loan account must be made in the same currency as the loan account. The amount that can be drawn depends upon the type of loan: •

Repayment and Annuity Loans The loan amount

•

Discounted Loans The outstanding principal which for discounted loans is the loan amount minus the discounted interest

•

Revolving For the first drawdown, the loan amount. All other following drawdowns can be up to the loan amount

•

Budget Any amount up to the credit limit.

3937 0408–930

3–3

Front Office Transactions

Transfer Transactions Transfers of the following items are accepted by Urbis: •

Cash to: – A domestic bank account – A foreign bank account

•

Movement of funds between an intra bank account to: – An Intra bank account – A domestic bank account – A foreign bank account

•

Transfer to a non-account holder

•

Bill payment

•

Loan early payment (via RDS only)

•

Loan payment (via RDS only)

Transfer transactions are processed by the Transfers (TRTFR) and the Transfers Interface (TTTFR) screens.

Cheque Negotiation Transactions The following types of cheque can be negotiated to buy from a client over the counter for immediate clearance: •

Intra bank

•

Travellers

•

Cashier’s

Cheque negotiation transactions are processed by the Cheque Negotiation (TRCNG) and the Cheque Negotiation Interface (TTCNG) screens. Cheques that are successfully negotiated for immediate clearance can either be paid in cash or credited to a client account. Details of all intra bank cheques presented for negotiation are checked that they have been issued, and checked against the Stopped Cheques list. If a cheque has not been issued or is found to be on the list, an error is returned to the RDS and the transaction is rejected. Cashiers cheques must have been issued and sold before they can be presented for negotiation. If not, an error is returned to the RDS and the transaction is rejected.

3–4

3937 0408–930

Front Office Transactions

Cheque Sale Transactions The following types of cheques can be sold to a client over the counter in both the base currency and in foreign currencies: •

Sale of travellers cheques for cash

•

Sale of travellers cheques for debit from an account

•

Sale of cashier’s cheques for cash

•

Sale of cashier’s cheques for debit from an account

•

Loan drawdown as a cashier’s cheque (via RDS only)

Cheque sale transactions are processed by the Cheque Sales (TRCSS) and Cheque Sales Interface (TTCSS) screens.

Bureau de Change Movement Transactions The following movements of currency from the bureau de change are processed by Urbis: •

Inward movement (via RDS only)

•

Outward movement (via RDS only)

Bureau de change movement transactions are processed by the Bureau de Change Movements (TTBDC) interface screen. Summary totals of currency moved as a result of bureau de change transactions can be recorded. Money received in charges should be included in the total amount moved inward for the currency in which the charge was taken.

3937 0408–930

3–5

Front Office Transactions

Retail Transaction Direct Entry Screens This section provides a description of the following screens: •

Deposits (TRDEP)

•

Withdrawals (TRWDR)

•

Transfers and Bill Payments (TRTFR)

•

Cheque Negotiation (TRCNG)

•

Cheque Sales (TRCSS)

For each screen the following is provided: •

A description of its use

•

An example of the screen

A full description of the fields on these screens is given in Section 7, “Definition of Field Names”.

3–6

3937 0408–930

Front Office Transactions

Deposits (TRDEP) This screen is used to enter and process financial deposit transactions. The type of deposit transaction is denoted by the transaction code received. The following transactions can be used on this screen: •

100 – Cash Deposit (same currency)

•

108 – Cash Deposit (different currency)

•

110 – Intra Bank Cheque Deposit

•

120 – Domestic Bank Cheque Deposit

•

124 – Foreign Bank Cheque Receipt Prior to Deposit

•

140 – Domestic Bank Cashier’s Cheque Deposit

•

190 – Credit Adjustment

The Cheque Details fields are entered for cheque deposit transactions only. The fields Cheque Bank and Cheque Branch can be left blank for intra bank cheque deposits. If these fields are entered for an intra bank cheque deposit, the Cheque Bank must be ‘RETAIL OWN BANK’ and the Cheque Branch must be the accounting centre of the Cheque Account. Note: For an intra bank cheque deposit, the cheque must have been issued but not presented. (See Section 8 “Account Based Cheques for Retail Banking”, in the Retail Clients and Accounts Guide.) The system validates the transaction and displays any errors, such as maximum balance violated. To override, enter an ‘Override Teller’ with a security level higher than the error. Some overrides may result in the transaction being posted to Error Suspense (see Section 6 “Internal Accounts”, for more information). To contra a deposit, the transaction must first be selected from the Retail Account Statement Inquiry (RASTI) screen. The transaction details are displayed on the Deposits (TRDEP) screen. To contra the deposit, switch the ‘Contra’ field on and enter an ‘Override Teller’. The ‘Override Teller’ can be the ‘Teller’ or must be the same security level or higher than the ‘Teller’. Notes: You cannot contra a transaction that was originally overridden. The Deposits (TRDEP) screen receives data for a deposit that includes a single cheque. Deposits that consist of several cheques are handled by the batch entry functions (see Section 4 “Back Office Transactions”, in the Financial Transactions Reference Guide).

3937 0408–930

3–7

Front Office Transactions

The following figure is an example of the Deposits (TRDEP) screen:

Figure 3–1. Deposits screen

3–8

3937 0408–930

Front Office Transactions

Withdrawals (TRWDR) This screen is used to enter and process withdrawal financial transactions. The type of withdrawal transaction is denoted by the transaction code received. The following transactions can be used on this screen: •

200 – Cash Withdrawal (same currency)

•

208 – Cash Withdrawal (different currency)

•

290 – Debit Adjustment

•

6nnn – Deferred Charges (where nnn is between 001 and 999)

The system validates the transaction and displays any errors, such as insufficient funds. To override, enter an ‘Override Teller’ with a security level higher than the error. Some overrides may result in the transaction being posted to Error Suspense (See Section 6 “Internal Accounts”, for more information). To contra a withdrawal, the transaction must first be selected from the Retail Account Statement Inquiry (RASTI) screen. The details are displayed on the Withdrawal (TRWDR) screen. To contra the withdrawal, switch the ‘Contra’ field on and enter an ‘Override Teller’. The ‘Override Teller’ can be the ‘Teller’ or must be the same security level or higher than the ‘Teller’. Note: You cannot contra a transaction that was originally overridden.

3937 0408–930

3–9

Front Office Transactions

The following figure is an example of the Withdrawals (TRWDR) screen:

Figure 3–2. Withdrawals screen

3–10

3937 0408–930

Front Office Transactions

Transfers and Bill Payments (TRTFR) This screen is used to enter and process transfers and bill payment financial transactions. The type of transfer or bill payment transaction is denoted by the transaction code received. The following transactions can be used on this screen: •

125/225 – Foreign Bank Cheque (same currency) Deposit and Withdrawal

•

127/227 – Foreign Bank Cheque (different currency) Deposit and Withdrawal

•

160/260 – Intra Bank Account Transfer Credit (same currency) and Debit

•

161/261 – Intra Bank Account Transfer Credit (different currency) and Debit

•

191 – Return Debit Reject to Domestic Clearing

•

291 – Return Credit Reject to Domestic Clearing

•

300 – Bill Payment by Cash to “Own Bank” Utility’s Client Account

•

310 – Bill Payment by Cash to Credit Outward Suspense (Domestic) Stage 1

•

320 – Bill Payment by Cash to Credit Outward Suspense (Foreign) Stage 1

•

331 – Bill Payment Credit to “Own Bank” Utility’s Client Account from Client Account

•

340 – Bill Payment Debit from Client Account to Domestic Client Account

•

350 – Bill Payment Debit from Client Account to Foreign Bank Account

Note: A foreign bank cheque is first deposited into an internal account using a 124 (Foreign Bank Cheque Receipt Prior to Deposit) transaction via the Deposit (TRDEP) screen. The transaction codes entered in the ‘From Transaction Code’ and ‘To Transaction Code’ fields must be a valid combination. The following table gives a list of the other fields that are mandatory for specific transactions. Table 3–1. Transfers and Bill Payments screen - Mandatory Fields Value of ‘From Transaction Code’

Value of ‘To Transaction Code’

Mandatory Fields

225

125

227

225

260

160

261

161

191

000

From Account Number, Amount, From Currency, Receiving Bank, Receiving Branch, Receiving Account Number

000

300

Amount, To Account Number, To Currency

000

310

Amount, To Account Number, To Currency, Bill Reference, Receiving Bank, Receiving Branch, Receiving Account Number

291

320

3937 0408–930

From Account Number, Amount, From Currency, To Account Number

3–11

Front Office Transactions

Value of ‘From Transaction Code’

Value of ‘To Transaction Code’

Mandatory Fields

nnn

331

From Account Number, Amount, From Currency, To Account Number, To Currency

340

000

From Account Number, Amount, From Currency, Bill Reference, Receiving Bank, Receiving Branch, Receiving Account Number

350

000

From Account Number, Amount, From Currency, Nostro, Bill Reference, Receiving Bank, Receiving Branch, Receiving Account Number

Notes: nnn must be defined by the user as a transaction on Transaction Definition (TRDFM) screen to be used on Transfers and Bill Payments (TRTFR) screen to debit the client account. Transactions, for which the ‘Receiving Bank Identifier’, ‘Receiving Branch’ and ‘Receiving Account’ fields are mandatory, have this information concatenated with the ‘Payment Reference’ or ‘Beneficiary Reference’. This information is then inserted in the Narrative field for sending when the transfer is made. Therefore the ‘Narrative’ field must not be used for these transactions, because it is used by the system. The system validates the transaction and displays any errors, such as insufficient funds. To override, enter an ‘Override Teller’ with a security level higher than the error. Some overrides may result in the transaction being posted to Error Suspense (see Section 6 “Internal Accounts”). To contra a transfer or bill payment transaction, the transaction must first be selected from the Retail Account Statement Inquiry (RASTI) screen. The transaction details are displayed on the Transfers and Bill Payments (TRTFR) screen. To contra the transaction, switch the ‘Contra’ field on and enter an ‘Override Teller’. The ‘Override Teller’ can be the ‘Teller’ or must be the same security level or higher than the ‘Teller’. Note: You cannot contra a transaction that was originally overridden.

3–12

3937 0408–930

Front Office Transactions

The following figure is an example of the Transfers and Bill Payments (TRTFR) screen:

Figure 3–3. Transfers and Bill Payments screen

3937 0408–930

3–13

Front Office Transactions

Cheque Negotiation (TRCNG) This screen is used to enter and process cheque negotiation transactions, that is the buying of a cheque from a client. These transactions have immediate clearance. The type of negotiation is denoted by the transaction code received. The following transactions can be used on this screen: •

400 – Intra Bank Debit (payer) when cash paid out

•

402 – Intra Bank Debit (payer) when account credited

•

440 – Travellers Cheque Credit when cash paid out

•

442 – Travellers Cheque Debit (payer) when account credited

•

450 – Intra Bank Cashier’s Cheque Debit when cash paid out

•

452 – Intra Bank Cashier’s Cheque Debit (payer) when account credited

If a negotiated cheque is drawn on an account held at your own bank, the system validates that the cheque has been issued to the cheque account but has not already been presented nor has it been stopped. The funds are then given to the client presenting the cheque either as cash or by crediting an account held at the bank immediately. For an intra bank cashiers cheque, the system ensures that the cheque has been sold and debits the cashiers cheque sales (CCSALE) internal account of the accounting centre with the total amount of the cheque. For travellers cheques, the system debits the travellers cheque negotiation (TCNEGO) internal account of the accounting centre with the total amount of the cheque. The internal account to be used is determined by the accounting centre, currency and function on the Accounting Centre Account (BRACA) screen. Note: If a client is paid the value of a cheque in cash, no entry should be received for the ‘To Account’ field. The system validates the transaction and displays any errors, such as insufficient funds. To override, enter an ‘Override Teller’ with a security level higher than the error. Some overrides may result in the transaction being posted to Error Suspense (see Section 6 “Internal Accounts”, for more information). To contra a cheque negotiation transaction, the transaction must first be selected from the Retail Account Statement Inquiry (RASTI) screen. The details are displayed on the Cheque Negotiation (TRCNG) screen. To contra the transaction, switch the ‘Contra’ field on and enter an ‘Override Teller’. The ‘Override Teller’ can be the ‘Teller’ or must be the same security level or higher than the ‘Teller’. Note: You cannot contra a transaction that was originally overridden.

3–14

3937 0408–930

Front Office Transactions

The following figure is an example of the Cheque Negotiation (TRCNG) screen:

Figure 3–4. Cheque Negotiation screen

3937 0408–930

3–15

Front Office Transactions

Cheque Sales (TRCSS) This screen is used to record sales of travellers and cashier’s cheques to a client. A cheque sale can be settled with cash or from an account. The type of cheque sale is denoted by the transaction code received. The following transactions can be used on this screen: •

600 – Travellers Cheques paid for by Cash

•

610 – Travellers Cheques paid for from Account (same currency) Credit

•

611 – Travellers Cheques paid for from Account (different currency) Credit

•

620 – Cashier’s Cheque paid for by Cash

•

630 – Cashier’s Cheque paid for from Account (same currency) Credit

•

631 – Cashier’s Cheque paid for from Account (different currency) Credit

As a result of a cheque sale transaction, the system credits the travellers cheque sales internal account of the accounting centre or the cashier’s cheque sales internal account of the accounting centre with the total amount of the sale. The account is determined by a combination of accounting centre, currency and function defined on the Accounting Centre Account (BRACA) screen. The function is either TCSALE for travellers cheques or CCSALE for cashiers cheques. Note: The teller must have been allocated travellers cheques in the vault using the Vault Movement (VIMVM) screen. Once the travellers cheque has been sold it can be issued to the client using the Travellers Cheque Issue Details (CKITM) screen that records the issue in the vault automatically. (See Section 3 “Vault Management”, in the Core Retail Functions and Inquiries Guide for details.) The system validates the transaction and displays any errors, such as insufficient funds. To override, enter an ‘Override Teller’ with a security level higher than the error. Some overrides may result in the transaction being posted to Error Suspense (see Section 6 “Internal Accounts” for more information). To contra a cheque sale transaction, the transaction must first be selected from the Retail Account Statement Inquiry (RASTI) screen. The details are displayed on the Cheque Sales (TRCSS) screen. To contra the transaction, set the ‘Contra’ field to Y and enter an ‘Override Teller’. The ‘Override Teller’ can be the ‘Teller’ or must be the same security level or higher than the ‘Teller’. Note: You cannot contra a transaction that was originally overridden.

3–16

3937 0408–930

Front Office Transactions

The following figure is an example of the Cheque Sales (TRCSS) screen:

Figure 3–5. Cheque Sales screen

3937 0408–930

3–17

Front Office Transactions

Retail Delivery System Screens This section provides a description of the following interface screens: •

Deposits (TTDEP)

•

Withdrawals (TTWDR)

•

Loan Drawdowns (TTLDD)

•

Transfers (TTTFR)

•

Cheque Negotiation (TTCNG)

•

Bureau de Change Movements (TTBDC)

•

Cheque Sales (TTCSS)

•

Balance Inquiry / Passbook Update (TTBPU)

For each interface screen the following is provided: •

A description of its use

•

An example of the interface screen

•

A list of the mandatory fields to be supplied by the RDS to Urbis

A full description of the fields on the interface screens, and valid entries, is given in Section 7, “Definition of Field Names”.

3–18

3937 0408–930

Front Office Transactions

Deposits Interface (TTDEP) This interface screen captures deposit transaction data from the RDS. The type of deposit transaction is denoted by the transaction code received. Transaction codes are documented in Appendix A “Transaction Types” and a list of valid transaction codes for this interface screen is given in Section 7 “Definition of Field Names”. Note: The Deposits Interface (TTDEP) screen has been designed to receive data for a commercial deposit that includes a single cheque. Deposits that consist of several cheques are handled by the batch entry functions; see Section 4 “Back Office Transactions” for details. If a teller has made a mistake in entering a deposit transaction, the RDS should be used to send contra details to the Withdrawals Interface (TTWDR) screen, see “Withdrawal Transactions”. The RDS can use the Deposits Interface (TTDEP) screen to contra an erroneous withdrawal transaction. To do this the RDS must send details of the contra transaction and set the ‘Contra’ indicator to ‘Y’. Urbis processes a contra withdrawal as a credit transaction. The following figure shows an example of the Deposits Interface (TTDEP) screen.

Figure 3–6. Deposits Interface screen The Deposits Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Transaction Code, Force Posting, Transaction Time, Account Number, Accounting Centre, Deposit Amount, Deposit Currency, Value Date, Contra Indicator, Passbook Available, Verified Note: ‘Nostro’ is mandatory for a transaction with a code of 113 or 115, or a contra transaction with a code of 241. For all other codes ‘Nostro’ must not be received. The Cheque Details fields are mandatory for a transaction with a code of 110, 111, 120, 121, 124, 140, 182 or 183.

3937 0408–930

3–19

Front Office Transactions

Loan Drawdown (TTLDD) This screen is an interface screen between the system and the RDS. The main functionality of the interface screen is to pass financial transactions to the Transaction module and carry out the necessary validation. The screen allows transfers from a loan account to up to four client accounts and one internal account. These accounts must be in the same currency. If a fee is specified in the drawdown transaction, the fee will be debited to the fee account specified on the Loan Drawdown (TTLDD) screen. Alternatively, the fee can be added to the loan fees balance. Internal accounts are used for multiple account transfers with accounts in different currencies or for drawdowns by cash and cheque. Transaction code 262 is the only transaction that is accepted by this screen. Transaction codes are documented in Appendix A “Transaction Types”. The following figure shows an example of the Loan Drawdown (TTLDD) screen.

Figure 3–7. Loan Drawdown screen

3–20

3937 0408–930

Front Office Transactions

Withdrawals Interface (TTWDR) This interface screen captures cash withdrawal transaction data from the RDS. Cash may be withdrawn against a client account via this interface screen. The type of withdrawal transaction is denoted by the transaction code received. Transaction codes are documented in Appendix A “Transaction Types” and a list of valid transaction codes for this interface screen is given in Section 7 “Definition of Field Names”. For cash advances on plastic cards, the account number received must refer to an internal account that is used to hold details for a particular card-processing centre. Information must also be supplied for the card details fields. Details of the transactions against the internal account can then be used for reconciliation. If a teller has made a mistake in entering a withdrawal transaction, the RDS should be used to send contra details to the Deposits Interface (TTDEP) screen. The RDS can use the Withdrawal Interface (TTWDR) screen to contra an erroneous deposit transaction. To do this the RDS must send details of the contra transaction and set the ‘Contra’ indicator to ‘Y’. Urbis processes a contra deposit as a debit transaction. The following figure shows an example of the Withdrawals Interface (TTWDR) screen.

Figure 3–8. Withdrawals Interface screen

3937 0408–930

3–21

Front Office Transactions

The Withdrawals Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Transaction Code, Force Posting, Transaction Time, Account Number, Accounting Centre, Withdrawal Amount, Withdrawal Currency, Value Date, Contra Indicator, Passbook Available, Verified Note: ‘Nostro’ and ‘Cheque Number’ are mandatory for a transaction with a code of 241. ‘Nostro’ is also mandatory for a contra transaction with a code of 113 or 115. For all other transaction codes ‘Nostro’ must not be received. ‘Authority Code’, ‘Card Number’ and ‘Expiry Date’ are mandatory for a transaction with a code of 209.

3–22

3937 0408–930

Front Office Transactions

Transfers Interface (TTTFR) This interface screen captures details of transfer transactions from the RDS. The type of transfer transaction is denoted by the transaction code received. Transaction codes are documented in Appendix A “Transaction Types”. The transaction codes received by the ‘From Transaction Code’ and ‘To Transaction Code’ fields must be a valid combination. A list of valid transaction code combinations for this interface screen is given in Section 7 “Definition of Field Names”. To make a transfer from an account held at your institution to another account, then the following destination account details must be sent by the RDS depending on the location of the account: •

For an intra bank destination account, the ‘To Account’ field must be supplied

•

For a destination account at a domestic bank, the ‘Receiving Account’ field must be supplied

•

For a destination account at a foreign bank, the ‘Beneficiary Reference’ and ‘Nostro’ fields must be supplied

For full details of all the fields that must be supplied for a given transaction, see Table 3-2 below. The following figure shows an example of the Transfers Interface (TTTFR) screen.

Figure 3–9. Transfers Interface screen The Transfers Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Force Posting, Transaction Time, Value Date, Passbook Available, Verified

3937 0408–930

3–23

Front Office Transactions

The following table gives a list of the other fields that are mandatory for specific transactions. Table 3–2. Transfers Interface screen - Mandatory Fields Value of ‘From Transaction Code’

3–24

Value of ‘To Transaction Code’

Mandatory Fields

000

300

From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Pay Reference

000

310

From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Pay Reference Receiving Bank Identifier, Receiving Accounting Centre, Receiving Account Number

000

320

From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Nostro, Beneficiary Reference, Pay Reference

000

370

From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Nostro, Pay Reference

214 or 215

000

From Account Number, From Accounting Centre, From Amount, From Currency, Beneficiary Reference, Receiving Bank Identifier, Receiving Accounting Centre

216 or 218

000

From Account Number, From Accounting Centre, From Amount, From Currency, Receiving Bank Identifier, Receiving Accounting Centre, Receiving Account Number

217 or 219

000

From Account Number, From Accounting Centre, From Amount, From Currency, Nostro, Beneficiary Reference

225

125 or 184

From Account Number, From Accounting Centre, From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Nostro

227

127

From Account Number, From Accounting Centre, From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Nostro

260

160, 165, 178 or 188

From Account Number, From Accounting Centre, From Amount, From Currency, To Account Number, To Accounting Centre, To Currency

261

161

From Account Number, From Accounting Centre, From Amount, From Currency, To Account Number, To Accounting Centre, To Currency

3937 0408–930

Front Office Transactions

Value of ‘From Transaction Code’ 191

Value of ‘To Transaction Code’

Mandatory Fields

000

From Account Number, Amount, From Currency, Receiving Bank, Receiving Branch, Receiving Account Number

330

331

From Account Number, From Accounting Centre, From Amount, From Currency, To Account Number, To Accounting Centre, To Currency, Pay Reference

340

000

From Account Number, From Accounting Centre, From Amount, From Currency, Pay Reference, Receiving Bank Identifier, Receiving Accounting Centre, Receiving Account Number

350

000

From Account Number, From Accounting Centre, From Amount, From Currency, Nostro, Beneficiary Reference, Pay Reference

291

Note: Transactions for which the ‘Receiving Bank Identifier’, ‘Receiving Accounting Centre’ and ‘Receiving Account’ fields are mandatory, have this information concatenated with the ‘Payment Reference’ or ‘Beneficiary Reference’. This information is then inserted in the Narrative field for sending when the transfer is made. Therefore the ‘Narrative’ field must not be used for these transactions, because it is used by the system. For transactions other than those detailed above, the ‘Narrative’ field is for documentary purposes only but it should be used as it provides useful information that can be sent electronically to the payee when a transfer is made.

3937 0408–930

3–25

Front Office Transactions

Cheque Negotiation Interface (TTCNG) This interface screen captures details of a cheque negotiation transaction from the RDS. The type of cheque that is negotiated is denoted by the transaction code; transaction codes are documented in Appendix A “Transaction Types”. On the Cheque Negotiation Interface screen, the ‘Cheque Amount’ received from the RDS must be the face value of the cheque being negotiated. Urbis determines whether any charges are needed and generates the appropriate transactions. The Product Transaction Types (PTTRM) screen is used to specify the transactions that are permitted against a product. Each transaction can be associated with a charge. This means that a charge can be applied automatically if a cheque is presented for negotiation that is not guaranteed. The charge will be levied automatically when a chargeable transaction is passed for an account. If a negotiated cheque is drawn on an account held at your own bank, Urbis checks online: •

The available balance

•

For the existence of any account holds

•

The validity of the cheque number and the cheque card number

An intra bank cheque is recognised by the entry in the ‘bank’ field. If this is equal to the blueprint value BP-OWN-BANK (default value 'RETAIL OWN BANK') then the cheque is an intra bank cheque and is processed as such. For an account held at your own bank, the drawer’s account is debited, whereas all other cheques are debited from the relevant cheque collection internal account of the accounting centre and sent for clearing. The internal account to be used is determined by the accounting centre, currency and function on the Accounting Centre Accounts (BRACA) screen. Where the function is either CCNEGO for cashiers cheque or TCNEGO for travellers cheques. Note: If a client is paid the value of a cheque in cash, no entry should be received for the ‘To Account’ and ‘To Accounting Centre’ fields.

3–26

3937 0408–930

Front Office Transactions

The following figure shows an example of the Cheque Negotiation Interface (TTCNG) screen.

Figure 3–10. Cheque Negotiation Interface screen The Cheque Negotiation Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Transaction Code, Force Posting, Transaction Time, Cheque Account, Cheque Accounting Centre, Cheque Number, Cheque Bank, Guaranteed, Cheque Amount, Cheque Currency, Value Date, Passbook Available, Verified.

3937 0408–930

3–27

Front Office Transactions

Bureau de Change Movements Interface (TTBDC) This interface screen receives information from the RDS and posts summary totals of currency movements. Summary totals by accounting centre will be received for currency movements due to bureau de change transactions. The movement can be inward or outward depending on the transaction code received; transaction codes are documented in Appendix A “Transaction Types” and a list of valid transaction codes for this interface screen is given in Section 7 “Definition of Field Names”. Bureau de change accounts must be available for each combination of accounting centre and currency. The account that is debited or credited by a movement transaction is determined by the combination of accounting centre and currency that is received by the Bureau de Change Movements (TTBDC) interface screen. Internal accounts for bureau de change movements are defined on the Accounting Centre Accounts (BRACA) screen and use the function code ‘BDCMOV’. The following figure shows an example of the Bureau de Change Movements (TTBDC) interface screen.

Figure 3–11. Bureau de Change Movements interface screen The Bureau de Change Movements Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Transaction Code, Force Posting, Transaction Time, Value Date, Accounting Centre, Currency, Amount.

3–28

3937 0408–930

Front Office Transactions

Cheque Sales Interface (TTCSS) This interface screen receives information from the RDS to record sales of travellers and cashier’s cheques in either base or foreign currency. A cheque sale can be settled with cash or from an account. The type of cheque sale is denoted by the transaction code received. Transaction codes are documented in Appendix A “Transaction Types” and a list of valid transaction codes for this interface screen is given in Section 7 “Definition of Field Names”. As a result of a cheque sale transaction, Urbis credits the travellers cheque sales internal account of the accounting centre or the cashier’s cheque sales internal account of the accounting centre with the total amount of the sale. The account is determined by a combination of accounting centre, currency and function defined on the Accounting Centre Accounts (BRACA) screen. The function is either TCSALE or CCSALE. Note: Urbis does not apply charges to cheque sales settled with cash when the ‘Force Posting’ indicator is set to Yes. In this case the charge amount must be posted manually. The Travellers Cheque Issue Details (CKITM) screen (see the Retail Clients and Accounts Administration Guide) is used to control the stock of travellers cheques in the bank’s vault. The Cheque Sales Interface (TTCSS) screen receives data from the RDS to record the sale of travellers cheques to customers. The following figure shows an example of the Cheque Sales Interface (TTCSS) screen.

Figure 3–12. Cheque Sales Interface screen The Cheque Sales Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Transaction Code, Force Posting, Transaction Time, Total Value, Cheque Currency, From Currency, Value Date, Passbook Available, Verified.

3937 0408–930

3–29

Front Office Transactions

Balance Inquiry / Passbook Update Interface (TTBPU) This interface screen receives data from the RDS that can cause one of two functions to be performed: •

Triggering of the supply of the current available balance to the RDS (the available balance includes only those transactions that have come to value)

•

Updating of a passbook

Normally, if a passbook update is requested, then only details that have not been printed previously will be returned to the RDS. However, if a ‘From Date’ is received from the RDS, all successful transactions on or from that date will be returned to the RDS for printing. If a ‘From Time’ is received in addition to a date, then all successful transactions from that date and time will be returned. Passbook details cannot be printed if an account hold indicator indicates that the passbook is lost or missing. The following figure shows an example of the Balance Inquiry / Passbook Update (TTBPU) interface screen.

Figure 3–13. Balance Inquiry / Passbook Update interface screen The Balance Inquiry / Passbook Update Interface screen must always receive data for the following fields: Input Date, Teller, Teller Sequence, Force Posting, Transaction Time, Action (B/P), Account Number. Note: The Transaction Code and Override Teller fields on this interface screen are not utilised in any circumstances. They are present so that all the Front Office Transaction interface screens have a standard appearance.

3–30

3937 0408–930

Section 4 Back Office Transactions Introduction Back office transactions are raised by the bulk entry of deposits and as a batch. For example, the end of day takings for a shop can be entered as a batch. There are three stages to entering a batch of transactions: 1.

Open a batch on the Retail Batch Opening (RBTHD) screen

2.

Enter batch details on the Batch Transaction Details (RBTDE) screen

3.

Close the batch on the Retail Batch Closure (RBTCL) screen

You must use the batch screens in the order given above. However, you can revisit the Batch Transaction Details (RBTDE) screen to add or delete transaction details before a batch is closed. Transactions entered on the Batch Transaction Details (RBTDE) screen must be for deposits and withdrawals of a single currency only. Therefore cross currency transactions must be manually converted to the batch currency before they are entered. You can delete a batch that has been opened and contains a number of entries by deleting the batch header. Batches are process by the RAPOSTUPD – Retail Batch Posting Update report (see the Retail On-Demand Reports Guide). When deposit and withdrawal transactions are received from the RDS via the Deposits (TTDEP) and Withdrawals (TTWDR) interface screens, the RDS assigns a ‘Teller Sequence’ number to it to maintain an audit trail. When you enter transactions via the Retail Transaction Direct Entry Screens, Urbis allocates a ‘Teller Sequence’ number to each transaction. This number combined with the input date and teller’s usercode identifies a transaction uniquely. When you enter batched transactions, Urbis allocates a ‘Teller Sequence’ number to each transaction. A batch is associated with a system generated user called ‘SYSTEM’ for audit purposes. Therefore, it is the combination of the ‘SYSTEM’ usercode, ‘Teller Sequence’ number and input date that identifies a transaction uniquely. Note: The transactions you enter via the batch processing screens either credit or debit client accounts only. You cannot make postings to general ledger accounts. For this you must use the batch processing screens described in ‘Entering Batch Postings’ in the General Ledger Administration Guide.

3937 0408–930

4–1

Back Office Transactions

This section provides a description of the following transaction screens: •

Retail Batch Opening (RBTHD)

•

Batch Transaction Details (RBTDE)

•

Retail Batch Closure (RBTCL)

For each screen the following is provided: •

A description of its use

•

An example of the screen

A full description of the fields on the screens, and valid entries, is given in Section 7, “Definition of Field Names”. Please refer to the Starter's Guide to Retail for a description of how to access and use screens and use the client identification and selection facilities.

4–2

3937 0408–930

Back Office Transactions

Retail Batch Opening (RBTHD) Use this screen to open a batch for entry of bulk deposit and withdrawal transactions. The transaction code you enter with each batch entry determines whether the entry is a deposit (credit) or withdrawal (debit). A batch can contain entries of a single currency only. When you have completed the Retail Batch Opening (RBTHD) screen successfully, the system presents the Batch Transaction Details (RBTDE) screen automatically. A batch number is allocated by the system automatically and is displayed on this screen. It is important to make a note of this number in case you need to revisit the batch at a later date. If you completed the optional ‘Account’, ‘Value Date’ and ‘Debit/Credit’ fields on the Retail Batch Opening (RBTHD) screen, the values are transferred to all the lines on the Batch Transaction Details (RBTDE) screen. You cannot overwrite these pre-filled values, and whichever setting you chose for the ‘Debit/Credit’ restricts the batch to containing either debit (withdrawal) or credit (deposit) entries. If you select the 'Both' option, you will be allowed to enter both debit and credit entries in the same batch. Note: If you enter either the ‘Account’ or the ‘Value Date’ field, you must also complete the ‘Debit/Credit'’ field. Otherwise the ‘Debit/Credit' field is optional. If a batch has been closed as unreconciled, then no postings have been made. The batch can be reopened using the Retail Batch Opening (RBTHD) screen. In this case, you must enter the batch number to identify the batch that is to be opened and click the Change button. You cannot reopen batches that have been closed as reconciled, since they will have been processed and postings made using the batch details. Notes: A user can enter batches for their own accounting centre from a terminal at any other accounting centre, in addition to their own. A batch is automatically closed as unreconciled if the terminal is logged off while the batch is still open. A batch can only be deleted if it is open and unreconciled. If the batch header is deleted all the associated transaction details are also deleted. Each user may have one batch only open at any one time.

3937 0408–930

4–3

Back Office Transactions

The following figure shows an example of the Retail Batch Opening (RBTHD) screen.

Figure 4–1. Retail Batch Opening screen

4–4

3937 0408–930

Back Office Transactions

Batch Transaction Details (RBTDE) Use this screen to enter bulk debits and credits to client accounts. Entries must be contained within a batch. A batch is opened on the Retail Batch Opening (RBTHD) screen. The entries you make on the Batch Transaction Details (RBTDE) screen are not posted until the batch is reconciled and closed. Batches are reconciled and closed using the Retail Batch Closure (RBTCL) screen. The Batch Transaction Details (RBTDE) screen can be reached via the Retail Batch Opening (RBTHD) screen only. This is true whether you want to add or delete entries in a batch. Note: You cannot change an individual entry by simply overtyping it. However, you can delete an entry and then add a corrected entry. If there are not enough lines on the screen to accommodate your input, use the scrolling facility: To do this, complete all the available lines and click OK. Transactions entered on the Batch Transaction Details (RBTDE) screen must be for deposits and withdrawals of a single currency only. Therefore cross currency transactions must be manually converted to the batch currency before they are entered. If one of your transaction details lines contains a deposit of a single cheque, you can enter the cheque details. If more than one cheque is deposited as a single transaction, you cannot enter the cheque details. Note: Each Intrabank Cheque Deposit (transaction code 110) must be entered on a separate details line and the cheque details must be entered. The system validates transactions entered on the Batch Transaction Details (RBTDE) screen in the same way as if they were received by the Deposits Interface (TTDEP) or Withdrawals Interface (TTWDR) screens. Note: No fields can be amended individually, but details lines can be deleted and new details lines can be added.

3937 0408–930

4–5

Back Office Transactions

The following figure shows an example of the Batch Transaction Details (RBTDE) screen.

Figure 4–2. Batch Transaction Details screen

4–6

3937 0408–930

Back Office Transactions

Retail Batch Closure (RBTCL) Use this screen to close a batch and post the entries it contains. When you reach this screen, you should enter values for the fields by adding up the entries from your input forms manually. If your entries match the values calculated by the system you can close the batch as ‘Reconciled’. Otherwise you can still close the batch but as it is unreconciled, the system will not post the entries. Unreconciled batches that have been closed can be reopened, amended and reconciled at a later date using the Retail Batch Opening (RBTHD) screen. The following figure shows an example of the Retail Batch Closure (RBTCL) screen.

Figure 4–3. Retail Batch Closure screen

3937 0408–930

4–7

Back Office Transactions

4–8

3937 0408–930

Section 5 Charges Introduction The system provides the ability to charge a client for certain activities during the life of an account, as follows: •

on processing a transaction, for example, cheque withdrawal; known as an Item Charge within the system

•

on processing an event, for example, closing an account; also known as an Item Charge within the system

•

on the turnover of an account; known as a Turnover Charge within the system

•

on a periodic basis, for example, for the maintenance of the account; known as a Periodic Charge within the system.

The product states what kind of charging is to be made (item, turnover or both) and the level (low, normal or high) on an account. Note: For an immediate charge or on settlement of deferred charges, when no funds are available and only credit balance is allowed, the charge is posted to error suspense account. To set up products, transactions and charges, see the Retail Clients and Accounts Administration Guide. To set up loan products, see the Retail Lending Administration Guide.

3937 0408–930

5–1

Charges

Item Charge These are charges on a transaction or an event. Transaction: An item charge on a transaction occurs if a charge is attached to the transaction defined for the product. It will be charged using a 5xxx code where xxx is the original transaction. The 5xxx transaction must be set up on the Product Transaction Types (PTTRM) screen as well as the xxx transaction for which the charge is being made. The amount to be charged is calculated using the transaction amount and the charge code attached to the xxx transaction. Event: An event charge is either charged automatically on an event (see Table 5-1) or entered manually via the Deferred Charges Entry (RDCHE) screen. Event charges are in the 6000 range. The transaction must be set up on the Product Transaction Types (PTTRM) screen against a product for the charge to be made. See ‘Event Based Charges’ for details on entering a manual charge and the automatically charged events. Item charges may be charged immediately or deferred. Deferred charges are accrued using the 801 transaction and can be seen on the Retail Account Inquiry 3 (RAC3I) screen as ‘Outstanding Charges’. Deferred charges are settled to the account on the next Charges Settlement date using the 810 transaction. Note: Manual event charges must be defined on the Retail Transaction Definition (TRDFM) screen.

Turnover Charge This is a charge based upon the turnover of the account. To charge for the turnover of an account: •

Attach transactions 6600 (for credit turnover) and 6610 (for debit turnover) to the product on the Product Transaction Maintenance (PTTRM) screen

•

Indicate which deposit (100-199) or withdrawal (200-299) transactions are to be charged for by associating a charge code to the transaction definition on the Product Transaction Types (PTTRM) screen

Turnover is calculated each day using the credit or debit balance and the charge table indicated by the 6600 or 6610 transaction. The accrued amount can be seen on the Retail Account Inquiry 3 (RAC3I) screen as ‘Outstanding Turnover Charges’. On the Charges Settlement Frequency, the charge is settled to the account using the 6600 and 6610 transactions.

5–2

3937 0408–930

Charges

Periodic Charge These are charges made on a periodic basis, for example, maintenance charge. A periodic charge is made if a 6620 transaction is associated to the product on the Product Transaction Types (PTTRM) screen. This charge is calculated, using the value balance and the charge table indicated by the 6620 transaction, and charged to the account on the Periodic Charges Frequency.

Event Based Charges Manual Event Based Charge If an event occurs for a charge which is not automatically created, the user can enter a charge on the Deferred Charges Entry (RDCHE) screen. To process a manual charge the following is required: •

Set up charge on the Retail Transaction Definition (TRDFM) screen

•

Set up charge transaction (6xxx) on the Product Transaction Types (PTTRM) screen as deferred

•

Posted manually through the Deferred Charges Entry (RDCHE) screen as an amount. This must be checked to make sure it is within the minimum and maximum amounts on the Retail Charge Conditions (PTCHM) screen

The manual charge is accrued using the 801 transaction, displayed as ‘Outstanding Charges’ on the Retail Account Inquiry 3 (RAC3I) screen. The charge is settled, with all other deferred charges (5xxx and 6xxx including turnover charges), using the 811 transaction on the Charges Settlement Frequency.

3937 0408–930

5–3

Charges

Automatic Event Based Charge The following table lists the automatic charges available in the system: Note: Fees can be automatically charged for Arrears Events. A transaction must be defined on the Retail Transaction Definition (TRDFM) screen in the range 6000-6999. These transactions may then be associated to a loan product on the Product Transaction Types (PTTRM) screen as deferred with a charge code. On processing of the Arrears Event against an Arrears Case, the fee will be automatically posted to the loan account. Table 5–1. Automatic Charges Transaction Code

Charge for

How set-up?

How trigger / calculate charge?

How accrue deferred charge?

How settle charge?

6010

Close Account

On the Product Transaction Types (PTTRM) screen.

On the Close Client Account (RACLS) screen using charge appropriate to the closing balance (including other outstanding charges and interest) on charge code record indicated by 6010 transaction.

N/A

Using 6010 transaction on account closure.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

Note: Charge can be tiered and can be amount or rate.

Shown on the Close Client Account (RACLS) screen as closing charges.

6020

Standing Order Mandate

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

5–4

On ADD of record on the Retail Standing Orders Input (SOINP) screen using FLAT charge amount on charge code record indicated by 6020 transaction.

For immediate, using 6020.

3937 0408–930

Charges

Transaction Code

Charge for

How set-up?

How trigger / calculate charge?

How accrue deferred charge?

How settle charge?

6030

Change Standing Order Mandate

On the Product Transaction Types (PTTRM) screen as deferred or immediate.

On CHG of record on the Retail Standing Orders Input (SOINP) screen using FLAT charge amount on charge code record indicated by 6030 transaction.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

On OK with no changes on the Retail Account Statement Request (RASTR) screen using FLAT charge amount on charge code record indicated by 6080 transaction.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

On OK with statement number to be reprinted entered on the Retail Account Statement Request (RASTR) screen using FLAT charge amount on charge code record indicated by 6090 transaction.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

On stopping cheque(s) on the Stop Cheque Payment (CKSCA) screen using FLAT charge amount on charge code record indicated by 6120 transaction.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

On the Close Client Account (RACLS) screen, using ‘ t l ’i t t

N/A

Using 6190 transaction on account closure.

Note: Charge can only be a flat amount.

6080

Request Statement

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

6090

Reprint Statement (Original not received)

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

6120

Stop Cheque

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

6190

3937 0408–930

Account Closure - charges or penalty interest

On the Product Transaction Types (PTTRM) screen with ‘N Ch ’ h

For immediate, using 6030.

For immediate, using 6080.

For immediate, using 6090.

For immediate, using 6120.

5–5

Charges

Transaction Code

Charge for

How set-up?

How trigger / calculate charge?

How accrue deferred charge?

How settle charge?

a ‘No Charge’ charge.

‘account closure’ interest rate for settlement period and balances on the Product Interest Types (PTICM) screen. Shown as Closing Penalty Interest Charge.

During overnight process by the RTEXTRACT – Retail Transaction Extraction report, if an intra bank cheque is returned.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

During overnight process by the RTEXTRACT – Retail Transaction Extraction report, if an intra bank cheque is returned.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

During overnight process by the RTBATCHUPD – Batch Update report, if a domestic cheque is returned.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency.

Note: Even if transaction is not set-up, transaction is generated if interest rate setup on the Product Interest Types (PTICM) screen and ‘Interest Condition at Closure’ set to ‘Special Rate’ on the Product Maintenance Screen 1 (PTA1M). 6350

Intra Accounting Centre Beneficiary Returned Cheque

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

6360

Intra Accounting Centre Payer Returned Cheque

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

6370

Domestic Beneficiary Returned Cheque

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a

5–6

For immediate, using 6350.

For immediate, using 6360.

3937 0408–930

Charges

Transaction Code

Charge for

How set-up?

How trigger / calculate charge?

flat amount. 6380

Domestic Payer Returned Cheque

On the Product Transaction Types (PTTRM) screen as deferred or immediate. Note: Charge can only be a flat amount.

3937 0408–930

During overnight process by RTBATCHUPD – Batch Update report, if a domestic cheque is returned.

How accrue deferred charge?

How settle charge?

screen.

For immediate, using 6370.

For deferred, using 801, shown as outstanding charge on the Retail Account Inquiry 3 (RAC3I) screen.

For deferred, using 811 with other ‘deferred’ charges on Charges Settlement Frequency. For immediate, using 6380.

5–7

Charges

5–8

3937 0408–930

Section 6 Internal Accounts Introduction Internal accounts are debited or credited as a result of the following transactions: •

Bureau de Change movements Used by the Bureau de Change Movements (TTBDC) interface screen to indicate the internal account to be credited for inward movements and debited for outward movements

•

Cashier’s cheque negotiation Used by the Cheque Negotiation (TRCNG) and Cheque Negotiation Interface (TTCNG) screens to indicate the internal account to debit when negotiating a cashier’s cheque

•

Cashier’s cheque sales Used by the Cheque Sales (TRCSS) and Cheque Sales Interface (TTCSS) screens to indicate the internal account to credit when selling a cashier’s cheque

•

Travellers cheque negotiation Used by the Cheque Negotiation (TRCNG) and Cheque Negotiation Interface (TTCNG) screens to indicate the internal account to debit when negotiating a travellers cheque

•

Travellers cheque sales Used by the Cheque Sales (TRCSS) and Cheque Sales Interface (TTCSS) screens to indicate the internal account to credit when selling a travellers cheque or a block of travellers cheques

•

Foreign currency cheques for collection Used by the Deposits (TRDEP) and Deposits Interface (TTDEP) screens to indicate the internal account to post to when a foreign currency cheque is deposited

•

Payment orders for cash collection Used when a payment order is for collection by a non-account holder. Payment orders of this type can be entered on the Batch Transaction Details (RBTDE) screen.

Error suspense accounts should be identified for every accounting centre. An error suspense account is used when a forced transaction forces an account into overdraft that is not permitted to have a debit balance. In addition, error suspense accounts are used when the system cannot locate the account that should receive a posting as a result of a transaction or if an account is not specified in the correct currency or the account has been blocked. The product for internal accounts to be used as error suspense accounts must include all transaction on the Product Transaction Types (PTTRM) screen. Note: Internal accounts may be created if you have processing requirements over and above those supplied by the system.

3937 0408–930

6–1

Internal Accounts

This section provides a description of the Accounting Centre Accounts (BRACA) screen: For this screen the following is provided: •

A description of its use

•

An example of the screen

A full description of the fields on the screens, and valid entries, is given in Section 7, “Definition of Field Names”. Please refer to the Starter's Guide to Retail for a description of how to access and use screens and use the client identification and selection facilities.

Create Internal Accounts Internal accounts are opened in the same way as a client account (see the Retail Clients and Accounts Administration Guide). However, the product template upon which the account is based must belong to the ‘Internal’ product category and the client required must be an ‘internal’ client type. An internal product template should be defined as follows: •

A product is required for each internal account use and then copied for each required currency

•

No interest or charges, are required

•

No special processing is required, for example no cards, no cheques, no joint account holders.

•

The clients allowed must be of type ‘Internal’

•

The transactions allowed should reflect the use of the internal account.

Once the product is made live, an account can be opened using the internal client set up.

6–2

3937 0408–930

Internal Accounts

Accounting Centre Accounts (BRACA) Once an internal account has been opened, it has to be associated with a function so that it can be used during relevant processing. The Accounting Centre Accounts (BRACA) screen is used to indicate which accounts are to be used to receive postings as a result of particular transactions within an accounting centre that are postings that affect the institution’s accounts (internal accounts rather than client accounts). For example, you can define a particular French Franc account as the collection account for foreign currency cheques (French Franc cheques in this case). Accounting Centre accounts can be allocated to the following functions: BDCMOV - Bureau de Change movements CCNEGO - Cashier’s cheque negotiation CCSALE - Cashier’s cheque sales CHQCOL - Foreign Bank Cheques for collection (same currency) DOMCRO - Domestic standing order ERRSUS - Error suspense FORCHQ - Foreign bank cheques for collection (different currency) FTDSUS - Fixed term deposit suspense PODCSH - Payment orders for cash collection TCNEGO - Travellers cheque negotiation TCSALE - Travellers cheque sales You can associate several accounts with an accounting centre/function combination in a single transaction. With the exception of error suspense accounts, the same account can be allocated to more than one combination of accounting centre and function. You cannot allocate more than one account in a particular currency to the same function. Note: Only accounts with a product category of ‘Internal’ can be used on this screen. The account must be opened for the same accounting centre and currency with which it is associated on the Accounting Centre Accounts (BRACA) screen. If you close an account that is identified as an internal account, any postings that are made subsequently are sent to the relevant error suspense account.

3937 0408–930

6–3

Internal Accounts

The following figure shows an example of the Accounting Centre Accounts (BRACA) screen.

Figure 6–1. Accounting Centre Accounts screen

6–4

3937 0408–930

Section 7 Definition of Field Names Introduction This section provides a definition of all the field names on financial transaction screens. The fields are listed alphabetically and details of valid entries are given. If the field is prefilled with a value on the screen, or defaults to a value if left blank, these values are also given. Many of the codes and mnemonics given in this section may be changed when the system is installed at your bank. Table 7–1. Definition of Field Names

Field

Definition

Account

On the Batch Transaction Details (RBTDE) screen, this is used for the account against which a transaction is applied. On the Accounting Centre Accounts (BRACA) screen, this is the accounting centre account to which transactions associated with the function indicated by the ‘Function Code’ should be posted. One account is entered for each relevant currency. On the Retail Batch Opening (RBTHD) screen, this is the number of an account against which you wish to enter all transactions within a batched entry. This is transferred to all lines on the Batch Transaction Details (RBTDE) screen. This field is used to speed up batch entry when all transactions are against one account. If you make an entry in this field, you must set the ‘Debit or Credit Indicator’ also. On the Deposits Interface (TTDEP) screen, this is the number of the account upon which a cheque included in a deposit is drawn.

Account Currency

On the Deposits (TRDEP) screen, this is the currency in which the ‘Account’ is held to which the deposit is made. On the Withdrawals (TRWDR) screen, this is the currency where the ‘Account’ is held from which the withdrawal is made. Currency mnemonics are set up on the Currencies (CCYS) screen.

3937 0408–930

7–1

Definition of Field Names

Field

Definition

Account Number

On the Deposits Interface (TTDEP) and Deposits (TRDEP) screens, this is the account to which a deposit transaction is to be applied. On the Withdrawals Interface (TTWDR), Withdrawals (TRWDR). and Loan Drawdown (TTLDD) screens, this is the account against which a withdrawal transaction is to be applied. On the Balance Inquiry / Passbook Update (TTBPU) interface screen, this is the account for which a balance or a passbook update is required. An account number is a unique number assigned by the system when you open an account.

Account Number (Cheque Details)

The account number against which the cheque has been raised.

Accounting Centre

The identifier of the Accounting Centre associated with the transaction. It is set up on the Accounting Centres Maintenance (ACNTM) screen. On the Deposits Interface (TTDEP) and Deposits (TRDEP) screens, this is the accounting centre where the ‘Account’ is held to which the deposit is made. On the Withdrawals Interface (TTWDR) and Withdrawal (TRWDR) screens, this is the accounting centre where the ‘Account’ is held from which the withdrawal is made. On the Bureau de Change Movements Interface (TTBDC) screen, this is the teller’s accounting centre. Together with the currency, the accounting centre identifies the account against which the posting is made. On the Retail Batch Opening (RBTHD) and the Retail Batch Closure (RBTCL) screens, this is the accounting centre of the account that appears by default when the Retail Batch Details (RBTDE) screen is displayed. This is used to speed up data entry on the details screen. On the Retail Batch Details (RBTDE) screen, each detail line contains two accounting centre entry fields. The first is for the accounting centre of the account against which the individual transaction is to be performed. The second is used for cheque deposits to record the accounting centre of the cheque account. On the Accounting Centre Accounts (BRACA) screen, this is the accounting centre associated with the accounts listed. On the Deposits Interface (TTDEP) screen, this is the name of the accounting centre that issued a cheque included in a deposit.

Action

On the Balance Inquiry / Passbook Update (TTBPU) interface screen, this indicates whether a balance inquiry is being triggered or whether a passbook update is required:

• •

7–2

Balance Inquiry (B) Passbook Update (P)

3937 0408–930

Definition of Field Names

Field

Definition

Add / Delete

On the Batch Transaction Details (RBTDE) screen, this indicates the action you wish to take with the transaction detailed on the adjacent lines:

• • Amount

Add (A) Delete (D)

The amount to be posted in a transfer or bill payment transaction. This amount can be expressed in either the ‘From Currency’ or ‘To Currency’ depending on the transaction code. On the Bureau de Change Movements Interface (TTBDC) screen, this is the amount of currency bought or sold. On the Batch Transaction Details (RBTDE) screen, this is the amount to be debited or credited as a result of a transaction.

Authority Code (Plastic Card Cash Advance Details)

The code given by the issuer of a credit card to prove authorisation for a cash withdrawal against the card.

Bank (Cheque Details)

The name of the bank that issued a cheque included in a deposit.

Batch Number

A unique number automatically assigned to a batch by the system.

Beneficiary Reference

This is a client’s reference number for an item such as a standing order or direct debit. This, together with the bank identifier, accounting centre and account, are sent to the payee’s bank when the transfer is made. The reference is set-up on Payment Beneficiary Details (BENEM) screen.

Note:

Procedures for obtaining authority codes are not provided in Urbis.

This field is relevant to the following transactions only: transaction codes 214, 215, 217, 219, 320 and 350. Bill Reference

This is a client’s reference number for an item such as a standing order or direct debit. This, together with the receiving bank, branch and account, is sent to the payee’s bank when the transfer is made. This field is relevant to the following transactions only: transaction codes 310, 320, 340 and 350.

Branch (Cheque Details)

The name of the branch of the bank that issued a cheque included in a deposit.

Card Number (Plastic Card Cash Advance Details)

The number of a plastic card as it appears on the card.

3937 0408–930

7–3

Definition of Field Names

Field

Definition

Cash Commission

On the Cheque Negotiations screens, this is the commission that the bank will receive for cashing the cheque. On the Cheque Sales screens, this is the commission that the bank will receive for the sale of the cashiers cheque or travellers cheque. On the Bureau de Change Movements Interface (TTBDC) screen, this is the commission that the bank will receive for performing the bureau de change transaction.

Cashiers Cheque Number

The number of the cashiers cheque being sold.

Cheque Account

On the Batch Transaction Details (RBTDE) screen, this is used for cheque deposits to record the cheque account. On the Cheque Negotiations (TRCNG) and Cheque Negotiations Interface (TTCNG) screens, this is the number of an account upon which a cheque is drawn.

Cheque Account Number

The number of an account upon which a cheque is drawn.

Cheque Accounting Centre

The accounting centre where the ‘Cheque Account’ is held upon which a cheque is drawn.

Cheque Amount

On the Cheque Negotiation (TRCNG) and Cheque Negotiation Interface (TTCNG) screens, this is the face value of a cheque that is being drawn against the ‘Cheque Account Number’. On the Cheque Sales (TRCSS) screen, it is the total value of a cheque sale in the ‘Cheque Currency’. If the sale is of a block of cheques, the total value is derived by multiplying the number of cheques by the denomination

Cheque Bank

The clearing bank where the ‘Cheque Account’ is held upon which a cheque is drawn. For an intra bank cheque deposit, this can be left blank but if entered must be equal to the value in the blueprint parameter "BPOWN-BANK".

Cheque Branch

The clearing branch where the ‘Cheque Account’ is held upon which a cheque is drawn. For an intra bank cheque deposit, this must be the accounting centre (ACNTM) where the cheque account is held.

Cheque Card Number

The number of the cheque guarantee card that supports a cheque.

Cheque Currency

On the Cheque Negotiation screens, this is the currency in which the value of a cheque is drawn. For Eurocheques, the system checks the limit set for the currency on the Currencies (CCYS) table before accepting the transaction. On the Cheque Sales screens, this is the mnemonic of the currency of the cheque (or cheques) being sold. Currency mnemonics are set up on the Currencies (CCYS) table.

7–4

3937 0408–930

Definition of Field Names

Field

Definition

Cheque Number

The number of a cheque as it appears on the face of the cheque. This together with the account number and accounting centre identifies it uniquely. On the Deposits (TRDEP) screen, this is the number of the cheque to be deposited.

Cheque Number (Cheque Details)

The number of a cheque included in a deposit.

Contra

This indicates whether a transaction is a contra of an earlier transaction. A contra deposit is processed as a debit transaction. A contra withdrawal is processed as a credit transaction. When using an RDS interface system for front office transactions, a contra deposit is received from the RDS via the Withdrawals Interface (TTWDR) screen and the Loan Drawdown (TTLDD) screen. This is processed as a debit transaction. A contra withdrawal is received from the RDS via the Deposits Interface (TTDEP) screen and is processed as a credit transaction.

Cross Currency Transaction

This indicates whether a transaction involves a foreign currency, for example a Standing Order deposit from a domestic bank (different currency).

• •

Currency

On – Cross currency transaction Off – Single currency transaction

On the Bureau de Change Movements Interface (TTBDC) screen, this is the mnemonic of the currency to be bought or sold. Together with the accounting centre this determines the account against which the posting is made. On the Batch Transaction screens, this denotes the currency of the transactions contained in a batch. On the Accounting Centre Accounts (BRACA) screen, this is the currency of the adjacent account. Currency mnemonics are defined on the Currencies (CCYS) table.

Debit/Credit

This indicates whether you want to enter deposit (credit) or withdrawal (debit) transactions in a batch. Batch entries are restricted to the selection you make.

• • •

Credit (C) Debit (D) Both (Space)

An entry in this field is mandatory if you enter the ‘Account’ and ‘Value Date’.

3937 0408–930

7–5

Definition of Field Names

Field

Definition

Default GL Transaction Account

On the Retail Transaction Definition (TRDFM) screen, this field is used to define the general ledger account that is updated by default when the specified transaction occurs. You can enter:

• • •

A real general ledger account number ‘OC’, to use the Other Currencies account defined using the System Parameters (SPMTR) screen ‘N’, to indicate that this is a Nostro transaction that does not require a general ledger posting

This field can be left blank for inter-accounting centre transactions that do not require general ledger postings. The account defined using this field can be picked up as a default on the Product Transaction Types (PTTRM) screen or set specifically. Denomination

The face value of the cheque (or cheques) being sold.

Deposit Amount

The amount to be posted in a deposit transaction. This amount is expressed in the ‘Deposit Currency.

Deposit Currency

The currency in which the deposit is being made. Deposits can be composed of items of a single currency only and must be in the same currency as the account into which the deposit is being made. If a deposit is in a different currency to the account, then the deposit should be made into the appropriate accounting centre account. An appropriate deposit can then be made into the client’s account using the account’s currency.

Description

A text to describe the financial transaction represented by the ‘Transaction Code’.

End Travellers Cheque

For the sale of a block of travellers cheques, this is the number of the last cheque in the series. The first cheque is specified in the ‘Start Travellers Cheque’ field. For the sale of a single cheque, an entry in this field is not relevant. This field requires the following format: aaaaaa : reference nnnnnn : number of the cheque

Exchange Amount

The system automatically calculates this amount from the Transaction Amount and Rate entered. If the rate is not entered, the system calculates the exchange amount using the rate set-up on the Exchange Rate (EXCHM) screen. If the rate entered is close to 1, then the Exchange Amount should be manually calculated. The system checks the amount before accepting it.

7–6

3937 0408–930

Definition of Field Names

Field

Definition

Exchange Rate Group

The exchange rate group to be used for cross currency transactions. This identifies a table of exchange rates on the Exchange Rates (EXCHM) screen. This field is used only if the ‘Cross Currency Transaction’ field is set to Yes.

Expiry Date (Plastic Card Cash Advance Details)

The month and year that a card is due to expire.

Fees Account

The account to which the fee is to be debited if specified for the drawdown transaction. This is used on the Loan Drawdown (TTLDD) account.

Force Posting

This is used by the RDS to indicate that a transaction was completed during a period when communications to Urbis were unavailable. This is a Yes/No style question:

• •

Yes (Y) No (N)

The indicator is set to No when a connection between the RDS and Urbis is available and the ‘Input Date’ and the online system date match. The indicator is set to Yes to mark a transaction as entered into the RDS earlier than it can be posted to Urbis. Under these circumstances transactions are stored in the RDS until they can be posted to Urbis. When the transactions are posted to Urbis they are ‘force posted’ i.e. they are applied regardless of whether they pass validation. From Account

On the Transfers Interface (TTTFR) screen, this is the account from which a transfer is made. If an entry is received from the RDS, it must be a client account that is defined to the system. If an entry is not received the transfer is of cash or a cheque. On the Cheque Sales Interface (TTCSS) screen, this is the account to be debited to pay for a cheque sale. This relevant only if a cheque sale is paid for out of an account.

From Account Currency

This is the currency of the account to be debited if the sale is paid for out of an account. An entry in this field is not relevant if the sale is paid for with cash. For a cross currency transaction that involves one foreign currency, the system converts the currency of the ‘From Amount’ to the ‘To Currency’. For a cross currency transaction that involves two foreign currencies, the system converts the currency of the ‘From Amount’ to base currency first and then to the ‘To Currency’. The ‘Sell’ rate held on the Exchange Rates (EXCHM) screen is used for a local to foreign currency conversion and the ‘Buy’ rate is used for a foreign to local currency conversion. Currency mnemonics are defined on the Currencies (CCYS) screen.

3937 0408–930

7–7

Definition of Field Names

Field

Definition

From Account Number

On the Transfers and Bill Payments (TRTFR) screen, this is the account from which a transfer is made. On the Cheque Sales (TRCSS) screen, this is the account to be debited to pay for a cheque sale. This is relevant only if a cheque sale is paid for out of an account.

From Accounting Centre

On the Transfers Interface (TTTFR) and Transfers and Bill Payments (TRTFR) screens, this is the identifier of the Accounting Centre from which a transfer is made. It is set up on the Accounting Centres Maintenance (ACNTM) screen. On the Cheque Sales Interface (TTCSS) and Cheque Sales (TRCSS) screens, this is the accounting centre where the account is held that is to be debited to pay for a cheque sale. An entry in this field is not relevant if the sale is to be paid for with cash.

From Amount

The amount to be transferred from the ‘From Account’ to the ‘To Account’.

From Currency

On the Transfers Interface (TTTFR) screen, this is the currency of the amount to be transferred. On the Transfers and Bill Payments (TRTFR) screen, this is the currency of the "From Account". On the Cheque Sales Interface (TTCSS) screen, this is the currency of the account to be debited if the sale is paid for out of an account. An entry in this field is not relevant if the sale is paid for with cash. For a cross currency transaction that involves one foreign currency, the system converts the currency of the ‘From Amount’ to the ‘To Currency’. For a cross currency transaction that involves two foreign currencies, the system converts the currency of the ‘From Amount’ to base currency first and then to the ‘To Currency’. The ‘Sell’ rate held on the Exchange Rates Maintenance (EXCHM) table is used for a local to foreign currency conversion and the ‘Buy’ rate is used for a foreign to local conversion.

7–8

From Date

The date from when the passbook entries are to be supplied for printing. Only transactions on or from that date will be forwarded to the RDS for printing. In addition to a date you can enter a ‘From Time’.

From Time

The time on the ‘From Date’ after when the entries are to be forwarded to the RDS for printing. Only transactions on or from that time will be printed. Time format is HHMM.

3937 0408–930

Definition of Field Names

Field

Definition

From Transaction Code

This is the code that represents the type of transaction that causes a transfer from an account. This is used in conjunction with ‘To Transaction Code’ to define the exact transfer that takes place. Therefore, the entries in these two fields must be a valid combination. On the Transfers and Bill Payments (TRTFR) screen, valid entries are: •

0 - When ‘To Transaction Code’ is 300, 310 or 320

•

191, 291, 340 or 350 - When ‘To Transaction Code’ is 0

•

225 - When ‘To Transaction Code’ is 125

•

227 - When ‘To Transaction Code’ is 127

•

260 - When ‘To Transaction Code’ is 160

•

261 - When ‘To Transaction Code’ is 161

On the Transfers Interface (TTTFR) screen, valid entries are: •

0 - When ‘To Transaction Code’ is 300, 310, 320 or 370

•

214, 215, 216, 217, 218, 219, 291, 340 or 350 - When ‘To Transaction Code’ is 0

•

225 - When ‘To Transaction Code’ is 125 or 184

•

227 - When ‘To Transaction Code’ is 127

•

260 - When ‘To Transaction Code’ is 160, 165, 178 or 188

•

261 - When ‘To Transaction Code’ is 161

•

330 - When ‘To Transaction Code’ is 331

See Appendix A “Transaction Types” for a list of transaction codes by transaction type. Function Code

A code that represents the type of entries posted to an accounting centre account: BDCMOV - Bureau de Change movements CCNEGO - Cashier’s cheque negotiation CCSALE - Cashier’s cheque sales CHQCOL - Cheques for collection FORCHQ - Foreign currency cheques for collection FTDSUS - Fixed term deposit suspense PODCSH - Payment orders for cash collection TCNEGO - Travellers cheque negotiation TCSALE - Travellers cheque sales ERRSUS - Error suspense DOMCRO - Standing order The error suspense account is used when the system cannot locate the account that should receive a posting as a result of a transaction. For example if an account is not specified in the correct currency or the account has been deleted.

3937 0408–930

7–9

Definition of Field Names

Field

Definition

Guaranteed

This indicates whether the full value of a cheque is guaranteed to be paid by the issuer.

• •

Enter Yes in this field if the cheque is guaranteed Enter No in this field if the cheque is not guaranteed

If this field is set to No, charges can be applied automatically. Input Date

The date that a transaction or batch is input. This must be set to the current online processing date unless ‘Force Posting’ is set to Y.

Internal Account

The loan amount is transferred to this internal account number if the same bank holds the loan account and the internal account.

Issue

This field is needed if there is more than one issue of a vault item. It indicates whether an issue of a currency note or travellers cheque is current, in the process of being withdrawn or has already been withdrawn.

• • • Narrative

C - Current W - Being withdrawn O - Out of circulation

This is a documentary field that enables details about a transaction to be recorded. For example, if a client is fulfilling a payment order to an external organisation, you can record the reason for the transfer. In this case, the narrative, can be transferred electronically to the payee when the payment amount is sent. Note: This field must not be utilised for payments, such as bill payments or direct debit payments to foreign banks, because the system uses it to hold details of the payment reference, receiving bank, and receiving account.

Nostro

•

Nostro Required

This indicates whether a nostro should be entered as part of the transaction details on the transaction input screen.

• •

7–10

This is the nostro account that is used for transactions. Most transactions do not require nostro accounts. However when transactions are defined on the Retail Transaction Definition (TRDFM) screen, an indicator may be set specifying that a nostro is required.

On – Nostro required Off – No, nostro not required

Number

The number of a cheque included in a deposit.

Number of Cheques

The total number of cheques sold in a transaction.

3937 0408–930

Definition of Field Names

Field

Definition

Number of Credits

The total number of credit entries that a batch contains. There are two versions of this field on the screen:

Number of Debits

•

Entered Enter the number of credits you believe a batch contains.

•

Calculated The system displays the number of credits entered on the Batch Transaction Details (RBTDE) screen.

The total number of debit entries that a batch contains. There are two versions of this field on the screen:

•

Entered Enter the number of debits you believe a batch contains.

•

Calculated The system displays the number of debits entered on the Batch Transaction Details (RBTDE) screen.

Override Teller

The usercode of a supervisor with sufficient authority to override a validation error or warning. Security levels are allocated to a user on the Users (USERS) screen. Error messages are allocated an override level on the Error Message (EMSGM) screen.

Passbook Available

This indicates whether a passbook is available for printing of transaction details. This is a Yes/No style question, it is answered as follows:

• •

Yes (Y) No (N)

If the indicator is set to Yes, details of unprinted transactions are passed to the RDS when the transaction is complete. The RDS controls printing. Payment Reference

This is a client’s reference number that appears on a bill. This, together with the bank identifier, accounting centre and account, are sent to the payee’s bank when the bill payment is made. This field is relevant to bill payment transactions only (transaction codes 300 to 370).

Rate

If an individually negotiated exchange rate has been used for the transaction, then enter the negotiated rate in this field, and also enter the Rate Type field. This rate is not subject to verification by Urbis. On the front office transaction entry screens, the Rate is used to calculate the Exchange Amount. If the exchange rate is close to 1, the system checks the rate using the blueprint parameters BP-HIXRATE and BP-LO-XRATE, to understand if the rate is a multiply or divide exchange rate type. If the entered rate falls within the rates defined by these blueprints, the Exchange Amount must be manually calculated.

Rate Type

3937 0408–930

This shows whether the exchange rate entered in the "Rate" field is to be multiplied with or divided from the amount of the transaction.

7–11

Definition of Field Names

Field

Definition

Receive Accounting Centre

Enter the accounting centre or branch of the bank receiving the loan amount if the receiving bank is not the same as the bank where the loan account is held.

Receive Accounts

Enter the account number that is to be credited with the loan amount.

Receive Account Number

This is the account at an external bank to which a payment, such as a bill payment, is to be made.

Receive Bank

When a payment, such as a bill payment, is made to an account at another bank, this is the identifier of the bank at which the destination account is held.

Receive Branch

This is the branch at an external bank to which a payment, such as a bill payment, is to be made.

Receive Amounts

Enter the amount that is to be credited to the Receive Account.

Receive Banks

Enter the name of the bank receiving the loan amount if the receiving bank is not the same as the bank where the loan account is held.

Receiving Account

This is the account at an external bank to which a payment, such as a bill payment or a direct debit payment, is to be made.

Receiving Accounting Centre

This is the accounting centre at an external bank to which a payment, such as a bill payment or a direct debit payment, is to be made.

Receiving Bank Identifier

When a payment, such as a bill payment or a direct debit payment, is made to an account at another bank, this is the identifier of the bank at which the destination account is held.

Reconcile Batch

This indicates whether you want to close a batch as reconciled. If a batch is reconciled, the entered totals match the calculated totals. The batch is then processed and postings made. If you want to close the batch without processing or posting, then do not reconcile the batch. This is a Yes/No style question, it is answered as follows:

• •

7–12

On – Reconcile batch Off – Reconciliation not required

Reference

A number assigned by the system to each transaction within a batch. This number is unique.

Start Reference

This field is used for scrolling purposes. You enter the ‘Reference’ number with which you the display to start. This field is relevant only if you are changing the contents of a batch.

3937 0408–930

Definition of Field Names

Field

Definition

Start Travellers Cheque

For the sale of a block of travellers cheques, this is the number of the first cheque in the series. The last cheque is entered in the ‘End Travellers Cheque’ field. For the sale of a single cheque, this is the number of that cheque (no entry in the ‘End Travellers Cheque’ field is required). This field requires the following format: aaaaaa : reference nnnnnn : number of the cheque

Teller

The identifier for the teller that input the transaction. Tellers are identified by their Usercodes. Usercodes are set up on the Users Maintenance (USERS) screen. When combined with the ‘Input Date’, ‘Teller Sequence’ and ‘Transaction Code’, it uniquely identifies the transaction.

Teller Sequence

This is a sequential number allocated to a transaction by the system. The number is unique to the system. When combined with the ‘Input Date’, ‘Teller’ and ‘Transaction Code’, it uniquely identifies the transaction.

To Account

On the Transfers Interface (TTTFR) screen, this is the account to which a transfer is made. On the Cheque Negotiation Interface (TTCNG) screen, this is the account to which the value of a cheque is to be credited. No entry is made in this field if the client is cashing the cheque. This must be an account that is defined to the system. It can be a client or a loan account. For external transfers, it must be the collection account.

To Account Currency

This is the currency of the account that receives a transfer.

To Account Number

On the Transfers and Bill Payments (TRTFR) screen, this is the account to which a transfer is made. On the Cheque Negotiation (TRCNG) screen, this is the account to which the value of a cheque is to be paid.

To Accounting Centre

3937 0408–930

The identifier of the Accounting Centre to which the value of a transaction is paid. It is set up on the Accounting Centres Maintenance (ACNTM) screen.

7–13

Definition of Field Names

Field

Definition

To Currency

On the Transfers and Bill Payments (TRTFR) and Transfers Interface (TTTFR) screens, this is the currency of the account that receives a transfer. On the Cheque Negotiation Interface (TTCNG) screen, this is the currency in which the value of a cheque is to be paid to a client. If the value of the cheque is to be paid into an account, the ‘To Currency’ must match the currency of the ‘To Account’. For a cross currency transaction that involves one foreign currency, the system converts the currency of the ‘From Amount’ to the ‘To Currency’. For a cross currency transaction that involves two foreign currencies, the system converts the currency of the ‘From Amount’ to base currency first and then to the ‘To Currency’. The ‘Sell’ rate held on the Exchange Rates Maintenance (EXCHM) table is used for a local to foreign currency conversion and the ‘Buy’ rate is used for a foreign to local conversion.

To Transaction Code

This is the code that represents the type of transaction that causes a transfer to an account. This is used in conjunction with ‘From Transaction Code’ to define the exact transfer that takes place. Therefore, the entries in these two fields must be a valid combination. On the Transfers (TRTFR) screen the following transactions are valid: •

0 – When ‘From Transaction Code’ is 191, 291, 340 or 350

•

125 – When ‘From Transaction Code’ is 225

•

127 – When ‘From Transaction Code’ is 227

•

160 – When ‘From Transaction Code’ is 260

•

161 – When ‘From Transaction Code’ is 261

•

300, 310 or 320 – When ‘From Transaction Code’ is 0

On the Transfers Interface (TTTFR) screen the following transactions are valid: •

0 - When ‘From Transaction Code’ is 191, 291, 214, 215, 216, 217, 218, 219, 340 or 350

•

125 or 184 - When ‘From Transaction Code’ is 225

•

127 - When ‘From Transaction Code’ is 227

•

160, 165, 178 or 188- When ‘From Transaction Code’ is 260

•

161 - When ‘From Transaction Code’ is 261

•

300, 310, 320 or 370 - When ‘From Transaction Code’ is 0

•

331 - When ‘From Transaction Code’ is 330

See Appendix A “Transaction Types” for a list of transaction codes by transaction type.

7–14

3937 0408–930

Definition of Field Names

Field

Definition

Total Credit Value

The value of credits that a batch contains. There are two versions of this field on the screen:

Total Debit Value

•

Entered Enter the value of credits you believe a batch contains.

•

Calculated The system displays the value of credits entered on the Batch Transaction Details (RBTDE) screen.

The value of debits that a batch contains. There are two versions of this field on the screen:

•

Entered Enter the value of debits you believe a batch contains.

•

Calculated The system displays the value of debits entered on the Batch Transaction Details (RBTDE) screen.

Total Value

The total value of a cheque sale in the ‘Cheque Currency’. If the sale is of a block of cheques, the total value is derived by multiplying the number of cheques by the denomination.

Transaction

A code that represents the type of transaction that is input. The Batch Transaction Details (RBTDE) screen can handle deposit and withdrawal transactions only. See Appendix A “Transaction Types” for a list of transaction codes by transaction type. For a list of the valid transaction codes for deposits and withdrawals see ‘Transaction Code’ field.

3937 0408–930

7–15

Definition of Field Names

Field

Definition

Transaction Code

A code that represents the type of transaction that is input. When combined with the ‘Input Date’, ‘ Teller’ and ‘Teller Sequence’, it uniquely identifies the transaction. All the transaction input screens for the front office can handle a number of related transactions. See Appendix A “Transaction Types” for a list of transaction codes by transaction type. The transaction codes that are valid for each screen are. •

For the Deposits (TRDEP) screen: 100, 108, 110, 120, 140, 190

•

For the Withdrawals (TRWDR) screen: 200, 208, 290 and charges with codes between 6000 and 6999

•

For the Cheque Negotiation (TRCNG) screen: 400, 402, 440, 442, 450, 452

•

For the Cheque Sales (TRCSS) screen: 600, 610, 611, 620, 630, 631

•

For the Deposits Interface (TTDEP) screen: 100, 101, 108, 110, 111, 113, 115, 116, 117, 120, 121, 124, 132, 140, 179, 181, 182, 183, 190, 199, 791, 792, 793 For a contra withdrawal, the withdrawal transaction codes given for the Withdrawals Interface (TTWDR) screen are allowed.

•

For the Withdrawals Interface (TTWDR) screen: 200, 201, 208, 209, 212, 213, 241, 290, 299, 891, 892, 893 and charges with codes between 6000 and 6999 For a contra deposit, the deposit transaction codes given for the Deposits Interface (TTDEP) screen are allowed.

•

For the Cheque Negotiation Interface (TTCNG) screen: 185, 186, 187, 400, 402, 430, 432, 440, 442, 450, 452

•

For the Bureau de Change Movements Interface (TTBDC) screen: 500, 510

•

For the Cheque Sales Interface (TTCSS) screen: 600, 610, 611, 620, 630, 631

•

For the Loan Drawdown (TTLDD) screen, 262 only

The Balance Inquiry / Passbook Update (TTBPU) screen does not utilise the Transaction Code field. Transaction Time

The time that a transaction was entered. Time is in the format HHMMSS. When using the transaction input screen, the transaction time is displayed on entering the screen and is updated when the data is transmitted to the system.

7–16

3937 0408–930

Definition of Field Names

Field

Definition

Valid on Screen

This indicates the financial transaction interface screen on which the transaction code can be used. This can be: TTDEP – Deposits (also valid on TRDEP screen) TTWDR - Withdrawals (also valid on TRWDR screen) TTLDD - Loan Drawdowns TTTFR - Transfers (also valid on TRTFR screen) TTCSS - Cheque Sales (also valid on TRCSS screen) TTCNG - Cheque Negotiation (also valid on TRCNG screen) TTBDC - Bureau de Change

Value Date

The date when the transaction comes to value. This must not be a holiday or a weekend. For back-dated transactions, it must be after the latest settlement date. For deposits, this is normally the transaction processing date plus the number of days for clearing assigned to the deposited item. On the Retail Batch Opening (RBTHD) screen, this is the value date of all entries in a batch of transactions. This date is transferred to the Batch Transaction Details (RBTDE) screen together with your entry in the ‘Account’ field. If you make an entry in this field, you must set the ‘Debit or Credit Indicator’ also.

Vault Item Code

A code of up to six characters used to identify a type of travellers cheque that can be held in the vault. This code is defined on the Vault Item Code Maintenance (VICDM) screen.

Verified

This indicates whether a teller has checked the client’s signature during a transaction. This is a Yes/No style question, it is answered as follows:

• •

Yes (Y) No (N)

Withdrawal Amount

The amount to be posted in a withdrawal transaction. This amount is expressed in the ‘Withdrawal Currency’.

Withdrawal Currency

The currency in which the withdrawal is being made. Withdrawals can be composed of items of a single currency only and must be in the same currency as the account from which the withdrawal is being made. If a withdrawal is in a different currency to the account, then the withdrawal should be made into the appropriate accounting centre account. A withdrawal can then be made from an accounting centre account in the currency required.

3937 0408–930

7–17

Definition of Field Names

7–18

3937 0408–930

Appendix A Transaction Types Introduction The transactions that you can enter into the system are grouped according to one of the following types: •

Deposits

•

Withdrawals

•

Bill payments

•

Cheque negotiations

•

Bureau de Change movements

•

Cheque sales

•

Other liability transaction for loans

•

Other liability transactions for non-loans

•

Other asset transactions for loans

•

Other asset transactions for non-loans

•

Transactions raised from wholesale banking activities

•

Charges

•

Cross Accounting Centre Transactions

Individual transactions are represented to the system by a code. Each transaction type is allocated a numeric series of codes. This section lists transaction codes by type. In addition to the transactions types listed above, this section describes the codes used for automatic event charges. Transaction types and associated codes are defined on the Retail Transaction Definition (TRDFM) screen (see Section 2).

3937 0408–930

A–1

Transaction Types

Transaction Codes The following tables define the codes that the system uses to represent transactions. Note: Throughout the table, ‘same currency’ indicates that the currency of the transaction is the same as the currency of the account against which the transaction is to be actioned, whereas ‘different currency’ indicates that the currencies are different.

Deposits Deposit transactions use the code series 100 to 199.

A–2

Transaction Code

Description

100

Cash Deposit (same currency)

101

Loan Fees Payment by cash

102

Standing Order Deposit from Intra Bank Account (different currency)

103

Standing Order Deposit from Domestic Bank Account (different currency)

104

Standing Order Deposit from Foreign Bank Account (different currency)

105

Standing Order Deposit from Intra Bank Account (same currency)

106

Standing Order Deposit from Domestic Bank Account (same currency)

107

Standing Order Deposit from Foreign Bank Account (same currency)

108

Cross Currency Cash Deposit (different currency)

110

Intra Bank Cheque Deposit

111

Loan Fees Payment by Intra Bank Cheque

112

GIRO / PO Credit to Inward Payment Order Suspense (Domestic)

113

GIRO / PO Credit to Inward Payment Order Suspense (Foreign)

114

GIRO / PO Credit to Client Account from Domestic (GL Nostro)

115

GIRO / PO Credit to Client Account from Foreign (GL Nostro)

120

Domestic Bank Cheque Deposit

121

Loan Fees Payment by Domestic Bank Cheque Deposit

124

Receipt of Foreign Bank Cheque (any currency) Prior to Deposit

125

Foreign Bank Cheque (same currency) Deposit

127

Foreign Bank Cheque (different currency) Deposit

140

Domestic Bank Cashier’s Cheque Deposit

142

Cashiers Cheque Reimbursement Receipt

150

Direct Debit Deposit from Intra Bank Account (different currency)

151

Direct Debit Deposit from Domestic Bank Account (different currency)

152

Direct Debit Deposit from Foreign Bank Account (different currency)

3937 0408–930

Transaction Types

Transaction Code

Description

155

Direct Debit Deposit from Intra Bank Account (same currency)

156

Direct Debit Deposit from Domestic Bank Account (same currency)

157

Direct Debit Deposit from Foreign Bank Account (same currency)

160

Intra bank Account Transfer Credit (same currency)

161

Intra bank Account Transfer Credit (different currency)

162

Loan Drawdown (Credit)

165

Loan Fees Internal Account Transfer Credit Loan Early Closure

171

Cash Deposit

172

Intra Bank Cheque Deposit

173

Domestic Bank Cheque Deposit

174

Foreign Bank Cheque Deposit

178

Intra Account Transfer Credit

179

Loan write off Loan Early Payments

181

Cash Deposit

182

Intra Bank Cheque Deposit

183

Domestic Bank Cheque Deposit

184

Foreign Bank Cheque Deposit

188

Intra Account Transfer Credit

190

Credit Adjustment

191

Return Debit Reject to Domestic Clearing

195

Foreign Institution Nostro Credit (same currency)

196

Foreign Institution Nostro Credit (different currency)

197

Transfer Credit (Between wholesale and retail or vice versa)

198

Charges/Interest Credit (debited from another Account)

199

Deposit Error

Note: Transactions 197/297 are used to transfer the balances from accounts in an interest netting group to the group account for the purpose of reflecting the balance. This enables the netted interest to be calculated.

3937 0408–930

A–3

Transaction Types

Withdrawals Withdrawal transactions use the code series 200 to 299. Note: The code series 5000–6999 is used for charges (see “Charges” later in this section). Charges are treated by the system as withdrawal transactions.

A–4

Transaction Code

Description

200

Cash Withdrawal (same currency)

202

Standing Order payments to other ‘own bank’ account (different currency)

203

Standing Order payments to Domestic bank account (different currency)

204

Standing Order payments to Foreign bank account (different currency)

205

Standing Order payments to other ‘own bank’ account (same currency)

206

Standing Order payments to Domestic bank account (same currency)

207

Standing Order payments to Foreign bank account (same currency)

208

Cross Currency Cash Withdrawal (different currency)

209

Cash Advance against a Plastic Card

210

Intra Bank Cheque Withdrawal

214

GIRO / PO Debit from Domestic Outward Payment Order Suspense account to Cash Collection at Domestic bank

215

GIRO / PO Debit from Client account to Cash Collection at Domestic bank

216

GIRO / PO Debit from Domestic Outward Payment Order Suspense account to Client account at Domestic bank

217

GIRO / PO Debit from Foreign Outward Payment Order Suspense account

218

GIRO / PO Debit from Client account to Domestic (GL Nostro)

219

GIRO / PO Debit from Client account to Foreign (GL Nostro)

220

Domestic Cheque Withdrawal

225

Foreign Bank Cheque Withdrawal (same currency)

227

Foreign Bank Cheque Withdrawal (different currency)

240

Cashier’s Cheque Withdrawal

250

Direct Debit payments to other ‘own bank’ account (different currency)

251

Direct Debit payments to Domestic bank account (different currency)

252

Direct Debit payments to Foreign bank account (different currency)

255

Direct Debit payments to other ‘own bank’ account (same currency)

256

Direct Debit payments to Domestic bank account (same currency)

257

Direct Debit payments to Foreign bank account (same currency)

260

Intra bank Account Transfer Debit (same currency)

261

Intra bank Account Transfer Debit (different currency)

3937 0408–930

Transaction Types

Transaction Code

Description

262

Loan Drawdown (Debit)

270

Cash Withdrawal from ATM

275

EFTPOS Withdrawal

291

Return Credit Reject to Domestic Clearing

295

Foreign Institution Nostro Debit (same currency)

296

Foreign Institution Nostro Debit (different currency)

297

Transfer Debit (Between wholesale and retail or vice versa)

298

Charges/Interest Withdrawal (to credit another Account)

299

Withdrawal Error

Note: Transactions 197/297 are used to transfer the balances from accounts in an interest netting group to the group account for the purpose of reflecting the balance. This enables the netted interest to be calculated.

Bill Payments Bill payment transactions use the code series 300 to 399. Transaction Code

Description

300

Bill Payment by Cash to “Own Bank” Utility’s Client Account

310

Bill Payment by Cash to Credit Outward Suspense (Domestic) Stage 1

311

Bill Payment by Cash to Debit Outward Suspense (Domestic) Stage 2

320

Bill Payment by Cash to Credit Outward Suspense (Foreign) Stage 1

321

Bill Payment by Cash to Debit Outward Suspense (Foreign) Stage 2

331

Bill Payment Credit to “Own Bank” Utility’s Client account from Client Account

340

Bill Payment Debit from Client Account to Domestic Bank account (Nostro)

350

Bill Payment Debit from Client Account to Foreign Bank account (Nostro)

360

Bill Payment from Domestic Clearing to “Own Bank” Utility’s Client Account

370

Bill Payment from Foreign Clearing to “Own Bank” Utility’s Client Account

3937 0408–930

A–5

Transaction Types

Cheque Negotiation Cheque negotiation transactions use the code series 400 to 499. Transaction Code

Description

400

Intra Bank Debit (payer) when cash paid out

401

Intra Bank Credit - whether cash or account credit

402

Intra Bank Debit (payer) when account credited

440

Travellers Cheque Debit (payer) when cash paid out

441

Travellers Cheque Credit to Accounting Centre account

442

Travellers Cheque Debit (payer) when account credited

450

Cashier’s Cheque Debit (payer) when cash paid out

451

Cashier’s Cheque Credit to Accounting Centre account

452

Cashier’s Cheque Debit (payer) when account credited

499

Cheque Negotiation Error

Bureau de Change Movements Bureau de change movement transactions use the code series 500 to 599.

A–6

Transaction Code

Description

500

Inward Movement

510

Outward Movement

599

Bureau de Change Movement Error

3937 0408–930

Transaction Types

Cheque Sales Cheque sale transactions use the code series 600 to 699. Transaction Code

Description

600

Travellers Cheques paid for by Cash

610

Travellers Cheques paid for from Account (local currency) Credit

611

Travellers Cheques paid for from Account (foreign currency) Credit

615

Travellers Cheques paid for from Account (local currency) Debit

616

Travellers Cheques paid for from Account (foreign currency) Debit

620

Cashier’s Cheque paid for by Cash

630

Cashier’s Cheque paid for from Account (local currency) Credit

631

Cashier’s Cheque paid for from Account (foreign currency) Credit

635

Cashier’s Cheque paid for from Account (local currency) Debit

636

Cashier’s Cheque paid for from Account (foreign currency) Debit

699

Cheque Sales Error

3937 0408–930

A–7

Transaction Types

Other Liability Transactions Other liability transactions use the code series 700 to 799.

Other Liability Transactions for Non-Loans Transaction Code

Description

700

Standard Credit Interest Accrual

701

Notional Credit Interest Accrual

710

Interest Settlement Credit

750

Domestic Cheques Come to Value

Other Liability Transactions for Loans Transaction Code

Description Adjustment Credits-Performing Loans

791

Loan Interest Adjustment Credit

792

Interest Arrears Adjustment Credit

793

Principal Arrears Adjustment Credit

794

Non-Performing Loan – Loan Interest Credit Adjustment Adjustment Credits-Non Performing Loans

A–8

795

Loan Interest Adjustment Credit

796

Interest Arrears Adjustment Credit

797

Principal Arrears Adjustment Credit

790

Already Paid Interest Amount Refund

798

Arrears Interest after ‘Final Day’ Debit Adjustment (Non-Performing)

3937 0408–930

Transaction Types

Other Asset Transactions Other liability transactions use the code series 800 to 899.

Other Asset Transactions for Non-Loans Transaction Code

Description

800

Account Debit Interest Accrual

801

Deferred Charges Accrual

802

Unutilised Overdraft Fee Accrual

810

Interest Settlement Debit

811

Deferred Charges Settlement Debit

812

Unutilised Overdraft Fee Settlement

820

Withholding Tax Debit

823

Cheque Encashment Cash Commission

830

Travellers Cheque Encashment Cash Commission

832

Travellers Cheque Purchase Cash Commission

840

Cashier’s Cheque Encashment Cash Commission

842

Cashier’s Cheque Purchase Cash Commission

845

Bureau de Change Cash Commission

Other Asset Transactions for Loans Transaction Code

Description

850

Loan Interest Accrual

851

Loan Interest Arrears Interest Accrual

852

Loan Principal Arrears Interest Accrual

853

Non-Performing Loan Interest Accrual

854

Non-Performing Loan Interest Arrears Interest Accrual

855

Non-Performing Loan Principal Arrears Interest Accrual

856

After Final Demand Interest Accrual

860

Loan Interest Settlement Debit

862

Interest Arrears Interest Settlement Debit on IS date

864

Principal Arrears Interest Settlement Debit on IS date

866

After Final Demand Interest Settlement

870

Non-Performing Loan Interest Settlement Debit

3937 0408–930

A–9

Transaction Types

Transaction Code

Description

872

Non-Performing Loan Interest Arrears interest Settlement Debit on IS date

874

Non-Performing Loan Principal Arrears interest Settlement Debit on IS date Adjustment Debits-Performing Loans

A–10

891

Loan Interest Adjustment Debit

892

Interest Arrears Adjustment Debit

893

Principal Arrears Adjustment Debit

3937 0408–930

Transaction Types

Transaction Codes for Accounting Models Accounting models can be used to post amounts from a wholesale transaction to a retail client account. The transaction code must be within the range given in the following table. If no code is specified on the accounting model, a default transaction code of 900 will be used for a credit posting and a code of 950 for a debit posting. Transaction Code

Description

900

Default Wholesale Credit Transfer

901 to 924

Reserved for user defined Wholesale Credit Transfers

950

Default Wholesale Debit Transfer

951 to 974

Reserved for user defined Wholesale Debit Transfer

For more information on accounting models, see Setting Up Accounting Models in the Guide to Setting Up.

3937 0408–930

A–11

Transaction Types

Charges A charge transaction code is composed of the original transaction code prefixed by 5. For example, the transaction code for a travellers cheque cash sale is 600 therefore the code representing the charge for the sale is 5600. Charges that relate to transactions other than financial transactions (for example, the charge for opening an account) are represented by a code between 6000 and 6999. The following table shows these codes. Transaction Code

Description

6020

Standing Order Mandate

6030

Change Standing Order Mandate

6080

Request Statement

6090

Reprint Statement (Original not received)

6110

Extra Statement Copies printed

6120

Stop cheque

6190

Account Closure - charges or penalty interest

6350

Intra Accounting Centre Beneficiary Returned Cheque

6360

Intra Accounting Centre Payer Returned Cheque

6370

Domestic Beneficiary Returned Cheque

6380

Domestic Payer Returned Cheque

6600

Credit Turnover Charge

6610

Debit Turnover Charge

6620

Periodic Charge

The Product Transaction Types (PTTRM) screen is used to specify the transactions that are permitted against a product. Each transaction can be associated with a charge. The charge will be levied automatically when a chargeable transaction is passed for an account. Charges are applied to accounts as withdrawal transactions. Adjustments are applied to accounts as either withdrawals or deposits depending on whether the adjustment is positive or negative.

A–12

3937 0408–930

Transaction Types

Cross Accounting Centre Transactions The following ranges of transaction codes are used for automatically generated cross accounting centre transactions. These are: Transaction Code

Description

1000 – 1999

Cross accounting centre transactions generated for 100-999 transactions (account side)

2000 – 2999

Cross accounting centre transactions generated for 100-999 transactions (teller side)

3000 – 3999

Cross accounting centre transactions generated for 5xxx transactions (teller side)

4000 – 4999

Cross accounting centre transactions generated for 5xxx transactions (account side)

7000 – 7999

Cross accounting centre transactions generated for 6xxx transactions (account side)

8000 – 8999

Cross accounting centre transactions generated for 6xxx transactions (teller side)

3937 0408–930

A–13

Transaction Types

A–14

3937 0408–930

Appendix B Accounting Entries All financial transactions are defined on the Retail Transaction Definition (TRDFM) screen (see Section 2 of this guide) and are represented by Transaction Codes (see Appendix A). These transactions generate accounting entries that are listed in this appendix. Accounting entries for the following are described in the this section: 1.

Demand, Fixed Term Deposits and Savings •

•

•

2.

Client Triggered −

Cash

−

Cheques

−

Transfer

−

Bill Payments

−

Cheque Negotiation

−

Cheque Sales

−

Travellers Cheque Sales

System Triggered −

Direct Debits

−

Standing Orders

System Generated −

Interest

−

Charges

Loans •

3937 0408–930

Performing Loan Activities −

Drawdown

−

Interest (includes accrual, settlement, reduction/refund, adjustments) and Fees

−

Loan Repayment

−

Loan Early Repayment

−

Loan Early Closure

−

Status change to Non-Performing

B–1

Accounting Entries

•

•

3.

−

Interest (includes accrual, settlement, reduction/refund)

−

Loan Re-payment

−

Final Demand

−

Provisions

−

Write-off (partial and full)

−

Status change to Performing

After Final Demand Loan Activities −

Interest (includes accrual, settlement, reduction/refund)

−

Loan Re-payment

Other •

4.

Non-Performing Loan Activities

Bureau de Change

Retail Cross Accounting Centre Postings •

Retail Cross Currency Postings

•

Retail Cross Currency, Cross Accounting Centre Postings

Transactions can be made with or without charges. Whether or not a charge will be applied depends on whether the transaction code has been set up on the Product Transaction Types (PTTRM) screen for the product and the amount of the charge has been set up on the Retail Charge Conditions (PTCHM) screen.

B–2

3937 0408–930

Accounting Entries

Demand/Fixed Term Deposits/Savings Client Triggered Cash Cash Deposit to Account (same currency) Txn Code

Amount

Dr/ Cr

100

Deposit Amount

Dr Cr

5100

Charge Amount

Dr Cr

Product Account

Transaction Account Till

Client Account Client Account Relevant Charges

Cash Deposit to Account (different currency) A deposit in Currency 1 (CUR1) to an account of Currency 2 (CUR2). Txn Code

Amount

Dr/ Cr

108

Deposit Amount

Dr Cr

208

Deposit Amount

Dr Cr

Product Account

Transaction Account Currency Position

Client Account (CUR2) Till (CUR1) Currency Position

Cash Withdrawal from Account (same currency) Txn Code

Amount

Dr/ Cr

Product Account

200

Withdrawal Amount

Dr Cr

Client Account

5200

Charge Amount

Dr Cr

Client Account

3937 0408–930

Transaction Account

Till Relevant Charges

B–3

Accounting Entries

Cash Withdrawal from Account (different currency) A withdrawal in Currency 1 (CUR1) from an account of Currency 2 (CUR2) Txn Code

Amount

Dr/ Cr

Product Account

208

Withdrawal Amount

Dr Cr

Client Account (CUR2)

108

Withdrawal Amount

Transaction Account

Currency Position

Dr Cr

Till (CUR1)

Currency Position

Cheques Intra Bank Cheque Deposit, Cheque and Account in the same currency The bank should be defined as ‘RETAIL OWN BANK’ Txn Code

Amount

Dr/ Cr

110

Cheque Amount

Dr Cr

Product Account

Transaction Account Intra bank clearing

Client A/C beneficiary

If the cheque clears during the overnight, the following occurs: 210 5110 5210

Cheque amount Charge amount Charge amount

Dr Cr

Client A/C payer

Dr Cr

Client A/C beneficiary

Dr Cr

Client A/C payer

Intra bank clearing Relevant charge A/C Relevant charge A/C

If the transaction is rejected, the transaction 110 is reversed and if applicable, charges are applied: 110 6350 6360

B–4

Negative Cheque Amount Charge Amount Charge Amount

Dr Cr

Intra Bank Clearing Client A/C Beneficiary

Dr Cr

Client A/C Beneficiary

Dr Cr

Client A/C Payer

Relevant Charge A/C Relevant Charge A/C

3937 0408–930

Accounting Entries

Domestic Bank Cheque Deposit, Cheque and Account in same currency The cheque deposit is cleared instantly as clearing banks funds are certain. On the cheque value date, a transaction is raised by the system transferring the amount in clearing to the Nostro of the pay account bank. The Nostro account is dependent on the cheque details being entered. Cheque deposit Txn Code

Amount

Dr/ Cr

120

Cheque Amount

Dr Cr

5120

Charge Amount

Product Account

Transaction Account Domestic Clearing

Client A/C

Dr Cr

Client A/C

Dr Cr

Domestic Clearing

Relevant Charge A/C

Cheque Clearance (on value date) 750

Cheque Amount

Domestic Clearing

If the cheque is rejected, the following transaction is also raised: 291

Cheque Amount

Dr Cr

191

Cheque Amount

Dr Cr

6380

Charge Amount

Dr Cr

Client A/C GL Contra Account GL Contra Account Domestic Clearing Client A/C Relevant Charge A/C

Domestic Bank Cheque Deposit, Cheque and Account in different currencies All domestic clearing will be in one currency. Therefore, any cheques not in this currency will be treated as a foreign bank cheque as will accounts in different currencies as given below. Domestic Bank Cheque Withdrawal, Cheque and Account in the same currency These transactions will be automatically carried out as they are delivered to the system via records provided by the clearing house. Cheque withdrawal via clearing: Txn Code

Amount

Dr/ Cr

Product Account

220

Cheque Amount

Dr Cr

Client A/C

5220

Charge Amount

Dr Cr

Client A/C

3937 0408–930

Transaction Account Domestic Clearing Relevant Charge A/C

B–5

Accounting Entries

Cheque Clearance (on the same date) 120

Cheque Amount

Dr Cr

Domestic Clearing Domestic Clearing

If the cheque is rejected, for example due to insufficient funds, the only transaction would be a charge to the client account and the details would be returned via a file to clearing: 6370

Charge Amount

Dr Cr

Client A/C Relevant Charge A/C

Domestic Bank Cheque Withdrawal, Cheque and Account in different currencies Domestic clearing is in one currency and therefore any cheques not in this currency is treated as a foreign bank cheque, as will accounts in different currencies as given below. Foreign Bank Cheque Deposit, Cheque and Account in the same currency The funds are cleared before they are deposited to the client account, as foreign bank funds are not certain. They are held until the funds are confirmed as available before they are credited to the account. Receipt of cheque:

B–6

Txn Code

Amount

Dr/ Cr

124

Cheque Amount

Dr Cr

Product Account

Transaction Account Cheques due to Clients

Foreign Cheques for Coll

3937 0408–930

Accounting Entries

When funds are confirmed as available, the following transactions are raised manually: 225

Cheque Amount

Dr Cr

125

Cheque Amount

Dr Cr

Foreign Cheques for Coll Cheques due to Clients GL Contra Account Client A/C

295

Cheque Amount

Dr Cr

Nostro A/C

5125

Charge Amount

Dr Cr

Client A/C

GL Contra Account Relevant Charges A/C

If the cheque is rejected, the following transaction is raised: 225

Cheque Amount

Dr Cr

Foreign Cheques for Coll Cheques due to Clients

Foreign Bank Cheque Deposit, Cheque and Account in different currency The funds need to be cleared before they can be deposited to the client account as foreign bank funds are not certain. They are held until the funds are confirmed as available before they are credited to the account. Receipt of cheque Txn Code

Amount

Dr/ Cr

124

Cheque Amount (cheque currency)

Dr Cr

Product Account

Transaction Account Cheques due to Clients

Foreign Cheques for Coll

When funds are confirmed as available, the following transactions are raised manually: 227

Cheque Amount (cheque currency)

Dr Cr

127

Cheque Amount (account currency)

Dr Cr

Cheque Amount (cheque currency)

Dr Cr

Nostro A/C

Charge (account currency)

Dr Cr

Client A/C

296 5127

Foreign Cheques for Coll Cheques due to Clients Currency Position Client A/C Currency Position Relevant Charge A/C

If the cheque is rejected, the following transactions are raised manually: 227

3937 0408–930

Cheque Amount

Dr Cr

Foreign Cheques for Coll Cheques due to clients

B–7

Accounting Entries

Transfer Transfers are made between two internal accounts For all transfers, both transactions must be entered as they work as a pair Transfer between Intra Bank Accounts (same currency) Txn Code

Amount

Dr/ Cr

Product Account

260

Payment Amount

Dr Cr

Client A/C Payer

160

Payment Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Client A/C Beneficiary

5260

Charge

Dr Cr

Client A/C Payer

5160

Charge

Dr Cr

Client A/C Beneficiary

Relevant Charges Relevant Charges

Account Deposit from Intra Bank Account (different currency)

B–8

Txn Code

Amount

Dr/ Cr

Product Account

261

Payment Amount

Dr Cr

Client A/C Payer (Cur 1)

161

Payment Amount

Dr Cr

5261

Charge

Dr Cr

Client A/C Payer (Cur 1)

5161

Charge

Dr Cr

Client A/C Ben (Cur 2)

Transaction Account

Currency Position Currency Position Client A/C Ben (Cur 2) Relevant Charges Relevant Charges

3937 0408–930

Accounting Entries

Bill Payments A customer can pay a bill in a number of ways: By cash to a Utility’s Account held at the bank (Bill Payment by Cash to ‘Own Bank’ Utility’s Client Account): Txn Code

Amount

Dr/ Cr

300

Payment Amount

Dr Cr

5300

Charge Amount

Dr Cr

Product Account

Transaction Account Till

Client Account Till Relevant Charges

By cash to a Utility’s Account held at another domestic bank (Bill Payment by Cash to Credit Outward Suspense (Domestic) Stage 1): Txn Code

Amount

Dr/ Cr

310

Payment Amount

Dr Cr

5310

Charge Amount

Dr Cr

Product Account

Transaction Account Till

Outwd Dom Bill Pay Till Relevant Charges

Note: There is no interface to perform Stage 2 processing that would generate a 311 (Bill Payment by Cash to Debit Outward Suspense (Domestic) Stage 2) to send the payment to clearings. By cash to a Utility’s Account held at a foreign bank (Bill Payment by Cash to Credit Outward Suspense (Foreign) Stage 1): Txn Code

Amount

Dr/ Cr

320

Payment Amount

Dr Cr

5320

Charge Amount

Dr Cr

Product Account

Transaction Account Till

Outwd Foreign Bill Pay Till Relevant Charges

Note: There is no interface to perform Stage 2 processing that would generate a 321 (Bill Payment by Cash to Debit Outward Suspense (Foreign) Stage 2) to send the payment to clearings.

3937 0408–930

B–9

Accounting Entries

By transfer from a Client Account to a Utility’s Account held at a the bank (Bill Payment Credit to ‘Own Bank’ Utility’s Client Account from Client Account): Txn Code

Amount

Dr/ Cr

Product Account

2nn

Payment Amount

Dr Cr

Client A/C Payer

331

Payment Amount

Dr Cr

52nn

Charge Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Client A/C Beneficiary Client A/C Payer Relevant Charges

Note: The 2nn transaction is a user defined transaction that withdraws funds from the client account. By transfer from a Client Account to a Utility’s Account held at a domestic bank (Bill Payment Debit from Client Account to Domestic Bank Account): Txn Code

Amount

Dr/ Cr

Product Account

340

Payment Amount

Dr Cr

Client Account

5340

Charge Amount

Dr Cr

Client Account

Transaction Account

Domestic Clearing Relevant Charge A/C

By transfer from a Client Account to a Utility’s Account held at a foreign bank (Bill Payment Debit from Client Account to Foreign Bank Account): Txn Code

Amount

Dr/ Cr

Product Account

350

Payment Amount

Dr Cr

Client Account

5350

Charge Amount

Dr Cr

Client Account

Transaction Account

Nostro A/C Relevant Charge A/C

In addition to the above transactions that are triggered by clients of the bank to pay their bills, payments may be received, via clearings, from clients who hold accounts at other banks into a utility’s account held at the bank: By transfer from Domestic Clearing to a Utility’s Account held at a the bank (Bill Payment from Domestic Clearing to ‘Own Bank’ Utility’s Client Account):

B–10

Txn Code

Amount

Dr/ Cr

360

Payment Amount

Dr Cr

Product Account

Transaction Account Domestic Clearing

Client Account

3937 0408–930

Accounting Entries

By transfer from Foreign Clearing to a Utility’s Account held at a the bank (Bill Payment from Foreign Clearing to ‘Own Bank’ Utility’s Client Account): Txn Code

Amount

Dr/ Cr

370

Payment Amount

Dr Cr

Product Account

Transaction Account Nostro A/C

Client Account

Cheque Negotiation Cheque negotiation is currently for internal use only (cheques issued on accounts held at the bank). Intra-Bank Cheque for Cash Txn Code

Amount

Dr/ Cr

Product Account

400

Cheque Amount

Dr Cr

Client A/C Paying

5400

Charge

Dr Cr

Client Account

Transaction Account

Till Relevant Charges

Intra-Bank Cheque for Account This process avoids the delay in clearing between book and value date. Txn Code

Amount

Dr/ Cr

Product Account

401

Cheque Amount

Dr Cr

Client A/C Paying

402

Cheque Amount

Dr Cr

5401 5402

Charge Charge

Transaction Account

GL Contra Account GL Contra Account Client A/C Receiving

Dr Cr

Client A/C Paying

Dr Cr

Client A/C Receiving

Relevant Charges Relevant Charges

Traveller’s Cheques purchased for cash in the same currency Txn Code

Amount

Dr/ Cr

Product Account

440

Cheque Amount

Dr Cr

Traveller’s Cheques

5440

Charge

Dr Cr

Traveller’s Cheques

3937 0408–930

Transaction Account

Till Relevant Charges

B–11

Accounting Entries

Traveller’s Cheques purchased for credit to client’s account in same currency There are no charges for this facility Txn Code

Amount

Dr/ Cr

Product Account

441

Cheque Amount

Dr Cr

Traveller’s Cheques

442

Cheque Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Client Account

Cashier’s Cheques purchased for cash in the same currency Txn Code

Amount

Dr/ Cr

Product Account

450

Cheque Amount

Dr Cr

Cashier’s Cheques

5450

Charge

Dr Cr

Cashier’s Cheques

Transaction Account

Till Relevant Charges

Cashier’s Cheques purchased for crediting client’s account in the same currency

B–12

Txn Code

Amount

Dr/ Cr

Product Account

451

Cheque Amount

Dr Cr

Cashier’s Cheques

452

Cheque Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Client’s Account

3937 0408–930

Accounting Entries

Cashier’s Cheque Sales By Cash, cheque and cash in the same currency Txn Code

Amount

Dr/ Cr

620

Cheque Amount+Charge

Dr Cr

Charge

Dr Cr

5620

Product Account

Transaction Account Till

Cashier’s Cheques Cashier’s Cheques Relevant Charges

By Transfer, cheque and account in the same currency Txn Code

Amount

Dr/ Cr

Product Account

630

Cashier’s Cheque Amount

Dr Cr

Client’s Account

Cashier’s Cheque Amount

Dr Cr

Charge

Dr Cr

635 5630

Transaction Account

GL Contra Account GL Contra Account Cashier’s Cheques Client’s account Relevant Charges

By Transfer, cheque and account in a different currency Txn Code

Amount

Dr/ Cr

Product Account

631

Cashier’ Cheque Amt in A/C currency

Dr Cr

Client’s Account

636

Cashier’s Cheque Amt in Cheque currency

Dr Cr

5631

Charge in Account currency

Dr Cr

3937 0408–930

Transaction Account

Currency Position A/C Currency Position A/C Cashier’s Cheques Client’s Account Relevant Charges

B–13

Accounting Entries

Reimbursement of Intra Bank Cashier’s Cheque Deposit Deposit of Cheque Txn Code

Amount

Dr/ Cr

140

Cheque Amount

Dr Cr

Product Account

Transaction Account GL Contra Account

Client’s A/C

Overnight 240

Cheque Amount

Dr Cr

Cashier’s Chq for Reimb GL Contra Account

Reimbursement of Bank Cashier’s Cheque Deposit These transactions are treated the same way as normal cheque clearance methods.

B–14

3937 0408–930

Accounting Entries

Travellers Cheque Sales Sale by cash, cheque and cash in the same currency Txn Code

Amount

Dr/ Cr

600

Travellers Cheque Amt + Charge

Dr Cr

Charge

Dr Cr

5600

Product Account

Transaction Account Till

Traveller’s Cheques Travellers Cheques Relevant Charges

Sale by transfer, cheque and account in the same currency Txn Code

Amount

Dr/ Cr

Product Account

610

Travellers Cheque Amt

Dr Cr

Client’s Account

615 5610

Travellers Cheque Amt Charge

Dr Cr Dr Cr

Transaction Account

GL Contra Account GL Contra Account Travellers Cheques Client’s Account Relevant Charges

Sale by transfer, cheque and account in a different currency Txn Code

Amount

Dr/ Cr

Product Account

611

Travellers Cheque Amt in Account currency

Dr Cr

Client’s Account

616

Travellers Cheque Amt in Cheque currency

Dr Cr

Charge in Account currency

Dr Cr

5611

3937 0408–930

Transaction Account

Currency Position A/C Currency Position A/C Travellers Cheques Client’s Account Relevant Charges

B–15

Accounting Entries

System Triggered Direct Debits For a direct debit payment to be made, a mandate must be raised for the paying account. Direct debit mandate entries are made on the Direct Debit Mandate Maintenance (APDDM) screen. Direct debit transaction entries are made on the Direct Debit Batch Entry (APBDM) screen. All direct debit transactions are automatic. Intra Bank Account Payment and Deposit (same currency) These transactions are generated when the ‘Receive Bank Identifier’ on Direct Debit Mandate Maintenance (APDDM) screen is left blank. This indicates that the collecting account is also within the bank. Txn Code

Amount

Dr/ Cr

Product Account

255

Payment Amount

Dr Cr

Client A/C Payer

155

Payment Amount

Dr Cr

5255

Charge

Dr Cr

Client A/C Payer

5155

Charge

Dr Cr

Client A/C Beneficiary

Transaction Account

GL Contra Account GL Contra Account Client A/C Beneficiary Relevant Charges Relevant Charges

Intra Bank Account Payment and Deposit (different currency) These transactions are generated when the ‘Receive Bank Identifier’ on the Direct Debit Mandate Maintenance (APDDM) screen is left blank. This indicates that the collecting account is also within the bank.

B–16

Txn Code

Amount

Dr/ Cr

Product Account

250

Payment Amount

Dr Cr

Client A/C Payer (Cur 1)

150

Payment Amount

Dr Cr

5250

Charge

Dr Cr

Client A/C Payer (Cur 1)

5150

Charge

Dr Cr

Client A/C Ben (Cur 2)

Transaction Account

Currency Position Currency Position Client A/C Ben (Cur 2) Relevant Charges Relevant Charges

3937 0408–930

Accounting Entries

Account Payment to Domestic Bank Account (same currency) Txn Code

Amount

Dr/ Cr

Product Account

256

Payment Amount

Dr Cr

Client A/C

156

Payment Amount

Dr Cr

5256

Charge

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Domestic D/D Clearing Client A/C Relevant Charges

Account Payment to Foreign Account (same currency) Txn Code

Amount

Dr/ Cr

Product Account

257

Payment Amount

Dr Cr

Client A/C

Transaction Account

GL Contra Account

157

Payment Amount

Dr Cr

D/D for Collection

5257

Charge

Dr Cr

Client A/C

295

Payment Amount

Dr Cr

D/D for Collection

195

Payment Amount

Dr Cr

GL Contra Account

Relevant Charges GL Contra Account GL Contra Account Nostro A/C

Account Deposit from Domestic Bank Account (same currency) Txn Code

Amount

Dr/ Cr

156

Payment Amount

Dr Cr

Product Account

GL Contra Account Client A/C

256

Payment Amount

Dr Cr

Domestic D/D Clearing

5156

Charge

Dr Cr

Client A/C

3937 0408–930

Transaction Account

GL Contra Account Relevant Charges

B–17

Accounting Entries

Account Deposit from Foreign Account (same currency) Txn Code

Amount

Dr/ Cr

Product Account

295

Payment Amount

Dr Cr

Nostro A/C

195

Payment Amount

Dr Cr

257

Payment Amount

Dr Cr

157

Payment Amount

Dr Cr

5157

Charge

Dr Cr

Transaction Account

Currency Position Currency Position For Cur D/D Collection For Cur D/D Collection Currency Position Currency Position Client A/C Client A/C Relevant Charges

Account Payment to Domestic Bank Account (different currency) Txn Code

Amount

Dr/ Cr

Product Account

251

Payment Amount

Dr Cr

Client A/C

151

Payment Amount

Dr Cr

5251

Charge

Dr Cr

Transaction Account

Currency Position Currency Position Domestic D/D Clearing Client A/C Relevant Charges

Account Payment to Foreign Account (different currency) Txn Code

Amount

Dr/ Cr

Product Account

252

Payment Amount

Dr Cr

Client A/C

152

Payment Amount

Dr Cr

B–18

Currency Position Currency Position For Cur D/D Collection

5252

Charge

Dr Cr

Client A/C

296

Payment Amount

Dr Cr

For Cur D/D Collection

196

Payment Amount

Dr Cr

Transaction Account

Relevant Charges Currency Position Currency Position Nostro A/C

3937 0408–930

Accounting Entries

Account Deposit from Domestic Bank Account (different currency) Txn Code

Amount

Dr/ Cr

151

Payment Amount

Dr Cr

Product Account

Transaction Account Currency Position

Client A/C

251

Payment Amount

Dr Cr

Domestic D/D Clearing

5151

Charge

Dr Cr

Client A/C

Currency Position Relevant Charges

Account Deposit from Foreign Account (different currency) Txn Code

Amount

Dr/ Cr

Product Account

296

Payment Amount

Dr Cr

Nostro A/C

196

Payment Amount

Dr Cr

252

Payment Amount

Dr Cr

152

Payment Amount

Dr Cr

5152

3937 0408–930

Charge

Dr Cr

Transaction Account

Currency Position Currency Position For Cur D/D Collection For Cur D/D Collection Currency Position Currency Position Client A/C Client A/C Relevant Charges

B–19

Accounting Entries

Standing Orders Standing Orders are entered on the Retail Standing Orders Input (SOINP) screen. Standing Orders are automatic transactions. The transactions raised are the same for any Payment Type. Intra Bank Account Payment and Deposit (same currency) These transactions are generated when the Standing Order Type is set to ‘CC’ (Client Account to Client Account) Txn Code

Amount

Dr/ Cr

Product Account

205

Payment Amount

Dr Cr

Client A/C Payer

105

Payment Amount

Dr Cr

5205

Charge

Dr Cr

Client A/C Payer

Dr Cr

Client A/C Beneficiary

5105

Charge

Transaction Account

GL Contra Account GL Contra Account Client A/C Beneficiary Relevant Charges Relevant Charges

Intra Bank Account Payment and Deposit (different currency) These transactions are generated when the Standing Order Type is set to ‘CC’ (Client Account to Client Account) Txn Code

Amount

Dr/ Cr

Product Account

202

Payment Amount

Dr Cr

Client A/C Payer (Cur 1)

102

Payment Amount

Dr Cr

5202

Charge

Dr Cr

Client A/C Payer (Cur 1)

Dr Cr

Client A/C Ben (Cur 2)

5102

B–20

Charge

Transaction Account

Currency Position Currency Position Client A/C Ben (Cur 2) Relevant Charges Relevant Charges

3937 0408–930

Accounting Entries

Account Payment to Domestic Bank Account (same currency) These transactions are generated when the Standing Order Type is set to ‘EX’ (Client Account to External Account) Txn Code

Amount

Dr/ Cr

Product Account

206

Payment Amount

Dr Cr

Client A/C

106 5206

Payment Amount Charge

Dr Cr Dr Cr

Transaction Account

GL Contra Account GL Contra Account Domestic S/O Clearing Client A/C Relevant Charges

Account Payment to Foreign Account (same currency) These transactions are generated when the Standing Order Type is set to ‘EX’ (Client Account to Client Account). Payment sent with instructions. Txn Code

Amount

Dr/ Cr

Product Account

207

Payment Amount

Dr Cr

Client A/C

107

Payment Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account S/O for Collection

5207

Charge

Dr Cr

Client A/C

295

Payment Amount

Dr Cr

S/O for Collection

195

Payment Amount

Dr Cr

Relevant Charges GL Contra Account GL Contra Account Nostro A/C

Account Deposit from Domestic Bank Account (same currency) Deposits that will enter the system via an interface and therefore are automatic. Txn Code

Amount

Dr/ Cr

106

Payment Amount

Dr Cr

Product Account

GL Contra Account Client A/C

206

Payment Amount

Dr Cr

Domestic S/O Clearing

5106

Charge

Dr Cr

Client A/C

3937 0408–930

Transaction Account

GL Contra Account Relevant Charges

B–21

Accounting Entries

Account Deposit from Foreign Account (same currency) Deposits will enter the system via an interface and are therefore automatic. Payment received with instructions. Txn Code

Amount

Dr/ Cr

Product Account

295

Payment Amount

Dr Cr

Nostro A/C

195

Payment Amount

Dr Cr

207

Payment Amount

Dr Cr

107

Payment Amount

Dr Cr

5107

Charge

Dr Cr

Transaction Account

Currency Position Currency Position For Cur S/O Collection For Cur S/O Collection Currency Position Currency Position Client A/C Client A/C Relevant Charges

Account Payment to Domestic Bank Account (different currency) These transactions are generated when the Standing Order Type is set to ‘EX’ (Client Account to External Account) Txn Code

Amount

Dr/ Cr

Product Account

203

Payment Amount

Dr Cr

Client A/C

103 5203

B–22

Payment Amount Charge

Dr Cr Dr Cr

Transaction Account

Currency Position Currency Position Domestic S/O Clearing Client A/C Relevant Charges

3937 0408–930

Accounting Entries

Account Payment to Foreign Account (different currency) These transactions are generated when the Standing Order Type is set to ‘EX’ (Client Account to External Account) Payment sent with instructions. Txn Code

Amount

Dr/ Cr

Product Account

204

Payment Amount

Dr Cr

Client A/C

104

Payment Amount

Dr Cr

Transaction Account

Currency Position Currency Position For Cur S/O Collection

5204

Charge

Dr Cr

Client A/C

296

Payment Amount

Dr Cr

For Cur S/O Collection

196

Payment Amount

Dr Cr

Relevant Charges Currency Position Currency Position Nostro A/C

Account Deposit from Domestic Bank Account (different currency) Deposits will enter the system via an interface and are therefore automatic. Txn Code

Amount

Dr/ Cr

103

Payment Amount

Dr Cr

Product Account

Transaction Account Currency Position

Client A/C

203

Payment Amount

Dr Cr

Domestic S/O Clearing

5103

Charge

Dr Cr

Client A/C

Currency Position Relevant Charges

Account Deposit from Foreign Account (different currency) Deposits will enter the system via an interface and are therefore automatic. Txn Code

Amount

Dr/ Cr

Product Account

296

Payment Amount

Dr Cr

Nostro A/C

196

Payment Amount

Dr Cr

204

Payment Amount

Dr Cr

104

Payment Amount

Dr Cr

5104

3937 0408–930

Charge

Dr Cr

Transaction Account

Currency Position Currency Position For Cur S/O Collection For Cur S/O Collection Currency Position Currency Position Client A/C Client A/C Relevant Charges

B–23

Accounting Entries

System Generated Interest Interest is accrued automatically by the conditions set up on the product and account. Standard Credit Interest Standard credit interest is accrued when the Offset credit interest field is set to ‘Do Not Offset Interest’ on the Product Maintenance 1 (PTA1M) screen. Txn Code

Amount

Dr/ Cr

700

Daily Accrual Amount

Dr Cr

Product Account

Transaction Account Interest Expense

Accrual Account

Accrual Settlement – on the settlement day defined on the account Txn Code

Amount

Dr/ Cr

710

Sum of Daily Accruals

Dr Cr

Product Account

Transaction Account Accrual Account

Client Account

Notional Credit Interest Notional credit interest is accrued when the Offset credit interest field is set to ‘Offset Against Debit Interest’ on the Product Maintenance 1 (PTA1M) screen. Txn Code

Amount

Dr/ Cr

701

Daily Accrual Amount

Dr Cr

Product Account

Transaction Account Interest Income (OD’s)

Accrual Account

Notional credit interest is offset against standard debit interest and therefore does not settle. One of three options will occur on settlement day, as follows:

B–24

•

If credit interest is greater than debit interest the accrual to date will be removed using transaction 701 and 800 respectively.

•

If credit interest is less than debit interest, the net balance is settled using transaction 810.

•

If credit interest is less than debit interest, the net balance is settled using transaction 710 and 810. To ensure the netted amounts do not stay on the GL, the GL Asset Account, GL Product Account and GL Transaction Account on the Product Transaction Types (PTTRM) screen should use the same values for transaction 701 as has been used for transaction 800 and 710 as 810.

3937 0408–930

Accounting Entries

Standard Debit Interest Daily Accrual Txn Code

Amount

Dr/ Cr

Product Account

800

Daily Accrual Amount

Dr Cr

Accrual Account

Transaction Account

Interest Income (OD’s)

Accrual Settlement – on the settlement day defined on the account Txn Code

Amount

Dr/ Cr

Product Account

810

Sum of Daily Accruals

Dr Cr

Client Account

Transaction Account

Accrual Account

Unutilised Overdraft Interest This transaction is treated as a charge because it is settled according to the settlement frequency defined for charges and not interest. However, it can be treated in the general ledger as interest by settling up the transactions in the same way as for Standard Debit Interest. Daily Accrual Txn Code

Amount

Dr/ Cr

Product Account

802

Daily Accrual Amount

Dr Cr

Deferred Charges Rcvble

Transaction Account

Interest Income (OD’s)

Accrual Settlement – on the settlement day defined on the account Txn Code

Amount

Dr/ Cr

Product Account

812

Sum of Daily Accruals

Dr Cr

Client Account

3937 0408–930

Transaction Account

Deferred Charges Rcvble

B–25

Accounting Entries

Credit Interest Settlement to another Account Occurs when Settlement Client Account is defined when the account was opened on the Client Account Maintenance (CAHDR) screen. Accrual Settlement – on the settlement day defined on originating account. Txn Code

Amount

Dr/ Cr

710

Sum of Daily Accruals

Dr Cr

298

Sum of Daily Accruals

Dr Cr

198

Sum of Daily Accruals

Dr Cr

Product Account

Transaction Account Accrual Account

Originating Client A/C Originating Client A/C GL Contra Account GL Contra Account Settlement Client A/C

Debit Interest Settlement to Another Account Occurs when Settlement Client Account is defined when the account was opened on the Client Account Maintenance (CAHDR) screen. Accrual Settlement – on the settlement day defined on originating account. Txn Code

Amount

Dr/ Cr

Product Account

810

Sum of Daily Accruals

Dr Cr

Originating Client A/C

198

Sum of Daily Accruals

Dr Cr

298

B–26

Sum of Daily Accruals

Dr Cr

Transaction Account

Accrual Account GL Contra Account Originating Client A/C Settlement Client A/C GL Contra Account

3937 0408–930

Accounting Entries

Charges There are two types of charges that can be applied to an account: •

Transaction Based: This charge is raised automatically if it is set up on the Product Transaction Types (PTTRM) screen. These are immediate charges and appear on the account on the originating transaction code. Transaction based charges are numbered 5*** where the *** is the originating transaction code. For example, a charge for transaction 100 will be numbered as 5100.

•

Event Based: These are raised on events that occur but may not appear on statements. For example, statement requests. These charges are raised if the transaction has been set up on the Product Transaction Types (PTTRM) screen. Event based charges are numbered 6***. These charges can be immediate, as they occur or deferred where they will be settled as per the charges frequency set up on the account. If they are charged immediately, the 6*** code will be used and if deferred the accrual will use 801 and settle using 810.

Note: Not all charges can be deferred. For example, closure charges cannot be deferred. Transaction Based Charges (5*** codes) Immediate charge on transaction date. Txn Code

Amount

Dr/ Cr

Product Account

5***

Charge amount

Dr Cr

Client A/C

Transaction Account

Relevant Charges

Event Based Charges (6*** codes) – Immediate Charge Immediate charge on event date. Txn Code

Amount

Dr/ Cr

Product Account

6***

Charge amount

Dr Cr

Client A/C

3937 0408–930

Transaction Account

Relevant Charges

B–27

Accounting Entries

Event Based Charges (6***) – Deferred Charge Accrual on event date Txn Code

Amount

Dr/ Cr

Product Account

801

Charge amount

Dr Cr

Deferred Charges

Transaction Account

Relevant Charges

Settlement on Charges Settlement Frequency date

B–28

Txn Code

Amount

Dr/ Cr

Product Account

811

Charges accrued

Dr Cr

Client Account

Transaction Account

Deferred Charges

3937 0408–930

Accounting Entries

Loans Performing Loan Activities Drawdown To drawdown a loan, the relevant transaction is entered through the front office system via the Deposits (TRDEP) or Deposits Interface (TTDEP) screen for cash and cheque and the Loan Drawdowns (TTLDD) for transfer. By Cash To reflect a loan drawdown by cash, the GL ‘Loan Accounts’ Account is debited and the GL ‘Till’ Account is credited with the loan amount using the cash withdrawal (same currency) transaction (200), as follows: Txn Code

Amount

Dr/ Cr

Product Account

200

Loan Amount

Dr Cr

Loan Accounts

Transaction Account

Till

By Cashiers Cheque To reflect a loan drawdown by cashiers cheque, the GL ‘Loan Accounts’ Account is debited and the GL ‘Intra Bank Clearing’ Account is credited with the loan amount using the cashier cheque withdrawal transaction (240), as follows: Txn Code

Amount

Dr/ Cr

Product Account

240

Loan Amount

Dr Cr

Loan Accounts

3937 0408–930

Transaction Account

Intra Bank Clearing

B–29

Accounting Entries

By Transfer To reflect a loan drawdown by transfer, the GL ‘Loan Accounts’ Account is debited and the GL ‘Suspense’ Account is credited with the loan amount using the loan drawdown debit transaction (262). The system automatically generates the required number (up to 4) of loan drawdown credit transactions (162) to debit the GL ‘Suspense’ Account and credit the GL Product Account relating to the client account being credited (the 162 transaction definition of the product is used to ascertain the GL account), as follows: Txn Code

Amount

Dr/ Cr

Product Account

262

Loan Amount

Dr Cr

Loan Accounts

162

Transfer Amount

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Receiving Accounts

Interest and Fees Interest Accrual The system automatically accrues interest daily for each loan account during the overnight process using the RETLOANREP – Retail Loan Overnight Processing report. Loan Interest To reflect the interest accrued on a loan, the GL ‘Accrued Interest Receivable on Loans’ Account is debited and the GL ‘Loans Interest Income’ Account is credited with the amount of interest accrued using the interest accrual transaction (850), as follows: Txn Code

Amount

Dr/ Cr

Product Account

850

Interest Accrued for day on Loan

Dr

Accrued Interest Receivable on Loans

Cr

B–30

Transaction Account

Loans Interest Income

3937 0408–930

Accounting Entries

Principal Arrears Interest To reflect the interest accrued on principal arrears, the GL ‘Accrued Interest Receivable on Loan Principal Arrears’ Account is debited and the GL ‘Loan Principal Arrears Interest Income’ Account is credited with the amount of interest accrued using the principal arrears interest accrual transaction (852) as follows: Txn Code

Amount

Dr/ Cr

Product Account

852

Interest accrued for day on Principal Arrears

Dr

Accrued Interest Receivable on Loan Principal Arrears

Transaction Account

Loan Principal Arrears Interest Income

Cr

Interest Arrears Interest To reflect the interest accrued on interest arrears, the GL ‘Accrued Interest Receivable on Loan Interest Arrears’ Account is debited and the GL ‘Loan Interest Arrears Interest Income’ Account is credited with the amount of interest accrued using the interest arrears interest accrual transaction (851), as follows: Txn Code

Amount

Dr/ Cr

Product Account

851

Interest accrued for day on Interest Arrears

Dr

Accrued Interest Receivable on Loan Interest Arrears

Cr

3937 0408–930

Transaction Account

Loan Interest Arrears Interest Income

B–31

Accounting Entries

Interest Settlement The system automatically settles interest at the defined settlement period for each loan account during the overnight process (RETLOANREP). Interest is settled/charged to the loan account as ‘settled unpaid’ that may be paid by the client when the payment apportionment processing is performed later during the overnight process. Loan Interest To reflect the settlement of interest to a loan account, the GL ‘Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on Loans’ Account is credited with the amount of interest accrued for the period using the interest settlement transaction (860), as follows: Txn Code

Amount

Dr/Cr

Product Account

860

Interest accrued for period on Loan

Dr

Loan Accounts

Transaction Account

Accrued Interest Receivable on Loans

Cr

Principal Arrears Interest To reflect the settlement of interest accrued on principal arrears to a loan account, the GL ‘Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on Loan Principal Arrears’ Account is credited with the amount of interest accrued for the period using the interest settlement transaction (864) as follows:

B–32

Txn Code

Amount

Dr/Cr

Product Account

864

Interest accrued for period on Principal Arrears

Dr

Loan Accounts

Cr

Transaction Account

Accrued Interest Receivable on Loan Principal Arrears

3937 0408–930

Accounting Entries

Interest Arrears Interest To reflect the settlement of interest accrued on interest arrears to a loan account, the GL ‘Loan Accounts ’ Account is debited and the GL ‘Accrued Interest Receivable on Loan Interest Arrears’ Account is credited with the amount of interest accrued for the period using the interest settlement transaction (862), as follows: Txn Code

Amount

Dr/Cr

Product Account

862

Interest accrued for period on Interest Arrears

Dr

Loan Accounts

Cr

Transaction Account

Accrued Interest Receivable on Loan Interest Arrears

Interest Reduction / Refund For Loans, interest may be: •

reduced for interest that has been settled but unpaid for the last and previous periods

•

reduced for interest that has been accrued for the current period

•

refunded for interest that has been settled and paid by the client

To reduce of refund interest, the relevant information is entered using the Arrears Management Interest Reduction / Refund (AMRT2) screen.

3937 0408–930

B–33

Accounting Entries

Interest Reduction for Settled Unpaid Interest To reflect the reduction in interest settled but unpaid by the client on a loan, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loans Interest Income’ Account is debited with the amount of interest to be reduced using the loan interest adjustment transaction (791), as follows: Txn Code

Amount

Dr/Cr

Product Account

791

Reduction Amount

Cr

Loan Accounts

Dr

Transaction Account

Loans Interest Income

To reflect the reduction in interest settled but unpaid by the client on principal arrears, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loan Principal Arrears Interest Income’ Account is debited with the amount of interest to be reduced using the principal arrears interest adjustment transaction (793), as follows: Txn Code

Amount

Dr/Cr

Product Account

793

Reduction Amount

Cr

Loan Accounts

Dr

Transaction Account

Loan Principal Arrears Interest Income

To reflect the reduction in interest settled but unpaid by the client on interest arrears, the GL ‘Loan Accounts Account is credited and the GL ‘Loan Interest Arrears Interest Income’ Account is debited with the amount of interest to be reduced using the interest arrears interest adjustment transaction (792), as follows: Txn Code

Amount

Dr/ Cr

Product Account

792

Reduction Amount

Cr

Loan Accounts

Dr

B–34

Transaction Account

Loan Interest Arrears Interest Income

3937 0408–930

Accounting Entries

Interest Reduction for Accrued Interest To reflect the reduction in interest accrued for period for the loan, the GL ‘Accrued Interest Receivable on Loans’ Account is credited and the GL ‘Loans Interest Income’ Account is debited with the amount of interest to be reduced using the loan interest accrual transaction (850), as follows: Txn Code

Amount

Dr/Cr

Product Account

850

Reduction Amount

Cr

Accrued Interest Receivable on Loans

Dr

Transaction Account

Loans Interest Income

To reflect the reduction in interest accrued for period on principal arrears, the GL ‘Accrued Interest Receivable on Loan Principal Arrears’ Account is credited and the GL ‘Loan Principal Arrears Interest Income’ Account is debited with the amount of interest to be reduced using the principal arrears interest accrual transaction (852), as follows: Txn Code

Amount

Dr/Cr

Product Account

852

Reduction Amount

Cr

Accrued Interest Receivable on Loan Principal Arrears

Dr

Transaction Account

Loan Principal Arrears Interest Income

To reflect the reduction in interest accrued for period on interest arrears, the GL ‘Accrued Interest Receivable on Loan Interest Arrears’ Account is credited and the GL ‘Loan Interest Arrears Interest Income’ Account is debited with the amount of interest to be reduced using the interest arrears interest accrual transaction (851), as follows: Txn Code

Amount

Dr/Cr

Product Account

851

Reduction Amount

Cr

Accrued Interest Receivable on Loan Interest Arrears

Dr

3937 0408–930

Transaction Account

Loan Interest Arrears Interest Income

B–35

Accounting Entries

Interest Refund To reflect the refund of interest paid by a client, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loans Interest Income’ Account is debited with the amount of interest to be refunded, using the refund interest paid transaction (790), as follows: Txn Code

Amount

Dr/Cr

Product Account

790

Refund Amount

Cr

Loan Accounts

Dr

Transaction Account

Loans Interest Income

Interest Adjustments To adjust interest e.g. where an interest rate change for a client was not affected as agreed, an adjustment may be entered using the back-office functionality, RBTHD, RBTDE and RBTCL. Credit To reflect an interest credit adjustment, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loans Interest Income’ Account is debited with the amount of interest to be adjusted using the loan interest credit adjustment transaction (791), as follows: Txn Code

Amount

Dr/Cr

Product Account

791

Adjustment Amount

Cr

Loan Accounts

Dr

Transaction Account

Loans Interest Income

To reflect a principal arrears interest credit adjustment, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loan Principal Arrears Interest Income’ Account is debited with the amount of interest to be adjusted using the principal arrears interest credit adjustment transaction (793), as follows: Txn Code

Amount

Dr/Cr

Product Account

793

Adjustment Amount

Cr

Loan Accounts

Dr

B–36

Transaction Account

Loan Principal Arrears Interest Income

3937 0408–930

Accounting Entries

To reflect an interest arrears interest credit adjustment, the GL ‘Loan Accounts ’ Account is credited and the GL ‘Loan Interest Arrears Interest Income’ Account is debited with the amount of interest to be adjusted using the interest arrears interest credit adjustment transaction (792), as follows: Txn Code

Amount

Dr/Cr

Product Account

792

Adjustment Amount

Cr

Loan Accounts

Dr

Transaction Account

Loan Interest Arrears Interest Income

Debit To reflect an interest debit adjustment, the GL ‘Loan Accounts’ Account is debited and the GL ‘Loans Interest Income’ Account is credited with the amount of interest to be adjusted using the loan interest debit adjustment transaction (891), as follows: Txn Code

Amount

Dr/Cr

Product Account

891

Adjustment Amount

Dr

Loan Accounts

Cr

Transaction Account

Loans Interest Income

To reflect a principal arrears interest debit adjustment, the GL ‘Loan Accounts’ Account is debited and the GL ‘Loan Principal Arrears Interest Income’ Account is credited with the amount of interest to be adjusted using the principal arrears interest debit adjustment transaction (893), as follows: Txn Code

Amount

Dr/Cr

Product Account

893

Adjustment Amount

Dr

Loan Accounts

Cr

3937 0408–930

Transaction Account

Loan Principal Arrears Interest Income

B–37

Accounting Entries

To reflect an interest arrears interest debit adjustment, the GL ‘Loan Accounts ’ Account is debited and the GL ‘Loan Interest Arrears Interest Income’ Account is credited with the amount of interest to be adjusted using the interest arrears interest debit adjustment transaction (892), as follows: Txn Code

Amount

Dr/Cr

Product Account

892

Adjustment Amount

Dr

Loan Accounts

Cr

Transaction Account

Loan Interest Arrears Interest Income

Fees Charged A fee transaction may be generated by a function e.g. an arrears event has a fee associated with it, that is identified by the relevant fee transaction code. To reflect a fee being charged against a loan account, the GL ‘Loan Accounts’ Account is debited and the GL ‘Loan Fee Income’ Account is credited with the fee using the appropriate fee transaction (6000 - 6999), as follows:

B–38

Txn Code

Amount

Dr/Cr

Product Account

60006999

Fee amount

Dr

Loan Accounts

Cr

Transaction Account

Loan Fee Income

3937 0408–930

Accounting Entries

Loan Repayment When a client makes a repayment, the repayment amount is credited to the loan account either through the front-office via the Deposits (TRDEP) or Deposits Interface (TTDEP) screen, for cash or cheque, or during the overnight process for standing order or direct debit processing by RTBATCHUPD. The repayment amount is then apportioned during the overnight process by RETLOANREP according to the system rules. By Cash To reflect a loan payment by cash, the GL ‘Loan Accounts’ Account is credited and the GL ‘Till’ Account is debited with the loan payment using the cash deposit (same currency) transaction (100), as follows: Txn Code

Amount

Dr/Cr

Product Account

100

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Till

By Cheque INTRA BANK To reflect a loan payment by intra bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Intra Bank Clearing’ Account is debited with the loan payment using the intra bank deposit transaction (110), as follows: Txn Code

Amount

Dr/Cr

Product Account

110

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Intra Bank Clearing

DOMESTIC BANK To reflect a loan payment by domestic bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Clearing’ Account is debited with the loan payment using the domestic bank deposit transaction (120), as follows: Txn Code

Amount

Dr/Cr

Product Account

120

Loan Payment

Cr

Loan Accounts

Dr

3937 0408–930

Transaction Account

Clearing

B–39

Accounting Entries

FOREIGN BANK To reflect a loan payment by foreign bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Nostro’ Account is debited with the loan payment using the foreign bank deposit transaction (125), as follows: Txn Code

Amount

Dr/Cr

Product Account

125

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

GL Contra Account

By Standing Order INTRA BANK To reflect a loan payment by intra bank standing order, the GL ‘Loan Accounts’ Account is credited and the GL ‘Suspense ’ Account is debited with the loan payment using the SO Deposit to intra bank account transaction (105). The system automatically generates the SO payment to ‘own bank’ transaction (205) to credit the GL ‘Suspense’ Account and debit the GL Product Account relating to the client account being debited (the 205 transaction definition of the product is used to ascertain the GL account), as follows: Txn Code

Amount

Dr/Cr

Product Account

105

Loan Payment

Cr

Loan Accounts

Dr 205

Dr

Transaction Account

GL Contra Account Receiving Accounts

Cr

GL Contra Account

DOMESTIC BANK To reflect a loan payment by domestic bank standing order, the GL ‘Loan Accounts’ Account is credited and the GL ‘Clearing’ Account is debited with the loan payment using the SO Deposit from domestic bank account transaction (106), as follows: Txn Code

Amount

Dr/Cr

Product Account

106

Loan Payment

Cr

Loan Accounts

Dr

B–40

Transaction Account

GL Contra Account

3937 0408–930

Accounting Entries

FOREIGN BANK To reflect a loan payment by foreign bank standing order, the GL ‘Loan Accounts’ Account is credited and the GL ‘Nostro’ Account is debited with the loan payment using the SO Deposit from foreign bank account transaction (107), as follows: Txn Code

Amount

Dr/Cr

Product Account

107

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

GL Contra Account

By Direct Debit INTRA BANK To reflect a loan payment by DD, the GL ‘Loan Accounts’ Account is credited and the GL ‘Suspense’ Account is debited with the loan payment using the DD Deposit from own bank account transaction (155). The system automatically generates the DD payment to ‘own bank’ transaction (255) to debit the GL ‘Suspense’ Account and credit the GL Product Account relating to the client account being credited (the 255 transaction definition of the product is used to ascertain the GL account), as follows: Txn Code

Amount

Dr/Cr

Product Account

155

Loan Payment

Cr

Loan Accounts

Dr 255

Dr Cr

3937 0408–930

Transaction Account

GL Contra Account Receiving Accounts GL Contra Account

B–41

Accounting Entries

Loan Early Repayment When a client makes an early repayment, the repayment amount is credited to the loan account either through the front-office via the Deposits (TRDEP) or Deposits Interface (TTDEP) screens for cash or cheque, or the Transfers (TRTFR) or Transfers Interface (TTTFR) screens for a transfer of funds from a deposit account. The repayment amount is then apportioned during the overnight process by RETLOANREP according to the system rules. By Cash To reflect a loan early payment by cash, the GL ‘Loan Accounts’ Account is credited and the GL ‘Till’ Account is debited with the loan amount using the cash deposit (same currency) transaction (100), as follows: Txn Code

Amount

Dr/Cr

Product Account

181

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Till

By Cheque INTRA BANK To reflect a loan early payment by intra bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Intra Bank Clearing’ Account is debited with the loan payment using the intra bank deposit transaction (182), as follows: Txn Code

Amount

Dr/Cr

Product Account

182

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Intra Bank Clearing

DOMESTIC BANK To reflect a loan early payment by domestic bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Clearing’ Account is debited with the loan payment using the domestic bank deposit transaction (183), as follows: Txn Code

Amount

Dr/Cr

Product Account

183

Loan Payment

Cr

Loan Accounts

Dr

B–42

Transaction Account

Domestic Clearing

3937 0408–930

Accounting Entries

FOREIGN BANK To reflect a loan early payment by foreign bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Nostro’ Account is debited with the loan payment using the foreign bank deposit transaction (184), as follows: Txn Code

Amount

Dr/Cr

Product Account

184

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

GL Contra Account

By Transfer Both the ‘to’ and ‘from’ transaction codes are entered as a 188. To reflect a loan early payment by transfer, the GL ‘Loan Accounts’ Account is credited and the GL ‘Current Accounts’ Account is debited with the loan payment using the transfer credit transaction (188), as follows: Txn Code

Amount

Dr/Cr

Product Account

188

Loan Payment

Cr

Loan Accounts

Dr 188

Dr Cr

3937 0408–930

Transaction Account

GL Contra Account Receiving Accounts GL Contra Account

B–43

Accounting Entries

Loan Early Closure When a client makes an early closure payment, the closure amount is credited to the loan account either through the front-office via the Deposits (TRDEP) or Deposits Interface (TTDEP) screens, for cash or cheque, or the Transfers and Bill payments (TRTFR) or Transfers Interface (TTTFR) screens for a transfer of funds from a deposit account. The closure amount is then apportioned during the overnight process by RETLOANREP – Retail Overnight Processing report according to the system rules. By Cash To reflect a loan closure amount by cash, the GL ‘Loan Accounts’ Account is credited and the GL ‘Till’ Account is debited with the loan amount using the cash deposit (same currency) transaction (100), as follows: Txn Code

Amount

Dr/Cr

Product Account

171

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Till

By Cheque INTRA BANK To reflect a loan closure amount by intra bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Intra Bank Clearing’ Account is debited with the loan payment using the intra bank deposit transaction (172), as follows: Txn Code

Amount

Dr/Cr

Product Account

172

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

Intra Bank Clearing

DOMESTIC BANK To reflect a loan closure amount by domestic bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Clearing’ Account is debited with the loan payment using the domestic bank deposit transaction (173), as follows: Txn Code

Amount

Dr/Cr

Product Account

173

Loan Payment

Cr

Loan Accounts

Dr

B–44

Transaction Account

Domestic Clearing

3937 0408–930

Accounting Entries

FOREIGN BANK To reflect a loan closure amount by foreign bank cheque, the GL ‘Loan Accounts’ Account is credited and the GL ‘Nostro’ Account is debited with the loan payment using the foreign bank deposit transaction (174), as follows: Txn Code

Amount

Dr/Cr

Product Account

174

Loan Payment

Cr

Loan Accounts

Dr

Transaction Account

GL Contra Account

By Transfer Both the ‘to’ and ‘from’ transaction codes are entered as a 178. To reflect a loan closure amount by transfer, the GL ‘Loan Accounts’ Account is credited and the GL ‘Current Accounts’ Account is debited with the loan payment using the transfer credit transaction (178), as follows: Txn Code

Amount

Dr/Cr

Product Account

178

Loan Payment

Cr

Loan Accounts

Dr 178

Dr Cr

3937 0408–930

Transaction Account

GL Contra Account Receiving Accounts GL Contra Account

B–45

Accounting Entries

Change of Status to Non Performing Loans When a loan is deemed to be non-performing, the accrued and settled/charged unpaid interest is moved in the GL to indicate the loan is non-performing, by a ‘non-performing’ arrears event being processed during the overnight process, AMCSTLUPD, as described below. 1.

Interest Accrued:

Txn Code

Amount

Dr/Cr

Product Account

850 (Rev)

Interest accrued on Loan PTD

Cr

Accrued Interest Receivable on Loans

and

Dr

Accrued Interest Receivable on NonPerforming Loans

853 Dr

Loans Interest Income

Cr

852 (Rev) and

Interest accrued on Loan Principal Arrears PTD

Cr

Non-Performing Loans Suspended Interest Income Accrued Interest Receivable on Loan Principal Arrears

Dr

Accrued Interest Receivable on NonPerforming Loan Principal Arrears

855

Dr

Loan Principal Arrears Interest Income

Cr

851 (Rev) and

Interest accrued on Loan Interest Arrears PTD

Cr

Non-Performing Principal Arrears Suspended Interest Income Accrued Interest Receivable on Loan Interest Arrears

Dr

Accrued Interest Receivable on NonPerforming Loan Interest Arrears

854

Dr Cr

B–46

Transaction Account

Loan Interest Arrears Interest Income

Non-Performing Interest Arrears Suspended Interest Income

3937 0408–930

Accounting Entries

2.

Interest Settled Unpaid:

Txn Code

Amount

Dr/Cr

Product Account

850,

Interest Settled Unpaid on Loan

Dr

Loans Interest Income

853

Cr Non-Performing Loans Suspended Interest Income

and 870 852, 855

Principal Arrears Interest Settled Unpaid on Loan

Dr

Interest Arrears Interest Settled Unpaid on Loan

Dr

Cr

Loan Principal Arrears Interest Income Non-Performing Principal Arrears Suspended Interest Income

and 874 851, 854 and 872

3937 0408–930

Transaction Account

Cr

Loan Interest Arrears Interest Income Non-Performing Interest Arrears Suspended Interest Income

B–47

Accounting Entries

Non Performing Loan Activities Interest Interest Accrual The system automatically accrues interest daily for each non-performing loan account during the overnight process. Loan Interest To reflect the interest accrued on a non-performing loan, the GL ‘Accrued Interest Receivable on a Non-performing Loans’ Account is debited and the GL ‘a Non-performing Loans Suspended Interest Income’ Account is credited with the amount of interest accrued using the nonperforming interest accrual transaction (853), as follows: Txn Code

Amount

Dr/Cr

Product Account

853

Interest accrued for day on Loan

Dr

Accrued Interest Receivable on a Nonperforming Loans

Cr

Transaction Account

Non-performing Loans Suspended Interest Income

Principal Arrears Interest To reflect the interest accrued on principal arrears for a non-performing loan, the GL ‘Accrued Interest Receivable on a Non-performing Loan Principal Arrears’ Account is debited and the GL ‘Non-performing Loan Principal Arrears Suspended Interest Income’ Account is credited with the amount of interest accrued using the non-performing interest accrual transaction (855) as follows: Txn Code

Amount

Dr/Cr

Product Account

855

Interest accrued for day on Principal Arrears

Dr

Accrued Interest Receivable on Nonperforming Loan Principal Arrears

Cr

B–48

Transaction Account

Non-performing Loan Principal Arrears Suspended Interest Income

3937 0408–930

Accounting Entries

Interest Arrears Interest To reflect the interest accrued on interest arrears for a non-performing loan, the GL ‘Accrued Interest Receivable on Non-performing Loan Interest Arrears’ Account is debited and the GL ‘Non-performing Loan Interest Arrears Suspended Interest Income’ Account is credited with the amount of interest accrued using the non-performing interest accrual transaction (854), as follows: Txn Code

Amount

Dr/Cr

Product Account

854

Interest accrued for day on Interest Arrears

Dr

Accrued Interest Receivable on Nonperforming Loan Interest Arrears

Cr

Transaction Account

Non-performing Loan Interest Arrears Suspended Interest Income

Interest Settlement The system automatically settles interest at the defined settlement period for each non-performing loan account during the overnight process (RETLOANREP). Interest is settled/charged to the loan account as ‘settled unpaid’ that may be paid by the client when the payment apportionment processing is performed later during the overnight process. Loan Interest To reflect the settlement of interest to a loan account, the GL ‘ Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on Non-Performing Loans’ Account is credited with the amount of interest accrued for the period using the interest settlement transactions (860 and 870), as follows: Txn Code

Amount

Dr/Cr

Product Account

860

Interest accrued for period on Loan

Dr

Loan Accounts

870

Cr Dr Cr

3937 0408–930

Transaction Account

Accrued Interest Receivable on Loans Accrued Interest Receivable on Loans Accrued Interest Receivable on NonPerforming Loans

B–49

Accounting Entries

Principal Arrears Interest To reflect the settlement of interest accrued on principal arrears to a loan account, the GL ‘Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on Non-Performing Loan Principal Arrears’ Account is credited with the amount of interest accrued for the period using the interest settlement transactions (864, 874) as follows: Txn Code

Amount

Dr/Cr

Product Account

864

Interest accrued for period on Principal Arrears

Dr

Loan Accounts

874

Cr

Dr

Transaction Account

Accrued Interest Receivable on Loan Principal Arrears Accrued Interest Receivable on Loan Principal Arrears

Cr

Accrued Interest Receivable on NonPerforming Loan Principal Arrears

Interest Arrears Interest To reflect the settlement of interest accrued on interest arrears to a non-performing loan account, the GL ‘Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on NonPerforming Loan Interest Arrears’ Account is credited with the amount of interest accrued for the period using the interest settlement transactions (862, 872), as follows: Txn Code

Amount

Dr/Cr

Product Account

862

Interest accrued for period on Interest Arrears

Dr

Loan Accounts

872

Cr

Dr

Cr

B–50

Transaction Account

Accrued Interest Receivable on Loan Interest Arrears Accrued Interest Receivable on Loan Interest Arrears Accrued Interest Receivable on NonPerforming Loan Interest Arrears

3937 0408–930

Accounting Entries

Interest Reduction / Refund For non-performing loans, interest may be: •

reduced for interest that has been settled but unpaid for the last and previous periods

•

reduced for interest that has been accrued for the current period

•

refunded for interest that has been settled and paid by the client

To reduce of refund interest, the relevant information is entered using the Interest Reduction / Refund (AMRT2) screen. Interest Reduction for Settled Unpaid Interest To reflect the reduction in interest settled but unpaid by the client on a non-performing loan, the GL ‘ Loan Accounts’ Account is credited and the GL ‘Non-Performing Loans Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing loan interest adjustment transaction (795), as follows: Txn Code

Amount

Dr/Cr

Product Account

795

Reduction Amount

Cr

Loan Accounts

Dr

Transaction Account

Non-Performing Loans Suspended Interest Income

To reflect the reduction in interest settled but unpaid by the client on principal arrears for a nonperforming loan, the GL ‘Loan Accounts’ Account is credited and the GL ‘Non-Performing Loan Principal Arrears Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing principal arrears interest adjustment transaction (797), as follows: Txn Code

Amount

Dr/Cr

Product Account

797

Reduction Amount

Cr

Loan Accounts

Dr

3937 0408–930

Transaction Account

Non-Performing Loan Principal Arrears Suspended Interest Income

B–51

Accounting Entries

To reflect the reduction in interest settled but unpaid by the client on interest arrears for a nonperforming loan, the GL ‘Loan Accounts’ Account is credited and the GL ‘Non-Performing Loan Interest Arrears Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing interest arrears interest adjustment transaction (796), as follows: Txn Code

Amount

Dr/Cr

Product Account

796

Reduction Amount

Cr

Loan Accounts

Dr

Transaction Account

Non-Performing Loan Interest Arrears Suspended Interest Income

Interest Reduction for Accrued Interest To reflect the reduction in interest accrued for period for a non-performing loan, the GL ‘NonPerforming Accrued Interest Receivable on Loans’ Account is credited and the GL ‘NonPerforming Loans Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing loan interest accrual transaction (853), as follows: Txn Code

Amount

Dr/Cr

Product Account

853

Reduction Amount

Cr

Accrued Interest Receivable on NonPerforming Loans

Dr

B–52

Transaction Account

Non-Performing Loans Suspended Interest Income

3937 0408–930

Accounting Entries

To reflect the reduction in interest accrued for period on principal arrears for a non-performing loan, the GL ‘Accrued Interest Receivable on Non-Performing Loan Principal Arrears’ Account is credited and the GL ‘Non-Performing Loan Principal Arrears Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing principal arrears interest accrual transaction (855), as follows: Txn Code

Amount

Dr/Cr

Product Account

855

Reduction Amount

Cr

Accrued Interest Receivable on NonPerforming Loan Principal Arrears

Dr

Transaction Account

Non-Performing Loan Principal Arrears Suspended Interest Income

To reflect the reduction in interest accrued for period on interest arrears for a non-performing loan, the GL ‘Accrued Interest Receivable on Non-Performing Loan Interest Arrears’ Account is credited and the GL ‘Non-Performing Loan Interest Arrears Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the non-performing interest arrears interest accrual transaction (854), as follows: Txn Code

Amount

Dr/Cr

Product Account

854

Reduction Amount

Cr

Accrued Interest Receivable on NonPerforming Loan Interest Arrears

Transaction Account

Non-Performing Loan Interest Arrears Suspended Interest Income

Dr

Interest Refund To reflect the refund of interest paid by a client for a non-performing loan, the GL ‘Loan Accounts’ Account is credited and the GL ‘Loans Interest Income’ Account is debited with the amount of interest to be refunded, using the refund interest paid transaction (790), as follows: Txn Code

Amount

Dr/Cr

Product Account

790

Refund Amount

Cr

Loan Accounts

Dr

3937 0408–930

Transaction Account

Loans Interest Income

B–53

Accounting Entries

Loan Payment Loan payments received once a loan is non-performing are processed as if the loan is performing.

Final Demand After the loan or overdraft becomes non-performing, the bank can decide to demand all the owing monies by a ‘final demand’ arrears event being processed during the overnight process, using the AMCSTLUPD – Retail Arrears Management Overnight Processing report. After the Final Demand event has been processed, interest is accrued using a new interest penalty rate on the sum of the outstanding principal and principal arrears. With interest charged on interest arrears continuing as prior to the final demand. The accrued interest and suspended interest income are reflected in a new GL account to reflect interest after final demand. To reflect a ‘final demand’ event in the GL, the Interest Accrued for the period to date, for the loan, principal arrears and interest arrears is settled as described in under ‘Non-Performing Loan Activities’ - Interest Settlement’. As the client’s loan account balances are reflected in the GL as one balance, no GL movements are required to reflect that the Principal Outstanding balance is moved to Principal Arrears balance.

Provisions To make or remove a provision, the relevant information is entered using the Arrears Management - Provision and Write-Off Maintenance (AMRWM) screen. A future requirement is for the GL transactions to be automatically generated and processed (see appendix A for details). Note: The GL transactions are not automatically generated and will need to be manually entered using the back-office functionality, Batch Header (BHEAD), General Ledger Debit (GLDR), General Ledger Credit (GLCR) and Batch Close (BCLOS) screens. Make a Provision To reflect a provision for a non-performing loan that may not be paid, the GL ‘Loan Provisions’ Account is credited using the General Ledger Credit (GLCR) screen and the GL ‘Loan Provisions Charge’ Account is debited using the General Ledger Debit (GLDR) screen with the provision amount, as follows: Amount

Dr/ Cr

GL Account

Provision Amount

Cr

Loan Provisions

Dr

B–54

GL Account

Loan Provisions Charge

3937 0408–930

Accounting Entries

Remove a Provision To reflect that a provision is no longer required for a non-performing loan, the GL ‘Loan Provisions’ Account is debited using the General Ledger Debit (GLDR) screen and the GL ‘Loan Provisions Charge’ Account is credited using the General Ledger Credit (GLCR) screen with the provision amount, as follows: Amount

Dr/ Cr

GL Account

Provision Amount

Dr

Loan Provisions

Cr

GL Account

Loan Provisions Charge

Write-off (Partial and Full) To partially or fully write-off a loan, the relevant information is entered using the Arrears Management - Provision and Write-Off (AMRWM) screen. A future requirement is for the GL transactions to be automatically generated and processed (see appendix A for details). Note: The required transactions are not automatically generated and will need to be manually entered using the back-office functionality, as described below Full Write-Off To reflect a full write-off, interest is settled using the GL transactions specified in ‘NonPerforming Loan Activities’ – Interest Settlement. The user must then manually process the full write-off by: •

If any provisions have been made these must be removed, using the process described under ‘Remove a Provision’.

•

Using the back-office batch transaction entry screens to write-off the loan amount by processing a loan write-off transaction (179) using the Batch Transaction Details (RBTDE) screen: Txn Code

Amount

Dr/ Cr

Product Account

179

Loan Balance

Cr

Loan Accounts

Dr

•

Transaction Account

Loan Write-off

The loan may then be closed using the Loan Early Closure (RLECM) screen to schedule the closure during the overnight process.

3937 0408–930

B–55

Accounting Entries

Partial Write-Off To reflect a partial write-off the user must manually process the partial write-off by: •

If any provisions have been made these may be removed, using the process described under ‘Remove a Provision’.

•

Using the back-office batch transaction entry screens to write-off the loan amount by processing a loan write-off transaction (179) using the Batch Transaction Details (RBTDE) screen: Txn Code

Amount

Dr/ Cr

Product Account

179

Write-Off Amount

Cr

Loan Accounts

Dr

Transaction Account

Loan Write-off

Change of Status to Performing Loans If a loan was changed to non-performing in error or a client starts making payments, the loan status may be changed back to performing. In that case, all the GL transactions that were generated and processed when the loan was made ‘non-performing’ are generated and processed to move the accrued and settled interest GL account balances from non-performing to performing. Each transaction listed as a credit under ‘Status Change to Non-Performing Loan’ is generated and processed as a debit and each transaction listed as a debit is generated and processed as a credit.

B–56

3937 0408–930

Accounting Entries

After Final Demand Loan Activities All activities for a Non-Performing Loan may occur, for which the GL updates described in the previous section will be processed except for interest accrual, interest settlement and interest reduction/refund. These activities will be satisfied by the requirements described below.

Interest Interest Accrual To reflect the interest accrued on the after final demand balance and interest on interest arrears, the GL ‘Accrued Interest Receivable on a Non-performing Loan After Final Demand’ Account is debited and the GL ‘Non-performing Loan After Final Demand Suspended Interest Income’ Account is credited with the amount of interest accrued using the after final demand interest accrual transaction (856) as follows: Txn Code

Amount

Dr/ Cr

Product Account

856

Interest accrued for day on After Final Demand balance

Dr

Accrued Interest Receivable on Nonperforming Loan After Final Demand

plus

Cr

Transaction Account

Non-performing Loan After Final Demand Suspended Interest Income

Interest accrued for day on Interest Arrears

Interest Settlement To reflect the settlement of interest accrued after final demand to a non-performing loan account after final demand, the GL ‘Non-Performing Loan Accounts’ Account is debited and the GL ‘Accrued Interest Receivable on Non-Performing Loan After Final Demand’ Account is credited with the amount of interest accrued for the period using the after final demand interest settlement transaction (866) as follows:

Txn Code

Amount

Dr/ Cr

Product Account

866

Interest accrued for period After Final Demand

Dr

Loan Accounts

3937 0408–930

Cr

Transaction Account

Accrued Interest Receivable on NonPerforming Loan After Final Demand

B–57

Accounting Entries

Interest Reduction / Refund For non-performing loans after final demand, in addition to the interest that may be reduced and refunded for a non-performing loan prior to final demand, interest may be: •

reduced for after final demand interest that has been settled but unpaid

•

reduced for after final demand interest that has been accrued for the period

These are each described below. Interest Reduction for After Final Demand Settled Unpaid Interest To reflect the reduction in interest settled but unpaid by the client on after final demand interest for a non-performing loan, the GL ‘Loan Accounts’ Account is credited and the GL ‘NonPerforming Loan After Final Demand Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the loan adjustment transaction (794), as follows: Txn Code

Amount

Dr/ Cr

Product Account

794

Reduction Amount

Cr

Loan Accounts

Dr

Transaction Account

Non-Performing Loan After Final Demand Suspended Interest Income

Interest Reduction for After Final Demand Accrued Interest To reflect the reduction in interest accrued for period on after final demand for a non-performing loan, the GL ‘Accrued Interest Receivable on Non-Performing Loan After Final Demand’ Account is credited and the GL ‘Non-Performing Loan After Final Demand Suspended Interest Income’ Account is debited with the amount of interest to be reduced using the after final demand interest accrual transaction (856), as follows: Txn Code

Amount

Dr/ Cr

Product Account

856

Reduction Amount

Cr

Accrued Interest Receivable on NonPerforming Loan After Final Demand

Dr

B–58

Transaction Account

Non-Performing Loan After Final Demand Suspended Interest Income

3937 0408–930

Accounting Entries

Loan Payment Loan payments received once a loan is non-performing and after final demand, are processed as if the loan is performing.

3937 0408–930

B–59

Accounting Entries

Other Bureau De Change Bureau De Change transactions would normally be posted as a summary at the end of day. By Cash, for Cash Txn Code

Amount

Dr/ Cr

100

Inward Currency

Dr Cr

500

Inward Currency

Dr Cr

510

Outward Currency

Dr Cr

Product Account

Transaction Account Till

Branch Cash Account Branch Cash Account Currency Position Currency Position Branch Cash Account

200

Outward Currency

Dr Cr

Branch Cash Account

845

Charge

Dr Cr

Branch Cash Account

Till Relevant Charges

By Account, for cash Txn Code

Amount

Dr/ Cr

Product Account

260

Inward Currency

Dr Cr

Client Account

160

B–60

Inward Currency

Dr Cr

500

Inward Currency

Dr Cr

510

Outward Currency

Dr Cr

Transaction Account

GL Contra Account GL Contra Account Branch Cash Account Branch Cash Account Currency Position Currency Position Branch Cash Account

200

Outward Currency

Dr Cr

Branch Cash Account

845

Charge

Dr Cr

Branch Cash Account

Till Relevant Charges

3937 0408–930

Accounting Entries

By Cash, for Account Txn Code

Amount

Dr/ Cr

100

Inward Currency

Dr Cr

500

Inward Currency

Dr Cr

510

Outward Currency

Dr Cr

260 160 845

Outward Currency Outward Currency Charge

Dr Cr Dr Cr

Product Account

Transaction Account Till

Branch Cash Account Branch Cash Account Currency Position Currency Position Branch Cash Account Branch Cash Account Contra Account Contra Account Client Account

Dr Cr

Branch Cash Account Relevant Charges

By Account, for Account Txn Code

Amount

Dr/ Cr

Product Account

260

Inward Currency

Dr Cr

Client Account

160

Inward Currency

Dr Cr

500

Inward Currency

Dr Cr

510

Outward Currency

Dr Cr

260

Outward Currency

Dr Cr

160

Outward Currency

Dr Cr

845

3937 0408–930

Charge

Dr Cr

Transaction Account

Contra Account Contra Account Branch Cash Account Branch Cash Account Currency Position Currency Position Branch Cash Account Branch Cash Account Contra Account Contra Account Client Account Branch Cash Account Relevant Charges

B–61

Accounting Entries

Retail Cross Accounting Centre Postings If a transaction performed at one accounting centre is actioned against a real account held at another accounting centre, then cross accounting centre postings are required to balance the general ledger at each accounting centre. For example, the following postings are required for a cash deposit of £100 made at one accounting centre for a current account held at another accounting centre: •

Client’s account is credited with £100

•

Product general ledger account that represents the current account product is credited with £100 at the accounting centre of the current account

•

Transaction general ledger account that represents the cash till is debited with £100 at the accounting centre where the transaction took place

To enable the general ledger of each accounting centre to balance, the following additional postings are generated by the system: •

At the accounting centre holding the client’s account, the general ledger account that represents cross accounting centre debits is debited with £100

•

At the accounting centre at which the transaction took place, the general ledger account that represents cross accounting centre credits is credited with £100

The general ledger accounts to be used for the credits and debits between specified accounting centres is defined using the Cross Accounting Centre Rules (ACRLM) screen, described in the Guide to Setting Up the Retail System. The following table shows an example of a retail cross accounting centre posting. A GBP cash deposit in accounting centre A to an account based in accounting centre B. The amount of the transfer is £100. Trn

100

Account

Till

Centre A

Centre B

Dr

Cr

Dr

Cr

£

£

£

£

100

Product Account

100

Accounting Centre Control Accounting Centre Control

B–62

100 100

3937 0408–930

Accounting Entries

Retail Cross Currency Postings If a transaction is performed in one currency is to be actioned against a real account held in another currency, then the transactions used need to be set up to pass through an Other Currencies Control Account. Unlike the Cross Accounting Centre Postings, there is no transaction raised automatically. Instead the balancing is made through the transaction set up. Retail transactions are defined on the Retail Transaction Definition screen (TRDFM). For a transaction to allow a cross currency transaction, the Cross Currency Transaction indicator must on. The Default GL Transaction Account, on (TRDFM) should be defined as the Other Currencies Control Account. The ledgers will always balance, because all cross currency transactions work in pairs. Each transaction is in the currency of the client / internal account it represents, thus when moving between the two accounts there is a debit and credit posting in each currency. The GL Transaction Account for both of the transactions in the pair need to be the same Other Currencies Control Account, so that on consolidation to base currency, the two amounts will contra leaving only the effect on the Product Accounts. Any differences in the Other Currencies Control Account due to subsequent movements in the exchange rate or a different rate being used are profits and losses on exchange. Example: A cross currency transfer from an account in GBP to an account in USD. The amount of the transfer is £100 at an exchange rate of 1.4 £/$.

Trn

261

Account

Product Account Other Currencies Control

161

Other Currencies Control Product Account

3937 0408–930

Centre A

Centre A

Dr

Cr

Dr

Cr

£

£

$

$

100 100

140 140

B–63

Accounting Entries

Retail Cross Currency, Cross Accounting Centre Postings Should a cross currency transaction be between two accounts in different accounting centres, the same rules apply. The Transaction account is posted to the Centre of the Teller that performed the transaction, thus that centre receives the profit or loss on exchange. The following table contains an example of this type of transaction. The example is of a cross currency transfer from an account in GBP at Centre A to an account in USD at Centre B. The Teller is at Centre A and the amount of the transfer is £100 at an exchange rate of 1.4 £/$.

Trn

261

Account

Product Account Other Currencies Control

161

Other Currencies Control

Centre A

Centre B

Dr

Cr

Dr

Cr

Dr

Cr

Dr

Cr

£

£

$

$

£

£

$

$

100 100

140

Product Account

140

Accounting Centre Control Accounting Centre Control

B–64

140 140

3937 0408–930

Index A Accounting Centre Accounts screen Description of, 6-3 Example of, 6-4 Accounting Entries, B-1 Automatic Charge, 5-4

B Back Office, 1-6 Back Valued Transactions, 1-7 Balance Inquiry / Passbook Update interface screen Description of, 3-30 Example of, 3-30 Batch Transaction Details screen Description of, 4-5 Example of, 4-6 Bill Payments, 2-10 Transaction codes, A-5 BRACA screen, 6-3 to 6-4 Bureau de change Transaction codes, A-6 Bureau de Change Movements, 3-27 to 3-28 Bureau de Change Movements interface screen Description of, 3-28 Example of, 3-28

C Cash Depositing, 2-3 Charges, 1-8, 5-1, 5-2, 5-3 Transaction codes, A-12 Cheque negotiation Transaction codes, A-6 Cheque Negotiation (TRCNG) Description of, 3-14 Example of, 3-15 Cheque Negotiation interface screen Description of, 3-26 Example of, 3-27

3937 0408–930

Cheque negotiations, 3-25 to 3-27 Cheque sales Transaction codes, A-7 Cheque Sales, 3-28 to 3-29 Cheque Sales (TRCSS) Description of, 3-16 Example of, 3-17 Cheque Sales interface screen Description of, 3-29 Example of, 3-29 Cheques Clearing, 2-3 Depositing, 2-3 Withdrawals, 2-8 Clearing Domestic bank cheques, 2-5 Foreign bank cheque, 2-7 Intra bank cheques, 2-4 Cross Accounting Centre Transaction codes, A-13

D Definition of field names, 7-1 Deposits, 3-19 Transaction codes, A-2 Deposits (TRDEP) Description of, 3-7 Example of, 3-8 Deposits interface screen Description of, 3-19 Example of, 3-19 Direct Entry Transactions, 3-6

E Event Based Charges, 5-3

F Field Names Definition, 7-1 Front Office, 1-2

Index-1

Index

I Item Charge, 5-2

L Loan Drawdown interface screen Description of, 3-20 Example of, 3-20 Loan Drawdowns, 3-3

M Manual Charge, 5-3

N Notice accounts, 3-3

O Other Asset Transactions for Loans Transaction codes, A-9 Other Asset Transactions for Non-Loans Transaction codes, A-9 Other Liability Transactions for Loans Transaction codes, A-8 Other Liability Transactions for Non-Loans Transaction codes, A-8

P Passbook accounts, 1-4, 1-8 Periodic Charge, 5-3

R RBTCL screen, 4-7 RBTDE screen, 4-5 to 4-6 RBTHD screen, 4-3 to 4-4 Retail Batch Closure screen Description of, 4-7 Example of, 4-7

Index-2

Retail Batch Opening screen Description of, 4-3 Example of, 4-4 Retail Transaction Definition screen Description of, 2-2 Example screen, 2-2

S Security, 1-4, 1-8

T Transaction codes Bill Payments, A-5 Bureau de change, A-6 Charges, A-12 Cheque negotiation, A-6 Cheque sales, A-7 Cross Accounting Centre, A-13 Deposits, A-2 Other Asset Transactions for Loans, A-9 Other Asset Transactions for Non-Loans, A-9 Other Liability Transactions for Loans, A-8 Other Liability Transactions for Non-Loans, A-8 Withdrawals, A-4 Transaction Codes, A-1 to A-12 Transaction types Code tables, A-1 to A-12 Introduction, A-1 Transactions Direct Entry Screens, 3-6 Transfers, 3-22 to 3-25 Transfers and Bill Payments (TRTFR) Description of, 3-11 Example of, 3-13 Transfers interface screen Description of, 3-23 Example of, 3-23 TRCNG screen, 3-14 TRCSS screen, 3-16 TRDEP screen, 3-7 TRDFM screen, 2-2 TRTFR screen, 3-11 TRWDR screen, 3-9 TTBDC interface screen, 3-27 to 3-28 TTBPU interface screen, 3-30 TTCNG interface screen, 3-26 to 3-27 TTCSS interface screen, 3-28 to 3-29 TTDEP interface screen, 3-19

3937 0408–930

Index

TTLDD interface screen, 3-20 TTTFR interface screen, 3-23 to 3-25 TTWDR interface screen, 3-19 to 3-22 Turnover Charge, 5-2

V Validation Errors Effect of Overriding, 1-4, 1-8, 5-4 Validation of Transactions, 1-7

3937 0408–930

W Withdrawals, 3-19 to 3-22 Transaction codes, A-4 Withdrawals (TRWDR) Description of, 3-9 Example of, 3-10 Withdrawals interface screen Description of, 3-21 Example of, 3-21

Index-3

Index

Index-4

3937 0408–930