CAMT Support in KMyMoney

[Jan Ritzerfeld]

Am Sonntag, 26. Januar 2025, 16:39:44 CET schrieb Jan Ritzerfeld via KMyMoney:
> Am Donnerstag, 23. Januar 2025, 08:26:25 CET schrieb Thomas Baumgart via
> 
> KMyMoney:
> > On Sonntag, 12. Januar 2025 16:48:49 CET Jan Ritzerfeld via KMyMoney wrote:
> [...]
> > > As far as I know, there will be a mandatory switch to CAMT in November
> > > this
> > > year. Does anyone know if KMyMoney supports these specific fields or if
> > > there’s a workaround to view this information from AqBanking?
> > 
> > Where did you get the information that CAMT will become mandatory
> > later this year? Once details are clear(er) we can certainly work out
> > a solution. I doubt that there currently is a workaround.
> 
> Regarding EBICS I'm pretty confident:
> https://www.ebics.de/de/datenformate/format-lifecycle
>
> And the Sparkassen (Finanz Informatik) mention both FinTS and EBICS: 
> https://www.ksk-koeln.de/fi/home/produkte/banking-und-software/weitere-services/formatabkuendigung.html
> [...]

Unfortunately, i didn't get any response to this mail. Yesterday I read, 
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:

Recently, my bank introduced the Kundensystem-ID check, requiring me to update 
AqBanking. During this process, I discovered that CAMT is now supported and 
offers significantly more structured and detailed information than MT940. 
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. Worse, the previously helpful MREF details no longer appear 
in the Memo field. As a result, I cannot determine who (my wife or me) 
triggered certain transactions.  

Gruß
 Jan
-- 
A fool must now and then be right by chance.