Sorry Rich for getting back so late... been away. Re the 30,60,90 day aging problem, If I bill some one say on the 5th of March and they are say on a 30 day account with me, the payment will be due on the 30th of April, not the 5th of April (all invoices for march would be settled on the last day of April) by which time sql has pushed the invoice into the 60 day column, thats my problem.
Re the payment problem, The old accounting systems and indeed the way it works here still is that a Payment is made on the statement, not the invoice, what this means is that a payment is made and that is offset against the outstanding balance on the statement. Sql pays against invoice. What my customers want to see is the lump sum payment made so they can reconcile that amount, not the individual payments to invoices. Sql doesn't capture lump sum payments (of course it can but gets messy with journal entries) and these need to be reflected on the statement to the customer. It was easier to export the data to a spreadsheet and to manually put in the payment than trying to mess with the database as the section of the DB where the payments were reflected was difficult to locate and so trying to then add up the various payments in different sections of the DB was just getting messy (and expensive from a programming perspective as it got more tricky) so I pulled the plugged, and put together a simple spreadsheet template that we copy and paste the data to and then add a line item from the bank statement. I have about 20 Statements a month and takes about an hour a month to do, so wasn't worth throwing large sums of money at it. We still use the AR Aging report but now just as a cross check to make sure that the bottom line tallies. Tim Wade Penguin Products On Thu, Mar 10, 2011 at 7:29 PM, Rich Shepard <[email protected]>wrote: > On Wed, 9 Mar 2011, Penguin Products wrote: > > The AR Aging Report, gets you half way there... >> > > Hello Tim, > > Now I see the statement option on the bottom. When I look at A/R reports I > tend to look at the outstanding page, not the aging page. > > > The added problem I have is that they pay on the last day of the month for >> the previous months invoices... so even the "30, 60, 90 day listing isn't >> quite accurate for me. >> > > I don't see why not. What you see before applying the payment should be > the current aging. > > ... that interrogated the Database but struggled finding the payments made >> >> as they were allocated to individual invoices and not as a total. >> > > Ah. So when a check comes in you apply it to the oldest outstanding > invoice and work your way forward? After doing this, doesn't the aging > report reflect what's still outstanding? > > > Rich > > _______________________________________________ > 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
