-
-
Notifications
You must be signed in to change notification settings - Fork 49
Description
Is your feature request related to a problem?
Yes. The existing mis.total.committed.purchase model tracks the total confirmed value of Purchase Orders (POs), regardless of whether they have been invoiced.
This is problematic for Budget vs. Commitment vs. Actual reporting because:
Once a PO line is invoiced, its cost moves to "Actuals" (e.g., account.move.line).
The value remains in the "Commitment" column (mis.total.committed.purchase).
This results in a double-counting of the cost and provides a misleading Remaining Budget figure (it shows the cost twice: as a commitment and as an actual).
For accurate forward-looking financial reports, a "Commitment" should only represent the open liability that has not yet been invoiced.
Describe the solution you'd like
Maybe the mis_builder_total_committed_purchase module could be modified so that the underlying model/view (mis.total.committed.purchase) only includes the uninvoiced amount of confirmed purchase order lines.
This aligns the model's behavior with the highly useful mis.committed.purchase model found in the mis_builder_demo module, making it suitable for tracking genuine open financial forecasts/commitments.
Describe alternatives you've considered
The alternative is to create a new, separate module (e.g., mis_builder_uninvoiced_committed_purchase) to provide the desired "uninvoiced only" model.
However, since tracking only uninvoiced commitments is the most common requirement for accurate financial planning, modifying the existing model is preferred to make it immediately useful without requiring an extra module or confusing model choices.