1.11 Process Incoming SWIFT LAU

This topic describes the flowchart of the incoming message SWIFT LAU.

Figure 1-12 Incoming SWIFT LAU

Description of "Figure 1-12 Incoming SWIFT LAU"

The Inbound message workflow is explained below:

• The user can validate inbound messages with the S-Block data. The checksum value is regenerated in Electronic Messaging Service, based on SWIFT LAU parameters and the HMAC-SHA256 algorithm.
• The regenerated checksum is compared with the checksum present in the received message, and further processing is carried out in Oracle FLEXCUBE Universal Banking based on data verification.
• LAU checksum-validated messages are uploaded into the Incoming Message Browser screen with the status Unprocessed, for Oracle FLEXCUBE Universal Banking to create relevant contracts.
• The encrypted S-Block checksum values in the received messages are updated in the SWIFT LAU field and the checksum generated by Electronic Messaging Service for all incoming messages are updated in the LAU Validation field of the Incoming Message Browser screen.
• Messages that have failed in LAU checksum validation are uploaded into the incoming message browser with the status Repair.
• Messages with the status Repair in the incoming message browser will hold differences in checksum data present in SWIFT LAU and LAU Validation fields.
• Incoming messages without S-Block are uploaded in the incoming browser with the status Repair, and data is not updated in the SWIFT LAU field while the Electronic Messaging Service generated checksum is updated in the LAU VALIDATION field.