Sales Commission and Incentive Engine

The problem

Commission is calculated in a spreadsheet that one person owns, and everybody distrusts it. Standard Zoho CRM workflow rules can multiply a deal amount by a fixed percentage — and that is roughly where they stop. They cannot express a rate that steps up once a rep passes 80% of quota, a deal split three ways where the overlay specialist gets a different rate from the account executive, a clawback when a customer refunds in month two, a payout that only vests when Zoho Books actually records the payment, or a quarterly accelerator that depends on the whole team hitting target.

So the plan lives in a workbook. Reps rebuild it independently to check their own number. Disputes go to the CFO. When someone leaves mid-quarter nobody is sure what is owed. And the reason the workbook survives is not that it is good, it is that the CRM genuinely cannot represent the plan.

This engine is built to order against your actual plan documents. There is no generic download — ECOSIRE reads your comp plans, builds the calculation logic in Deluge, and installs it into your Zoho org.

What ECOSIRE builds

Plans as data, not as code you cannot read

Commission Plans, Plan Tiers, Quotas, Rate Cards and Plan Assignments are custom modules in Zoho CRM (or Creator records where the volume warrants it). A plan is configured, not hard-coded: effective dates, measurement period, basis, tier thresholds and rates, caps and floors are all editable by an authorised administrator without a developer. When your plan changes in January you change records, not scripts.

Every plan carries effective dating, so re-running a prior period uses the rates that were in force then, not today's.

The calculation engine

A set of Deluge custom functions computes commission per crediting event. It handles:

Tiered and accelerated rates — marginal tiers (each band paid at its own rate) or cliff tiers (the whole attainment paid at the achieved rate), because plans genuinely differ and getting this wrong changes payouts materially. Attainment is measured against a quota record for the rep and period.

Splits — a deal can be credited across multiple participants by percentage or by fixed amount, with different roles carrying different rate cards. Validation ensures splits total 100% before a deal can be marked closed-won, enforced through a Deluge validation on the Deal.

Basis selection — commission on revenue, on gross margin where cost data exists on the product line, or on a fixed value per unit. Margin-based plans read product cost from Zoho CRM Products or from Zoho Books items depending on where you maintain it.

Collection-based vesting — the common and important case. Commission is accrued on closed-won but only becomes payable when Zoho Books records payment against the invoice. A scheduled function polls the Books Invoices and Payments APIs, matches payments to the originating Deal, and moves accrued commission to payable in proportion to the amount collected. Partial payments vest partially.

Clawbacks — refunds, credit notes, cancellations within a defined window, or invoices that age beyond a defined days-past-due threshold reverse the corresponding commission. Reversals post as their own signed adjustment records rather than editing history, so a statement always reconciles.

Team and manager components — override commission on team attainment, and pool bonuses distributed by a defined rule.

Statements, approval and payout

Each period closes into a Commission Statement per participant: every crediting event, the plan and tier applied, the basis, the rate, the amount, the vesting state, and every adjustment. Reps see their own statement in a Zoho CRM Sigma widget or a Creator portal page — their own, and only their own, enforced by sharing rules and Deluge permission checks.

A dispute is raised against a specific line rather than by email. Statements move through review, approval and locked states; a locked statement cannot be silently recomputed, and any post-lock correction lands in the next period as a visible adjustment.

Approved payouts export in your payroll format, or create Bills in Zoho Books for commission paid to contractors, or post a journal entry for the accrual. Where you run Zoho People, statement approval can raise the corresponding payroll input record.

Auditability

Every calculation writes a record showing its inputs — the deal, the plan version, the tier hit, the attainment at the time, the rate, the FX rate if multi-currency — so any number on a statement can be explained a year later without rerunning anything. That property, more than any single feature, is what ends the spreadsheet.

Who it is for

Sales organisations of roughly five to two hundred quota-carrying people on Zoho CRM whose plans have real structure — tiers, splits, clawbacks or collection-based vesting. If everyone earns a flat percentage of closed revenue with no conditions, a CRM workflow rule already does that and you should not buy this.

How delivery works

Scoping call. Bring your actual comp plan documents and, ideally, one completed period's spreadsheet. We work through every clause, including the ones nobody has written down, and identify the ambiguities before they become disputes.

Fixed quote. Written scope covering plan types, modules, functions, statement design and integrations, with timeline and fixed price. Nothing is built until you approve it.

Build. Typically two to four weeks. Built in a sandbox or development environment against copied data — never calculated against live commission records.

Install in test, then production. We deploy to test and re-run one or two closed historical periods, then reconcile our output line by line against the spreadsheet you actually paid from. Every variance is explained before we go further — sometimes the variance is a bug in ours, and sometimes it is an error in the workbook. Production migration follows your sign-off.

Support. A defined post-go-live support window covering defects and plan-configuration adjustment, with administrator documentation and training so your operations team can change plans without calling us.