MT940 import does not work

Christian Stimming stimming at
Sun Sep 24 16:46:28 EDT 2006

Am Sonntag, 24. September 2006 22:17 schrieb L.W. van Braam van Vloten:
> dependenciies), and built a new gnucash package. I used the .configure
> options --enable-mt940 and --enable-hbci and everything compiled nicely.

For the record and archives: 
The trunk-SVN and to-be 2.2.x branch does not have a separate --enable-mt940 
option anymore, this functionality will be included in --enable-hbci already 
(and configure will error out to tell you this). On the other hand, in the 
2.0.x version these two arguments are necessary, just as you reported 

> 1. So my questions are: Does anyone have an idea what I can do to make the
> MT940 import function work?
> 2. Is there a way (like a logging or so) to follow in more detail the
> working of the import function? (I would like to know why it doesn't see
> the data in my file as MT940 formatted information)

There should be some messages on the console window/command line. Start 
gnucash from a command line window by typing "gnucash". On the failed mt940 
import, you should see some messages in that command line window.

Also, we need to know the exact aqbanking version.

> 3. Are there any sample files in MT940 format available, so I can test the
> import with a file that worked for someone else? (I found a QIF file
> somewhere and that seemed to work fine)

I don't have an anonymized data file available; I only got one that needs to 
be kept private. Sorry for that, but with that MT940 file this used to work 
fine. You might consider sending one file to me privately so that I can check 
whether this is indeed mt940.

> 4. Is there a description of the MT940 format that gnucash expects, so I
> can check the file from my bank?

I thought the HBCI specifications have a section about SWIFT MT940 somewhere 
in the appendix, see (Part D). E.g. the 
first characters in the file should be ":20:..."


More information about the gnucash-devel mailing list