| 2013-08-09 13:30:19 |
Stefan Rijnhart (Opener) |
description |
account/report/account_aged_partner_balance.py does a lot of queries in the form of
WHERE account_move_reconcile.create_date > %s
where the report start date (e.g. '2013-08-09') is substituted in the argument. Of course, create_date is not a field of type date but of datetime. A datetime argument like '2013-08-09' constitutes the *start* of the day, so that te expression is actually true for any time on that very day. The effect is that reconciliations of the start date of the report are ignored, and the amounts of the reconciled move lines will feature in the report.
Accountants checking the results of the reconcilations that they just made may be surprised (if not worried).
A solution could be to craft the query arguments in the form of '2013-08-09 23:59:59', so that reconciliations created on the report start date are taken into account. |
account/report/account_aged_partner_balance.py does a lot of queries in the form of
WHERE account_move_reconcile.create_date > %s
where the report start date (e.g. '2013-08-09') is substituted in the argument. Of course, create_date is not a field of type date but of datetime. A datetime argument like '2013-08-09' constitutes the *start* of the day, so that the expression is actually true for any time on that very day. The effect is that reconciliations of the start date of the report are ignored, and the amounts of the reconciled move lines will feature in the report.
Accountants checking the results of the reconcilations that they just made may be surprised (if not worried).
A solution could be to craft the query arguments in the form of '2013-08-09 23:59:59', so that reconciliations created on the report start date are taken into account. |
|
