That was also part of the problem in that the payment was made in a different time period to when the invoices were issued (Invoices issued March, Payment made April) and it was getting very complicated trying to get a "foolproof" formula to add up the payments from different time periods and keep it separate from the invoices. and although they would not make 2 payments in a day they do occasionally make more than one payment in a time period which added to the confusion. There is also the complication of discount issues for prompt payments which results in a "negative invoice" being issued in the payment time period, not the invoicing time period which doesn't help and the additional problems with errors and rounding inaccuracies that occur when you start adding and doing calculations and you should hear the accountants squeal if you tell them they have paid you 1 cent short of what they actually paid. These accountants seem to strike the fear into my customers and I need happy customers... need I say more!
If you understood what I just wrote you well done because to tell you the truth the more I look at this the more confused I get (maybe thats why I run a small company and not a multinational!) But thanks for taking the trouble to reply Bernd. Tim Wade Penguin Products On Mon, Aug 16, 2010 at 10:13 AM, Bernd Plagge <[email protected]>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Tim, > > the system is recording the payment receipt date. > Can't you just add up all payments for a given day? > How likely is it that a customer makes two payments per day? > > Regards, > Bernd > > On Mon, 16 Aug 2010 08:58:49 +0200 > Penguin Products <[email protected]> wrote: > > > Hi Paul > > > > There is nothing wrong with Sql-Ledger or LedgerSMB, its just that some > of > > us need (especially here in South Africa), those who deal with monthly > > accounts for our customers, need to see the actual payment from the > > customer. > > > > What happens is that the agreement we have with our customers, is for > > example for all Purchases made by that customer between 1 march and 31 > > march, so long as he pays us by the 30 April (Last day in April) he will > not > > pay interest or penalties on that amount. This is what we call a 30 day > > account, although its not strictly 30 days as stuff bought on 1 March is > > more like 60 days but for better or worse, that is the system that is > used > > here. > > > > What this means that at the end of each month, we produce a report for > our > > customers which we call a statement in it we show all the invoices still > > outstanding in the current, 30 day, 60 day etc columns but again the 30 > day > > for example being what was due to be paid on the last day of the previous > > month, not what was owed 30 days from date of invoice, if you get my > meaning > > from the paragraph above. We put in the customers payment in the > apropriate > > column and we show a running balance down the right hand side and across > > the bottom what is owed in the current, 30 days 60 days etc. The invoices > we > > could sort out with a PHP script as that Data we could get at and sort > > etc... The problem comes with the payment. The customer wants to see on > the > > statement what he paid and on what date, he is not worried about which > > invoice its allocated to and the problem was there was no specific > address > > on the database that captured the customers specific payment and the > date. > > One could add a journal entry into the general ledger, but it gets messy > and > > is prone to error as you capture the payment in one place and then > capture > > it again in the payments section to satisfy the needs of Sql-Ledger or > > LedgerSMB. > > > > Its just one of those annoying things 95% of the information is there but > > unfortunately the 5% is critical to the report and the changes that need > to > > be made to incorporate the 5% dont warrant the work and the cost. The > Copy > > and paste works well enough for us into a spreadsheet and is not tooooo > much > > of a problem, it would be nice though if we could handle it all in one > > package but then I guess if life was too easy too many people would be > out > > of work and we would be bored stiff. Just thought I would mention it so > that > > as these packages improve and develop it could possibly form part of a > > future upgrade. > > > > I hope that my lengthy explanation helps, Paul, its not that Sql or SMB > are > > faulty, some of us just need 2 additional bits of information (Payment > and a > > date linked to a customer) that due to the way Sql and SMB operate are > not > > captured at this stage and as it is not something that appears to be > > universally used across the world I understand why it does not form part > of > > the packages report architecture. > > > > Tim Wade > > Penguin Products > > > > > > > > On Fri, Aug 13, 2010 at 9:32 PM, Paul Tammes <[email protected]> wrote: > > > > > The customer paid plus 250 and minus 60 making a total payment of 190. > > > You received 250 minus 60 making a total receipt of 190. > > > > > > Both SQL ledger and SMBledger report the very same, which seems totally > > > correct and adequate to me. > > > Sorry but I do not grasp the problem. > > > > > > > > > 2010/8/11 Alf Newman <[email protected]> > > > > > >> I make sql-Ledger. > > >> sale invoice for $250. > > >> credit note for $60. > > >> customer he now pay balance of $190. > > >> cash receipt report for this month shows receipt of $250, and receipt > of > > >> *-*$60. > > >> where is receipt of $190 as paid by customer ? > > >> how to do correct entry to make correct report receipts ? > > >> thanks you > > >> > > >> > > >> _______________________________________________ > > >> 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 > > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEUEARECAAYFAkxo8zEACgkQpYU8M8PbPV6rwgCYvywlD5UghEb0iXRXClovJGAQ > VQCgo+g1rc2bvZYSGlQOu5O05mV6MZo= > =IOi/ > -----END PGP SIGNATURE----- > _______________________________________________ > 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
