CAMT Support in KMyMoney

[Jan Ritzerfeld]

Am Donnerstag, 27. November 2025, 18:16:27 CET schrieb Martin Preuss via 
KMyMoney:
> Hi,
> 
> Am 27.11.25 um 17:58 schrieb Jan Ritzerfeld via KMyMoney:
> 
> [...]>> And the Sparkassen (Finanz Informatik) mention both FinTS and EBICS:
> >> https://www.ksk-koeln.de/fi/home/produkte/banking-und-software/weitere-se
> >> rvices/formatabkuendigung.html [...]
> > 
> > Unfortunately, i didn't get any response to this mail. Yesterday I read,
> 
> [...]
> 
> Hmm, what response did you expect, if I may ask?

Sure. I actually read the source code of Aqbanking's and KMM's importer. I 
read the SWIFT specs and the ISO 20022 specs. That took me hours. Thomas asked 
me how to switch to CAMT and how to find out whether his bank supports it. I 
answered him how he could do that. I would have been happy to hear some 
feedback like "Ah, I tried and it worked/didn't work and I could/couldn't 
reproduce your problem."

> Calling the bank for transactions is AqBanking's job, KMM just calls the
> appropriate function of AqBanking for this.

I know. Where did I say anything different?

> AqBanking has support for CAMT download since 2018 and I use it with my
> accounts since then - albeit not with KMM. 

I know. Again, where did I say anything different?

> So the only thing for the user
> to do was to switch on the option "Prefer CAMT Download".

That's what I said 10 months ago: We will have to move to CAMT. 
 
> [...]> that you now have exactly the problems I talked about 10 months ago.
> :-/
> > So, here again is my initial report about the missing parts in
> 
> > KMyMoney's CAMT support:
> [...]
> 
> There is no missing CAMT support in KMM (see above). 

Where did I write that CAMT support is missing in KMyMoney?

> The problem is rather
> that banks also immediately switched to the *latest* version of
> CAMT.052.001.08 (from CAMT.052.001.02 which was used for a long time now)

Sorry, this was announced officially almost a year ago! These links were 
included in my original mail. Obviously, you didn't you read them:
| Ab dem 23. November 2025 sind MT940 und MT942 kein DK-Standard mehr.
| Außerdem entfällt die Unterstützung für die Version 02 der camt.052/camt.
| 053/camt.054.
https://www.ebics.de/de/datenformate/format-lifecycle
| 23. November 2025: Bereitstellung von Umsatz­informationen. Die SWIFT-
| Formate MT940 und MT942 werden abgeschaltet und bei den im ISO 20022-
| Nachrichten­standard gelieferten Umsatz­informationen im camt-Format ist
| eine Aktualisierung der Version von 02 auf 08 erforderlich.
https://www.ksk-koeln.de/fi/home/produkte/banking-und-software/weitere-services/formatabkuendigung.html
> and needlessly removed support for older CAMT versions,

Pardon? I think the ZKA knows better what they need than we do.

> at that time AqBanking didn't have an importer for that (see https://
www.aquamaniac.de/rdm/projects/aqbanking/wiki/Camt_2025_11 for details on the 
matter).

Actually, the problem was that AqBanking ignored all the announcements. And 
not that the banks did what they said months ago. That explains why you are so 
upset...

> Well, adding such an importer was just a matter of adding two files so it is
> now supported by AqBanking (and thus by KMM).
> 
> MREF should now also be provided by AqBanking (if delivered by the bank).

When I had a look at the source more than 10 months ago, I thought that the 
information I was missing would have to be imported as "localName" when using 
CAMT (since MREF is SWIFT):
| AqBanking, for example, imports: "NtryDtls/TxDtls/RltdPties/Dbtr/Nm" or 
| "NtryDtls/TxDtls/RltdPties/Cdtr/Nm" as "localName".  
| Unfortunately, KMyMoney does not seem to import or display this field when 
| switching to CAMT. 

Gruß
 Jan
-- 
Why do divorces cost so much? --  Because they're worth it! --