Ask, reply and learn. Join the community of Akaunting.
Instead of having separated customer and vendor entity they should be store as person entity and categories them as customer and vendor. This way it is possible for a person to be categories as a customer and as a vendor at same time.
I don't agree, the current structure works perfectly.
well the structure remain for the front end users. this is just going to change data layer structure normalize it and make it simpler to manage user roles and categories.
I agree with Amir - use another accounting software and planning to switch and they do it as Amir stated - Why should I mentain 2 sets of data about 1 entity - as amir stated - the entity should be entered once and then categorised accordingly - I would also add a list of contacts within the entity with at least basic information - name, surname, telephone number and email address
Is there an extension that would allow me to do so? In my current workflow it's critical that I have them as one entity in some cases, since our company sometimes sells to the same entity it buys from and we need to see such transactions occurring under the same entity. Not one being in the Customers page and the other being in the Vendors page.
Yes I wish this would happen. we should be able to choose if we want the person to be a customer, vendor or both. just like when we add items we can choose if its a sale item, purchase item or both.
at the moment when I issue a refund I have to add the customer again as a vendor. by doing this there is no way to link the invoice from the customer to the vendor bill.
Showing 1 to 6 of 6 discussions