49 thoughts on “SWIFT MT940 Customer Statement – Detailed analysis”

    1. The MT940 is usually sent by a bank to another bank (concentrating institution) which is authorized by the account owner (a company or a bank) to receive it while the MT950 is usually sent by a bank directly to the account owner. The MT940 can also be sent to the account owner directly of course. In the MT940, additional information about the line statements can be provided. You can also find the Forward Available Balance in the MT940. But both are account statements and the one or the other may be used in many cases.

      1. Shashidhar Pande

        Hi Paul,

        Thanks for sharing valuable info about MT940/MT950 message. I have one query, regarding Additional Information (F86). Is there any standards specified for sharing information in F86. E.g. If multiple information is provided in this field, then what should be delimiter/separator to differentiate between two or more values(like in F61 statement line // is used to differentiate between Owner Ref and Sender Ref).

        1. In the SWIFT standards, we read that the format of the field 86 is 6*65x. Up to 6 lines with maximum 65 characters.
          Except what you read in the usage rules, I am not aware of other specificities.
          But an agreement is possible between two or more parties to structure this field according to their own needs.
          They will then decide how to structure it.

      2. Hello Jean,
        1. Tag 61 is mandatory in case of MT940 and non mandatory in case of MT950. Hence I would say, MT940 is a detailed statement, whereas MT950 not necessarily detailed statement, it could just be a summary by providing only the opening balance and closing balance.
        2. Presence of tag 86 in 940 and absence in 950. Implies, additional information to the account owner can be provided in 940 and not in 950

        1. Hi Srikanth, Thanks for your contribution. I fully agree with the point 2. As for the point 1, I checked the SWIFT specifications again and the Tag 61 is optional.

  1. Thanks a lot Paul. Is it also true that mt940 only includes entries which are results of swift messages but mt950 includes all types of entries.

    1. Hi Pramod, Both MT940 and MT950 are account statements with all entries booked on the account, no matter if entries result from SWIFT messages or not. An account statement with entries resulting only from SWIFT messages would not make sense at all. The customer would never know exactly how much money he has on the account and could therefore not be able to make any decision. Account statements always include all entries independent of the origin. Thanks for allowing me to clarify this. If you have further question, do not hesitate.

  2. Each MT940 message come to bank in relation to respective MT103 message next day.

    If a Bank has Nostro account with another Bank. Then I want to know which Banks creates and send MT940 message for a MT103 payment. is the Nostro Bank creates MT940 or Transaction initiated Bank.

    1. The MT940 is an account statement. The sender of the MT940 is the account holder and the receiver is the account owner.
      It does not matter if the account is a Nostro or a Vostro. The sender is always the account holder and the receiver is always the account owner. Let me know if you need more explanation.

  3. Hi Jean Paul,

    I would like to ask you one question:

    – is there a way to send MT940s through a correspondent bank?

    Just to describe the issue I am facing (as the client): I want to activate MT940 (receiving bank will be BNP) and sender will be BYLADEM1001. I have contacted the sender bank and they said that they should send the MT940 statement through a correspondent bank (in my case BYLADEMM) – looks like the same bank (maybe its the central office).

    Is that possible? Which whom of the parties should I sign the agreements in case this is possible?

    Thank you for your time!
    Sorin

    1. Hi Sorin,
      The answer to first question is clearly Yes. It is possible and you do not have the choice in this case. BYLADEM1001 (1 at position 8) is a not connected BIC and therefore cannot send messages. For cost reduction and efficiency, they have centralised the sending of MT940 in the main office. For the receiver, it does not matter that much. You get the account statement anyway. It is just that the sender BIC will be different. Everything else will be the same.
      For the second question, I do not know. There are so many cases and regulation is different per country. If anyone can help, feel free to do so.

      1. Karthikeyan Thondiraj

        Hi Sorin

        Yes, you can sign the agreement with the BYLADEMM for the account statement. As Jean rightly pointed out that any Swift BIC with the eight digit ending with 1 is an “Invalid Swift bic” – meaning not connected and hence cannot send or receive. However, in those cases all the details availability and the agreement can be signed with the Head office Swift bic.

        Hope this clarifies., sorry i was just going through the reply, noticed this one.

        Regards
        KT

  4. Hi Jean Paul,

    I would like to know if the MT940 carries a field for the deposit date of cash/cheques. and If not, are there any unused fields in the MT940 format where the bank could specify the date as a text field so that the same would reflect in customer EBRS

    Thanks in advance
    Tharindu

    1. Hi Tharindu,
      there is no specific field in the MT940 for the deposit date of cash/cheques. In the statement line, there is a 34 long field where you can potentially put that information. If not, you have Information to Account Owner (Field 86) that is pretty long and could bear that information too.
      The receiving party must be informed about position, format and length of that information if it should process it STP. If not you can write explicitly “Deposit date of cash YYYYMMDD”.

    1. Hi Everton,
      Option P allows you to provide the BIC of the account owner in addition to the account number. This option is generally used when the receiver is not the account owner. It is receiving it on behalf of the account owner. The BIC allows to easily identify the account owner and forwards him the statement if required.

  5. Hi,
    I am a little confused regarding the account holder and account owner.
    I am stuck on this as my bank is not providing the correct header details and I am unclear as to what exactly I should be asking for.

    I am trying to configure an bound integration for my bank statement with a new format of MT940 but I am having issues as my file is missing the BIC and Bank code.

    I assume, my company – Company X is the account holder and therefore the receiver of this information. Is this correct?
    I don’t expect to have a account owner BIC that varies from the account holder.

    I would expect my statement to be named

    ‘MT940HSSBCCE x x x x x x x’

    Thanks

    1. Hi Susan, my understanding is that your company (company X) is the receiver and your bank is the sender. Since you are receiving the account statement from SWIFT, it should contain an application Header Block for Output Message. You can find the specifications here with examples. Please check and let me know if you have further questions.

  6. Hi Paul,

    We generate MT940 statement for a date range (eg : 01-03- 2019 to 30-04-2019). It is split into multiple messages.

    In all the messages, the Intermediate Account opening balance tag (Tag 60M ) is always populating date as 01-03- 2019 and Intermediate Account closing balance(Tag 62M) is always populating as 30-04-2019, whereas the balances are populating as per the corresponding opening date and closing date of transaction in a message.

    Is this the correct functionality?”

    1. Hi Anoop,
      Sorry for not answering before. I am very busy at the moment.

      To be strict, the date of the Intermediate Account opening balance tag (Tag 60M) should ideally take the date of the last (debit or credit) entry and the date of the Intermediate Account closing balance(Tag 62M) should also ideally take the date of the last (debit or credit) entry.
      That totally makes sense. In reality, people do not care that much about those dates as long as the balances are correct. What truly matters in a statement are the dates of the opening and closing balances.
      Dates of Closing Available Balance and Forward Available Balance are really important too. They must be correct. If you can easily fix the dates of intermediate balances, do it. Receivers won’t waste time asking themselves the same question.

      Regards,
      Jean Paul

  7. Hello Jean Paul

    This is a great site and I am very appreciative of the resources shown and the clear explanations. Question – is it acceptable per MT940 standard to have “blank space” between one statement the next? See below example:

    -}

    {1:

    I am receiving this from a bank currently and the bank is pushing back on removing space. Our integration however is rejecting because of this space. Thanks!

    1. Hello Matt,

      Thanks for the appreciation! Characters in the SWIFT MT world are not always an easy topic.
      If I understand correctly, you have two CrLf characters between one statement and the other and your integration does not expect that.
      Unfortunately that specific point is not clear in the SWIFT standards. The standard specifies the use of CrLf for fields, but does not say anything about the end of the message. At least I am not aware of. However, I have already seen applications like your integration that reject messages if two CrLf come at the end. They expect only one CrLf.

      So You cannot oblige the bank to remove the space based on the standards. 🙁 I hope you find a solution.

      Best regards,
      Jean Paul

  8. Hello Jean Paul

    This is a great site and i refer it lots of time to find out answers. Related to MT940/950 i have a question. When the MT statements gets broken into multiple pages i.e. what is the length of page so that the generated MT messages gets reported in multiple pages ?

    1. Hi Anul,
      Thanks for your appreciation 🙂
      The maximum length of a SWIFT MT940 or MT950 message is 2000 characters. When a statement is broken into multiple pages, the sequence number in the field 28C must be populated accordingly.

      1. Hi Jean. Can you please tell us what is the MT940 file size? (in kb/mb?) And what would be the Swift Message file size as well?

    1. I would say it is probably YES, but I am sure. Please check the documentation of Oracle EBS Financials or check with Oracle directly.

  9. Hi Jean Paul,

    One question I have received regarding the sending of MT940, is there a rules from SWIFT that mention that in order to send an MT940 to company a SWIFT contrat is mandatory.
    I thought that MT940 can be send without having a SWIFT contract has long company sent the instruction to the bank to send MT940?

    1. Hi Mark,
      Not sure what you mean with a SWIFT contract. I am not aware of any contract required in that context. But your bank may have specific rules.
      In the SWIFT standard, it is said that the MT940 can be sent to a party authorised by the account owner to receive the information. Obviously, the receiving party must be reachable through the SWIFT network.

  10. Hi Jean Paul,

    I am from a Software Product Company delivering MT 940 statement through our system. I understand if the message size is more than 2000 characters, the message needs to be split into multiple pages with incremental message sequence number. In case if we are generating more than one page, what should the value of tag 60 and 62 in each of pages? Same value for 60 and 62 across pages?

    Thanks is advance

    1. Hi,
      Below are the SWIFT rules.
      The first customer statement message for a specified period must contain field 60F (first opening balance); additional statement messages for the same statement period must contain field 60M (intermediate opening balance).
      If there is only one customer statement message transmitted for the period, this field must use tag option F, that is, 62F (final closing balance). When several messages are transmitted for the same statement period, all messages except the last message must contain field 62M (intermediate closing balance); the last message of the statement must contain field 62F.

      Regards,
      Jean Paul

  11. Hi Jean Paul,
    my task is to process received MT 940 messages, especially doing stuff when a split message has fully received. The sequence number is just a counter. How can I recognize that all sequences of the MT 940 are received?

  12. Hi Jean, hope you are good?

    We (bank) currently deliver the MT-940 to our end clients (corporates) via SFTP. A client requests that the MT-940 should be delivered to their corporate BIC.

    Is this a possibility? Could you share some thought on this?

    Many thanks,
    Toluth

    1. Hi Toluth,
      we (bank) are looking to offer to our clients the possibility to deliver the MT-940 via SFTP, but I couldn’t find technical specification about how to implement this in our Swift Alliance. How did you implement your service MT-940 via SFTP?.
      Thanks in advance for your help.

  13. Hi Jean,
    In MT940/ MT942 can tag 86 Information to Account Owner (which is coming after field 61) can it come without tag 61? as 61 is optional tag

  14. Hi Jean,

    I am doing freelancer service for UK comapny from india.

    Uk Comapny transfered the money to my local bank thru wire transfer .My bankers(ICICI) received the payment.

    They said that ,we received the money , but without MT940 we couldnt able to transfer the money to your account.

    so you have to request your company to ask the sender bank(HSBC) to send the MT940 in the swift Header.

    whereas my contract comapny said that you have to ask your bank to contact hsbc to resend the MT940

    Really I dont know what i have to do next. whom should sort out my issue?.

    Thank you

  15. Hi Jean,

    Im really struggling trying to find specifications (or at least consistent information) regarding format and/or delimiters when MT940 Statements are paged into multiple pages and sent in a single file. We have seen many variations and would like to know if any are considered more correct. Here is an example of what I have seen:

    {4:
    statement page 1
    -}
    {4:
    statement page 2
    -}

    or
    {4:
    statement page 1
    -}
    $
    {4:
    statement page 2
    -}

    Any help on this would be greatly appreciated

  16. Hi Jean,

    We are experiencing an issue with one of our bank account MT940 files in that it doesn’t provide a tag 86 for certain transactions. We queried this with the bank as we could see the additional details for these transactions on the online statement.
    Is was their response: the product code for Direct Debits is 1855 – Automated Data Capture Entry, and because the direct debits are not managed within our system that send out the MT940 messages, there is no rule in place to populate these fields.

    Have you seen this issue before and do you know of a workaround or fix?

    Kind regards
    Natalie

  17. HI team

    Can any one explain what is “Tag 20 – Transaction Reference Number ”
    as inquired by Mr. Hamza

    Regards

Leave a Comment

Your email address will not be published. Required fields are marked *