6. Annexure 1 - Utilization Transactions

Utilization is a change in the Facility Available Amount. Whenever a contract is booked using a particular Line Code, then the respective line/main line’s Available Amount should be altered in Oracle Banking ELCM.

All utilization transactions maybe captured in their own external systems or through the ‘Utilization Transaction’ screen. The utilization details for each transaction taken place in the external product processor have to be sent to Oracle Banking ELCM through Gateway online Inbound or Gateway Batch Inbound process.

Following utilizations transactions allowed by Oracle Banking ELCM:

Each of the above utilization transactions (apart from Query transaction) has the following sub transactions:

This chapter contains the following sections:

6.1 New Utilization

The process wherein a facility is given to a customer and is utilized by the customer is called a Utilization Process. Utilization Process is termed as a New Utilization when the customer utilizes his facility in a new transaction.

A New Utilization Transaction can arise from any kind of transaction like Loan input, Letter of credit input, Bill/Collection input, foreign exchange deal input, and so on.

New utilization involves the following actions:

6.1.1 Input Utilization

New Utilization process increases the Utilization Amount and decreases the Available Amount for the associated Liability, Facility, or Exposure. If the Liability Facility, Sector Facility Or Country Facility has an associated Main Line then the utilization will reflect at all the parent levels.

Following data are input for a New Utilization transaction.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Source

Alphanumeric (35)

Indicates the product proces­sor name from where the trans­action has been originated. This field is as part of Header section

(Source Code)

Yes

2

TxnID

Alphanumeric (35)

Indicates the Transaction Id of the message. Transaction Id should be unique across the sys­tem. This informa­tion is captured as part of header.

Yes

3

Action

Alphabet (10)

Indicates the transaction type. This field is as part of Header section (opera­tion Code)

Yes

4

Utilization Branch

AlphaNumeric (3)

Indicates the transaction branch. This field is as part of Header section (Branch code).

Yes

5

External Refer­ence Number

AlphaNumeric (30)

Specifies the product proces­sor reference number

Yes

6

Customer

Number

AlphaNumeric(11)

Specifies the Cus­tomer Number of the utilization transaction. Cus­tomer Number entered should be valid Customer Number in Oracle Banking ELCM system.

Yes

7

Liability Number

AlphaNumeric(11)

 

Specifies the Lia­bility Number of the utilization transaction. Lia­bility Number entered should be valid Liability Number in Oracle Banking ELCM system.

Yes

8

Facility code

AlphaNumeric(9)

Specifies the Facility Code of the utilization transaction. Facil­ity Code entered should be valid Facility Code in Oracle Banking ELCM system.

No

9

Facility Serial

Number

Numeric (2)

Specifies the Facility Serial number of the uti­lization transac­tion

No

10

Utilization

Amount

Numeric

Indicates the Utili­zation Amount

Yes

11

Utilization Cur­rency

AlphaNumeric (3)

Indicated the cur­rency of the utili­zation transaction.

Currency code entered should be valid currency code in Oracle Banking ELCM system.

Yes

12

Utilization

Product

Alphabet (10)

Indicates Exter­nal product code of the utilization transaction

No

13

Tenor Basis

Alphabet (1)

 

Indicates the tenor bases of the transaction

No

14

Tenor

Numeric

Indicates the tenor of the trans­action

No

15

Maturity Date

Date

Specifies the maturity date

of the transaction

No

16

Matured

Amount

Numeric

Specifies the maturity amount of the transaction

No

17

Matured

Alphabet (1)

Indicates whether transaction is matured or Not.

No

18

Uncollected

Amount

Numeric

Specifies the uncollected amount of the transaction

No

19

Amount Tag

Alphabet (20)

Indicates the type of the component of the transaction.

No

20

Module

Alphabet (10)

Indicates the module of the transaction

No

21

Transaction

Initiated Date

Date

Indicates the date and time when the transaction was entered in product proces­sor.

Yes

22

Value Date

Date

Specifies the Value date of the transaction. If value is not passed then sys­tem defaults to Oracle FLEX­CUBE ELCM present branch date.

No

23

Authorization

Status

Alphabet (1)

Indicates whether transaction should be author­ized online or not. Possible values are “A” (Author­ize online) and “U” (upload trans­action as unau­thorized).

Default value is U

No

24

Force Authoriza­tion

Alphabet (1)

Indicates whether transaction should ignore the overrides occurred in the process or not. Possible values “Y” (force author­ize) and “N” (not force authorized). Default value is “N”

No

25

User ID

AlphaNumeric(11)

Specifies valid Oracle FLEX­CUBE ELCM user id, who is per­forming the oper­ation. This field is as part of Header section (User ID)

Yes

26

Simulate

Alphabet(1)

Indicates if the transaction should be used only for simula­tion. Possible Val­ues ‘Y’ (simulate) and ‘N’ (actual transaction). Default value is ‘N’

No

27

Block Reference

Number

Alphanumeric(50)

Specifies a valid block number for a facility. If liabil­ity and facility details for new uti­lization and the facility match, the earmarked amount corre­sponding to the block maintained for the facility is made available for the new utiliza­tion.

No

6.1.2 Validations for a New Utilization Process

Apart from the mandatory checks, system performs the following validations:

6.1.2.1 Overrides for New Utilization process

System raises overrides for the following actions

6.1.2.2 Credit Exception Management (Multi Authorization)

As part of the Utilization Transaction process, Oracle Banking ELCM provides the Credit

Exception Management feature. This process will be executed in the following case.

Inputted Transaction Amount Crosses Specified Limit

At facility maintenance level, you can specify what would be the Maximum Transaction amount, which can be processed without any RISK department approval. If the transaction amount is greater than the specified amount then system passes this transaction to Multi Authorization stage.

Example

Assume that facility has been maintained with following details

If the utilization amount is greater than 10,000.00 (INR) then the system passes these transactions to Multi authorization stage.

For more details, refer the section Credit Exception Management in the Process Flows document.

Inputted Transaction Amount Crosses the Breached Limit

At Facility Maintenance, you can specify a Maximum Breach Amount above which necessary approval is required from RISK department. If the transaction has been breached, that is, the utilized and the breached amount are greater than the specified breached amount, then the system passes this transaction to Multi authorization stage.

In the above example, if the utilized amount is greater than 1,20,000.00 then the system passes these transactions to Multi Authorization stage. If the utilized amount is between 1,00,000 and 1,20,000 then the system throws an override.

Note

If transaction is Force Authorized then the system uploads the transaction as authorized and the system sends the information to RISK department. RISK department cannot reject this transaction.

