6.4 Upload the Contracts for Amendment

This topic describes how to upload the contracts for amendment.

From an external system, you can upload contracts that require amendment in Oracle Banking Treasury Management. The system will distinguish between the new and the contracts 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 contract exists in the system or not. If the contract does not exist in the system, an error message is displayed to notify that the contract is not amended.

The Reference Number provided by the external system has to same if it is a new contract or if it is an amendment to an existing contract.

When you upload a new contract, the Reference Number is displayed in the User Reference Number field for that contract. The User Reference Number is basis for checking whether the contract exists or not.

The upload for contract amendment will trigger the ‘CAMD’ event. The same event is triggered even when you amend the ‘MM Contract Online’ screen.

The fields amended for the Money Market module are as follows:

  • Holiday Currency
  • Move Forward
  • Move Payment Schedules
  • Move Revision Schedules
  • Receivable tracking Parameters
  • Liquidation – Auto/Manual
  • Internal Remarks
  • Demand Basis
  • Schedule Details
  • Settlement Details

The amendments of the following fields considered as a 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
  • Broker

Note:

In case the request is a financial amendment, then the contract is reversed and rebooked. If it is a non-financial amendment, then the normal amendment procedure is followed, and the version number is changed, each time the contract is amended.

In the case of financial amendment, Settlement Instructions requires special handling.

Note:

If the request received has settlement details, then the values sent as part of the upload should be uploaded. If Settlement Details are not sent, then the details corresponding to the parent contract is copied to the child contract (if they are not specified at the time of creation).If the request is a financial amendment, then the contract is reversed and rebooked. If it is a non-financial amendment, then the normal amendment procedure is followed, and the version number is changed each time the contract is amended

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

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’ should 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.

You can maintain the type of confirmation in the MM Contract Confirmation screen. The option list displays all open and authorized MM contracts. The Confirmation message of the parent message is suppressed if the counterparty of the parent contract and the current contract are the same. In case the counterparty of the parent and child are the same, then in case the parent contract is confirmed, then the child will also be marked as confirmed. If the parent is not confirmed, then it is marked as confirmed, and the incoming confirmation is matched with the child contract.