Matt,

There might be a use case for it, but as I mentioned, it’s just too darned easy 
already to switch between books. With the example of the club book I manage, I 
have to sometimes record my own expenses in my personal books, and then in the 
club books as a contribution in-kind. The workflow is simple enough to click 
File > filename.gnucash at the bottom of the list, enter the transaction again 
from the club’s perspective and then switch back. If I really had a more 
difficult task, I’d attempt an export/import scenario. (waiting till 3.0 anyway 
on that count since the present importer doesn’t like Gnucash’s own exports 
much)

It’s probably best to leave this as-is.

The use case with a greater need (which is still a long way off) is multiple 
users editing the same file in a network environment.

Regards,
Adrien

> On Feb 6, 2018, at 7:53 PM, Matt Graham <matt_graham2...@hotmail.com> wrote:
> 
> The only other thing to add - this all presumes that you need separation. 
> Probably do for your businesses (tax and legal reasons - I have no idea), but 
> don't forget that GNUCash reports are very flexible - you choose the accounts 
> you want included.
> 
> I don't use the business features though - I'm not sure whether they would be 
> as flexible.
> 
> You could have two different root accounts for each business (each with their 
> own assets, expenses, liabilities, and income sub accounts) and go from there.
> 
> I'm sure I just gave a few accountants on this list a heart attack...
> 
> Ultimately, as others have said, opening different files for each business is 
> probably a better way to go.
> 
> David/Adrian/John - is opening multiple windows a feature we should be 
> putting into bugzilla for eventual incorporation? I'm getting the impression 
> that V3.0 onwards will be much easier to fix up stuff like this.
> 
> Thanks and regards,
> Matt
> 
> 
> -------- Original message --------
> From: Roger Hatton <rogh...@gmail.com>
> Date: 7/2/18 08:58 (GMT+10:00)
> To: gnucash-user@gnucash.org
> Subject: New Entities
> 
> Does GNU Cash support more than one entity?
> In other words separate ledgers for separate business names?
> Using the one single downloaded GNU Cash system?
> Process advice appreciated.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.gnucash.org%2Fmailman%2Flistinfo%2Fgnucash-user&data=02%7C01%7C%7C84e11b321bfc4040f86708d56dacb622%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636535510911511456&sdata=0yjSI3HEmIcgJ0O6YlWxXsER5VqgDAKSM36SHFtWpvw%3D&reserved=0
> If you are using Nabble or Gmane, please see 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.gnucash.org%2Fwiki%2FMailing_Lists&data=02%7C01%7C%7C84e11b321bfc4040f86708d56dacb622%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636535510911511456&sdata=7DOvQGlFHI88FacJjXqZSqSRe0GwZAcmFHHAEwBZxBY%3D&reserved=0
>  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.

Reply via email to