Reference › Test Case Reference › Assertion Descriptions › Other Assertions › Validate SWIFT Message Assertion

Validate SWIFT Message Assertion

The Validate SWIFT Message assertion lets you validate the syntax and semantics of SWIFT messages.

The assertion includes the following fields:

Name

Defines the name of the assertion.

If

Specifies the behavior of the assertion from the drop-down list.

then

Specifies the step to which to redirect if the assertion fires.

Log

Identifies event text to print if the assertion fires.

The assertion also includes the following SWIFT-specific fields:

SWIFT Message Type

Specifies the message type with which to validate the message. The available message types are MT, MX, and SEPA. The default message type is MT.

For the message type MT, DevTest supports the following categories:

MT1nn

Customer Payments

MT2nn

Financial Institution Transfers

MT3nn

FX, Money Market, and Derivatives

MT4nn

Collections and cash letters

MT5nn

Securities Markets

MT7nn

Documentary Credits and Guarantees

MT9nn

Cash Management and Customer Status

For the message type SEPA, DevTest supports the following categories:

• Resolution of Investigation (camt.029.001.03)
• Payment Cancelation Request (camt.056.001.01)
• Customer Credit Transfer Initiation(pain.001.001.03)
• Customer Payment Status Report (pain.002.001.03)
• Financial Institution Payment Status Report (pacs.002.001.03S2)
• Payment Return (pacs.004.001.02)
• Financial Institution Customer Credit Transfer (pacs.008.001.02)

For the message type MX, DevTest supports the latest versions (as of February 2014) of the full catalog of ISO20022 messages, which are listed at http://www.iso20022.org/full_catalogue.page.

Validation Syntax only

Specifies whether the assertion validates syntax and semantics.

Values:

• Selected: The assertion validates only the syntax.
• Cleared: The assertion validates both syntax and semantics.

Default: Cleared

If you click Run Assertion, any validation errors appear in the System Messages window.

Notes:

• Ensure that lines in MT messages end with the required Carriage Return/Line Feed characters (0D0A in ASCII hex; 0D25 in EBCDIC hex). Otherwise, the following error is reported.

  "The input Swift message cannot be parsed because of invalid syntax. Please check the message structure. Take notice of block separators,carriage-return line-feed characters and the presence of mandatory blocks."
  

• Ensure that an MT message has no invalid trailing spaces before the end of a line. The reported errors are sometimes unclear.

  For example, if the following line

  :32A:071119EUR50000, 
  

  contains an invalid trailing space before the end of the line, DevTest reports the error message:

  "T43 - The integer part of Rate must contain at least one digit. A decimal comma is mandatory and is included in the maximum length tag:32A."
  

• Ensure that the MX messages conform to the supported versions.

  For example, camt.052.001.04 is supported but the older camt.052.001.01 is not.