CAMT Support in KMyMoney

[Martin Preuss]

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
[...]>> 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?
[...]

You didn't. I was just wondering, why you're discussing this here and not on the AqBanking list. I still do.

[...]>> 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.
>> :-/
[...]

Hmm, I still don't see the problem. The decision to change to CAMT has always been in the hand of the user since at least 2019.


[...]>> 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:
[...]

No, I don't regularly read this list, because most of the time the subject is not aqbanking-related, and if they are most of the times I get a mail from Thomas or others. So I don't have to.

[...]> 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 ;-)

[...]> 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.

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

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".

[...]
>> 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.

[...]> | 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 ;-)


Regards
Martin


-- 
"Things are only impossible until they're not."