Skip to main content

Processing MT 940 files

The MT 940 bank file is a standard report type that is part of the SWIFT bank messaging system. It is a summary report of entries booked to an account similar to the camt.053 bank file. However, it differs from the camt.053 significantly in that the MT 940 specification is less rigid, giving banks room to make their own MT 940 file definitions.

Although the implementation might vary from bank to bank and country to country, the overall structure needs to follow the MT 940 specification. However, we do recommend using camt files instead of MT 940 if your bank provides the option.

Setting up targets for MT 940 processing

Every bank that produces MT 940 reports can use its own interpretation of the standard specification. To be able to parse these reports, FinDock needs to know which bank they are from.

So, for each originating bank of your MT 940 reports, you need to configure a target in ProcessingHub. Before you proceed, please confirm that the bank uses a supported BIC (see below).

To add a target for MT 940 processing:

  1. Launch the FinDock app and go to the Setup tab.
  2. Under Extensions - System, click the ProcessHub tile.
  3. Go to the Targets sub-tab and click Add Target.
    ProcessingHub targets
  4. Give the target a transparent name (to distinguish from other targets), select PaymentHub MT940 as the type, then click Save.
    New MT 940 target
  5. Add the BIC and account number for the bank, then click Save. (Keep duplication protection enabled unless you need it off for testing.)
    New MT 940 target settings
  6. Repeat for each bank account as needed.

MT 940 message structure

When an MT 940 file is uploaded, FinDock parses the file into Transaction Set records with linked Transaction records.

For every Field :20 in the file, FinDock creates a Transaction Set record, and for every Field :61, a Transaction record is created. For example, an MT 940 file can look like this:

:20Transaction Set 1
:25Account of Transaction Set 1
:60FOpening balance of Transaction Set 1
:61Transaction 1 Linked to Transaction Set 1
:86Included in Transaction 1
:86Included in Transaction 1
:86Included in Transaction 1
:61Transaction 2 Linked to Transaction Set 1
:62FClosing balance of Transaction Set 1
:20Transaction Set 2
:25Account of Transaction Set 2
:60FOpening balance of Transaction Set 2
:61Transaction 3 Linked to Transaction Set 2
:86Included in Transaction 3
:62FClosing balance of Transaction Set 2

MT 940 field mapping

The following table outlines common mapping between MT 940 fields and fields on Transaction Set or Transaction.

FieldSub-fieldTransaction Set FieldTransaction Field
:20 Transaction ReferenceElectronic Sequence
:21: Related ReferenceNot mapped
:25: Account IdentificationIBAN
:28C: Statement Number/Sequence NumberNot mapped
:60F:/:60M: Opening Balance D/C mark * amountOpening Balance
:60F:/:60M: Opening Balance DateFrom Date
:60F:/:60M: Opening Balance CurrencyIsoCurrencyIsoCurrency
:62F:/:62M: Opening Balance D/C mark * amountClosing Balance
:62F:/:62M: Opening Balance DateTo Date
(calculated from file)Number of Credit Entries
(calculated from file)Number of Debit Entries
(calculated from file)Total Amount Credit
(calculated from file)Total Amount Debit
:61: Statement Line1: Value DateValue Date
:61: Statement Line2: Entry DateDate
:61: Statement Line3: Debit/Credit markType
:61: Statement Line3: Debit/Credit markReversal Indicator
:61: Statement Line5: AmountAmount
:61: Statement Line6: Transaction TypeReported Payment Method
:61: Statement Line6: Identification CodeReported Payment Method Code
(Unique per MT 940 implementation)Iban
(Unique per MT 940 implementation)Account Holder Name
(Unique per MT 940 implementation)Payment Reference
Full :61: line and all related :86: contentRaw XML Entry

Extend MT 940 processing with Guided Matching

Out of the box, FinDock extracts the information from MT 940 files required to update payment records in Salesforce. However, the files may contain more information that you would also like to use.

Using Guided Matching, you can do just about anything you want with the information in the MT 940. For example, you could parse the Raw XML Entry field and extract unique information for your own purposes. You can also create rules that extend the logic of the already parsed data on Transaction Set and Transaction records.

Supported BICs for MT 940

Below is a list of the BICs FinDock currently supports. Additional BICs can be added upon request. If your BIC is not included, please contact FinDock Support.

    • ABNANL2A
  • Banco Santander
    • ABBYGB2L
  • BancoPosta
  • Barclays
    • BARCGB22
    • BUKBGB22
    • GB26BARC
  • Commerzbank AG
    • DRESDEFF100
  • ING
    • INGBNL2A
  • Lloyds
    • LOYDGB2L
    • LOYDGB21682
    • NWBKGB2L
    • RABONL2U
  • Royal Bank of Scotland
    • RBOSGB2L
  • SNS
    • SNSBNL2A
    • TRIONL2U