SWIFTStandards - Category n - Common Group Messages

1 SWIFTS tandardsCategory nCommon Group MessagesNovember 2003 Standards ReleaseStandards Release Guide 2003 - Final edition - February 20031 Legal NoticesIMPORTANT NOTE: You may install and use this publication only if you have entered into the relevant licence agreementwith swift . Please refer to such licence agreement to determine what you may or may not do with it. Note however that inthe case of a Single User Licence , this publication must be installed on a standalone machine for access by one person atany one time, and references to "organisation" in these notices are to the ordering customer (BIC 8). In the case of a ServerLicence , this publication can also be installed on a server for access within the organisation of the ordering customer (BIC8), and references to "organisation" are then to all those swift Users belonging to the same Group as the ordering customer(BIC8) for traffic aggregation SCRL (" swift "), avenue Ad le 1, B-1310 La Hulpe, Belgium, 2002.

2 All rights reserved. No partof this publication may be copied or reproduced, stored in a retrieval system, sold or transferred to any person, in whole orin part, in any manner or form or on any media, without the prior written permission of swift . The recipient is, however, authorised to copy or reproduce this publication within its own organisation as may be reasonably necessary for the purposefor which it is supplied. Any such copy or reproduction will include the following: acknowledgement of the source, refer-ence and date of publication, and all notices set out on this publication may contain proprietary and/or confidential information of swift and/or its suppliers.

3 The recipientshould not disclose this publication outside its organisation without the prior written permission of swift has used reasonable efforts to ensure accuracy of its contents, swift assumes no liability for any inad-vertent error or omission that may appear in this publication. The information in this publication is the latest available at thedate of its production, and may change from time to and PatentsSWIFT, , the swift logo, Sibos, Accord and swift -derived product and service names - such as but notlimited to SWIFTNet and SWIFTA lliance - are trademarks of SCRL. swift is the trading name of All other product or company names that may be mentioned in this publication are trademarks or registered trade-marks of their respective owners.

4 Patent pending: SWIFTNet - TrustAct - 2003 editionStandards Release Guide 2003 - Final edition - February 20032 SWIFTS tandards - Category nLegal NoticesOverviewAdded message TypesRemoved message TypesModified message TypesAdded message TypesNoneRemoved message TypesNoneModified message TypesMTN90 MTN913 Standards Release Guide 2003 - Final edition - February 2003 OverviewSWIFTS tandards - Category nMT n90 Advice of Charges, Interest and Other AdjustmentsMT n90 ScopeThis message type is sent by an account servicing institution to the account is used to advise charges, interest or other adjustments which have been debited or credited to the account owner saccount.

5 It provides details of charges which are previously unknown to the n90 Format SpecificationsMT n90 Advice of Charges, Interest and Other AdjustmentsStatusTagField reference Number16x 1M21 Related Reference16x 2M25 Account Identification35x 3M32aValue Date, Currency Code, AmountC or D 4O52aOrdering InstitutionA or D 5M71 BDetails of Charges6*35x 6O72 Sender to Receiver Information6*35x 7M = Mandatory O = OptionalMT n90 Network Validated RulesThere are no network validated rules for this message n90 Field Specifications1. Field 20: Transaction reference NumberFORMAT16xPRESENCEM andatoryStandards Release Guide 2003 - Final edition - February 20034 SWIFTS tandards - Category nMT n90 DEFINITIONThis field specifies the reference assigned by the Sender to unambiguously identify the VALIDATED RULESThis field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).

6 2. Field 21: Related ReferenceFORMAT16xPRESENCEM andatoryDEFINITIONThis field contains the reference of the transaction to which the charge(s), interest or other adjustment(s) in this messageapply, eg, field 20 Transaction reference Number of the related swift VALIDATED RULESThis field must not start or end with a slash / and must not contain two consecutive slashes // (Error code(s): T26).3. Field 25: Account IdentificationFORMAT35x(Account)PRESENCE M andatoryDEFINITIONThis field identifies the account that has been debited or credited for the charges, interest or other adjustment(s).4. Field 32a: Value Date, Currency Code, AmountFORMATO ption C6!

7 N3!a15d(Date) (Currency) (Amount)Option D6!n3!a15d(Date) (Currency) (Amount)5 Standards Release Guide 2003 - Final edition - February 2003MT n90 SWIFTS tandards - Category nPRESENCEM andatoryDEFINITIONThis field specifies the value date and amount of the charges, interest or other C specifies the value date, currency and amount D specifies the value date, currency and amount VALIDATED RULESDate must be a valid date expressed as YYMMDD (Error code(s): T50).Currency must be a valid ISO 4217 currency code (Error code(s): T52).The integer part of Amount must contain at least one digit. A decimal comma is mandatory and is included in the maximumlength.

8 The number of digits following the comma must not exceed the maximum allowed for the specified currency (Errorcode(s): C03, T40, T43).5. Field 52a: Ordering InstitutionFORMATO ption A[/1!a][/34x]4!a2!a2!c[3!c](Party Identifier)(BIC)Option D[/1!a][/34x]4*35x(Party Identifier)(Name & Address)PRESENCEO ptionalDEFINITIONThis field identifies the ordering institution of the initial transaction, if different from the Receiver, ie, the account VALIDATED RULESThe BIC must be a swift registered address, either connected or non-connected (Error code(s): T27, T28, T29, T45).The BIC must not be a BEI, ie must not be of subtype BEID, MCCO, TESP or TRCO (Error code(s): C05).

9 6. Field 71B: Details of ChargesFORMATO ption B6*35x(Narrative)In addition to narrative text, the following line formats may be used:Line 1/8a/[3!a13d][additional information](Code) (Currency) (Amount) (Narra-tive)Standards Release Guide 2003 - Final edition - February 20036 SWIFTS tandards - Category nMT n90 Lines 2-6[//continuation of additional information](Narrative)PRESENCEM andatoryDEFINITIONThis field contains a specification of the charges, interest or other adjustment(s).CODESIn Category 1 and 2 Messages , Code may contain one or more of the following codes, followed, where relevant, by thecurrency and amount:COMMOur related telephone relating to the most appropriate and efficient means of telecommunications available, eg, swift , telex, telephone, facsimile, as determined by the party executing the payment telex Category 4 and 7 Messages , Code may contain one or more of the following codes, followed, where relevant, by thecurrency and amount.

10 AGENTA gent s correspondent s discountINSURI nsurance and Release Guide 2003 - Final edition - February 2003MT n90 SWIFTS tandards - Category nCODESIn Category 5 Messages , Code may contain one or more of the following codes, followed, where relevant, by the currencyand including insurance, added taxUSAGE RULESIf Currency is present, the number of digits following the decimal comma in Amount will not be validated against themaximum allowed for the specified code used in this field must be between slashes and must appear at the beginning of a text must not start with a slash and, if used, must begin on a new line and be the last information in the Field 72: Sender to Receiver InformationFORMAT6*35x(Narrative)In addition to narrative text, structured text with the following line formats may be used.