Approval Workflow (Multi-Level Approval)
What is a commission approval workflow?
A commission approval workflow is the defined sequence of checks a payout passes through between being calculated and being paid. In its usual form it runs: validation, review, approval, notification. Everything sitting inside that sequence is a pending payout, and nothing leaves the business until the sequence completes.
Multi-level approval means the sequence requires more than one signature, typically a first-line manager who knows the deals, and then Finance, who owns the money. The two are checking different things, which is exactly why both are needed. A manager can spot that a deal was credited to the wrong rep. Finance can spot that the total is $40,000 above the accrual.
This workflow is the honest answer to the question reps ask most often, which is why commission takes a week or two to arrive after the commission period closes. It is not administrative sloth. It is the last point at which a wrong number is still cheap to fix.
The four stages
StageWhoWhat is being checked1. ValidationSystem or commission adminIs the data complete and sane? Missing close dates, deals with no owner, values that fell out of the CRM sync.2. ReviewThe rep's managerAre the deals right? Correct owner, correct splits, correct credit. The manager knows things the data does not.3. ApprovalFinanceDoes the total hold up? Reconciles against the accrual, no outliers, budget and policy exceptions signed off.4. NotificationSystemThe rep is told what is being paid, and why, before the money lands.
Stage four is routinely dropped, and it is the cheapest of the four. A rep who learns what they are being paid at the same moment as the bank does has been given no chance to catch an error while it is still correctable, which is how a preventable dispute becomes an expensive one.
A worked example
Maya's February commission is calculated on 3 March at $4,000.
Validation flags nothing. Review catches the problem: her manager sees that one deal was booked at $50,000 but the signed order form was $48,000, because the CRM was never updated after a last-minute discount. The figure is adjusted to $3,840. Approval by Finance confirms the revised total reconciles to the February accrual. Notification tells Maya, before payday, that she is being paid $3,840, and which deal changed.
The workflow did its job. Without stage two, Maya would have been overpaid $160 and the money would have come back later as a clawback, which costs several times more in admin and a great deal more in goodwill. Without stage four, she would have opened a dispute on payday asking why she was short.
What this means?
For Finance, this is a segregation-of-duties control, and it should be treated with the seriousness that implies. The person who calculates commission should not be the person who approves it. In a spreadsheet process, they are usually the same person, which means there is no control at all, only a habit.
For RevOps, the workflow is the main determinant of how long the close takes, and therefore of when reps get paid. Each stage adds days. The question worth asking of every stage is what it has actually caught in the last twelve months. A review step that has never changed a number is not a control. It is a delay with a job title.
And the design constraint that catches people out: the payout period has to be set after the realistic approval window, not before it. A plan promising payment on the 5th, run through a workflow that reliably takes until the 9th, has written a check the process cannot cash, every single month.
Common mistakes
1. One person calculating and approving
Not a workflow. There is no independent check, and no auditor will accept it as one.
2. Approvers who rubber-stamp
An approval step where the approver has no practical way to interrogate the numbers is theatre. If the manager cannot see the deals behind the figure, they are approving a total, which is to say they are approving nothing.
3. Too many levels
Every additional approver adds days and diffuses responsibility. Three signatures where two would do is not more control, it is less, because nobody in a chain of three believes the check is really theirs.
4. No notification stage
The cheapest stage, and the most frequently skipped. Telling reps what is coming, and why, before it arrives prevents more disputes than any other single step. See commission transparency.
How Visdum handles approval workflows
In a spreadsheet process the workflow exists only as a chain of emails. The file goes to a manager, comes back with a comment, gets edited, goes to Finance, and at no point is there a record of who approved what, or what the numbers looked like when they approved it. If someone is on leave, the sequence simply stops.
Visdum makes the workflow an explicit, configured sequence rather than an email chain. Calculated commission is held as pending until each required approver signs off, and approvers see the deals behind the figures rather than only a total, so review is a real check instead of a formality. Multi-level approval routes through as many stages as the policy requires, with delegation when someone is away, so the close does not stall on one person's inbox. Every approval, rejection, and adjustment is written to the audit trail with a name and a timestamp, which is what turns the workflow into a control Finance can evidence. Once approved, the payout releases on the scheduled payout period, and reps are notified with the reasoning attached.
Take a self-guided product tour to see this in action, or read the complete commission close playbook.
Related terms
Pending Payout · Payout Period · Commission Audit Trail · Commission Dispute Resolution · Commission Statement
Calculate your OTE in 30 seconds
Frequently asked questions
What is a commission approval workflow?
A commission approval workflow is the defined sequence of checks a payout passes through between calculation and payment: validation, review, approval, and notification. Everything inside that sequence is a pending payout, and nothing is released until it completes. It is the control that stops incorrect commission leaving the business, and it is why payment follows the period rather than closing it.
What is multi-level approval?
Multi-level approval means a payout requires more than one signature before release, typically a first-line manager and then Finance. They are checking different things: the manager knows whether the deals and credit are right, while Finance knows whether the total reconciles to the accrual. Both checks are needed, which is why one approver is rarely enough.
Why does commission take so long to be paid after the period ends?
Because it is passing through the approval workflow. The data has to be validated, the deals reviewed by a manager, the total approved by Finance, and the rep notified. That window is what prevents wrong payouts going out. It usually takes one to two weeks, and it should be published in the plan so no rep reads it as a delay.
Who should approve commission payouts?
At minimum, someone other than the person who calculated them. Segregation of duties is the whole point of the control. In practice the first approver is the rep's manager, who can verify deals and credit, and the second is Finance, who can verify that the total reconciles. In a spreadsheet process these are often the same person, which means there is no control.
How many approval levels should a commission plan have?
Usually two, rarely more than three. Every additional approver adds days to the close and diffuses responsibility, because nobody in a long chain believes the check is really theirs. The useful test for each stage is what it has actually caught in the past year. A review step that has never changed a number is a delay, not a control.
What is the notification stage in an approval workflow?
It is the step where the rep is told what is being paid, and why, before the money arrives. It is the cheapest stage and the most frequently skipped. A rep who discovers their payout at the same moment as their bank has no chance to catch an error while it is still cheap to fix, which turns a preventable question into a dispute.