Corrections and clawbacks
When a deal changes after payday, the difference finds its own way home.
A deal gets discounted, cancelled or reassigned months later. Prowi recalculates with the original rules, compares it to what was paid and books the difference on the current statement. History stays untouched.
Clawbacks are where spreadsheets break.
Someone edits a March cell in May. Nobody can reconstruct what was actually paid, at which rate, for which version of the deal. So either the rep keeps the overpayment or finance quietly eats it.
So the one moment that needs trust most is the one with the least evidence.
Prowi notices because every record has a history.
Every synced deal is versioned. Value changed, deal cancelled, refunded, reassigned to another rep, or a record that now meets the filter criteria it missed before. Each one is a trigger, nobody has to report it.
So corrections happen because the data moved, not because someone complained.
Current data, original rules.
The January commission is recalculated on today’s deal value with January’s rate, even if the rate changed in March. The difference to what was paid is the correction.
So it is fair to the rep and fair to the company, every time.
Corrections chain. They never double-count.
Each correction shows only the change since the last one and links back to the original. On the statement the rep sees the breakdown: added, deleted, changed, with the deal and the amount.
So a rep can read exactly why a number moved, without a meeting.
You decide how far back to look.
Each model has a corrections window: how many periods back Prowi monitors and how many corrections one commission can receive. One to three for fast-closing deals, twelve for subscriptions with twelve-month clawback clauses, zero to disable. Statements with corrections still go through approval.
So clawbacks become policy you set once, not plumbing you fight monthly.
How corrections work
The rules the engine follows, in order.