Re: [GNC] How to Manually Match transactions
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
Re: [GNC] How to Manually Match transactions
Option A is extensively documented, if you understand that once the first import is successfully completed with full assignment of destination accounts, then the second import is simply that: another import. Presumably, if you assign destination accounts upon import, then you can avoid most 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 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 transactions, success. For both options, use U+C. The match happened with a C but using U+C will fix the transaction where the 2 dates don't match. Again, option 1 is what you want and option 2 is a good recovery to fix the issue. Thanks again to everyone for your help. 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 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 < > 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 > > gnucash-user@gnucash.org > > To update your subscri
Re: [GNC] How to Manually Match transactions
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 transactions, success. For both options, use U+C. The match happened with a C but using U+C will fix the transaction where the 2 dates don't match. Again, option 1 is what you want and option 2 is a good recovery to fix the issue. Thanks again to everyone for your help. 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 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 < > 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 > > 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. > > > ___ > 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. > ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription
Re: [GNC] How to Manually Match transactions
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 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 < > 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 > > 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. > > > ___ > 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. > ___ 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.
Re: [GNC] How to Manually Match transactions
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 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 > 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. > ___ 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.
Re: [GNC] How to Manually Match transactions
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 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.
Re: [GNC] How to Manually Match transactions
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 than if you write a physical check to a friend and they don't cash it for a week.(or longer) I suppose one could always include this clearing date in the Notes or Memo if it was thought to be important. Regards, Adrien On 11/19/20 3:54 PM, Frank H. Ellenberger wrote: 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 duplicate created won't have the date that matches one of the 2 banks for correctness purposes. : it is possible to keep both dates. The more common case is: you send money from account A to accout B. It disappears from accout A today and reappears on account B after the weekend. The proper solution is to use a "very current" asset account "money in transfer" between the two real accounts. In your case you can use a corresponded very current liability account. But I do not know the right english term of it. Just create the account and reassign the splits from your Imbalance-USD to the newly created account. ___ 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.
Re: [GNC] How to Manually Match transactions
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 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. I use the OFX import all the time and get matching. Sometimes I have to force it to look for a match (check the R column). And sometimes, it matches too good and thinks it finds a duplicate (a charge that occurs every 2 weeks) so I have to force it to bring it in by checking the import column. Should I be getting the data from the banks in QIF instead, does that work better then OFX/QFX for GnuCash import? Should be just the same. <> -- Stephen M Butler, PMP, PSM stephen.m.butle...@gmail.com kg...@arrl.net 253-350-0166 --- GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8 ___ 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.
Re: [GNC] How to Manually Match transactions
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 duplicate > created won't have the date that matches one of the 2 banks for correctness > purposes. : it is possible to keep both dates. The more common case is: you send money from account A to accout B. It disappears from accout A today and reappears on account B after the weekend. The proper solution is to use a "very current" asset account "money in transfer" between the two real accounts. In your case you can use a corresponded very current liability account. But I do not know the right english term of it. Just create the account and reassign the splits from your Imbalance-USD to the newly created account. Regards Frank ___ 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.
Re: [GNC] How to Manually Match transactions
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 description and other fields to recognise a match. You should however be able to at the import stage of the second file, override the import matcher decisions prior to actual import in the import matcher window display. You can uncheck the A, C, or U checkbox and check one of the others as appropriate prior to importing the data. I always manually check the importer decisions particularly in regard to matching credit card and Paypal accounts with my bank accounts. The Paypal often has different dates to my bank accounts for example. Once you have ascertained the transactions where this is likely to occur scanning the matcher window for them is usually quite quick. You can also adjust the option selections in the Import preferences. Make sure the Bayesian matching is selected and the Update match action (these are usually the defaults). David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html ___ 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.
Re: [GNC] How to Manually Match transactions
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? On Thu, Nov 19, 2020 at 11:48 AM Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > 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 transaction. > > The longer answer: > > Step 1: > > I *highly* recommend turning on View > Transaction Journal View, at > least temporarily. This will show all splits of a transaction for easy > viewing. (I use this view permanently) > > Step 2: > > From account 1 (either credit card or bank, your choice) observe the > two splits shown. One should be a debit (Dr.—left column figure) and one > should be a credit (Cr.—right column figure). > > If you are looking at the Credit Card, you should see > > Dr. Credit Card > Cr. Checking Account > > and the opposite if you are viewing the Checking Account. I use > Debit(Dr.) and Credit(Cr.) because the informal labels change based on > the type of account viewed and might even be confusing. > > Debits increase asset and expense accounts, debits increase equity, > liability, and income accounts. > > If *instead* you see: > > Dr. Credit Card > Cr. Imbalance > > and, > > Dr. Imbalance > Cr. Checking Account > > then the import created two separate transactions instead of only one. > (as I guessed above in the short answer) > > Simply fix *one* of them—e.g., > > Dr. Credit Card > Cr. Checking Account (re-assigned from Imbalance) > > and *delete* the other transaction in the opposite account. > > > > It would be good to review the Help & Guide documents concerning > imports, specifically with respect to how to assign the 'transfer' > account properly so that you end up with one transaction instead of two. > The QFX file might list each side of the transaction separately and the > importer is treating it as two separate rather then two sides of, the > same transaction. That's a user fix either before or during the import. > > > > Regards, > Adrien > > On 11/19/20 12:29 PM, 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 transaction on 2020-01-19 that is a payment > > for $amount which is the credit card payment from checking account > > > > Account 2 (bank account) has a transaction on 2020-01-21 that is a > > withdrawal for $amount which is the checking account payment to the > credit > > card. > > > > The Transfer for the transactions in each account are currently set to > > Imbalance-USD. When I change the Account 1 transaction Transfer field to > > Account 2 - a new transaction is created in Account 2 instead of matching > > to the existing one. > > ___ > 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. > ___ 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.
Re: [GNC] How to Manually Match transactions
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 transaction on 2020-01-19 that is a payment for $amount which is the credit card payment from checking account Account 2 (bank account) has a transaction on 2020-01-21 that is a withdrawal for $amount which is the checking account payment to the credit card. The Transfer for the transactions in each account are currently set to Imbalance-USD. When I change the Account 1 transaction Transfer field to Account 2 - a new transaction is created in Account 2 instead of matching to the existing one. _ Manually -- you pick one of those dates and enter a single transaction. I usually have the bank payment entered in by hand and then do an OFX import of the CC file. The match happens automatically during the import. You can't do the match afterwards without manually removing one of them and adjusting the other. -- Stephen M Butler, PMP, PSM stephen.m.butle...@gmail.com kg...@arrl.net 253-350-0166. --- GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8 ___ 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.
Re: [GNC] How to Manually Match transactions
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 transaction. The longer answer: Step 1: I *highly* recommend turning on View > Transaction Journal View, at least temporarily. This will show all splits of a transaction for easy viewing. (I use this view permanently) Step 2: From account 1 (either credit card or bank, your choice) observe the two splits shown. One should be a debit (Dr.—left column figure) and one should be a credit (Cr.—right column figure). If you are looking at the Credit Card, you should see Dr. Credit Card Cr. Checking Account and the opposite if you are viewing the Checking Account. I use Debit(Dr.) and Credit(Cr.) because the informal labels change based on the type of account viewed and might even be confusing. Debits increase asset and expense accounts, debits increase equity, liability, and income accounts. If *instead* you see: Dr. Credit Card Cr. Imbalance and, Dr. Imbalance Cr. Checking Account then the import created two separate transactions instead of only one. (as I guessed above in the short answer) Simply fix *one* of them—e.g., Dr. Credit Card Cr. Checking Account (re-assigned from Imbalance) and *delete* the other transaction in the opposite account. It would be good to review the Help & Guide documents concerning imports, specifically with respect to how to assign the 'transfer' account properly so that you end up with one transaction instead of two. The QFX file might list each side of the transaction separately and the importer is treating it as two separate rather then two sides of, the same transaction. That's a user fix either before or during the import. Regards, Adrien On 11/19/20 12:29 PM, 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 transaction on 2020-01-19 that is a payment for $amount which is the credit card payment from checking account Account 2 (bank account) has a transaction on 2020-01-21 that is a withdrawal for $amount which is the checking account payment to the credit card. The Transfer for the transactions in each account are currently set to Imbalance-USD. When I change the Account 1 transaction Transfer field to Account 2 - a new transaction is created in Account 2 instead of matching to the existing one. ___ 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.
[GNC] How to Manually Match transactions
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 for $amount which is the credit card payment from checking account Account 2 (bank account) has a transaction on 2020-01-21 that is a withdrawal for $amount which is the checking account payment to the credit card. The Transfer for the transactions in each account are currently set to Imbalance-USD. When I change the Account 1 transaction Transfer field to Account 2 - a new transaction is created in Account 2 instead of matching to the existing one. ___ 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.
