Working on MT940 importer

Martin Preuss martin at aquamaniac.de
Fri Sep 12 13:22:44 CDT 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Friday 12 September 2003 11:50, Best, Jan-Pascal van wrote:
[...]
> Yes, I've read those. I looked at the OpenHBCI C API at
> http://openhbci.sourceforge.net/doc/api/group__HBCI__APIg.html
> but didn't find anything in there to parse MT940 files directly,
> so I kind of gave up on that.
Well, the current implementation of the SWIFT parser expects a string which 
contains the MT940. You could read a whole file into a string and pass it on 
to the method SWIFTparser::readMT940().

However, in newer versions the parser is implemented as a plugin to OpenHBCI 
(which we could make accessable via the OpenHBCI-API).

[...]
> It doesn't seem like there is a C wrapper
> function available, at least not in core/swiftparser.h. Would it
> be possible to create one?
Yes, that should not be too hard to perform.

[...]
> Some more things: is the booking code (you call it "transaction key")
> interpreted somewhere? Is there a possibility to allow unstructured
>
> :86: fields (my bank has them)? Maybe the bank-specific parsing should
That code is not interpreted by the parser (I can't tell whether Christian's 
GNUCash-HBCI-code makes use of it, though).
Currently the :86: tag is parsed in any case, but we could add a flag 
parameter to change this behaviour. What does this :86: tag contain in your 
bank's MT940 anyway ? Doesn't it contain ?XX fields (like it is supposed to)?


kind regards
Martin


- -- 
LibChipcard - http://www.libchipcard.de
OpenHBCI - http://www.openhbci.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/YZ50wcZBcYAOyGYRAn0mAJwKMrPh2bQq29s3CLzvbze9x1jRWgCfbP4r
5dektDbyUCfVmjD/0qGBTeM=
=CRL9
-----END PGP SIGNATURE-----



More information about the gnucash-devel mailing list