Before Saving a manually booked transaction, you can manually trigger some of the processing steps mentioned in the table above, and thereby enrich the transaction. On saving the transaction followed by Authorization, the Outbound transaction is processed through the remaining processing Activities as mentioned above.

On clicking the Enrich button in the main tab of the Transaction input screen, the activities till Charge computation are performed. The Enrich option is especially useful when you would like to view the Payment chain determined by the system and change any of the parties including the Receiver and Currency Correspondent, if required, based on specific customer instructions for routing the payment.

User can save the transaction after specifying all of the mandatory fields.

On Save, system performs Transaction Validations. If any of the validations fails then system shows an error message on the screen detailing the error. You can then correct the error and click on Save button again. If all the validations are successful then the transaction is saved and a confirmation message is shown. At the bottom of the transaction screen, the Authorization Status is shown as ‘Unauthorized’, Transaction Status as ‘Active’ and the Maker ID and Maker Date stamp is displayed. The transaction is now pending authorization by a different user after which the transaction processing will begin.

For Outbound payment instructions received through Channels through ReST/SOAP services, system automatically creates a transaction and a Transaction Reference number. The transaction is auto-authorized. It is then processed through the activities as mentioned in the above table.

• SSI Label field is added in the request XML for Outbound payments of all payment types.
• If both Customer ID and SSI Label are present in the request, then system will validate whether SSI Label is applicable for the customer, Network & currency. If not, it will be moved to Settlement Review Queue for editing the SSI Label.
• If Customer ID is not present in the request and only SSI Label is present, Customer ID is derived from the debit Account and SSI Label validation will be done.
• Enrichment of the payment request will be done, by fetching the Beneficiary details based on the SSI Label. This will be done by the system before validating the transaction mandatory fields.

  Note:

  If SSI label is provided for a transaction, then beneficiary/party details if present in the payment request will be overwritten by the SSI label details fetched except for field70/72 details.
• If both the SSI Label and the Beneficiary Account (Ultimate Beneficiary/Beneficiary Institution) details are not passed, then the default instruction, if maintained for the Customer and Network, will be defaulted by system by fetching the corresponding SSI Label.

On clicking of this button, below sub screen is launched.

Figure 10-4 Transaction Preview Details

Description of "Figure 10-4 Transaction Preview Details "

On clicking of OK, then the transaction preview validations is done.