Hi Kevin,
I managed to get the M940 import and matching to work on a dev environment that we are about to go live on. That was in V12P25.  Have just upgraded to V12P26, and the M940 import is giving an error on the sign of opening and closing balances. 
Are you able to import a M940 bank statement? - and do you have any documentation on the BSILIB.CHK_SNS(CURFIELD) and BSILIB.CONV_MNT(CURFIELD) function calls that seem to be where my import is currently falling down.

Hi John thanks for the info.  Sorry I lost momentum on my testing with this MT940 and don't have any good insights on those fields that you referenced.  Did you find that you were able to get it to work pretty much out of the box or was there any programming required to get it working?

It works pretty well out of the box.  You may/will have to tweak the segment definitions depending on how your bank delivers the file. In this particular case I had to accommodate the fact the the statement arrives within a SWIFT transmission wrapper, but was easy to get around that.  The other issue was that multiple statements arrive within a single transmission, so you have changing segment identifiers on the :60F: and :62F: records.  Once you realise that the statement import loads the data into the BSIIMP and BSIIMPD tables, it is pretty easy to map incoming data to fields in these tables.

My best tip would be to work on getting the statement to import as a flow type of 'Reconcilliation Only' under 'Bank Import settings'  Get that working before you even attempt to use Standard or 'Post Validation Transfer' flows.

At this stage my biggest challenge is getting some information on the BSILIB functions, which you can use to transform your imported data.

It works pretty well out of the box.  You may/will have to tweak the segment definitions depending on how your bank delivers the file. In this particular case I had to accommodate the fact the the statement arrives within a SWIFT transmission wrapper, but was easy to get around that.  The other issue was that multiple statements arrive within a single transmission, so you have changing segment identifiers on the :60F: and :62F: records.  Once you realise that the statement import loads the data into the BSIIMP and BSIIMPD tables, it is pretty easy to map incoming data to fields in these tables.

My best tip would be to work on getting the statement to import as a flow type of 'Reconcilliation Only' under 'Bank Import settings'  Get that working before you even attempt to use Standard or 'Post Validation Transfer' flows.

At this stage my biggest challenge is getting some information on the BSILIB functions, which you can use to transform your imported data.

Thanks for the recommendations John, very helpful.

Hi Kevin, if the above suggested answer helped, please do mark it as verified  for the benefit of others in this forum :). Thank you!

Also, if you have a minute, tell us about your great experience on Sage City, take this short survey

In the Bank Statement Import HowTo Guide is a section about the data field mapping of the segments with information about the expected content/format.

For details of the MT940 format I recommend the SWIFT MT940 documentation in addition to documentation your bank provides on their implementation of MT940.

Regarding the BSILIB functions, they are generally used to convert file format specific data formats into a more generic, X3-suitable format. For example, MT940 amounts have a comma as decimal delimiter so this needs to be converted to the X3 standard.
You can create your own function as well if needed or (for something simple) use a X3 formula to format the content.

Regards,
Ulrich

Absolutely!  You HAVE to have the format documentation to make any sense of it.  I used the Deutshe Bank documents I found on the web