David R: Clever observation. I think that in this case
1425 appears because there are two different credit cards
using the same parent account and those transactions were charged with the
card ending in 1425. However, the card used information did not get posted
in GnuCash. I think the importer
I think your problem arises from there being multiple flags. The main
data stream is coming from 8320, but each of the
transactions within that account has 1425 within the
transaction. So each of the transactions is a transfer from one credit card
account to another. I’m guessing that the OFX
David,
Going from memory here, but don't the importers require the FITID to be
unique and not imported previously ? Any chance your bank is duplicating
these and Gnucash assumes the txns were already processed ?
Cheers David H.
On Wed, 6 Dec 2023 at 16:49, David Carlson
wrote:
> That bug may
That bug may be a different symptom of the same problem or it may be a
different bug altogether. Interestingly, my file does have the
tag.
I attached my file to that bug report in case it helps with the diagnosis.
On Tue, Dec 5, 2023 at 9:56 PM john wrote:
>
>
> On Dec 4, 2023, at 18:47,
> On Dec 4, 2023, at 18:47, David Carlson wrote:
>
> New to me, anyway. Using release 4.8 in Linux importing to existing
> account which worked with a previous import last March with today's import
> I receive the error message "OFX File '/media...' 2 transactions processed,
> no
New to me, anyway. Using release 4.8 in Linux importing to existing
account which worked with a previous import last March with today's import
I receive the error message "OFX File '/media...' 2 transactions processed,
no transactions to match
Why did it not proceed with the import?
--
David
