This transaction processes incoming messages of different formats. A file can contain one or more messages in the respective format.
The processing of partial messages, like in SWIFT MT 700 and MT 701 messages, is supported. This means individual partial messages belonging together are accounted as one complete message and will be provided for further processing.
The application currently supports technical message formats (refer table in below section) in the processing of incoming messages.
Other message interfaces can be defined in compliance with the bank.
The messages are usually stored as text files in the subdirectories of the “Data” partition.
Thus, relative path names for defining the output directories are relative to the partition “Data”. If necessary for organizational reasons, absolute path names can also be defined. In doing so, the usage of the prefix 'db': (files in databases) is also possible. Optionally, incoming messages can be sent in separate directories per entity or in a common directory for the entire installation.
Message Type | Internal Channel | Subdirectory in Partition 'Data' | Services |
---|---|---|---|
DTALC | DTA | dtain | SRVDTA |
DTAEA | DTE | dtein | SRVDTE |
DTA Guarantees | DTG | dtgin | SRVDTG |
SWIFT | SWT | swtin | SRVSWI |
TradeConnect | TCO | tcoin | SRVTCI |
Telex | TLX | tlxin | SRVTLI |
EML | emlin | SRVEMI | |
Bolero | BOL | bolin | SRVBOI |
SWIFT FileAct | FIL | filin | SRVSFI |
allNETT | ANT | antin | SRVANI |
RIVO | RVO | rvoin | SRVRVI |
SmartForms | DOI | doiin | SRVDOI |
Incoming Invoice | FIL | invin | SRVINV |
EasySend | ESY | easyin | SRVESY |
Compliance | CCS | ccsin | SRVSWI |
Swift XML | SXO | sxiin | SRVSXI |
The transaction carries out the following steps:
By using the switches -I <Name of the ini file> in the command line of the processing system, various instances of this transaction can be started (e.g. one that starts SWIFT from 8 a.m. until 6 p.m. every 10 minutes and another instance for TradeConnect messages, that will only be started once a day).
For message types SWIFT XML, also called Swift MX, (e.g. ISO20022 CBPR+ XML payment messages), the new service SRVSXI has been introduced. This service is used for importing incoming messages, e.g. Pacs.008, Pacs.009 and Technical Ack/Nack MX transmission messages (as a result of a technical validation if the message is compliant as per Swift MX rulebooks). Examples: Incoming Pacs.008 messages are routed to the transaction CPTSET (similar to incoming MT103) and incoming Pacs.009 messages to transaction SPTROU (similar to MT202). The technical Ack/Nack acknowledgement message is not mapped to a contract but received only to register the Ack/Nack status of the contract.
For the processing of incoming items to function properly, it is necessary to enter a default entity in SWITSK.INI. This default entity is used if no other entity was assigned to the user. Access takes place as follows:
If a message can be assigned to a contract, the entity of the contract is used.
If no contract is available:
If no entity was identified in this way, the default entity specified in SWITSK.INI in section [Settings] under 'DefaultETY=' is used.
This logic for assigning entities can be customized for individual projects within the rule “SWITSK.DetermineETY”.
If a contract is available, the user group of the user responsible for the contract is selected. In all other cases the default user group of the selected entity is used as user group.
Tag 23X in SCORE messages can be used to indicate that a file (logically, this is seen as an attachment to the message) - in any format whatsoever - is attached to the message (which itself consists of several part-messages) that is transported outside the SWIFT FIN service. If the delivery channel indicated in Tag 23X is SWIFT FileAct, the application collates the various sub-messages and the attachment. The message only appears in the in-tray when the last sub-message and the attachment have been received.
Technical procedure:
When all the SCORE messages have been received, the collation process checks whether there is an SMX record in which sender, receiver and file name details match those contained in Tag 23X.
Messages received via FILEACT are processed by the SRVSFI service. An SMH record - with a CORTYP of 'FIL' and a message type of 'FILEACT' - is generated for each incoming file. In addition, a check is run to see whether there is already an SMX record in which sender, receiver and filename match the incoming file.
The trigger formats “Swift Alliance Access XML v2 as Trigger” and “Swift Alliance Access XML v2 PDU via MQ” support the reception of FILEACT attachments via XMLv2 messages.
Swift Alliance Access XML v2 as Trigger
Swift Alliance Access XML v2 via MQ
Incoming Email messages that contain a signature but for which no certificate or public key has been saved can be imported without any fields.
To this end, in file “emlmod.ini” in Section [System], the entry IGNSIGFLG='Y' must be set.
When a flag is set, errors in verifiying the signature in multipart/signed elements are ignored - the negative verification result is only registered in the raw text extracted.
Managers running in foreground mode always need to be started manually.
For some incoming message types, it is possible to send a notification E-Mail to a specified recipient. This E-Mail will contain a link, so that the correct transaction for the incoming message will be started.
If 'Send E-Mail' is checked a notification E-Mail will be generated.
The send method can be:
In the pickup directory E-Mail files will be generated.
In the SMTP block SMTP settings have to be specified.
For Windows System the Convert Lineend to 0D0A normally has to be checked.
The Command has to be a URL of the DNG HTML5 client with server and port.
Fields for the E-Mail:
The E-Mail text should contain the Tag <URL>. This tag will be replaced by the command, extended with a SPT.INR and a transaction name. When the receiver of the E-Mail clicks on this URL the HTML5 client is started and after login it is chained directly into the transaction for the incomming message.
SWITSK has a possibility to fetch e-mails from the remote mailbox via standard POP3/IMAP interface.
Currently, this feature is enabled for SmartForms and EasySend message types.
To turn it on - the checkbox Use Mailbox has to be ticked
When it's activated - the mailbox will be checked for new e-mails during the regular update of SWITSK.
Connection settings can be found under button E-mail Settings.
Once clicked - the following pop-up with the standard mail client configuration will appear:
Setting | Description |
---|---|
Protocol | POP3 - when downloading e-mails - removes them from server - has no folders IMAP - synchronizes mails with the server - can have folders |
Email address | The address of the mailbox to get e-mails from |
Password | Password for the mailbox |
Server | Address of e-mail server Prefix (e.g. pop3:) is not mandatory |
Port | Port of the e-mail server When Auto is chosen - the port will be auto-detected on the first connection to the mailbox and saved |
SSL\TLS | Checkbox that indicates if the secure connection should be used Can be auto-detected |
Mailbox folder | Only for IMAP Allows to Choose the dedicated folder for fetching e-mails |
Get Folders | Only for IMAP Fetches the list of available folders from the mail server |
Incoming Directory | Indicates the directory where the e-mails (*.eml) will be stored Defaulted with the incoming directory of the respective channel |
Test Connection | Button used for testing connection to the mailbox The answer from mail server will be displayed in prompt |
The following descriptions apply to all configuration panels for the message formats.
Field | Description |
---|---|
Execute | If the checkbox is checked, the message format of this transaction will be processed. |
Print type | Defines the time and design of the print of processed messages. The following settings are possible: 1. Do not print No printing takes place. 2. Print formatted messages after join + routing Prints a message in an enhanced (better readable) format after available partial messages (e.g. 700 and 701) were composed to one complete message and a mapping to an entity or to a user/user group took place. The checkbox “Print partial messages immediately” and the field “Text for Header” in the same line enables each partial message to be printed with another header than that of the complete message. For this purpose, for example, the header 'Partial message' can be used. The checkbox “Print erroneous messages immediately” and the field “Text for Header” in the same line enables the additional print of each erroneous message with a header other than the messages without any errors. For this purpose, for example, the header 'Erroneous message' can be used. 3. Print immediately in raw format (routing by receiver only) Prints a message in its original format, without reformatting the content and the output of the description texts for the tags. |
Text for Header | Header for prints to be used by default. |
Technical Form | Defines the technical layout of the print forms to be used. For more details see “Printing”. |
Get Printer from | Defines out of which contexts printers can be selected. The content of the context is defined for each of the following settings in the respective static data system (user, user group, entity). The setting 'local' defines that the printer is defined and used in this panel and not by following-up entity, user group or user. Details about follow-ups are described in “Printing”. * <not specified> * Here * Entity * User Group * Users Note: If all incoming messages have to be printed on one specific printer, 'Local' has to be selected, because it can be defined via the entries on this panel which is the printer to be used. |
Printer | Will only be considered, if “Get Printer from” = 'Local' is selected and enables the selection of the printer to be used. |
Paper Bin | Will only be considered, if “Get Printer from” = 'Local' is selected and defines which bin should be used for printing. If no bin is selected here, the default bin of the printer is used. |
for 2nd Page | Will only be considered if “Get Printer from” = 'Local' is selected and defines which bin should be used for the print from the 2nd page on. If no bin is selected here, the bin selected under “Paper Bin” is used. |
# of Copies | Number of prints (incl. original) |
Directory | Name of the directory in the “Data” partition, where the incoming messages to be processed are stored. In this case it is important, that the subdirectories “arc” and “error” exist in the specified directory. Otherwise, the file cannot be stored for archiving error handling. |
File Extension | The file extension of the incoming messages to be processed. |
Manager for Incoming Messages
Incoming SWIFT
TradeConnect
Telex
DTA Import L/C
DTA Export L/C
DTA Guarantees
Email
Bolero
SWIFT FileAct + XMLv2
allNETT
allNETT STT
SmartForms
EasySend
Incoming Invoices
SWIFT XML
RIVO
RIVO STT
This is the main panel which displays all the 'Incoming messages' which are available in their respective target directories. User is provided with the selection criteria to select the required service/message types which are to be listed and the incoming messages are displayed for those selected service types.
Datafield | Description |
---|---|
SWIFT | This checkbox defines if incoming SWIFT messages should be imported. Details are determined on the relevant panel. |
Telex | This checkbox defines if incoming telex messages are to be imported. Details are determined on the relevant panel. |
DTA Import L/C | This checkbox defines if DTA Import L/C messages are to be imported. Details are determined on the relevant panel. |
TradeConnect | This checkbox defines if TradeConnect messages are to be imported. Details are determined on the relevant panel. |
This checkbox defines if incoming e-mails are to be imported. Details are determined on the relevant panel. |
|
DTA Guarantees | This checkbox defines if DTA Guarantees messages are to be imported. Details are determined on the relevant panel. |
Bolero | This checkbox defines if incoming Bolero messages are to be imported. Details are determined on the relevant panel. |
FileAct | This checkbox defines if incoming FileAct messages are to be imported. Details are determined on the relevant panel. |
DTA Export L/C | This checkbox defines if DTA Export L/C messages are to be imported. Details are determined on the relevant panel. |
allNETT | This checkbox defines if incoming allNETT messages are to be imported. Details are determined on the relevant panel. |
SmartForms | This checkbox defines if SmartForms messages are to be imported. Details are determined on the relevant panel. |
Approved Payables Documents | This checkbox defines if Approved Payables Documents are to be imported. Details are determined on the relevant panel. |
EasySend | This checkbox defines if EasySend messages are to be imported. Details are determined on the relevant panel. |
Compliance | This checkbox defines if Compliance messages are to be imported. Details are determined on the relevant panel. |
Start Time of Job Date | This field displays the date and time the Task Manager was started. |
Automatic Termination Flag | This field defines the reason for terminating the Task Manager - at a predefined time. In this case enter the time in the field on the right side - if list empty. The Task Manager will then stop when the list of open transactions is empty. - manually only. In this case the Task Manager will stop in case the “stop” button is pressed. |
Redotime | This field contains the restart time of the Task Manager in seconds. If processing is set to 'automatic', the Task Manager will restart after this time selected. If 'manual' any time period entered is irrelevant. |
Application Trace Flag | This option sets the trace level of the transaction. Higher values mean more details. |
This is the configuration panel for Incoming SWIFT and SCORE messages. Option is available to specify the incoming target directories for SWIFT and SCORE messages, along with the required file extension for those message files. Additionally, user could also configure for Printing setup and activate Local authentication hash by providing their key details.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This configuration panel is for TradeConnect messages for TCWEB. Option is available to specify the incoming target directories for TradeConnect messages, along with the required file extension for those message files. The data structure is merged with DTA for LC messages and DTG for Guarantee messages. Additionally, user could also configure for Printing setup and activate Local authentication hash by providing their key details.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This configuration panel is for incoming Telex messages (electronic communication message, which was widely used before SWIFT). Option is available to specify the incoming target directories for Telex messages, along with the required file extension for those message files. Also the user could configure the printer setup.
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This is the configuration panel for Incoming DTA message for Import LC. Option is available to specify the incoming target directories for DTA Import LC messages, along with the required file extension for those message files. Additionally, user could also configure for Printing setup and activate Local authentication hash by providing their key details.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This is the configuration panel for Incoming DTA message for Export LC. Option is available to specify the incoming target directories for DTA Export LC messages, along with the required file extension for those message files. Additionally, user could also configure for Printing setup and activate Local authentication hash by providing their key details.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This is the configuration panel for Incoming DTA (DTG) message for Guarantee messages. Option is available to specify the incoming target directories for DTA Guarantee messages, along with the required file extension for those message files. Additionally, user could also configure for Printing setup and activate Local authentication hash by providing their key details.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
For details on configuring the Bolero Terminal see Configuring Incoming Messages. Option is available to specify the incoming target directories for Bolero messages, along with the required file extension for those message files. User could specify the bank's OWN RID/BIC for receiving these incoming Bolero messages. Also, the type of print out format can be specified.
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
This configuration panel allows the user to define the trigger format for the incoming SWIFT Fileact messages. The XML format is wrapped like header to the message. The MT body of such messages is internally routed to and processed by 'Incoming SWIFT' service. Option is also available to specify the incoming target directories for Fileact messages, along with the required file extension for those message files.
From the allNETT configuration panel, user could choose the type of printout format. Option is available for selecting the automatic processing of incoming allNETT messages and also option is available to specify the incoming target directories along with the required file extension for those messages files. The message type/format is an internal proprietary XSD standard.
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
For more details on this message type, please refer "SmartForm". Option is available to choose the incoming message type format for the incoming SmartForms. Most used format/type is 'PDF'. Also, option is available to specify the incoming target directories along with the required file extension for those messages files. Since PDF could contain, passwords, that could also be stored for easy import of incoming files.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
“EasySend” provides a no-code platform to transform any paperwork-based process into responsive digitized process. The platform provides to end-user, custom-tailored web forms to fill which are then converted to PDF (hand signature also supported) and sent to DOKA-NG. The content of the form is then mapped by this transaction ‘Manager of Incoming Messages (SWITSK)’ into the related business transaction and the PDF is attached as evidence.
Option is available to choose the incoming message type format for the incoming message. Most used format/type is 'PDF'. Also, option is available to specify the incoming target directories along with the required file extension for those messages files. Since PDF could contain, passwords, that could also be stored for easy import of incoming files.
Datafield | Description |
---|---|
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
For more details on this business module, please refer APF. Option is available to specify the incoming target directories for the incoming messages, along with the required file extension
for those message files.
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
Datafield | Description |
---|---|
Type of Print | cf Appendix A, Table PRT field PRTTYP |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |