The import should assign them to whatever accounts you map. (the ‘other side’ of each being the account you are importing) If any do not, they’ll be assigned to the imbalance account so they’ll be easy to find and fix.
The only issue with balances is that you’ll have to adjust your opening balance entry for that particular account. So if you started with 2018 with an opening balance there and then started entering or importing prior transactions, you’ll need the real opening balance from 2017 to have everything still be the correct balance as of today. While some may cringe at the suggestion, it’s quite easy to simply change the date on your opening balance entry to 1/1/17 and correct it. The other route would be to make a new opening balance entry as of that date, but this will look odd since it’s back-dated, and then you’ll need a correcting entry as of 12/31/17 to keep the 1/1/18 entry from doubling your balance. There are times when I see the point of correcting entries. This is not one of them, you’re re-building your books in a different format. The entries really shouldn’t be corrected, just translated. It’s okay to directly edit errors produced by either the import process or by choice of order of import. Regards, Adrien > On Feb 14, 2018, at 5:54 PM, Fran_3 via gnucash-user > <gnucash-user@gnucash.org> wrote: > > My concern was if we 'import' all the 2017 transactions it will mess up the > balances... but I guess they will all just sit in checking assigned to no > account. > We just thought it would be cleaner to have a separate 2017 file... > I'm going to post another question sorta relative to this so stand by. > Thanks, > Fran3 > > On Wednesday, February 14, 2018, 6:48:54 PM EST, Rich Shepard > <rshep...@appl-ecosys.com> wrote: > > On Wed, 14 Feb 2018, Fran_3 via gnucash-user wrote: > >> We have setup a gnucash file for 2018 and created all our customer and >> vendor accounts... plus customized the chart of accounts... and entered >> all the transactions to date. Now we want to do 2017. > >> Is there a way to export the structure leaving the vendors, customers, and >> customized chart of accounts in place so we can begin populating for 2017. >> Thanks for any help. > > Fran3, > > Were I you, I'd just start entering your 2017 data (in any order) and > GnuCash will place it appropriately by date. That's what I did when I > switched both business and personal books to gnucash in 2017, I entered all > the 2016 data when I had the time. > > There's no particular advantage to keeping separate books when you have > sufficient disk space available and can specify date ranges for all reports. > > Happy bookkeeping, > > Rich > _______________________________________________ > 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.
