These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Commission Calculation
- Features
- Review evidence
Review evidence
Review Decisions records an approved, rejected or returned decision against a plan, run, statement or schedule. Calculation Receipts records the outcome of the configured plan approval and run Advance actions, including skipped attempts. Record Attachments holds supporting files and their upload attribution. Together these records help the team reconstruct who acted, what record was involved and what result followed.
OverviewCalculation Exceptions×
Commission Calculation · Review evidence
New
Calculation Exceptions
Review decisions
| Decision number | Subject type | Subject reference | Decision | Reason code | Reviewer | |
|---|---|---|---|---|---|---|
| RD-56893 | Plan | Plan rd-214 | Returned | Approved as Submitted | RPS-18606 | |
| RD-13007 | Plan Line | Plan Line rd-430 | Returned | Amount Variance | RPS-70862 | |
| RD-95709 | Revenue Schedule | Revenue Schedule rd-326 | Returned | Missing Documentation | RPS-25978 | |
| RD-50458 | Billing Run | Billing Run rd-161 | Returned | Revenue Policy | RPS-36464 | |
| RD-30574 | Invoice | Invoice rd-637 | Returned | Terms Mismatch | RPS-36181 |
6 of 6 records
Plan rd-214Review decisions · RD-56893
PlanDecisionReturned
Reason codeApproved as Submitted
ReviewerRPS-18606
Decided at21 Oct
What you can do
Separate decisions from action results
A Review Decision identifies a person and the subject they reviewed. A Calculation Receipt records what happened when someone used Approve Plan or Advance. Finance Leadership can use both records to confirm an approved plan; Billing Operations uses the receipt to confirm a run transition. A Skipped result is an attempted action, so inspect the related record before assuming its status changed.
Keep an attachment tied to the exact parent record and uploader. When Revenue Accounting investigates a held schedule, its reason and supporting file should point to the same booking context. A later reviewer can then distinguish the source document from the human decision about it.
How the work is organized
- Human decision. Keep the reviewer, subject, reason and date on the decision record.
- Action result. Read the operation type and result on a receipt before claiming that a transition succeeded.
- Supporting file. Attach the relevant document with its parent reference, kind and uploader.
What to agree during setup
Agree which documents must accompany a plan approval, schedule hold or payout question. Use a consistent parent table and record reference convention so an attachment can be found later. Finance Leadership should make its own plan decision; the person preparing the plan supplies the context. Billing Operations should check receipts after each run action, especially when the action is skipped. Decide who resolves returned and rejected decisions and how that follow-up is recorded. Keep the original reason available when a corrected record returns for review.
Check the handoff on an actual case
A plan enters in review with an approval memo attached. Finance Leadership inspects its components and approves it. The team checks the Review Decision and Calculation Receipt for the plan. A repeated Approve Plan attempt creates a skipped result; that receipt should not be read as another approval. In the same period, a run is advanced from Draft to Validated. Billing Operations checks its successful receipt before continuing. Separately, a schedule on Hold has a returned decision with a reason. Revenue Accounting follows that exception and its supporting file. A reviewer can see which record was decided, who made the decision, and whether a configured action actually changed status.
What your team sees
- Calculation Exceptions — Rejected or returned decisions requiring follow-up.
- Comp Plans Awaiting Approval — The plan queue that needs a finance decision.
Follow the work through
Read plan review and run cycle.
What it keeps track of
Data model- Review decisions
- Approval and exception decisions recorded against a plan, calculation run, statement or schedule.
- Calculation receipts
- Immutable operation log of commission events: what ran, on which record, when, by whom and with what result.
- Record attachments
- Supporting documents attached to a commission record, such as order forms, approval memos and payout advice.
- Comp plans
- Sales compensation plans defining the quota target, period, owner and approval status for a rep or team.
- Calculation runs
- A commission calculation cycle for a period: which statements are ready, blocked or need attention before payout.
- Commission statements
- Statement issued to a payee for a period, carrying the commission total, payout status and balance owing.
- Commission schedules
- Earning schedules that spread booked revenue credit across a term so commission accrues correctly each period.
Who uses it
Permissions- Finance Leadership
- Approves plans.
- Billing Operations
- Checks run receipts.
- Revenue Accounting
- Handles schedule exceptions.
- Admin
- Manages attachment conventions.
Set up Commission Calculation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.