0% found this document useful (0 votes)
194 views6 pages

T24TEST

1. The transaction will breach the limit on account 89354 category 10001 by $991000. This category has already exceeded its limit by $989500. 2. No notice was given for a withdrawal from account 89354. 3. Various account numbers, transaction codes, and currency codes are listed with no other context provided.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
194 views6 pages

T24TEST

1. The transaction will breach the limit on account 89354 category 10001 by $991000. This category has already exceeded its limit by $989500. 2. No notice was given for a withdrawal from account 89354. 3. Various account numbers, transaction codes, and currency codes are listed with no other context provided.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 6

89354

CURR.89354.0000001
Transaction will breach the till 1000 category 10001 limit by USD 991000
Till 1000 category 10001 has exceeded the limit by USD 989500
ACCOUNT 89354 - NO NOTICE GIVEN FOR WITHDRAWAL
TT20108B02HL

localhost.localdomain
javascript:help("EB.TABLE.PROCEDURES","","","issueToken");
SORT FBNK.ACCOUNT BY CUSTOMER BREAK-ON "'P'" CUSTOMER TOTAL WORKING.BALANCE DET-
SUPP
### ### ##
Regular SB Accounts ( Non-Base branches

### ### ### ### ### #### ###

## ###

1. Mask = ##### - #####. No 1234 displayed as 1234

2. Mask = ##### - #####. No.1234567 displayed as 12 - 34567

3. Mask = R##### - #####. No. 1234 displayed as 00000 - 01234

4. Mask = R##### - #####. No. 1234567 displayed as 00012 - 34567

### #### #
###-#### #### ####

100112 JOINT
TT20108L12FC

14016 AL Position Account Category


EURUSD1401600010001

AC NO 11018 --100282
FT20108RY6NN
FT/20108/RY6NN
192963889211947.00
192963889211947.000002

USD DEBIT
EUR CREDIT

EUR-USD-14016-0001-0001 DEBIT
USD-EUR-14016-0001-0001 CREDIT

ENQ TXN.ENTRY

‫من العمبل دوالر‬


‫الى ح صرفة دوالر‬
‫من ح صرافة مقابل الدوالر بالفرتك‬
‫الى العمبل فرنك‬
‫من العميل يورو‬
‫الى يورو دوالر‬

‫من ح اليورو مقابل الدوالر بالمحلي‬


‫الى العميل دوالر‬

error "Report View - cannot read 15108002463344800 from &HOLD&"


BROWSER.PREFERENCES
The valid skin names are defined in BROWSER.PARAMETERS.

EB.SYSTEM.SUMMARY
RVN

USD-14213-0001-0001 AL IF Revaluation

LIMIT 129120.0008100.01

file:///C:/R20_AMR_ClientDocumentation_V1/R20_AMR_ClientDocumentation_V1_Unzip/Solu
tions/T24_Transact/Accounts/AC/Accounts/AccountMaintenance/Working_With.htm

EB.CONTRACT.ENTRIES

TRANSACTION.CHARGE

TRANSACTION ---UNIT.COST

An introduction
AC-Accounts
CO-Collaterals
DE-Delivery
DX-Derivatives
EB-Core Accounting
FD-Fiduciary
FR-FRA
FT-Funds Transfer
FX-Forex
LD_Loans and Deposits
MC-Multicompany
MD-Misc. Deals
MM-Money Market
PD-Past Due
PM-Position Management
RP-Repo
SC-Securities
SW-Swap

CLOSE 19698
11223 MOVE BALANCE
Txn Complete: 19698 16:03:20 02 NOV 2020 ACCOUNT.CLOSURE,INPUT I

GENERAL.CHARGE
FT.COMMISSION.TYPE
AC.CHARGE.REQUEST
TRANSACTION.CHARGE
IC.CHARGE.PRODUCT and IC.CHARGE.

As a first step, charges rules for a Bank are defined in tables like
TRANSACTION.CHARGE, HIGHEST.DEBIT, TURNOVER.DEBIT,
NUMBER.OF.DEBIT, GOVERNMENT.MARGIN, DEBIT.INT.ADDON,
ACCT.STATEMENT.CHARGE, BALANCE.REQUIREMENT,
NUMBER.OF.CREDIT, TURNOVER.CREDIT and
INTEREST.STATEMENT.

Value date is used to update the balances for interest purposes.


Whereas Exposure date is the date on which the available balance will be credited
and is given value for credit limit position processing.

18 APR 2020
193008060662618.00
100592 20958

TEC.ITEMS
This is the main table where all the items/events that may be monitored are
defined. FOR SMS OR EMAL
Create a record in EB.ALERT.REQUEST for the event ACCOUNT.DEBITED.

129120.0008100.01

LI20108XLLS3
129120.0000100.01

100100.0008100.01

Introduction to Account Interest and Charges


The bank may impose charges for maintaining and servicing the accounts.
These charges may be classified broadly as interest based charges and ledger fee
or transaction based charges.
These charges may be applied monthly, quarterly, half-yearly or annually.

Group specific interest and charges are configured using GROUP.DEBIT.INT (GDI) and
GROUP.CREDIT.INT (GCI) applications.
Account specific interest and charges are configured using ACCOUNT.DEBIT.INT (ADI)
and ACCOUNT.CREDIT.INT (ACI) applications.

Defines fixed or floating interest rate.


Floating interest rate refers to BASIC.RATE.TEXT and BASIC.INTEREST application to
get the rates.
The float or margin can be added or subtracted from the basic interest rate to
give the applicable floating rate.

BASIC.RATE.TEXT
This table defines Descriptions of the Basic Interest Rate table IDs to enable the
user to identify each one of them easily.
Each Description must be defined prior to creating Rates records for the
corresponding ID in the BASIC.
INTEREST rate table and will be used as the enrichment to the corresponding ID when
it is displayed or printed during T24 processing.
Up to 999 descriptions may be defined.

BASIC.INTEREST
This table allows various frequently used floating Rates, e.g. Base Rate, Prime
Rate, Overnight Rate etc.,
to be defined separately for each Currency and stored in a central place where
they can be accessed by T24 Applications as required.

GROUP.DEBIT.INT
The Group Debit Interest Table allows the specification of a calculation method of
debit interest for groups of accounts and
provides the link to the GENERAL.CHARGE table where the charges applicable to the
same groups of Accounts are specified.
Account groups are determined automatically on the basis of Customer and Account
details such as Residence, Sector, Account Category and Currency.
At the time of Account input, reference is made to ACCT.GEN.CONDITION and
CONDITION PRIORITY (Ref: General Tables) tables.
From these, a General Condition code is derived for later access to the
GROUP.DEBIT.INT table.
(For further information, see the ACCT.GEN.Condition and CONDITION.PRIORITY
tables.)

- Interest can be calculated on a Daily, Average, or Highest balance basis using


value dated balances.

- Rates can be fixed or linked to Basic Rates plus or minus a Margin.

- Different rates can be specified for different balance levels and may be linked
to the same or different basic rates. The rates may apply to the whole of the
balance or to the part between two balance levels.

- Using Group Level Conditions, it is possible to use the limits on individual


Accounts as the first level for debit interest so that one rate can be charged up
to the limit on any Account and another rate when the limit has been exceeded.
(Limits on individual Accounts are specified in the ACCOUNT.DEBIT.LIMIT Table.) In
this case a maximum of 2 rates may be specified.

Where special debit interest conditions apply to a specific account, reference


should be made to the table ACCOUNT.DEBIT.INT table.

190115 89117

BALANCE.REQUIREMENT charge

To collect every month end BALANCE.REQUIREMENT charge the follwing setup needs to
done.
1.Set the field CHARGE.CALCULATION as "M" in respective company record.
2.Create BALANCE.REUIREMENT record and set the fields BALANCE.TYPE as
AVERAGE/MINIMUM & Set the required amount should be mainatin in the field
DEFAULT.BAL.AMT.
3.Attach the above BALANCE.REQUIREMENT record to GENERAL.CHARGE record.
4.Attach the above GENERAL.CHARGE in the field "CHARGE.KEY" of an
GROUP.DEBIT.INT/ACCOUNT.DEBIT.INT record.
As per T24 functionality, BALANCE.REQUIREMENT charge will be applied when specified
balance is not maintained based on BALANCE.TYPE field defined in
BALANCE.REQUIREMENT record.
when we define the BALANCE.REQUIREMENT charge setup in GENERAL.CHARGE record and
the same is attached in the field "CHARGE.KEY" of an GROUP.DEBIT.INT /
ACCOUNT.DEBIT.INT record which implies that, the charge will be applicable to the
group of accounts / specific Account.

CONDITION.PRIORITY
This application defines the fields from CUSTOMER and ACCOUNT are to be used for
setting various group conditions.
The bank must work out which criteria are required for use particularly for ACCOUNT
conditions.

ACCT.GEN.CONDITION
Every group of account records that the Bank wants to classify is defined in this
application.
This classification is based on the conditions defined in the application
CONDITION.PRIORITY.
The purpose of this table is to define the rules for grouping together account
records for which the same interest and charges conditions apply.
Conditions for the calculation and application of interest and charges may then be
specified for the groups and overridden with special conditions
for individual account records.

Account groups are determined on the basis of CUSTOMER and ACCOUNT details.
The priority data items from CUSTOMER and ACCOUNT applications are specified in the
CONDITION.
PRIORITY file in the record whose ID is ACCOUNT.

The priority data items, which are used in the ACCT.GEN.CONDITION records are
defaulted from the CONDITION.PRIORITY record with ID ACCOUNT.
For further details regarding XXX.GEN.CONDITION applications, refer to the User
Guide on System Tables.

Each general condition record specifies the combination of field values defining
one account group.
The ID of the general condition record is referred to in other parts of the system
as the condition group.

Before any account can be opened, a suitable general condition record must exist in
order to determine the Group to which the account belongs,
also a capitalisation frequency record, debit and credit interest conditions (in
the CURRENCY of the account) for that group must have been defined.

Whenever input to an ACCOUNT record occurs, a condition group value is recalculated


according to the details held in this table.
Amending an ACCOUNT or CUSTOMER record may result in new interest conditions being
applied and possibly an adjustment to interest previously calculated.

If the details of an account match more than one general condition record, the
priority order is used to determine the group.
(The higher priority field with a match wins. Priority 1 is the highest priority.)

Till 1000 category 10001 has exceeded the limit by USD 1030700
AC.SUB.ACCOUNT
AC.AUTO.ACCOUNT
MAX.SUB.ACCOUNT

EB.SYSTEM.ID

INCORRECT CHECKDIGIT
BNUSER1 ACOF

ACCTEXEC1

77348

FT2010832KJK
FT20108Z5DDM

ACCTEXEC1 1100
BNUSER 1101
BRANCHMANAGER1 1105
AUTHOR 2400

EB.STP.CONDITION
This application is used for defining the conditions to set up the automatic
authorization that is required for selected transactions,
based upon the amount or the (debit or credit) account, ETC. to allow STP.
This is a new enhancement that is used for defining the various conditions based on

which the transactions are allowed for STP (Straight Through Processing or
automatic authorization).
The ID for this Application should be a valid VERSION record or a VERSION.CONTROL
record.
If the original Application other than a version (like CUSTOMER, ACCOUNT, ETC.)
should be entered as ID, it should have a VERSION.CONTROL record.

All Applications
There are five main files that must be set-up for Global Constraints

EB.GC.PARAMETER - System and Company level Parameter file


EB.GC.ACTIVE - Application Level Definition file
EB.GC.CONSTRAINTS - Constraints Definition file
EB.GC.GLOBAL - Global fields Definition
EB.GC.GROUP - Global Constraints Group Definition

You might also like