Upload Deals of Amendment

The topic describes how the user can upload Securities Deals through an external system to amend the deal in Oracle Banking Treasury Management

The system will distinguish between the new and the deals that require amendment based on the action code of the uploaded record. For a contract requiring amendment, the action code is ‘AMND’. If the action code is ‘AMND’, Oracle Banking Treasury Management will first check whether the deal exists in the system or not. If it does not exist in the system, an error message is displayed to notify that the deal cannot be amended. The Reference Number provided by the external system has to same if it is a new deal or if it is an amendment to an existing deal. When the user upload a new deal, the Reference Number is displayed in the User Reference Number field for that deal. The User Reference Number is the basis for checking whether the deal exists or not. The upload for contract amendment will trigger the ‘AMND’ event. The same event is triggered even when the amendment is done in the ‘Contract Online’ screen.

The fields that can be amended for a Securities Repo Deal are as follows:

• Verify Funds For Principal
• Verify Funds For Interest
• Verify Funds For Penalty Amount
• Verify Funds
• Holiday Currency
• Holiday Months
• Move Forward
• Move Payment Schedules
• Move Revision Schedules
• Move Disbursement schedules
• Receivable Tracking Parameters
• Liquidation – Auto/Manual
• Status Control – Auto/Manual
• Exposure Category
• Risk Free Exposure Amount.
• Internal Remarks
• Demand Basis
• Schedule Details
• Settlement Details
• The amendments through upload of the following fields are considered as financial amendment:
• Currency
• Counterparty
• Amount
• Booking Date
• Value Date
• Cr/Dr Branch Code
• Cr/Dr Account Number
• Holiday Currency
• Commitment (Revolving/ Non- revolving)
• Maturity Type
• User Input Maturity Date

Note:

• If the request received has settlement details, then the values sent as part of the upload are uploaded.
• If Settlement Details are not sent and are maintained in the list of amendable fields, then the details corresponding to the parent contract is copied to the child contract.
• In case the request is a financial amendment, then the contract is reversed and rebooked. If it is non-financial amendment, then the normal amendment procedure is followed.
• In case of financial amendment, Settlement Instructions requires a special handling.
• The financial amendment can be done only through upload and not through fronted.

However, if the SGEN message is already generated then financial amendment upload is not allowed.

For amending a contract, if the source is null, it indicates that the contract is created in Oracle Banking Treasury Management and the user are not allowed to amend. If the value is not null, then the user is allowed to amend a contract.

Reverse and Rebooking Contracts

While reversing and rebooking the parent contract details including the subsystems are copied to a new contract, and the parent is reversed, and the screen is in the new mode so that any details of the contract is changed. It is validated that no payment messages have been sent for the Reversed FCC ref no. A configurable override is displayed. If the payment messages are generated, then the Cancellation request messages (REVSWIFT) are generated. At the branch parameters maintenance, the option ‘User Ref No in Messages’ must be checked. The user reference number and the external reference number of the parent contract number are copied to the new contract. Deletion of the new contract will delete the reversal of the parent contract and set the value of user ref number and external ref number in the parent contract from the child contract. Authorization of the new contract will authorize the parent contract. It will not be possible to delete or authorize the reversal of the parent contract reference number without deleting or authorizing the child.