For more information, refer to the Credit Exception Management section in the Process Flows document.

6.1.3 Authorize Utilization

A New Utilization transaction can be entered as Authorized Online or Unauthorized. If the transaction is not authorized online, then Oracle Banking ELCM provides the facility to authorize the inputted transaction.

Apart from the Gate Way header information, Authorization process requires following the information.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Ref­erence Num­ber

AlphaNumeric

Specifies Oracle FLEX- CUBE ELCM utilization reference number

No

2

External Refer­ence Number

AlphaNu- meric(50)

If the product pro­cessor does not have OracleFL­EXCUBE ELCM utilization refer­ence number then it should pass the product processor refer­ence number.

Yes

3

AmountTag

AlphaNu- meric(20)

Amount tag would be required when there are multiple utiliza­tion for the same reference num­ber.

This tag would indicate which component needs to be authorized.

No

 

6.1.4 Delete Utilization

A New Utilization Transaction can be inputted as Authorized Online or Unauthorized. If transaction is not authorized online, then Oracle Banking ELCM provides the facility to delete the inputted transaction.

Apart from the Gate Way header information, delete process would require the following information.

SI.No

Field Name

Date

Remarks

Mandatory

1

Utilization Reference­Number

AlphaNumeric

(16)

Specifies Oracle Banking ELCM utilization refer­ence number.

No

2

External Ref­erence Num­ber

AlphaNumeric(

50)

If the product processor does not have Oracle FLEXCUBE ELCM utili­zation reference number then it should pass the product processor refer­ence number.

Yes

3

Amount Tag

AlphaNumeric(

20)

Amount tag would be required when there are multiple utilization for the same reference number.

This tag would indicate which component needs to be deleted.

No

6.1.5 Technical Undo (Special Delete)

This feature of gateway allows the external system to rollback previous inputted transaction in Oracle Banking ELCM. This feature is supported in Gateway Inbound (online), information required as part of Technical undo is also Transaction Id of the previous transaction.

Note

As part of technical undo transaction information related to header needs to be passed and in body only previous Transaction ID needs to be passed.

6.2 Increase/Decrease Utilization

Increase/Decrease utilization transaction would be used to modify the utilization amount of the transaction. This transaction will be used when customer is making payment for the loan or when the loan amount is modified.

Apart from the GW header information, system requires following information.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Refer­ence

Number

AlphaNumeric

(16)

Specifies Oracle Banking ELCM utilization refer­ence number

No

2

External Refer­ence

Number

AlphaNumeric(

50)

If the product pro­cessor does not have Oracle

FLEXCUBE ELCM utilization reference num­ber then it should pass the product processor refer­ence number.

Yes

3

Amount Tag

AlphaNumeric(

20)

Amount tag would be required when there are multi­ple utilization for the same refer­ence number.

This tag would indicate which component needs to be mod­ified.

No

4

Modified Utiliza­tion

Amount

Numeric

Indicates the Increase/Decrease Utiliza­tion Amount

Yes

5

Utilization Cur­rency

AlphaNumeric

(3)

Indicated the cur­rency of the utili­zation transaction.

Currency code entered should be valid currency­code in Oracle Banking ELCM system.

No

6

Transaction Initi­ated

Date

Date

Indicates the date and time when the transaction was entered in product proces­sor.

Yes

7

Value Date

Date

Specifies the Value date of the transaction.

No

8

Authorization

Status

Alphabet (1)

Indicates whether transaction­should be author­ized online or not. Possible values are “A” (Authorize online) and “U” (upload transac­tion as unauthor­ized).

Default value is U

No

9

Force Authoriza­tion

Alphabet (1)

 

Indicates whether transaction should ignore the overrides occurred in the process or not. Possible values “Y” (force author­ize) and “N” (not force author­ized). Default value is “N”

No

10

Simulate

Alphabet (1)

Indicates if the transaction should be used only for simula­tion. Possible Values ‘Y’ (simu­late) and ‘N’ (actual transac­tion). Default value is ‘N’

No

6.2.1 Validations for Modify Utilization Process

Apart from the mandatory checks, system performs the following validations

Other processing would be same as New Utilization Process.

6.3 Alter Utilization

Alter Utilization is used to modify the entire utilization transaction details. As part of Alter Utilization the external system should give the entire latest utilization details. Oracle Banking ELCM internally reverses previous transaction and upload alter utilization as the new utilization.

Example

Assume that loan has been created in the external system. As a part of loan creation, new utilization has been uploaded in Oracle Banking ELCM. When loan parameters like product code, tenor of loan, customer, and so on has to be changed then the loan transaction is modified and subsequently Alter Utilization needs to be passed to the Oracle Banking ELCM system.

Increase/decrease utilization would only modify only the utilization amount.

6.3.1 Input Alter Utilization

Oracle Banking ELCM internally reverses the previous transaction and upload Alter Utilization as a new utilization. New Utilization process increases the utilization amount and decrease the available amount for the associated liability, liability facility, sector facility, and country facility.

If the liability facility, sector facility or country facility has an associated Main Line then the utilization is recorded at all the parent levels.

Following data is captured for a Alter Utilization transaction.

SI No

Field Name

Data Type

Remarks

Mandatory

1

Source

AlphaNumeric(

35)

Indicates the product proces­sor name from where the trans­action has been originated. This field will be as part of Header section

(Source Code)

Yes

2

TxnID

AlphaNumeric(

50)

Indicates the Transaction Id of the message. Transaction Id should be unique across the sys­tem. This infor­mation is captured as part of header.

Yes

3

Action

Alphabet (10)

Indicates the transaction

type. This field will be as

part of Header section

(operation Code)

Yes

4

Utilization

Branch

AlphaNumeric (3)

Indicates the transaction branch. This field will be as part of Header section (Branch code).

Yes

5

External Refer­ence

Number

AlphaNumeric(

50)

Specifies the product proces­sor reference number

Yes

6

Customer Num­ber

AlphaNumeric(

11)

Specifies the Customer Num­ber of the utiliza­tion transaction. Customer Num­ber entered should be valid Customer Num­ber in Oracle Banking ELCM system.

Yes

7

Liability Number

AlphaNumeric(

11)

Specifies the Lia­bility Number of the utilization transaction.Liabil­ity Number entered should be valid Liability Number in Ora­cle FLEXCUBE ELCM system.

Yes

8

Facility Code

AlphaNumeric(9)

Specifies the Facility Code

of the utilization transaction.

Facility Code entered

should be valid Facility

Code in Oracle Banking

ELCM system.

Yes

9

Facility Serial

Number

