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:
- Launch the FinDock app and click the FinDock Setup tab.
- Go to Payment Processors & Methods, scroll down and install the MT-940 processor if you haven't already.
- In the installed processors table at the top, click MT-940.
- Click Add account and enter the required details.
(Use a transparent name to distinguish from other targets and keep duplication protection enabled unless you are testing.) - Click Save when you are done.
- Add a target each bank account that sends you MT-940 files.
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:
| Field | Record |
|---|---|
| :20 | Transaction Set 1 |
| :25 | Account of Transaction Set 1 |
| :60F | Opening balance of Transaction Set 1 |
| :61 | Transaction 1 Linked to Transaction Set 1 |
| :86 | Included in Transaction 1 |
| :86 | Included in Transaction 1 |
| :86 | Included in Transaction 1 |
| :61 | Transaction 2 Linked to Transaction Set 1 |
| :62F | Closing balance of Transaction Set 1 |
| :20 | Transaction Set 2 |
| :25 | Account of Transaction Set 2 |
| :60F | Opening balance of Transaction Set 2 |
| :61 | Transaction 3 Linked to Transaction Set 2 |
| :86 | Included in Transaction 3 |
| :62F | Closing 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.
| Field | Sub-field | Transaction Set Field | Transaction Field |
|---|---|---|---|
| :20 Transaction Reference | Electronic Sequence | ||
| :21: Related Reference | Not mapped | ||
| :25: Account Identification | Bank Account Number | ||
| :28C: Statement Number/Sequence Number | Not mapped | ||
| :60F:/:60M: Opening Balance D/C mark * amount | Opening Balance | ||
| :60F:/:60M: Opening Balance Date | From Date | ||
| :60F:/:60M: Opening Balance Currency | IsoCurrency | IsoCurrency | |
| :62F:/:62M: Opening Balance D/C mark * amount | Closing Balance | ||
| :62F:/:62M: Opening Balance Date | To 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 Line | 1: Value Date | Value Date | |
| :61: Statement Line | 2: Entry Date | Date | |
| :61: Statement Line | 3: Debit/Credit mark | Type | |
| :61: Statement Line | 3: Debit/Credit mark | Reversal Indicator | |
| :61: Statement Line | 5: Amount | Amount | |
| :61: Statement Line | 6: Transaction Type | Reported Payment Method | |
| :61: Statement Line | 6: Identification Code | Reported Payment Method Code | |
| (Unique per MT 940 implementation) | Bank Account Number | ||
| (Unique per MT 940 implementation) | Account Holder Name | ||
| (Unique per MT 940 implementation) | Payment Reference | ||
| Full :61: line and all related :86: content | Raw 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.
- ABN AMRO
- ABNANL2A
- Banco Santander
- ABBYGB2L
- BSCHESMM
- BSCHESMMXXX
- BancoPosta
- BPPIITRRXXX
- Bank für Sozialwirtschaft
- BFSW DE33 XXX
- Bank of Ireland
- BOFIIE2D
- Barclays
- BARCGB22
- BUKBGB22
- GB26BARC
- BNP Paribas Fortis
- GEBABEBB
- Commerzbank AG
- DRESDEFF100
- GLS Bank
- GENODEM1GLS
- ING
- INGBNL2A
- Lloyds
- LOYDGB2L
- LOYDGB21682
- LOYDGB21XXX
- NAT WEST
- NWBKGB2L
- NWBKGB2LXXX
- RABOBANK
- RABONL2U
- Royal Bank of Scotland
- RBOSGB2L
- RBOSGB2LXXX
- SNS
- SNSBNL2A
- TRIODOS
- TRIONL2U
- Volksbank Raiffeisenbank Dachau eG
- GENODEF1DCA