Armaghan Saqib wrote:
On 20/05/10 12:32, David Godfrey wrote:
Hi Armaghan,
As I am sure you are aware, I currently use LedgerSMB 1.2.17 (should
have gone to 1.2.21 by now but work keeps getting in the way :(
Hi David, thanks for the reply. Yes I know and have read you
contributions too (excellent work) :)
We actually have to deal with this ourselves, our solution is simple
just create both a customer and a vendor record with the same name.
Actually I would like to automate this probably with database triggers.
I think I can keep the customernumber/vendornumber same for both rows
and then do other things based upon this common number.
We do not transfer balances from customer to vendor or the other way.
Personally for ease of tracking on the accounting side, I feel it is
easier to require that the customer actually pay every invoice I
issue, and I pay every invoice they issue to me.
You could create a "linked account update" function that automatically
does both a "cash payment" and "cash receipt" for this scenario, but I
feel that it needlessly complicates tracking, to say nothing of the
problems that could arise if the other party does not do the same.
I am not sure how to handle this bit or probably write a new
function/form to transfer/adjust balances between the same customer and
vendor.
As I mentioned previously I don't like the idea of transferring balances
like that, if the other party does not do the same, it gets harder to
track and prove that "you have paid them by deducting what they owed you"
for example, if they never actually processed the invoice you issued to
them, perhaps because the postal system lost the letter, they would not
have record of owing you, therefore would claim that you had not paid them.
(I think that makes sense)
Having said that, if you were to proceed with a "balance transfer"
function here is how I would do it.
1. Require that linked customer/vendor accounts have an ID number in
the form L-1234 where only 1234 can vary. this should prevent clashes
with conventional accounts.
2. duplicate the "cash => payment" type interface. it could be an
extension to it but I think duplication would be safer.
This interface would be named something like "cash => reconcile linked"
It would have a dropdown that only shows linked accounts that have a non
zero balance for either the vendor or client side.
Instead of showing invoices and payments, it would show sales invoices
as + amounts and vendor invoices as - amounts (or the other way it
doesn't matter)
You could then select the check boxes for one or more + amounts and one
or more - amounts, click on the Update button, check for correctness and
post.
Behind the scenes this should raise a set of transactions in exactly the
same way as the cash payment and cash receipt screens do.
If an overpayment occurs then it would behave in exactly the same way
the existing payment methods do.
Regards
David Godfrey
Will be great if some other users can share how they are doing
it right now.
Thanks
Armaghan
--
http://www.ledger123.com/
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger