Vendor & customer same person

[tsagar]

Maf and all the others who so kindly responded, thank you.

I am currently doing it the way Maf suggested. I am creating a clearing
account for each customer / vendor and settling their accounts through that.

This, at best, is a workaround. This is not a 100% hygienic solution.
Ideally, there should be entities and not customers and vendors. Like I said
in one of my posts, we should be able to flag such entities as customer or
vendor or employee or agent or shareholder or lender or anything that is
possible. There is an ever present possibility that a customer could later
become a vendor or an employee or an agent. A user should be able to apply
multiple flags to an entity. Once the flags are applied, the entity details
should become accessible to different databases.

Most of the commercially available account packages do this. In fact, one
could easily say that this is the standard procedure.

Is there someone out there who's willing to make these changes in the form
of a modification project? If yes, I am willing to play the role of domain
consultant / business analyst. I can spare at least 8 hours each week (or
even more). I am an experienced domain consultant and can generate SDLC
artifacts including use cases and decision trees.

Best regards



--
View this message in context: http://gnucash.1415818.n4.nabble.com/Vendor-customer-same-person-tp1433340p4670383.html
Sent from the GnuCash - User mailing list archive at Nabble.com.