Numeric (2)

Specifies the Facility Serial number of the uti­lization transac­tion

Yes

10

Utilization

Amount

Numeric

Indicates the Utili­zation Amount

Yes

11

Utilization Cur­rency

AlphaNumeric (3)

Indicated the cur­rency of the utili­zation transaction.

Currency code entered should be valid currency code in Oracle Banking

ELCM system.

Yes

12

Utilization Prod­uct

Alphabet (10)

Indicates Exter­nal product code of the utilization transaction

No

13

Tenor Basis

Alphabet (1)

Indicates the tenor bases of the transaction

No

14

Tenor

Numeric

Indicates the tenor of the trans­action

No

15

Maturity Date

Date

Specifies the maturity date of the transaction

No

16

Maturity Date

Date

Specifies the maturity date of the transaction

No

17

Matured

Alphabet (1)

Indicates whether transaction is matured or Not.

No

18

Uncollected

Amount

Numeric

Specifies the uncollected amount of the transaction

No

19

Amount Tag

Alphabet (20)

Indicates the type of the compo­nent of the trans­action.

No

20

Module

Alphabet (10)

Indicates the module of the transaction

No

21

Transaction Initi­ated

Date

Date

Indicates the date and time when the transaction was entered in product proces­sor.

Yes

22

Value Date

Date

 

Specifies the Value date of the transaction. If value is not passed then sys­tem defaults to Oracle FLEX­CUBE ELCM present branch date.

No

23

Authorization

Status

Alphabet (1)

Indicates whether transaction should be author­ized online or not. Possible values

are “A” (Authorize online) and “U” (upload

transaction as unauthorized).

Default value is U

No

24

Force Authoriza­tion

Alphabet (1)

Indicates whether transaction should ignore the overrides occurred in the process or not. Possible values “Y” (force author­ize) and “N” (not fore authorized).

Default value is “N”

No

25

User ID

AlphaNumeric(

11)

Specifies valid Oracle FLEX­CUBE ELCM user id,

who is performing the operation. This field is as part of Header section (User ID)

Yes

26

Simulate

Alphabet(1)

Indicates if the transaction­should be used only for simula­tion. Possible Val­ues ‘Y’ (simulate) and ‘N’ (actual transaction).

Default value is ‘N’

No

6.4 Reverse Utilization

Reverse Utilization transaction is used to reverse an authorized utilization transaction. This is used when user/customer wants to close the transaction.

6.4.1 Input Reverse Utilization

Apart from the Gate Way header information, the system requires following information.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Refer­ence Number

AlphaNumeric (16)

Specifies Oracle Banking ELCM utilization refer­ence number.

No

2

External Refer­ence

Number

AlphaNumeric(

50)

If the product processor does not have Oracle FLEXCUBE ELCM utilization reference num­ber then it should pass the product processor refer­ence number.

No

3

AmountTag

AlphaNumeric(

20)

Amount tag would be required when there are multi­ple utilization for the same refer­ence number.

This tag would indicate which component needs to be modified.

No

4

Modified Utiliza­tion

Amount

Numeric

Indicates the Increase/Decrease Utiliza­tion Amount

Yes

5

Utilization Cur­rency

AlphaNumeric

(3)

Indicated the currency of the utilization trans­action.

Currency code entered should be valid cur­rency code in Oracle Banking ELCM system.

Yes

6

Transaction Initi­ated Date

Date

Indicates the date and time when the trans­action was entered in prod­uct processor.

Yes

7

Value Date

Date

Specifies the Value date of the transaction.

No

8

Authorization

Status

Alphabet (1)

Indicates whether transac­tion should be authorized online or not. Possible values are “A” (Authorize online) and “U” (upload transac­tion as unauthor­ized).

Default value is U

No

9

Force Authoriza­tion

Alphabet (1)

 

Indicates whether transac­tion should ignore the over­rides occurred in the process or not. Possible val­ues “Y” (force authorize) and “N” (not fore authorized).

Default value is “N”

No

10

Simulate

Alphabet(1)

Indicates if the transaction should be used only for simula­tion.

Possible Values ‘Y’ (simulate) and ‘N’ (actual transaction). Default value is ‘N’

No

 

6.4.1.1 Validations for Modify Utilization process

Apart from the mandatory checks, system performs the following validations:

Other processing are same as New Utilization Process.

6.5 Set Balance of Utilization Transaction

Set Balance Transaction is used when an external system processes the Utilization Transactions and then during EOD or some point of time the final balance of the utilization transaction is given to the Oracle Banking ELCM system.

Oracle Banking ELCM system updates the balance of the utilization transaction and subsequent difference in the utilization amount is updated at liability, facility, sector and country levels. If there facility, sector and country has a main line associated with it, then the system will update the utilization details in all the main lines.

Apart from the Gate Way header information, system requires following information.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Refer­ence Number

AlphaNumeric

(16)

Specifies Oracle FLEXCUBE ELCM utilization­reference num­ber.

No

2

External Refer­ence Number

AlphaNumeric(

50)

If the product processor does not have Oracle Banking ELCM utilization refer­ence number then it should pass the product processor refer­ence number.

Yes

3

AmountTag

AlphaNumeric(

20)

Amount tag would be required when there are multiple utilization for the same reference number. This tag would indicate which compo­nent needs to be modified.

No

4

Modified Utiliza­tion Amount

Numeric

Indicates the Increase/Decrease Utiliza­tion Amount

Yes

5

Utilization Cur­rency

AlphaNumeric (3)

Indicated the cur­rency of the utili­zation transaction. Cur­rency code entered should be valid cur­rency code in Oracle Banking ELCM system.

No

6

Transaction Initi­ated

Date

Date

Indicates the date and time when the trans­action was entered in prod­uct processor.

Yes

7

Value Date

Date

Specifies the Value date of the transaction.

No

8

Authorization Status

Alphabet (1)

Indicates whether transac­tion should be authorized online or not. Possible values are “A” (Authorize online) and “U” (upload transac­tion as unauthor­ized). Default

value is U

No

9

Force Authoriza­tion

Alphabet (1)

Indicates whether transac­tion should ignore the over­rides occurred in the process or not. Possible val­ues “Y” (force authorize) and “N” (not fore authorized).

Default value is “N”

No

10

Simulate

Alphabet(1)

Indicates if the transaction should be used only for simula­tion.

Possible Values ‘Y’ (simulate) and ‘N’ (actual trans­action).

Default value is ‘N’

No

6.5.0.1 Validations for Modify Utilization process

Apart from the mandatory checks, system performs the following validations:

