Hi, Am 11.04.20 um 19:49 schrieb David Carlson: > David T, > > You are right. I too am not sure why the (U)pdate option overwrites the > text of the existing transaction, but I think that it usually is offered as > the default when the date of the matched transaction is not the same as the > imported transaction, and possibly when the importer tries to match to a > transaction with a slightly different value. Like you I usually prefer to > keep the existing text.
There have been reasons why the update option is preferred: Date: You give the order on Friday, but the bank executes it on Monday. Amount: You use the teller machine of a third party, which charges higher fees than expected. Description: You enter a short description, but the bank completes it by e.g. additional SEPA details, .... or you have a scheduled transaction bank->expense:rent with a description "Monthly rent", but the real transaction has "Rent for <month> <year>" Question: what are the use cases, where it is the other way? > I get lazy with trying to match everything during the import when the clock > is running and Gnucash will soon be wanting to interrupt me with an > automatic save, so I often just let everything come in and sort it out > later. I have set autosave to once per day and save manually after finishing logical units. 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.
