OUTGOING MESSAGE OPERATIONS

Following the message "Entry" and "Verification" processes, the message is sent to the "Outgoing Message Provision Verification Menu". After the "Correspondent Relations" operations have been completed, the message could be sent to the "Branch Message Entry Menu" or forwarded to the "Outgoing Message Release Menu".

Backoffice checks the messages, keeps, saves and/or creates correspondent balances, and controls provisions. SWIFT Room checks and releases the messages, and follows the responses. (Message responses could be ACK or NAK).

In case a message takes the ACK code from the SWIFT-NET, the message status is reported back to the branch and a "Bank Reference Number" is generated in the for-mat O-001-0000001 (Outgoing Message-Branch Code-Unique Identifier)

INCOMING MESSAGE OPERATIONS

All The Incoming Messages Could Be Routed AUTOMATICALLY Using;
• Transaction Reference Number,
• Reference Number,
• Branches BIC Address,
• Message Type
criteria.

All The Incoming Messages Could Be Routed MANUALLY From the Routing Module;

Messages could be controlled and ROUTED to the concerned branches by the "SWIFT Room". Therefore,the BIC addresses are not explicitly required for the branches to receive messages.

After the routing step, the concerned brach is able to view the messages from the "Message Observation Menu" but cannot apply any operations onto these messages; as the message is not at the "Incoming Message Entry/Acceptance Menu" (first step for the branch is "Message Entry/Accept Menu") following the Exstre(MT950) Verification of Backoffice.

If a message does not belong to the branch at the "Incoming Message Entry/Accept Menu", it could be posted back to the Swift Room's "Message Routing Menu". If the message is labelled "O.K", any user having access to this menu is able to ACCEPT the message (i.e make its entry) and send it to "INCOMING MESSAGE VERIFICATION MENU".

Authorized users could verify the message or send it back to "Incoming Message Entry Menu". If a user verifies the message its spooled output is generated and sent to the printer. This printout becomes the only printed form of the message and with this output the user is able to make payments or other related operations.

A unique code for the bank's swift messages are also generated in this format (Direction-BranchCode-Unique Identifier) Ex. I-001-0000001(Incoming Message-Receiving Branch code is 001-Unique Identifier)

User Interface and Modules :

MESSAGE ENTRY MENU
Message entry is completed with all the rule checks (syntax & semantics, code words, text validations) performed by entry module. Receiving BIC, Sending BIC, Currencies, BKE checks and other related issues are verified.

If a message is rejected (NAK Negative Acknowledgement) by the SWIFT s.c.r.l Belgium; this message is processed automatically for correction.

VERIFICATION QUEUE
A verifier can verify the required message fields for verification upon customer instruction. This step can be performed again for the next step depending on the payment details such as amount, maker, branch and department.

TEMPORARY QUEUE
Messages can be created from the templates that are saved during the previous entries. All inquiries can be done with strict or tiered entries of almost all common fields of the messages.

RELEASE QUEUE
The Message release process is handled through this menu. The Backoffice or Operation Departments use this menu. This is the last process for the outgoing messages.

INCOMING SWIFT MESSAGES ROUTING ENTRY MENU
This is the first menu where all the incoming messages are processed. If the bank has only one BIC address then all messages arriving at this BIC address are routed to the related branches through this menu.

INBOUND QUEUE
This menu handles the acceptance/owning operations for the messages. If the message does not belong to the arriving branch, the user has the opportunity to send the message back to the "Incoming Routing Menu".