● Utilization Reference Number - If this value is passed, then the system checks whether it is a valid utilization reference number. If so the system reverses this reference number.

● External Reference Number - If Oracle Banking ELCM utilization reference number is not passed then system has to pass an External Reference Number. Based on this number system retrieves the Oracle Banking ELCM utilization reference number and do the process.

Other processing are same as New Utilization Process.

6.6 Query Utilization

A Query Utilization transaction can be performed on all the Contracts. Here on query only the consolidated information about the contract will be provided.

Apart from the Gate Way header information, Query process will require following the information.

SI.No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Ref­erence

Number

AlphaNumeric (16)

Specifies Oracle Bank­ing ELCM utilization reference number.

No

2

External Refer­ence

Number

AlphaNumeric(50)

If the product proces­sor does not have Ora­cle FLEXCUBE ELCM utilization reference number then it should pass the product pro­cessor reference num­ber.

Yes

3

AmountTag

AlphaNumeric(20)

Amount tag would be required when there are multiple utilization for the same refer­ence number.

This tag would indicate which component needs to be author­ized.

No

4

Simulate

Alphabet(1)

Indicates if the trans­action should be used only for simulation. Possible Values ‘Y’ (simulate) and ‘N’ (actual transaction).

Default value is ‘N’

No

6.7 Mature Utilization Transaction

Mature Transaction will be used to set the mature amount for that the specified contract Utilization Transactions and then the amount specified will be treated as the matured amount for that contract.

Oracle Banking ELCM system will update the mature amount of the utilization transaction. Apart from the Gate Way header information, system requires following information.

SI No

Field Name

Data Type (size)

Remarks

Mandatory

1

Utilization Ref­erence

Number

AlphaNumeric

(16)

Specifies Ora­cle Banking ELCM utiliza­tion reference number.

No

2

External Refer­ence

Number

AlphaNumeric(

50)

If the product processor does not have Ora­cle FLEX­CUBE ELCM utilization refer­ence number then it should pass the prod­uct processor reference num­ber

Yes

3

AmountTag

AlphaNumeric(

20)

Amount tag would be required when there are multi­ple utilization for the same reference num­ber.

This tag would indicate which component needs to be modified.

No

4

Modified Utili­zation

Amount

Numeric

Indicates the Increase/Decrease Utili­zation Amount

Yes

5

Utilization Cur­rency

AlphaNumeric

(3)

Indicated the currency of the utilization transaction.

Currency code entered should be valid cur­rency code in Oracle FLEX­CUBE ELCM system.

No

6

Transaction Ini­tiated

Date

Date

Indicates the date and time when the trans­action was entered in product proces­sor.

Yes

7

Authorization Status

Alphabet (1)

Indicates whether trans­action should be authorized online or not.

Possible values are “A” (Author­ize online) and “U” (upload transaction as unauthorized). Default value is U

No

8

Force Authori­zation

Alphabet (1)

Indicates whether trans­action should ignore the overrides occurred in the process or not. Possible values “Y” (force authorize) and “N” (not for authorized). Default value is “N”

No

6.8 Utilization Transaction Screen

All utilization requests explained above can also be raised through the ‘Limit Utilization’ screen.

You can invoke the ‘Limit Utilization’ screen by typing ‘GEDUTILS’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.

 

Note

The limit utilization feature explained in this section is available only if the Enterprise Limits and Collateral Management module has been set up in standalone mode. This screen can be launched only if ELCM license is purchased.

Utilisation Branch

Specify the branch where the utilization request should be processed. The adjoining option list contains all the branches maintained in the system. Select the appropriate one.

User Reference Number

Specify a unique reference number for the transaction.

Transaction Module

Specify the module for the transaction. The adjoining option list contains all the modules in the system. Select the appropriate one.

Transaction Date

Specify the date for the transaction.

Simulate

Select this check box to indicate that the details for the transaction being entered should be used only for simulation and not stored permanently within the system. After a simulated transaction has been successfully put through, the system displays the utilized amount for the facility and the for the liability.

Customer Number

Specify a valid customer number for the transaction. The adjoining option list contains all the customers maintained in the system. Select the appropriate one.

Utilisation Amount

Specify the amount for the utilization transaction.

Utilisation Currency

Specify the currency for the amount entered. The adjoining option list contains all the currencies maintained in the system. Select the appropriate one.

Utilisation Product

Specify the product for the transaction. The adjoining option list contains all the relevant products. Select the appropriate one.

Uncollected Amount

Specify the amount that has not yet been collected from the customer.

Tenor Basis

Select this check box to indicate that the utilization should be tracked tenor wise for the facility. You can specify the basis on which it is to be tracked in the ‘Tenor’ field.

Tenor

Enter the basis on which tenor tracking should be done for the utilization. You need to have checked the ‘Tenor Basis’ option before you can specify the basis here.

Maturity Date

Specify the date on which the transaction matures.

Amount Tags

Specify the component type for the transaction. The adjoining option list contains all the relevant tags. Select the appropriate one. The 'Amount Tag' entered in 'Amount Tag Maintenance' screen is displayed here.

Remarks

Enter any additional remarks that you wish to maintain for this transaction. You can enter up to 255 characters.

Value Date

Specify the value date for the transaction.

Line Code

Specify the line code to be used for the transaction. The adjoining option list contains all the line codes allowed. Select the appropriate one.

Serial No

The ‘Serial No’ field is disabled and it gets defaulted from the ‘Facilities Maintenance’ screen.

 

Block Reference Number

If you enter the block reference number, you can utilize the limit amount, thereby reducing the block amount. The extent of the amount utilized is released from the block amount

If you try to utilize more than limit amount, the system gives an override.

An error appears, when you try to utilize more than blocked amount by providing block reference number.

6.9 Reconciliation of Utilization Transactions

The Oracle Banking Enterprise Limits and Collateral Management (hereafter referred to as Oracle Banking ELCM) system receives Utilization Transactions (or contracts) from different external product processing systems. These external systems include Loans systems, Treasury systems, Trade and Finance systems and others. The bulk of the contract details remains with these external systems and the only the details required for processing will be sent to Oracle Banking ELCM.

During such Utilization Transactions, mismatch of details between the external product processor and Oracle Banking ELCM may occur. To handle such mismatches, the Oracle Banking ELCM system features an EOD Reconciliation Process to bring both system in sync by the end of the day.

EOD Reconciliation Process

As part of the EOD Reconciliation Process, an inbound transaction process happens wherein each product processor generates a batch file containing details pertaining to all the utilization requests for the day. The Oracle Banking ELCM system will process these batch files as part of EOD batch operation and perform the reconciliation process.

