On 07/25/11 01:35, Rolf Stöckli wrote:
Am 22.07.2011 17:53, schrieb Rich Shepard:
Reconciling bank statements has been discussed here before and, while
I've
followed the advice and suggestions in the threads, I'm still having
fits
each month.
Sooner or later we should arrive at a point where we can reproduce the
issue. One problem seems to be that under certain circumstances
bookings disappear.
I've tried the following:
Created an invoice, added 2 identical payments of 20 EUR. Then I open
the reconciliation screen.
- original SQL-Ledger: shows 1 entry of 20 EUR
- community version and L123: show 1 entry of 40 EUR
In my opinion, L123 and the community version show the correct value.
Do you agree with that and can you reproduce it on your systems?
Regards
Rolf
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
Rolf,
I'm using the latest L123 that was put out yesterday. I created a
transaction and committed it. Then I created another, exactly the same;
same date, source (In my house this is the check number), description
and credit amount. Committed it. So there's two:
2011-07-25 88888 bogus 20.00
2011-07-25 88888 bogus 20.00
In reconciliation if I choose detail I see both. In summary I see one
with a doubled credit amount. If I then change one of the sources
2011-07-25 88889 bogus 20.00
2011-07-25 88888 bogus 20.00
I get two separate entries on two separate lines under detail and
summary both. I leave date range blank and see only uncleared
transactions. If I then re-set the source and change, in this case, the
description
2011-07-25 88888 boguss 20.00
2011-07-25 88888 bogus 20.00
I then get the same display using detail but with summary I see two
entries in one group but a credit of 40.00 and only a single source.
Some of the values are blank in the listing, like so:
2011-07-25 88888 bogus 40.00
88888 boguss
This looks like in the summary mode the DB is being told to GROUP by
some fields and not others so that the fields that are given in the
GROUP clause are shown only once like the date, some are shown only once
but are totaled (because they're numeric values) like the credit amount,
and some listed twice because they're different. Of course postgresql
will GROUP in the order the criteria are given and nests the grouping
but the results are shown in the order they are given in the initial SELECT.
Perhaps what is needed is a field that is unique for each transaction (I
think you have that already) and include that field in the Group clause
but not in the SELECT list. Then every transaction would be listed
individually under each date. The credit amount would be summed or not
depending if it was in the GROUP clause; I can see real benefit in both.
Maybe another 'shepard box' to allow the user the choice? I'm ignorant
of perl's place in all of this and maybe some of these fields live on
different tables such that my suggestion couldn't work even if it was a
good one. Take from this what you will, and I hope my use of multiple
fonts doesn't screw up anybody's reader.
Kindest regards,
r
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
