mtn99

8/11/2019 mtn99

1/6

Standards

Standards MT November 2013

Message Reference Guide

MT n99 Free Format Message

This document describes a MT message exported from the MyStandardsweb platform. You can also consult this informa-tion online.

Published by SWIFT and generated by MyStandards.
http://www.swift.com/mystandardshttps://www2.swift.com/mystandards/baseStandards/mt/mtMessageDescription.faces?message=mt/2013.November/n99https://www2.swift.com/mystandards/baseStandards/mt/mtMessageDescription.faces?message=mt/2013.November/n99http://www.swift.com/mystandards

8/11/2019 mtn99

2/6


2 Message Reference Guide - MT n99 Free Format Message

Table of Contents

.Message Types ............................................................................................................................................................... 3

.MT n99 Free Format Message.................................................................................................................................. 4

.MT n99 Scope ......................................................................................................................................................... 4

.MT n99 Format Specifications .............................................................................................................................. 4

.MT n99 Network Validated Rules ........................................................................................................................ 4

.MT n99 Field Specifications .................................................................................................................................. 4

.1. Field 20: Transaction Reference Number.......................................................................................... 4

.2. Field 21: Related Reference ................................................................................................................. 5

.3. Field 79: Narrative .................................................................................................................................. 5

.MT n99 Examples ................................................................................................................................................... 5

.Example 1 ..................................................................................................................................................... 5

.Legal Notices ................................................................................................................................................................... 6

8/11/2019 mtn99

3/6

Message Types

3

Message Types

The following table lists all message types defined in this book.

For each message type, there is a short description, an indicator whether the message type requiresauthentication (Y/N), the maximum message length on input (2,000 or 10,000 characters), whether theuse of the message requires registration with SWIFT for use in a message user group (Y) or not (N)

and whether value date ordering (VDO) can be requested for the message (Y/N). Value date orderingcriteria are described in the Standards MT General Information.

MT MT Name Purpose Authen. Max.

Length

MUG VDO

n99 Free Format Mes-sage

Contains information for whichno other message type hasbeen defined

Y 2000 N N

8/11/2019 mtn99

4/6




MT n99 ScopeThis message type is:

used by financial institutions to send or receive information for which another message type is notapplicable.

used between a corporate and its financial institution for which another message type is not applica-ble.

The category digit should be chosen so the message will be routed to the unit of the Receiver which ismost capable of acting on the information.

This format does not apply to category 4 and 7. For more details, see the relevant category MessageReference Guidefor MT 499 and MT 799.

For use of messages in the corporate-to-bank environment, see the MT message implementation guideand message matrix for corporate customers available on www.swift.com.

MT n99 Format Specifications


Status Tag Field Name Content/Options No.

M 20 Transaction Reference Number 16x 1

O 21 Related Reference 16x 2

M 79 Narrative 35*50x 3

M = Mandatory, O = Optional

MT n99 Network Validated RulesThere are no network validated rules for this message type.

MT n99 Field Specifications

1. Field 20: Transaction Reference Number

FORMAT

16x

PRESENCE

Mandatory

DEFINITION

This field specifies the reference assigned by the Sender to unambiguously identify the message.
http://www.swift.com/

8/11/2019 mtn99

5/6


5

NETWORK VALIDATED RULES

This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Errorcode(s): T26).

2. Field 21: Related Reference

FORMAT

16x

PRESENCE

Optional

DEFINITION

This field contains a reference to the related message.


This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Errorcode(s): T26).

3. Field 79: Narrative

FORMAT

35*50x (Narrative)

PRESENCE

Mandatory

DEFINITION

This field contains the free format message.


If this message is used in category 1 or in category 2 and if the first six characters in line 1 contain thecharacter string /REJT/ or /RETN/, then it is mandatory to follow the Payments Reject/Return Guide-linesdescribed in the Standards MT Usage Guidelines(Error code(s): T80).

MT n99 Examples

Example 1

As any free format information may be provided in this message type, no message examples will beprovided.

8/11/2019 mtn99

6/6



Legal Notices

Copyright

SWIFT SCRL 2014. All rights reserved.

This material is a component of MyStandards, the SWIFT collaborative Web application used to man-age standards definitions and industry usage. It can only be used and distributed in accordance withMyStandards Terms of Use.

Unless otherwise agreed in writing with SWIFT SCRL, you have no right to:

- authorise external end users to use this component for other purposes than their internal use.

- remove, alter, cover, obfuscate or cancel from view any copyright or other proprietary rights noticesappearing in this physical medium.

- re-sell or authorise another party e.g. software and service providers, to re-sell this component.

Confidentiality

This publication may contain SWIFT or third-party confidential information. Only disclose it outside yourorganisation in accordance with MyStandards Terms of Use and your related license rights.

This component is provided 'AS IS'. SWIFT does not give and excludes any express or implied war-ranties with respect to this component such as but not limited to any guarantee as to its quality, supplyor availability.

Any and all rights, including title, ownership rights, copyright, trademark, patents, and any other intellec-tual property rights of whatever nature in this component will remain the exclusive property of SWIFT orits licensors.

Trademarks and Patents

SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:SWIFT, the SWIFT logo, 3SKey, Innotribe, Sibos, SWIFTNet, MyStandards, SWIFTReady, and Accord.

Other product, service, or company names in this publication are trade names, trademarks, or regis-tered trademarks of their respective owners.

Documents

mtn99