OpenERP Addons (modules)

partial reconciliation

Reported by Ferdinand on 2012-06-04
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenERP Addons
Medium
OpenERP R&D Addons Team 3
OpenERP Community Backports (Addons)
Undecided
Unassigned
6.1
Undecided
Pedro Manuel Baeza

Bug Description

to reproduce
create
2 invoices (100+200)
1 bank statement line (250)

go to manual reconciliation

mark all 3 line, do a partial reconciliation

the remaining 50 are written as residual to BOTH invoices which is wrong.

according to common accounting practice the older invoice has to be fully reconciled, the remaining 50 go to the newer invoice

Changed in openobject-addons:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)

Hello,

I made a fix for that "bug" but there is something that you need to know:
The balance for each invoice is recomputed like that:
(reconcile amount)/(number of invoice linked to the reconciliation)
but the reconcile amount stays the same
Like that the sum of each invoice's balance will give the reconcile amount and therefore accounting balance is preserved.
So:
- On the Accounting/Periodical Processing/reconciliation/Manual reconciliation the value given for the Partial reconcile will stay the same as before. (Example: I have two invoices with 1000 as Debit and 1 bank statement with 1500 as Credit. After partial reconciliation for those three, the partial reconcile amount will be 500 for each of them)
- When you look at the invoice (in other menu such as "customer Invoices" the balance will be the partial reconcile amount divided by the number of invoices linked in the same reconciliation).

Good luck,

Arnaud Pineux (API)

Changed in openobject-addons:
status: Confirmed → Fix Committed
Ferdinand (office-chricar) wrote :

Hu!
the correct rule (at least here in Austria) would be to fully reconcile the older invoice and do a partial reconcile for the other.

nevertheless it is clear that the sum of residuals must match the balance of the associated general ledger account(s)
hence it was a real bug

Changed in openobject-addons:
status: Fix Committed → New

Hi,

We cannot tell if it's the oldest one that must be fully reconcile or the newest one. That's why it's equally divided.

Good luck,

Arnaud Pineux

Changed in openobject-addons:
status: New → Fix Committed

Hello,

I think that you have to use the maturity date to determine the first invoices to fully reconcile.
If you don't consider the order of the invoices, you will never be able to track the unpaid invoices and send follow-ups.

Cheers
Guewen

Ferdinand (office-chricar) wrote :

There are these possibilities

* use comment https://bugs.launchpad.net/openobject-addons/+bug/1008774/comments/5
* ask the user which invoice to leave open
* do nothing - it is not useful to split the residual and does not conform to any accounting standards at all

qdp (OpenERP) (qdp) wrote :

hi c2c fellows,

although i understand your point of view, let me emphasize on the following points:
1) the behavior you're depicting is the one chosen when the reconciliation is made by vouchers. So this problem only occures when payments are not reconciled directly at their creation.
2) for me, the real bug was to present the 2 partially reconciled invoices with a residual amount of 50 each (total 100 residual while 50 only was on the partner balance). The patch of Arnaud fixes this and it's the most important.
3) fully reconcile one of the 2 invoices would implied to
- either split the payment line in two, in order to fully reconcile the oldest invoice (what if this payment was posted?)
- either change totally the way of managing reconciliations into OpenERP.
both solutions seem to be unacceptable according to me.

So we all know that this is not perfect but the reconciliation on vouchers was made to fulfil your needs depicted here, and i believe it can handle most of the situations for a majority of people. Thus for me, this patch solves the bug in an acceptable way, at least for the almost-ready-to-release-version.

Still, we will keep in mind this possible enhancement track while making the roadmap for the future.

Thanks for your understanding,
Quentin

Hi Quentin,

Ok, thanks for your explanation.

Guewen

qdp (OpenERP) (qdp) wrote :

the fix of this bug has been released under the revision 9156 of addons v7. The final patch is a bit different than the previously linked branch but it follows the same logic.

Thanks for the contribution,
Quentin

Changed in openobject-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers