Approvals
Commission statement approval workflow
Quota Queue separates calculation, locking, approval, and payment into explicit lifecycle steps. That prevents an open recalculation from being mistaken for a reviewed payroll result.
- Product location:
- Dashboard → Team → Approvals
- Reviewed:
- 2026-08-23
Before you begin
- Calculated statements
- A defined reviewer chain
- A locked pay period
Worked example
Northstar's two-step statement approval
Illustrative Northstar Software workspace. The people and transactions are fictional; the workflow and product UI are real.
| Step | Reviewer | Evidence checked |
|---|---|---|
| 1 | Sales manager | Deals, ownership, quota, and rep disputes |
| 2 | Finance administrator | Plan terms, adjustments, control total, and payout export |
Result: The statement cannot reach approved status until both authoritative steps complete.
Lifecycle boundaries
- 1
Calculate
Draft statements update from current source data, assignments, quotas, and published plan terms while the period is open.
- 2
Lock
Locking creates the statement snapshot used for review and prevents ordinary open-period changes from silently replacing it.
- 3
Release
Release sends the locked version into the authoritative approval workflow configured for the statement scope.
- 4
Review and resolve
Assigned reviewers approve their steps; representatives or reviewers can surface disputes that retain statement context and discussion.
- 5
Approve and pay
After required statements are approved, the period can advance to approved, support payout export, and later be marked paid.
Approval controls
- Role and scope-based workflow selection
- Ordered reviewer steps
- Statement and period status visibility
- Optional separation between the person who locks and the person who approves
- Durable approval and dispute history
- Reviewed payroll and warehouse export boundaries
When a result needs correction
Correct draft-period source data or terms at their source. After locking or approval, use the explicit reopen, dispute, or adjustment workflow appropriate to the lifecycle state. The objective is to preserve what reviewers saw and why a later result changed.
Product walkthrough
See the workflow in Quota Queue
These captures show the real product interface with demonstration data. Product UI shown as of August 2026.
Expected result
The approved period retains who reviewed each step, when they acted, what statement version they saw, and how disputes were resolved.
Open this workflow in Quota QueueTroubleshooting
Why can the next reviewer not approve?
Verify that the prior ordered step completed and that the current user has the required role and scope.
What if a reviewer finds an incorrect deal?
Use the dispute, correction, reopen, or adjustment path appropriate to the lifecycle state instead of bypassing the recorded workflow.