The Tutorial Guide I believe goes over the situation of both sides of a transaction being listed separately in the file.
Others can give better advice than I (and some may be using this exact workflow) but I believe that yes, GnuCash can see that the transactions are the same. (some minor csv manipulation might be in order though) Piecemeal importing is much better as you’re training the importer as you go. The workload reduces for subsequent imports. Regards, Adrien > On Jun 2, 2020 w23d154, at 4:57 AM, Gio Bacareza <[email protected]> wrote: > > Hi GNUCash experts, > > I'm planning to consolidate all my statements into 1 big CSV. This CSV > would naturally have an account field and a transfer field. > > Since all transactions are there, there will be instances where there will > be duplicates. For example, a statement from bank1 could have a transfer > from bank1 to bank2. So account = bank 1, transfer = bank 2, amount = -100 > for example. But, since I put in all together in 1 file, there will be > another line where account = bank 2, transfer = bank1, amount = 100. > > When I import this big file containing all transactions from different > statements, how will gnucash handle this? Can it automatically detect that > this is one and the same transaction? > > The alternative is to import account by account but that is too time > consuming for me. > > Is there a better way? > > -- > cheers, > > Gio _______________________________________________ gnucash-user mailing list [email protected] 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.