The “Manual/System” parameter specifies whether the mismatched transaction should be handled manually by the user or the system should perform the reconciliation process

The system reads all the batch files for reconciliation and perform a comparison of all the transaction that has been performed in the product process with the utilization transactions performed in Oracle Banking ELCM.

The following table shows the possible types of the mismatch.

 

Transaction Status in Product Processor/ Oracle Banking

 

Corresponding Utilization status in Oracle FLEXCUBE ELCM

 

Resulting Oracle FLEXCUBE ELCM Action

Not Saved

Saved

Reversal

Saved

Not saved

Upload

The above mentioned Oracle Banking ELCM action is performed only if the system parameter has been set to ’System’.

Viewing Mismatch Summary

You can view in the mismatch Summary screen all the counter transactions that has been performed by Oracle Banking ELCM for handling the mismatches. The summary also indicates whether the counter transactions have succeeded or failed.

For failed transactions, the reason for failure will be shown. You will have to take manual action in case of failed transactions.

6.10 Increasing/Decreasing Utilizations

You can modify the utilization amount of the transaction through the ‘Utilization Increase And Decrease’ screen. This transaction can be used when customer is making payment for the loan or when the loan amount is modified.

You can invoke the ‘Utilization Increase and Decrease’ screen by typing ‘GEDUTNID’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.

 

Note

The feature explained in this section will be available only if the Enterprise Limits and Col- lateral Management module has been set up in standalone mode. This screen can be launched only if ELCM license is purchased.

Utilization Reference No

Specify the reference number for the utilization that you want to modify. The adjoining option list contains all the utilizations in the system. Select the appropriate one. The system displays the user reference number, the utilization currency and the amount tag.

Utilization Amount

Enter the amount by which you wish to modify the utilization.

Action

Indicate the operation for the utilization – whether you would like to increase or decrease the utilization amount.

The ‘Limit Utilization’ screen will be displayed when you click on the ‘Details’ button where you can view the details of the original utilization request.

6.11 Linking an Utilization Transaction to a Facility

If you link an Oracle FLEXCUBE transaction to a facility, then based on the event of transaction corresponding, you need to process limits related data in Enterprise Limits and Collateral Management (ELCM) systems.

During processing if any error or override occurs in ELCM, then ELCM sends an error or override information to Oracle FLEXCUBE. Later Oracle FLEXCUBE displays the details to you. The Interface between Oracle FLEXCUBE and ELCM is online real time using HTTP and all transaction posted into ELCM is auto authorized. If delete or reversal action is triggered, the system will reverse the transaction in ELCM.

If a contact needs to be tracked under facility, then you have to link the contact to the facility and during transaction processing, Oracle FLXCUBE sends the utilization details to ELCM for processing.

The below diagram briefs the Utilization Transaction Integration Approach flow between Oracle FLEXCUBE and ELCM:

 

The table below explains the actions you can perform for which Oracle FLEXCUBE hands-off utilization transaction to ELCM:

 

Sl. No

 

Oracle FLEXCUBE Transaction Action

 

Utilization Transaction Action

1

New

New

2

Modify

Modify/ Increase/Decrease

3

Delete

Delete

4

Reverse

Reverse

5

Liquate

Liquate

6

Rollover

Rollover

7

Payment

Decrease

As part of the contract or transaction process, if a line code is linked to a contract then it is required to track the limits of the linked line. The system exposes limits process as subsystem and any module would interact with Limits subsystem.

The system allows you to trap all the utilization transaction. The system would interface with

ELCM Gateway HTTP to upload the utilization transactions in ELCM. Based on the utilization event, the system creates utilization request in ELCM format. It also logs transaction data and status of each utilization transaction.

6.11.1 Collateral Pool Utilization Transaction Process

You are allowed to link collateral pool as part of contact and upload all collateral pool utilization transactions in ELCM. You can process the following events as part collateral pool utilization:

The system allows you to plug the pool utilization data from Oracle FLEXCUBE and passes to ELCM using ELCM Gateway HTTP/WS communication channel.

6.11.2 Utilization Transaction Status

The following are the possible transaction status for utilization upload:

6.11.2.1 Transaction Status Success

Oracle FLEXCUBE sends the utilization transaction to ELCM and while processing this transaction, If ELCM processes it completely, then this transaction would be considered as success. Oracle FLEXCUBE would continue to process remaining contract process.

During transaction process, if transaction is uploaded successfully in ELCM and if any error or overrides (overrides not accepted) occurs in Oracle FLEXCUBE then uploaded transaction is reverted back using technical undo feature of ELCM.

6.11.2.2 Transaction Status Failure

Oracle FLEXCUBE sends the utilization transaction to ELCM and while processing this transaction, if any error occurs, ELCM sends failure status with error details to Oracle FLEXCUBE.

ELCM plug-in updates the transaction error objects which ELCM error code, as part of transaction process. Later Oracle FLEXCUBE checks the error object and subsequently raises error as part of contract process.

As part of the transaction process, if ELCM process is failed then ELCM error details are displayed to the user.

Note

6.11.2.3 Transaction Status Override

Oracle FLEXCUBE sends the utilization transaction to ELCM and while processing this transaction, if any override occurs, in such cases ELCM would generate override reference number (Multitrip ID) and log override details along with Multitrip ID for further reference. It marks the final transaction status as override and override details only with Multitrip ID is passed to Oracle FLEXCUBE for further processing.

ELCM plug-in would updates override details in Oracle FLEXCUBE error object it also logs the status and Multitrip ID as part of log table, later as part of transaction process Oracle FLEXCUBE checks the error object and subsequently raises transaction status as override.

Note

If overrides occur as part of transaction process, then the system displays the override de­tails to the user. You have an option to accept or reject the overrides.

If the override occurs as part of the request, XML Multitrip ID is also passed and this Multitrip ID is passed to ELCM as part of utilization transaction. As part of the utilization process in ELCM if same (previous transaction) overrides occurs, then it is accepted and the transaction is saved.

6.11.2.4 Transaction Status Dual Auth

Oracle FLEXCUBE sends the utilization transaction to ELCM and while processing this transaction, if any of the validation requires authorization, then ELCM processes the transaction completely and sends dual auth details and marks the transaction status as Dual auth required.

ELCM plug-in updates dual auth details in error object, later as part of transaction process it updates dual auth details in Oracle FLEXCUBE tables. It updates the Auth status for the dual auth error code as ‘U’ – Unauthorized, if you try to authorize the contract, Oracle FLEXCUBE will check whether contract has any unauthorized dual-auth error code. If yes, the system does not allow contract to be authorized, till all dual-auth error codes are authorized.

