[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 Thomas Baumgart changed: What|Removed |Added CC||mar...@aqbanking.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Baumgart --- Thanks for the information. CAMT.053 itself is not that new. I found traces dating back into 2018 (https://www.sepaforcorporates.com/swift-for-corporates/a-practical-guide-to-the-bank-statement-camt-053-format/). Since it is a SEPA thing, it is used throughout Europe. KMyMoney relies on the software provided by the (also open source) AqBanking project for this kind of interface. Scanning AqBanking, I found traces of camt.053.001.04 in its sources. So it could well be, that KMyMoney already supports that format through AqBanking. To gain more information, I added the AqBanking maintainer to this request. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 --- Comment #2 from mar...@aqbanking.de --- Hi, Am 16.07.22 um 14:57 schrieb Thomas Baumgart: [...] > --- Comment #1 from Thomas Baumgart --- > Thanks for the information. CAMT.053 itself is not that new. I found traces > dating back into 2018 > (https://www.sepaforcorporates.com/swift-for-corporates/a-practical-guide-to-the-bank-statement-camt-053-format/). > Since it is a SEPA thing, it is used throughout Europe. > > KMyMoney relies on the software provided by the (also open source) AqBanking > project for this kind of interface. Scanning AqBanking, I found traces of > camt.053.001.04 in its sources. So it could well be, that KMyMoney already > supports that format through AqBanking. To gain more information, I added the > AqBanking maintainer to this request. [...] AqBanking does support import of CAMT 053.001.04 and 052.001.02 documents. At least the latter is well tested, because it is heavily used when requesting tranaction statements from banks in CAMT format via HBCI/FinTS. CAMT 053.* should work also but is much less tested. Providing a test file might help improving the importer, if necessary. You can test importing such a file on command line via "aqbanking-cli". The command should be something like: ---X8 aqbanking-cli import -c output.ctx -f inputfile --importer=xml --profile="camt_053_001_04" ---X8 Other CAMT profiles can easily be added to AqBanking's XML importer. Regards Martin -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 Thomas Baumgart changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #3 from Thomas Baumgart --- I close this off here, as it is an upstream (AqBanking) issue (if any at all). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 --- Comment #4 from Arnold Huzen --- Hello and thank you for replying to my issue. In your reply you suggest importing the bankstatement through the commandline tool, but that was not what I want. I am looking for a way to import my bankstatement through the importer function of KMyMoney. When i choose File > Import... I only get 3 options: CSV, OFX and QIF. At this point I would like to see the option for CAMT.053. By the way, the executable for aqbanking-cli is not by default installed in the PATH of my Windows 11 computer. The commandline example doesn't work for that reason. Any ideas where to find it, if it was installed together with KMyMoney? Regards, Arnold Huzen -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 --- Comment #5 from mar...@aqbanking.de --- Hi, Am 21.07.22 um 16:42 schrieb Arnold Huzen: [...] > In your reply you suggest importing the bankstatement through the commandline > tool, but that was not what I want. I am looking for a way to import my > bankstatement through the importer function of KMyMoney. [...] That is just to verify whether your file can already be handled by AqBanking's importer. [...] > When i choose File > Import... I only get 3 options: CSV, OFX and QIF. At this > point I would like to see the option for CAMT.053. [...] AqBanking provides some generic GUI dialogs (hint for developers: AB_Banking_CreateImporterDialog and recently AB_Banking_CreateImporterDialogWithPresets) which allow for import of any file type which is supported by AqBanking by letting the user select file, importer and import profile. In case of CSV files import profiles can also be added and edited. But I don't know whether KMyMoney makes that importer available to the user. [...] > By the way, the executable for aqbanking-cli is not by default installed in > the > PATH of my Windows 11 computer. The commandline example doesn't work for that > reason. Any ideas where to find it, if it was installed together with > KMyMoney? [...] I don't know KMMs packaging, but if those binaries are provided in the package at all I would expect them in the same folder as the main executable... Regards Martin (AqBanking) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 456792] Adding support for new banking format CAMT.053
https://bugs.kde.org/show_bug.cgi?id=456792 --- Comment #6 from Thomas Baumgart --- Could be, that your version of KMyMoney did not get build with AqBanking support. If built in, you should see "File/Import/AqBanking Importer" and "Settings/Configure AqBanking". If both of them are missing, it was not build with AqBanking support. There is an external source provided by one of the devs that builds KMyMoney with AqBanking support for Windows. You may try it out. See https://kmymoney.org/snapshots.php To answer Martin's question: no, we don't package the binaries, only the libs. -- You are receiving this mail because: You are watching all bug changes.
