Compensate partners debits and credits
Approval rules defined from the interface on any model: block a button, a status change or a field until the right people have approved, with approval levels, a minimum number of approvals per level and an app listing the requests you made and the ones waiting for you.
One cutting, one issue of material: take a component out once, spread what was really consumed over every manufacturing order or operation it was used on, record the quantities made and split the time of the operation between them, with an approval step for the difference.
Cost a bill of materials at a given quantity, taking each component at the vendor price tier that quantity actually reaches, instead of at its standard price.
Grant the financial discount a customer negotiated without computing it by hand: a plan says how often it is granted, who gets it, on which turnover, how fast the invoices have to be paid and how much each step is worth. Every period, a run shows what each customer did and what he is owed, and once approved it writes the credit note.
Hand the bonus over as points instead of money: the approved run loads an eWallet, a gift card or a loyalty card of each customer with the amount he earned, which he spends on his next order instead of cashing a credit note.
Grant the bonus as a sale order on a service instead of a credit note: the run writes one order per customer, with the amount read from his turnover, and the salesperson can put the same discount on a quotation he is writing, computed in front of him.
Write the bonus for a class of customers or for a level of the segmentation instead of typing a condition: the plan is for the Gold and the Platinum of the B2B class, and one step of it may be reserved to one level, so the same plan grants 1% to a Silver and 2% to a Gold.