Use cases for Taxes, Discounts, Commissions and similar interfaces.
Table of Contents
There is need to put stamp on every invoice. This stamp is bought in Inland Revenue, and this is "document tax".
This tax is not related to price, quantity, amount of sold resources. It is document depended.
Example Every stamp is 1€
but when it is split:
Tax Line in invoice B comes from nothing. It might be added manualy, but it shall come from simulation.
For Case A there is possible to use Simulation and properly configured rules.
For Case A, after accepting decision to simulation, Tax Line movements shall diverge by its vat ratio.
Look at Tax Inclusive¶ System for more discussion.
This is not implemented yet price system in ERP5, but shall be supported by such interface.
For Invoice with total_price <= 5000 €: Tax Rate 12% For Invoice with total_price > 5000 €: Tax Rate 15%
Case 1 & Case 2 produce:
If trade condition is correctly defined, than tax is correct, so no tax related changes have to be done on Invoice.
Case of wrong Purchase Invoice Transaction from supplier:
Invoice 1 generated, system configured to support merging.
Invoice 1 updated.
Taxes are equal.
New line with taxable resource added to packing list
if you consider the packing list is just about saying "I moved this from here to there", you don't care about taxes yet and it's on the invoice that this has to be done. -jerome
Both orders' movements are merged at Invoice. Wanted behaviour: Invoice:
Same shall apply if there would be one order with such lines.
-- There is a category movement group for base_contribution at cell / line level on invoice builder -jerome