In ELCM if any error code requires dual authorization, the system triggers credit exception management process flow. You are allowed to accept or reject the validation (dual-auth) error code. On accept or reject of the validation code, ELCM handoffs these details to JMS queue and ELCM out adapter is used to invoke Oracle FLEXCUBE WS for updating status of dual- auth error code.

6.11.2.5 Authorization of utilization transaction

All utilization transactions which are uploaded from Oracle FLEXCUBE are auto authorized and if contract or transaction is deleted in Oracle FLEXCUBE then ELCM would trigger the reversal transaction.

Example

Assume the following:

Liability ‘COCACOLA’ is created in ELCM with below details:

Customer ‘C00001’ is created in Oracle FLEXCUBE and Customer ‘C00001’ is linked in

ELCM using liability ‘COCACOLA’ using customer liability linkage maintenance. Facility

Loan (CL module) has been inputted for customer ‘C00001’ created in Oracle FLEXCUBE

As part of loan processing, Oracle FLEXCUBE sends new utilization transaction to ELCM for the loan. As part of the utilization process ELCM updates utilized amount at facility level and liability level. The Liability details after loan transaction would be as below:

Assume that you have paid the first installment of amount 100,000 (principal) using CL payment screen in Oracle FLEXCUBE and after processing the transaction, the liability and facility details would be as below:

Note

Since line linked to loan is revolving, as part payment transaction ELCM would reduce amount utilized.

6.12 Global Utilization Tracking of Limits

6.12.1 Utilization Tracking

Facility utilization tracking is classified into two types.

According to the tracking type selected, limit utilization is tracked locally or globally. The facility utilization tracking is available in the GEDFACLT. Multiple regional (local) ELCM instances interact with global ELCM instance for limit utilizations.

Following example illustrates facility utilization tracking.

Facilities

Global/Local

Amount (GBP)

Test_1

Global

500000

Test_2

Local

200000

Case 1: Utilization success

Loan contract booking is initiated from the local instance for GBP 10000 under the Global facility.

Loan contract booking is initiated from the local instance for GBP 5000 under the Local facility.

Both the above utilizations are stored in the ELTB_UTIL_TXN_LOG (GESGLOUT) with the transaction status as ‘U’. The utilization transactions are replicated in the Global instance. After the replication is complete, the EJB scheduler attempts posting the utilizations in the Global instance and marks the transaction status as ‘W’.

After the postings are successfully done the transaction status is marked as ‘S’. The facilities are also displayed as utilized to the extent of the above mentioned respective amounts. The utilizations and the updated facilities are replicated to the local instance.

Case 2: Utilization Failure

Loan contract booking is initiated from the local instance for GBP 10000 under the Global facility.

Loan contract booking is initiated from the local instance for GBP 5000 under the Local facility.

Both the above utilizations are stored in the ELTB_UTIL_TXN_LOG with the transaction status as ‘U’. The utilization transactions are replicated in the Global instance. After the replication is complete, the EJB scheduler attempts posting the utilizations in the Global instance and marks the transaction status as ‘W’. If the scheduler is unable to post the utilizations for any reason, the transaction status is marked as ‘E’ with the failure reason.

The teller can ‘retry’ posting the utilizations by using the ‘Retry’ feature in the GESGLOUT screen. The utilizations are again marked as ‘U’ and the scheduler again tries posting them. After the postings are successfully done the transaction status is marked as ‘S’. The facilities are also displayed as utilized to the extent of the above mentioned respective amounts. The utilizations and the updated facilities are then replicated to the local instance.

6.12.2 Global Utilization Exception Summary

Global Utilization Exception Summary report is used for checking the response status (errors or overrides) of global utilization. In case of failure, you need to rectify manually.

You can invoke the ‘Global Utilization Exception Summary’ screen by typing ‘ELSGLOUT’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.

 

 

 

6.13 Value Dated Fee Processing

Oracle Banking ELCM provides capability to capture and compute fees based on different value dated/book dated balances for facilities, for which system provides for SDE which corresponds to these balances. Likewise, system supports collection for fees for different life cycle events of a collateral for which system provides for SDE which correspond to these events in addition to recurring fee on collateral amount as SDE.

In addition, Oracle Banking ELCM collects fee based on various amount tags.

The following are the different activities that takes place and it impact on each other.

Steps involved in processing fees

  1. Defining rules and attributes for fees – You can define rule for fees based on value dated (VD) balance or book dated (BD) balance amount tags maintained for facilities and event based tags maintained fro collaterals.
  2. Defining a class for fees - You can define a class for fees based on the holiday preferences maintained in the 'Fee and Accounting Class Maintenance' .
  3. Specifying fee details in facility/collateral – Based on fee rules with holiday preference parameters from fee class, specify other fee details at facility/collateral level.

6.13.1 Maintaining Rule

You can invoke this screen by typing ‘GEDRULES’ in the field at the top right corner of the application tool bar and clicking the adjoining arrow button.

 

Rule ID

Every fee rule is identified by a unique code, called a Rule ID. You can link a valid fee Rule ID to the fee classes. Fees for a limit/collateral with which you associate a fee class is calculated on the basis of the Rule that is associated with the class.

Rule Description

For every rule that you define, you can enter a description. Specifying a description helps identify a rule.

Fee Type

This component value defaults to the ‘Fee Rule Preferences’ defined in the ‘Facilities/Collateral Maintenance’ screen. Rate/Amount are calculated based on the ‘Basis Amount’ where as ‘User Input’ is standard amount entered in the ‘Fee Rule Preferences’.

SDE Type

Specify the System Data Elements (SDE). The adjoining option list displays a list of SDEs maintained in the system. Applicable SDEs based on entity type selected will be available for selection.

Day Basis

A day basis method is used for fee calculations.

Different values for the numerator basis are as explained below:

Different values for the denominator of the fee basis are as explained below.

Fee Component Type

Select the fee component type either as ‘Slab’ or ‘Tier’.

Fee Type

Select the fee type either as ‘Rate’ or ‘Amount’.

Entity Type

Select the entity type either as ‘Facility’ or ‘Collateral’. By default, ‘Facility’ is selected. If you select 'Entity Type' as ‘Facility’ and select Rule Type as ‘Event Based Fee’, the system displays an error message.

Rule Type

Select the rule type either as ‘Fee’ or ‘Event Based Fee’.

If ‘Rule Type’ is selected as ‘Event Based Fee', then the following SDEs should be selected for 'Event Based Fee'.

