On Fri, Jul 22, 2011 at 3:53 PM, Rich Shepard <[email protected]>wrote:
> On Fri, 22 Jul 2011, Jeff Kaminsky wrote: > > This sounds more like an error in a much earlier reconciliation, rather >> than a fault in the program. Am I wrong? >> > > Jeff, > > Shrug. > > After a borked postgres upgrade three years ago with my accountant's > urging I removed all transactions 2008 and earlier. So now all I have are > those from 1 Jan 2009 to today. > > I cannot recall when I first encounted this issue. I've ignored it for a > while and only this morning thought to ask about it on the list. I can go > through bank statements for the past 2.5 years, but the L123 entries have > matched the statements. If not -- usually because I transposed two numbers > when entering a GL transaction -- I correct it to match the statement. > > > Rich > ______________________________**_________________ > SQL-Ledger mailing list > [email protected] > http://lists.ledger123.com/**mailman/listinfo/sql-ledger<http://lists.ledger123.com/mailman/listinfo/sql-ledger> > I don't know if this will help or not but I had a very similar problem up until much earlier this year. I would need to switch to regular SQLedger to reconcile my accounts because of this type of discrepancy. Then back to L123. Someone on this list told me that what I needed to do was to not select the month of the reconciliation but to select the closing date of the statement only, even though it is the last day of the month, and to leave the opening date blank. I tried it and was surprised to find transactions that had not been ticked off, for whatever reason, all the way back to 2008. I almost couldn't believe my eyes. I don't know if this is any help but I thought it wouldn't hurt to say it anyway. Br Nicholas
_______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
