As always, thanks for your considered advice David. It's a single entity where everything is shared except for specific income and expenses. Separate books are not-on. I'm understanding you are suggesting a separate subaccount for each Enterprise/Project under the existing CoAs (eg Expenses:Maintenance:Camel farm). Every report would be customised for each Enterprise/Project.
> What you are required to do... I'm not an accountant so in Oz I assume it's: ... provide evidence for amounts in any tax returns if requested (ie give them the shoebox). > There is also a Jobs structure which can be used with specific projects and > allows invoices/bills to be grouped for a specific job for a single > customer/vendor. It is discussed in the help manual I've reviewed that but I understand (??) it's not applicable. I'm a big fan of the Tutorial and Concepts Guide where the examples teach you what the terminology means and how to apply it. Back to the camel farm. Just say you sell a sheep in Oz. If you have a road train full ( https://img.izismile.com/img/img3/20100721/640/road_trains_640_26.jpg ) then no worries, but if it's one you had better eat it because the proceeds wouldn't cover the bookkeeping cost. With fees, levies, industry funds, different tax treatments, various parties - there's 20 splits for that transaction (could be more if it has a lamb) so when you multiply it by the subaccounts, well, it's a suicide risk. https://bugs.gnucash.org/show_bug.cgi?id=113772#c6 > _______________________________________________ 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.
