SWIFT Editor

Sterling B2B Integrator provides you with an online editing interface, the SWIFT Editor, which enables you to correct a SWIFT message (MT and MX) that was returned due to an error in translation (a validation check failed) or transmission (including a process failure such as a negative acknowledgement (NAK)). The Sterling B2B Integrator maintains a link between every SWIFT message that is returned for reprocessing and its historical predecessor, so there is a record of every rejected message all the way back to the initial submission, including references to each person that modified the message and the return code (error status and reason).

The SWIFT Editor contains a sidebar on the left side that provides useful information about the document history and error reports that includes the reasons for an error that occurred.

The SWIFT Editor also enables you to search through the applicable code lists quickly and easily through the Tools section in the SWIFT Editor, including the following:

  • SWIFT_Addresses List
  • SWIFT_BaseAddresses List
  • SWIFT_IBANFormats Code List
  • SWIFT_Currencies Code List
  • SWIFT_Countries Code List
  • SWIFT_BICPlusIBAN and BICPlusIBAN Code Lists
  • SWIFT_SEPARouting Code List
  • NISOLanguage Code List

The editing process requires two different roles (performed by two separate people), per the SWIFT guidelines. Your system administrator will add the appropriate permission (listed in the table below) to the user accounts for both roles to enable each role to perform properly.

Role Description Permission Assigned
Editor This is the person who edits a SWIFT message. SWIFT Message Edit
Reviewer This is the person who submits modified messages to be resent. SWIFT Message Resend

The combination of both roles provides the “four eyes” validation required by SWIFT.

The editing process is as follows:

  1. An e-mail alert is sent to the configured address when an outbound translation has errors during FIN enveloping or when a NAK is received.
  2. The Editor searches for the returned message through the EDI Correlations search (searching for messages with ReadyForEdit status), and displays the message in the SWIFT Editor.
  3. After the Editor repairs the message (or verifies that it does not need repair) and saves it, a separate e-mail alert is sent to the address configured for the Reviewer (the person responsible for auditing the repair and resending the message).
  4. The Reviewer receives the e-mail alert and audits the message (looking for messages with ReadyForResend status). The Reviewer accesses the SWIFT Editor in read-only mode. The error report specifies the original errors and the modified and/or added fields as links to their position in the document.
  5. After reviewing a repair message, the Reviewer determines how to handle it. The Reviewer can:
    • Reject changes and mark the message for further edit.
    • Abort the repair process entirely.
    • Resend the message using the specified business process.

Editor Tasks

The Editor repairs and saves SWIFT messages that are returned or rejected because of translation or transmission errors.

The following caveats apply:

  • The error report displayed in the SWIFT Editor when a Reviewer accesses a repaired document shows all errors and links them to their position in the SWIFT Editor.
  • All groups and records can be collapsed and expanded as needed to focus viewing.
  • Highlighting an error icon in the SWIFT Editor displays the error message for reference.
  • The SWIFT Editor allows users to modify field values and add or delete instances of repeating groups and records.