All,

Just recently, American Express 'upgraded' their direct download services in a partnership with Intuit. Part of the effect of this appears to be (after talking with both tier 1 and tier 2 tech support) that they're no longer providing .ofx files directly. They are providing .qfx files, and I'm guessing they've been formatted differently enough that KMM doesn't recognize them. My actual problems are:

-When performing an OFX direct download (by 'update all accounts', using the latest Windows nightly build), there's an error message that says :
CCSTMTTRNRS: Account not found (Code 2003): The specified account number does not correspond to one of the user's accounts.
The account number is correct, and worked up until a few weeks ago.

-The manual download of a .qfx file yields a file that can't be imported into KMM manually, KMM complains about it being the wrong format. I can provide an example of it once I can get home and sanitize it if needed.

Anyone else having / avoiding this problem with American Express (credit card)?

For further weirdness, I've been getting the preceding error message with the latest Windows nightly. If I use the stable Windows 5.0.5 release, instead of an error message KMyMoney just hangs indefinitely at the 'contacting the financial institution' stage. I think the two builds use different compilers, but I'm not sure if they use different libOFX calls or anything.

OK, since I was refused support by American Express, I went poking in their .qfx file that you can download from their web site. I did notice that they're not using the same ACCTID fields as in my old OFX logs from them; in the old versions they spelled out the entire 15-digit account numbers in that field, but the newer .qfx only uses the last five digits of the account number. That might be the cause of the account-not-recognized error I was getting before.

Is there a way to change just the account number associated with the account for OFX direct download? Or would I have to unlink and relink the account?

Just FYI.. I am having the same problem.

I may have to cancel my AMEX accounts if they don't fix this.

thanks,

JV

I just fixed it for myself. You basically have to recreate the online account mapping/connection.

What you need to do is:
1. In KMM, delete the user. It will prompt you if you want to delete the associated accounts. I said, yes. KMM deleted the user and the online accounts. (it left the ledge accounts in KMM alone, just deleted the online connectivity)
2. Create a new user
3. Remember to hit the Retrieve Online Accounts button.
4. Go to your American Express account in KMM... right click and say Update account.
- If you try to, unmap account, it will give you an error. If you ask for it to update, it will realize it no longer is mapped to an online account and will error out. But now it will let you update the mapping between the KMM account and the online account.
5. Update any other account mappings.

If you look at the account number, you will now see that the first set of characters are tokenized and only the last 5 account number values are still numeric.

Hope this helps.

thanks,

JV

Just to clarify the above: the actions jvapr27 describes sound like if they are related to AqBanking and not KMyMoney. One can access them via the KMyMoney Settings menu, but he probably did this under "Settings/Configure AqBanking".

Regarding the error that occurred while "un-mapping the account": you probably don't get this error when you un-map the account as the very first action esp. before you delete any user in AqBanking. What you have done is removing data structures in AqBanking and then later on KMyMoney tries to use them again as part of the un-mapping operation. This of course failed. But KMyMoney can deal with the situation as you described and lets you map to a new account.

Hmm, if he's using AqBanking then his solution wouldn't work for me. I'm currently using version 5.0.80 (one of the nightlies) on Windows, which uses the libofx plugin.

I'm willing to give AqBanking a try for the first time in like a decade if it's possible on this build, or a recent build that's compatible with the same money file.

ipwizard wrote:Just to clarify the above: the actions jvapr27 describes sound like if they are related to AqBanking and not KMyMoney. One can access them via the KMyMoney Settings menu, but he probably did this under "Settings/Configure AqBanking".

Regarding the error that occurred while "un-mapping the account": you probably don't get this error when you un-map the account as the very first action esp. before you delete any user in AqBanking. What you have done is removing data structures in AqBanking and then later on KMyMoney tries to use them again as part of the un-mapping operation. This of course failed. But KMyMoney can deal with the situation as you described and lets you map to a new account.

That is correct. I did access the Aqbanking settings as mentioned.
If I remember correctly, I originally attempted to un-map the account and it was unsuccessful. However, this was after I had entered into the aqbanking settings. I also noticed I could not delete an account, I had to delete the user. Probably an issue with Aqbanking not KMyMoney. Even after I deleted the user, and associated accounts, in AqBanking, I tried to un-map the accounts, and failed. Thus, I tried to update the account and it failed but this time it unmapped the account on its own.

This was my first time having to do this so, yeah, pretty sure there is a more graceful way of doing it.

thanks,

JV