Rules and approvals
Discuss the review process and the evidence needed for your team.
THE SHARED WORKFLOW
RevexOne connects participants, performance measures, rules and payouts in one record, with sales commissions, customer and vendor rebates and quota planning on the same base.
CURRENT COMMISSION WORKFLOW
Every stage has a clear purpose. Select a step to see what happens there, or
HOW THE PRODUCTS CONNECT
Plan, Operate and Verify are available today. Optimize is planned and shown here so you can see the direction; it is not a current feature.
Define measures, participants, quotas and rules; try changes before approval.
Calculate earnings and prepare the cycle.
Check every calculation and approve it before anyone is paid.
Analytics on whether incentive spend worked, incentive budgets and territory design.
Quota and territory planning, what-if
Explore →OperationsLoad, calculate, check, approve and pay each cycle
Explore →Sales commissionsPlans, calculation, approvals and statements
Explore →Customer & vendor rebatesAgreements, accruals, claims, settlement
Explore →What each edition includes (Basic, Professional, Enterprise) is on Editions & pricing →
Ask RevexOne answers questions about plans and results using only the data the person asking is allowed to see. Agents, including outside AI tools connected through MCP, work under their own logins set up by an admin, with daily limits, and everything they do is tagged as theirs. By default an agent can read, prepare drafts and start runs that wait for a person; it cannot post or approve. A scheduled job’s first run is a test that posts nothing; after an admin reviews it, later runs may post on their own, and each posting names who allowed it. Paying people always needs a person’s approval, and payout checks flag unusual amounts for a person to clear or hold.
| Action | Person, by role | Agent default | Scheduled job after first-run review | Agent named by an admin |
|---|---|---|---|---|
| Read data | ✓ own access | ✓ its login’s scope | ✓ | ✓ |
| Prepare drafts (plans, adjustments, uploads) | ✓ | ✓ tagged as the agent’s | ✓ | ✓ |
| Start a calculation run | ✓ | ✓ result waits for a person | ✓ | ✓ |
| Submit for approval | ✓ | ✓ | ✓ | ✓ |
| Post results | ✓ within approval limits | — | ✓ after an admin approves its first, test run | Plannedonly record kinds the admin allows; can be taken back |
| Approve a payment | ✓ within limits | — | — | — always a person |
VERIFY WHAT MATTERS
Review supported permissions, exception handling, source evidence and operational procedures with the team. Available controls depend on the product release and implementation scope.
Discuss the review process and the evidence needed for your team.
Assess how source records and calculation explanations are presented.
Request verified information about hosting, access and support procedures.
NEXT STEP
Discuss how your plans, data and payout preparation fit the current product.