• Swift Message Format Generator
• Swift Codeword And Rule Engine
• Swift Text Validation Engine
• Swift Syntax&Semantics Check Engine
• Swift Language Support Engine
   - Turkish
   - English
SWIFT User Interfaces (Running on AS/400)

General Summary and Specifications :

All Incoming message types and 47 Outgoing message types (MT1XX, MT2XX, MT3XX, MT4XX, MT7XX, MT9XX) are supported by Global Bilisim's SKAY/400 User Interface software. MT6XX and the other types MT5XX , MT8XX of messages can be defined dynamically to our Interface and checked by Rule and Check Engines of the SKAY software. To add a outgoing message to SKAY/400 takes 2 or 3 business days.

Because we add them dynamically to the format,syntax,semantic,check,text validation and rule tables and their engines.

SAE, SAA make only syntax and semantics rule checks and don't make any Code Word or Text Validation checks. Because these rule checks(Other than syntax and semantics) done by bigger and competent software of SWIFT s.c.r.l in Belgium.

Almost all of the NAK reason code is that Code Words and Text Validation Error Codes.

There are Word Rules, Text Validation Rules, Syntax and Semantics Rules in SWIFT-NET.

SKAY do all checks for the user. The user have no possibility to make mistake related with these rules.

SKAY supplies 2 different languages(English and Turkish Languages) support for message entries.

These are why SKAY is "BUY and USE it"

Swift User Interface includes these modules :

Swift Message Format Generator: This module create the message dynamically with all alternate field options.

Swift Code Word And Rule Engine: Keeps the Code Words that using in SWIFT system and apply the rule checks to avoid "NAK" conditions.

Swift Text Validation Engine: Validate the text for example Turkish characters, special Characters like ":" "-" for every field differently.

Swift Syntax & Semantics Check Engine: Like SAE and SAA this module checks the message syntatically and avoid the "ALNK" conditions.

Swift Message Language Support Engine: There are 2 language support for the messages. The message Labels, Fields and Rules are set according to user. These languages are Turkish and English.

Routing Mechanism: Makes the routing of the incoming messages to the branches and refusal of the wrong messages to Backoffice Department with the explanations on it.

Operational Specifications :

OUTGOING MESSAGE OPERATIONS

After the message "Entry" and "Verification" processes, message send to the "Outgoing Message Provision Verification Menu". After the "Correspondent Relations" operations the message can be send back to the "Branch Message Entry Menu" or send forward to the "Outgoing Message Release Menu".

Backoffice checks the messages, keep, save or create correspondent balances, controls provisions. SWIFT Room check and release the messages and follows it's responses. (Messages responses can be ACK or NAK) . If a message take the ACK code from the SWIFT-NET then it's status give back to the branch and a "Bank Reference Number" generated in this format O-001-0000001(Outgoing Message-Branch Code-Unique Identifier)

INCOMING MESSAGE OPERATIONS

All the incoming messages are controlled and ROUTED the related branhces bye the "SWIFT Room". So BIC addresses are not needed for the branches to receive messages.

After the routing step the related brach can see the messages from the "Message Observation Menu" but can not do anything according to this messages. Because the message is not at the "Incoming Message Entry/Acceptance Menu" (first step for the branch is "Message Entry/Accept Menu") after the Exstre(MT950) Verification of Backoffice.

At the "Incoming Message Entry/Accept Menu" if the message is not belongs to branch, this message can send back to the Swift Room's "Message Routing Menu" again. If its okey, user that have this menu can ACCEPT the message(i.e make its entry) and send it to "INCOMING MESSAGE VERIFICATION MENU".

Authorized User can verify the message or send it back to "Incoming Message Entry Menu". If User verify the message it's spooled output generated and sended to the printer. This print out is the only printed form of the message and with this output user can do payment or other related operations. Also a unique code for the bank's swift messages are generated in this format (Direction-BranchCode-Unique Identifier) Ex. I-001-0000001(Incoming Message-Receiving Branch code is 001-Unique Identifier)