External Pricing Required

Select this check box if the pricing (Rate/Amount) for a particular fee (SDE) needs to be fetched from external pricing and billing system.

Note

6.13.2 Maintaining Fee Class

You can invoke this screen by typing ‘GEDCLSMT’ in the field at the top right corner of the application tool bar and clicking the adjoining arrow button.

 

Class Code

Before defining the attributes of a fee class, you should assign the class a unique identifier, called the Class Code.

Description

A brief description about the class. A description helps you to easily identify the class.

Start Date

Specify the start date from which the fee calculation starts. The start date can only be a current date or the future and it cannot be a back dated date.

End Date

Specify the end date till which the fees will be calculated.

Entity Type

You can select the ‘Entity Type’ as ‘Facility’ or ‘Collateral’. Based on this selection, appropriate ‘Rule Code’ and ‘Rule Type’ is displayed in the ‘Preferences’ tab.

6.13.2.1 Accounting Roles tab

You can specify accounting roles details in ‘Accounting Roles’ screen. Click ‘Accounting Roles’ tab to open this screen.

 

Accounting Role

Accounting Roles are tags that identify the type of accounting entry that is posted to an accounting head.

Accounting Head

The different General Ledgers (GLs) and Sub-Ledgers (SLs) maintained in your Chart of Accounts are referred to as accounting heads or account heads.

6.13.2.2 Events tab

You can specify event and accounting entries details in ‘Events’ screen. Click ‘Events’ tab to open this screen.

 

Event code

Specify the event code.

Accounting Role

Accounting Roles are tags that identify the type of accounting entry that is posted to an accounting head.

Amount Tag

Specify the amount tag.

Transaction Code

Indicates the type of accounting entry associated with every accounting entry.

Dr/Cr Indicator

Indicates whether the amount was debited or credited to the ‘Net’ Account

Netting

Select this drop-down list if you need netting for fee liquidation.

6.13.2.3 Preferences tab

Click ‘Preferences’ tab to open ‘Preferences’ screen.

 

 

Rule Code

You can link a valid fee Rule to the fee classes. Fees for a limit/collateral with which you associate a fee class is calculated on the basis of the Rule ID that is associated with the class.

Rule Type

Based on the rule code, the rule type gets defaulted.

Basis Amount

The following are the list of basis amount applicable for a collateral based on which the fees is calculated.

For collateral fees of type ‘Event Based Fee’, basis amounts ‘Collateral Value’ are applicable on which the fees is calculated. ‘Limit Contribution’ and ‘Available Amount’ are not applicable.

Accrual Required

Selecting this indicates that the fees have to be accrued.

Accrual Frequency

Specify the fee accrual frequency.

For limit/collateral fees, the 'Rule Type' of ’Fee’ can have any 'Accrual Frequency'. Ensure that accrual frequency is less than liquidation frequency.

Note

If a collateral fees of rule type ‘Fee’ is configured with 'Liquidation Frequency' as ‘One-Time’, then the 'Accrual Frequency' must be ‘One-Time’, if the value does not match the system displays appropriate error message.

Liquidate Frequency

Specify the fee liquidation frequency.

For collateral fees, the 'Rule Type' of ’Fee’ can have any 'Liquidation Frequency'.

Liquidation Method

The following are the liquidation method

Arrears

For collateral fees, the 'Rule Type' of ’Fee’ is collected/liquidated in 'Arrears' (For 'Fee Type' both 'Rate/Amount' and 'User Input').

Facility fee is collected at the end of liquidation cycle is marked as ‘Arrears’.

Advance

Liquidation method ‘Advance’ is not applicable for collateral fees. The system validates and throw an exception if ‘Entity Type’ is selected as ‘Collateral’ and for any of the fee rule 'Liquidation Method' is selected as ‘Advance’.

Facility fee is collected at the start of liquidation cycle is marked as ‘Advance’.

Event Based Fee

Applicable only for collateral.

Liquidation Preference

For collateral fees, the 'Rule Type' of ’Fee’ you can select 'Liquidation Preference' as 'Auto' or 'Manual'.

The 'Manual' fee liquidation is applicable only if in the 'Fee Rule Maintenance' screen, the 'Fee Type' is selected as 'User Input'. Liquidation preference manual is only applicable for facility fees.

External Pricing Required

This value is defaulted based on the rule selected in 'Fee Rule Maintenance' and you cannot modify this value.

Start Date

Specify the start date from which the fee need to be liquidated.

Start Month

Specify the start month from which the fee need to be liquidated.

Entity Type

Specify the entity type either ‘Facility’ or ‘Collateral’.

Waived

If this check box is selected, then the system does not calculate the fees.

Holiday Treatment

Ignore Holidays

If this check box is selected, then holiday treatment is not applied to calculate the next date. If this check box is not selected, then ‘Holiday Preferences’ settings are validated.

Move Across Month

If this check box is selected, then the system moves the date to next month. If this check box is unselected, then the system moves the date to next date.

Example

Working Day

30-Aug

1-Sep

Holiday

31-Aug

Schedule Movement

Move Forward

Calculated Next Date

31-Aug

In above mentioned example, if ‘Move Across Month’ is selected, then the system moves next date to 1-Sep. If ‘Move Across Month’ is not selected, then the system changes next date to 30-Aug.

Schedule Movement

Move Forward

In case calculated next date is holiday then date should be moved forward. In this case fee liquidation moves to 1st Sep which is next working date

Move Backward

In case calculated next date is holiday then date should be moved backward. In this case, fee liquidation moves to 30th Aug which is previous working date

Cascade Schedules

If cascade schedules is selected, then the next date is calculated on based on previous schedule date instead of start date.

If fee liquidation date for one of the liquidation cycle is changed based on holiday processing setting and if cascade schedule is selected future liquidation dates of corresponding fee gets modified as per the newly arrived liquidation date.

Holiday Check

If holiday treatment is applicable, then you can select ‘Local, ‘Currency’ or ‘Both’ based on your holiday maintenance.

If 'Both' is selected and 'Branch' or 'Currency' is holiday, then holiday processing setting is considered.

Holiday Currency

If holiday check is maintained as ‘Currency’ or ‘Both’ then currency code to be maintained here.

6.13.3 Accounting Entries for facility/collateral

This section contains details of the suggested accounting entries that can be set up, for ELCM Facility. The details of the suggested accounting entries are given event-wise.

Event Code

Description

INIT

Facility Initiation

AMND

Facility Amendment

UTIL

Facility Utilization

DUTL

Release of Utilization to Facility

FACR

Fee Accrual

FLIQ

Fee Liquidation

