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 B, the two
transactions will be matched to each other. This is the proactive
correct solution. So obvious.
2 - In the case import QFX from Account A and match is not made before
hand, then importing Account B won't find a match. Fix is to assign
either Account A or Account B transaction to the other account
respectively. Then delete the duplicate transaction, lets say, account
B has two entries because Account A was assigned to Account B as the
destination. Now, re-import Account B and the import matcher will now
match those two entries, success.
Again, option 1 is what you want and option 2 is a good recovery to fix
the issue.
On 11/19/2020 9:58 PM, Griff wrote:
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 importing, then did the import
and the matcher still did not find anything to offer up.
Too bad GnuCash does not allow selecting the match from the full list
of transactions or matching at other times besides import. Hopefully
this was a special case match issue and the norm will be to find a
match for the transfers like your example of PayPal and the multi-day
float.
Otherwise, I can manually fix the issue or use Frank's short-term float
account "money in transfer" to match the transactions.
I have the default import setting of bayesian and 1, 3, 6 for
thresholds, I tried changing the match display threshold to 0 but no
impact.
As a side note, I tested the QIF file for the same transactions instead
to see if that worked better and had the strange issue of GnuCash
hanging. Tried it several times with the same issue.
David places like PayPal/Venmo still enjoy the float on their end and
offer a rapid no-float option for a fee, win-win for them.
On Thu, Nov 19, 2020 at 5:54 PM David Carlson
<[1]david.carlson....@gmail.com> wrote:
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 <
[2]adrien.montele...@lusfiber.net> wrote:
> 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 11/19/20 3: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 the date that matches one of the 2 banks for
> correctness
> > purposes.
> >
> > To your suggestion of importing it all at once, that is not
possible as
> one
> > QFX file is from the credit card company download and the other
QFX is
> from
> > the different bank company's download. They will be two files.
> >
> > This is unfortunate as the matcher is only run on QIF import and
not
> > OFX/QFX import.
> > Should I be getting the data from the banks in QIF instead, does
that
> work
> > better then OFX/QFX for GnuCash import?
>
>
> _______________________________________________
> gnucash-user mailing list
> [3]gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> [4]https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> [5]https://wiki.gnucash.org/wiki/Mailing_Lists for more
information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
_______________________________________________
gnucash-user mailing list
[6]gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
[7]https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
[8]https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
References
1. mailto:david.carlson....@gmail.com
2. mailto:adrien.montele...@lusfiber.net
3. mailto:gnucash-user@gnucash.org
4. https://lists.gnucash.org/mailman/listinfo/gnucash-user
5. https://wiki.gnucash.org/wiki/Mailing_Lists
6. mailto:gnucash-user@gnucash.org
7. https://lists.gnucash.org/mailman/listinfo/gnucash-user
8. https://wiki.gnucash.org/wiki/Mailing_Lists
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
