diff options
| author | Laurent Smet <las@openerp.com> | 2017-04-11 11:09:01 +0200 |
|---|---|---|
| committer | qdp-odoo <qdp@odoo.com> | 2017-04-11 11:09:01 +0200 |
| commit | a8994b40754834b62038fcc0540cad766ac9e278 (patch) | |
| tree | dbf9ac8dbe9433fc5e46e1197ac6d673b483f8c6 /doc/python3.rst | |
| parent | 84e4f6b08c28888cc840c919616919ad19c367a5 (diff) | |
[IMP] account: use max_date instead of create_date for aged reports
Aged receivable/payable was using create_date of account_partial_reconcile to decide if a partner needs to be shown at a given date or not.
While it was not wrong, our decision to use the create_date was based on the fact that we wanted to be able to render the exact same report we had at a past date, so a the date of the reconciliation would be important... but since the unreconciliation was not forbidden it wasn't really the case.
Moreover, in some case where reconciliation is not at the same time the payment is recorded, this choice
- was confusing people about results given by the aged receivable/payable report.
- was confusing people about the 'Paid on...' line in the payment widget on the invoice, as they would see there a date unused by the system (although they would have liked too)
This was discussed in opw 31844. Was PR #16016
Diffstat (limited to 'doc/python3.rst')
0 files changed, 0 insertions, 0 deletions
