Have some good news and an even better solution that can be added to
the FAQ or How-to.
2 Options that work for associating/matching a transaction that does
not import match:
1 - Import from Account A and assign to Account B at import or before
importing Account B. Then when
duplication.
The Guide at 3.1.2 and Help at 6.16 cover these issues in some detail.
David T.
Original Message
From: Griff
Sent: Sat Nov 21 13:17:37 EST 2020
To: David Carlson
Cc: GnuCash List , Adrien Monteleone
Subject: Re: [GNC] How to Manually Match transactions
Have
Have some good news and an even better solution that can be added to the
FAQ or How-to.
2 Options that work for associating/matching a transaction that does not
import match:
1 - Import from Account A and assign to Account B at import or before
importing Account B. Then when importing Account
Thanks for the great suggestions everyone.
I tried the idea of changing from A to C during import and then looking for
a match but no matches were present to select from in the matcher dialog. I
even manually changed the date of the transaction in account A to match the
date of account B before
In the olden days some people would even try to take advantage of having a
lot of funds in "float" between various bank accounts. 來
On Thu, Nov 19, 2020, 6:12 PM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> Griff,
>
> Sorry, I misunderstood the original post. I thought it was a
Griff,
Sorry, I misunderstood the original post. I thought it was a single
import, not two separate ones.
David's suggestions should be the way to go in your case.
As for retaining the second date, (presumably from the Credit Card
account) see my reply to Frank.
Regards,
Adrien
On
Frank, I think it would still be proper to use a current asset account.
Should something interrupt the transit, the funds would not come out of
the original asset account.
But really, this now sounds more like a situation of simple clearing.
I'm not sure the second date is necessary any more
On 11/19/20 1:18 PM, Griff wrote:
Thanks Adrien and Stephen.
Both your solutions are good work arounds, sounds like the short
answer is it can't be done the nice way preserving data. The result
will be to manually delete one of the import transactions and the new
duplicate created won't have
Hello Griff,
Am 19.11.20 um 22:18 schrieb Griff:
> Thanks Adrien and Stephen.
>
> Both your solutions are good work arounds, sounds like the short answer is
> it can't be done the nice way preserving data. The result will be to
> manually delete one of the import transactions and the new
Griif
The import matcher should run on both the QIF import and the OFX/QFX import.
It also has a time window in which it tries to match existing transactions
which is not adjustable. Since the records are from two different companies
there may not however be sufficient matching data in the
Thanks Adrien and Stephen.
Both your solutions are good work arounds, sounds like the short answer is
it can't be done the nice way preserving data. The result will be to
manually delete one of the import transactions and the new duplicate
created won't have the date that matches one of the 2
On 11/19/20 10:29 AM, Griff wrote:
Here is a very simple question but I can't figure out how to do this.
I have searched the documentation and this mailing list.
How do I manually match 2 transactions:
I have 2 account that have had data imported via qfx.
Account 1 (credit card) has a
The most likely correct short answer: the import created two
transactions rather than one. Your correction of the Imbalance
assignment is not creating a new transaction, but correcting only one of
the existing two separate transactions. Commit this fix, and then delete
the extraneous
Here is a very simple question but I can't figure out how to do this.
I have searched the documentation and this mailing list.
How do I manually match 2 transactions:
I have 2 account that have had data imported via qfx.
Account 1 (credit card) has a transaction on 2020-01-19 that is a payment
14 matches
Mail list logo
