> On 27 Aug 2019, at 22:29, elvis <el...@dogonfire.com> wrote: > >>> >>> Hi Michael, >>> >>> This is how I would do it. I'm assuming you have around 30 people to >>> account for. >>> >>> Make up all your accounts and sub accounts and sub sub accounts and cross >>> accounts. >>> >>> Have a transaction in each person's account with all the splits possible. >>> >>> Each dinner copy the last transaction and alter the amounts. Maybe 20 >>> seconds each so you are looking at about 15 minutes to update the whole. >>> >>> >>> I'm assuming your primary document is some kind of piece of paper your >>> members fill out. If you have a spreadsheet on entry you would just massage >>> it and import it. >>> >>> By the time you much around with business features you might as well just >>> copy transactions. >>> >>> >>> Lawrence >> Thanks, Lawrence. >> >> The difficulty this suggestion doesn’t solve is in generating a report >> listing Gift-Aid-eligible totals for each member - the identity of the >> contributing member in each income account tree is at the twig level: >> >> Income:Destination1:MemberA >> Income:Destination2:MemberA >> Income:Destination3:MemberA >> etc >> fo > > You would do a joint income account that goes to separate member balances > that can be split up as to purpose.
If I understand what you mean, doesn’t this just do the multiplication in a different order? Income:MemberA:Destination1 Income:MemberA:Destination2 ... Income:MemberB:Destination1 Income:MemberB:Destination2 etc., which just shifts the awkward report from all contributions by MemberX to all receipts for Destination99. > > The Gnucash reports are very flexible, the balance sheet should do that, it > isn't really income it is a member balance which is an asset. I do the same > thing for my super fund and it works a treat. I have used Gnucash for 12 > years and I don't use the business features except for our big invoices, > maybe 5 a month. Everything else I use something else and just post totals. > Once you have clickey clacked 30 times to enter every invoice you will feel > like punching the screen . Exactly! This is why I’m attracted to the idea of importing invoice transactions from a CSV file, which would be edited on a spreadsheet to deal with minor variations in attendance at each meeting. Michael > > > >> all need to be picked up and added together for each destination and each >> member. >> >> The Customer-based model would ease that aspect. >> >> Unfortunately, there doesn’t seem to be a way of creating regularly repeated >> invoices as Scheduled Transactions, but I’m currently thinking along the >> lines of creating an invoice for each member for the default amounts at the >> beginning of the year, and then duplicating these invoices, one for each >> member for each meeting. After each meeting, I would edit each invoice if >> necessary (to deal with absences and variations in contributions) then post >> and pay them. >> >> This way the Destination accounts don’t need children and the annual Gift >> Aid Report can be populated from Customer Reports. >> >> I’ll do some experiments… >> >> Michael >> >>>> Thanks, >>>> >>>> Michael >>>> >>>> _______________________________________________ >>>> 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.