PRLQ

Pay Receive Liquidation

INIT: Facility Initiation

Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

CONASSETGL

EFF_LINE_AMT

Dr

CONASSETOFF

EFF_LINE_AMT

Cr

 

 

 

AMND: Facility Amendment

Accounting Role

Amount Tags

Dr/Cr. Indicator

CONASSETOFF

EFF_LINE_AMT_DECR

Dr

CONASSETGL

EFF_LINE_AMT_DECR

Cr

CONASSETGL

EFF_LINE_AMT_INCR

Dr

CONASSETOFF

EFF_LINE_AMT_INCR

Cr

UTIL: Facility Utilization

Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

CONASSETGL

UTIL_INCR

Cr

CONASSETOFF

UTIL_INCR

Dr

DUTIL: Release of Utilization to Facility

Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

CONASSETGL

UTIL_DECR

Dr

CONASSETOFF

UTIL_DECR

Cr

FACR: Fee Accrual

Arrears Fee- Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

RULEINC

RULE_ACCR

Cr

RULEREC

RULE_ACCR

Dr

FLIQ: Fee Liquidation

Arrears Fee- Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

RULEREC

RULE_LIQD

Cr

CUSTOMER

RULE_LIQD

Dr

FACR: Fee Accrual

Advance Fee- Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

RULEINC

RULE_ACCR

Cr

RULERIA

RULE_ACCR

Dr

FLIQ: Fee Liquidation

Advance Fee- Accounting Entries

Accounting Role

Amount Tags

Dr/Cr. Indicator

RULERIA

RULE_LIQD

Cr

CUSTOMER

RULE_LIQD

Dr

PRLQ: Pay Receive Liquidation

Accounting Role

Amount Tags

Dr/Cr. Indicator

EFFLINE_AMTINC

EFFLINE_AMT_PAY

Dr

CUSTOMER

EFFLINE_AMT_PAY

Cr

EFFLINE_AMTINC

EFFLINE_AMT_REC

Cr

CUSTOMER

EFFLINE_AMT_REC

Dr

 

6.13.4 Derived Amount Tags

Following are the derived amount tags available for configuring the accounting entries.

Derived Amount Tag

Amount Tag Description

Amount Tag Revolving Formula

Amount Tag Non-Revolving Formula

FINAL_LIMIT_AMT

Final Limit Amount

ADDITION ( EFF_LINE_AMT , TFR_AMT )

ADDITION ( EFF_LINE_AMT , TFR_AMT )

FINAL_LIM­IT_AMT_INCR

Final Limit Amount Increase

ADDITION ( EFF_LINE_AMT_INCR , TFR_AMT_INCR )

ADDITION ( EFF_LINE_AMT_INCR , TFR_AMT_INCR )

FINAL_LIM­IT_AMT_DECR

Final Limit Amount Decrease

ADDITION ( EFF_LINE_AMT_­DECR , TFR_AMT_­DECR )

ADDITION ( EFF_LINE_AMT_­DECR , TFR_AMT_­DECR )

UNAVAIL_AMT_INCR

Unavailable Amount Increase

MAX ( ZERO , ZERO )

MAX ( ZERO , MAT_AMT_INCR )

UNAVAIL_AMT_­DECR

Unavailable Amount Decrease

MAX ( ZERO , ZERO )

MAX ( ZERO , MAT_AMT_DECR )

6.13.5 Derived Value Dated tags

Following are the derived value dated tags available for configuring the accounting entries.

Derived Value Dated Tag

Derived Value Dated Tag Description

Value dated Revolving Formula

Value dated Non Revolving Formula

OVERLINE_AMT_2

OVER­LINE_AMT_2

MAX ( SUBTRACT ( UTIL_AMT , FINAL_LMT ) , ZERO )

MAX ( SUBTRACT ( UTIL_AMT , FINAL_LMT ) , ZERO )

BD_OVER­LINE_AMT_2

OVER­LINE_AMT_2

MAX ( SUBTRACT ( BD_UTIL_AMT , BD_FINAL_LMT ) , ZERO )

MAX ( SUBTRACT ( BD_UTIL_AMT , BD_­FINAL_LMT ) , ZERO )

BD_UNUTIL_AMT_1

BD_UNUTIL_AMT_1

SUBTRACT ( BD_LIMIT_AMT , BD_UTIL_AMT )

SUBTRACT ( BD_LIM­IT_AMT , BD_UTIL_AMT )

BD_FINAL_LMT

BD_FI­NAL_LMT

ADDITION ( BD_EF­F_LINE_AMT , BD_TFR_AMT , BD_NTG_AMT )

ADDITION ( BD_EF­F_LINE_AMT , BD_T­FR_AMT , BD_NTG_AMT )

BD_UTL_AMT_2

BD_UT­L_AMT_2

ADDITION ( BD_UTIL_AMT , ZERO )

SUBTRACT ( BD_UTIL_AMT , BD_MAT_AMT )

BD_UNU­TIL_AMT_2

BD_UNU­TIL_AMT_2

SUBTRACT ( BD_FI­NAL_LMT , BD_UTIL_AMT )

SUBTRACT ( BD_FI­NAL_LMT , BD_UTIL_AMT )

BD_OVER­LINE_AMT_1

BD_OVER­LINE_AMT_1

MAX ( SUBTRACT ( BD_UTIL_AMT , BD_LIMIT_AMT ) , ZERO )

MAX ( SUBTRACT ( BD_UTIL_AMT , BD_LIMIT_AMT ) , ZERO )

UNUTIL_AMT_1

UNU­TIL_AMT_1

SUBTRACT ( LIM­IT_AMT , UTIL_AMT )

SUBTRACT ( LIM­IT_AMT , UTIL_AMT )

FINAL_LMT

FINAL_LMT

ADDITION ( EFF_LINE_AMT , TFR_AMT , NTG_AMT )

ADDITION ( EFF_LINE_AMT , TFR_AMT , NTG_AMT )

UTL_AMT_2

UTL_AMT_2

ADDITION ( UTIL_AMT , ZERO

SUBTRACT ( UTIL_AMT , MAT_AMT )

UNUTIL_AMT_2

UNU­TIL_AMT_2

SUBTRACT ( FINAL_LMT , UTIL_AMT )

SUBTRACT ( FINAL_LMT , UTIL_AMT

OVERLINE_AMT_1

OVER­LINE_AMT_1

MAX ( SUBTRACT ( UTIL_AMT , LIM­IT_AMT ) , ZERO )

MAX ( SUBTRACT ( UTIL_AMT , LIM­IT_AMT ) , ZERO )