CAMT Support in KMyMoney

[Jan Ritzerfeld]

Am Donnerstag, 27. November 2025, 20:18:13 CET schrieb Martin Preuss via 
KMyMoney:
> Hi,
> 
> Am 27.11.25 um 19:38 schrieb Jan Ritzerfeld via KMyMoney:
> > Am Donnerstag, 27. November 2025, 18:16:27 CET schrieb Martin Preuss via
> [...]
> > I know. Where did I say anything different?
> [...]
> 
> You didn't. I was just wondering, why you're discussing this here and not on
> the AqBanking list. I still do.

Fair enough. I'm already subscribed to aqbanking-user because I tried to 
update aqbanking packages for openSUSE to 6.6.0 as I originally wrote:
| Recently, my bank introduced the Kundensystem-ID check, requiring me to
| update AqBanking. 

When I did this I "accidentally" learned about the other stuff like SWIFT, 
CAMT and so on. And then I tried CAMT with KMM but I noticed that KMM didn't 
handle that as well as I hoped it would. Since there was no problem with 
AqBanking, I proactively started the discussion here 10 months ago before CAMT 
would become mandatory.

> [...]
> [...]> Pardon? I think the ZKA knows better what they need than we do.
> [...]
> Sure, of course, they *always* even know best, that's what my experience
> taught me, too ;-)

I fear that we cannot change that and just have to deal with that. :-/
 
> [...]> 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...
> [...]
> 
> Yes, what an inspiring comment, those always make me want to drop my datime
> work and immediately go write and maintain software for free in my spare
> time.

Been there, done that. Feel free to google me. E.g., regarding this banking 
stuff:
https://build.opensuse.org/users/jritzerfeld#tab-pane-comments

> Really, it's not that hard to get what I'm upset about here.

Well ...

> All I'm saying is you could have discussed this with the AqBanking team or
> at least followed it up, instead of waiting 10 months and then saying "I
> told you so".

... for me there was, and is, no problem with AqBanking.I know that you and 
your team is very busy and, thus, I didn't want to bother you with stuff you 
don't control like the KMM import details.

> [...]
> >> 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):
> [...]
> MREF+ is used in SWIFT documents, but mandate reference is also provided by
> CAMT.052 and as such represented by AqBanking in the field "mandateId" of
> AB_TRANSACTION.

Yes, and when I downloaded and compared SWIFT MT940 and CAMT v8 files for my 
banking account in January, it looked like I want "localName". CAMT offers 
significantly more structured and detailed information than MT940 in my 
opinion. MREF is just an UUID different for each "Lastschriftmandat" and only 
helped me to indirectly distinguish my wife and me by learning all of them. 
However, and IIRC, in CAMT, you directly get the name of the person who 
triggered an transaction in "localName".

> [...]> | 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.
> [...]
> 
> *That's* to be discussed here, but of course you know that already ;-)

Yes, because that's a quote from my original mail and exactly why I wanted to 
discuss here and not on aqbanking-user. :-D

Gruß
 Jan
-- 
Everyone hates me because I'm paranoid.