If you can’t beat them, join them with the TOFU … There’s one thing where seperate customer accounts might shine:
If you’ve got a customer or vendor with non-typical balance e. g. overpayments or refunds it will get put on the other side of the balance sheet. Kind regards Christian Kluge Am 05.04.2019 um 18:38 schrieb Adrien Monteleone: > From using other A/R software, the only purpose I can see to separate > customer accounts is for informational purposes. Since GnuCash was setup to > provide this information via reports using a consolidated A/R, the purpose is > served just as well and there are less accounts to deal with. You don’t need > to hide or otherwise archive old customer accounts when no longer needed. If > you want an at-a-glance per customer, you can just leave a Receivable Aging > report tab open. I have to deal with an outside A/R package for a client and > their separate account structure is much more maintenance and messy compared > to GnuCash’s approach. (might also be an issue with the quality of the code > between the two packages, admittedly) > > Regards, > Adrien > >> On Apr 4, 2019, at 8:56 PM, David Cousens <davidcous...@bigpond.com> wrote: >> >> Christian, >> >> It is clearly a design choice. I had wanted to setup separate A/R accounts >> for customers but Derek advised me that this was not the way the business >> features in GnuCash worked. Derek opted for a single A/R account and the >> ability to filter to provide specific customer information. I didn't >> particularly find that a problem when I was using Gnucash for a business >> though. >> >> David >> _______________________________________________ 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.
