Commission logic built for how sales actually happens
Multi-basis rules, four tiering models, hierarchy rollup, and full settlement-to-vendor-bill remittance — one policy engine for Sales Order, invoice, and payment triggers.
Commission logic is rarely simple — it depends on product, category, margin, discount level, target attainment, and where a rep sits in the org chart. Trigger-only apps compute a number and stop there, leaving approval, settlement, and refund reversals to spreadsheets while finance reconciles payouts by hand every pay period.
A single policy engine matches rules by product, category, customer, or margin; supports flat, percentage, amount-range, and target-attainment tiers; rolls earnings up an approval hierarchy; and carries every entry from draft through approval, settlement, and vendor-bill remittance — with reversal handling built in for refunds.
A complete commission engine, not a calculator
Every capability below is implemented in the module.
Multi-Basis Rule Engine
Trigger commission on order confirmation, invoice validation, or customer payment. Compute on net revenue, tax-included total, or profit margin.
Four Computation Models
Mix percentage, fixed-amount, amount-range tiers, and target-attainment tiers within a single rule set, per rule.
Margin Floor & Discount Ceiling
Set a minimum margin percent below which a line earns nothing, and a maximum discount above which commission is voided.
Sales Targets & Attainment
Monthly, quarterly, annual, or custom targets per salesperson or team, with live attainment progress bars.
Multi-Level Hierarchy Rollup
A configurable percentage of a rep's earned commission automatically rolls up to their manager on every policy.
Approval Workflow & Ledger
Every earned amount lands in an auditable ledger and moves draft → confirmed → approved → settled → paid with full chatter history.
Refund & Reversal Handling
Crediting an invoice automatically creates a negative counter-entry, so chargebacks stay in sync with the ledger.
Settlement & Vendor-Bill Remittance
Collect approved entries into a settlement, lock the period, and generate a vendor bill ready to post — for employees and external agents alike.
Leaderboards & Live Preview
Pivot and graph views rank reps by commission earned, and a live estimated-commission field sits right on the sale order.
How it works
Configure policies
Define policies with rules scoped by product, category, or customer, a computation model, tiers, and guard limits.
Sales happen
As orders are confirmed, invoices validated, or payments registered, the engine matches the right policy and rule.
Entries post automatically
Commission entries land in the ledger in draft, ready for the rep to confirm and a manager to approve.
Settle and pay
Approved entries are collected into a settlement, locked for the period, and remitted as a vendor bill.
See it in action
From policy configuration to settlement, every screen in the commission workflow.
Two active policies at a glance — trigger, base, and rule count visible right from the kanban.
A policy's Rules tab: percentage, tiered, and fixed-amount rules stacked in one plan, plus scope and guard settings.
Every earned entry in one ledger — amount, policy, and state badge on each row.
A single entry's full trail: policy, rule, base amount, and earned commission.
Pivot view breaking down commission earned by salesperson and rule.
The same data as a bar-chart leaderboard for a quick performance read.
Target cards with live attainment progress bars per rep.
List view surfaces target amount, achieved amount, and attainment percent side by side.
Settlement batches with totals and state, ready for approval and payout.
A collected settlement showing its member entries and total before it is locked and billed.
Right inside the sale order: an estimated commission field and a smart button straight to the rep's entries.
Frequently asked
Does this replace Odoo's native commission features?
It goes well beyond the built-in basics. On top of configurable SO, invoice, and payment triggers, you get four tiering models, margin and discount guards, hierarchy rollup, targets with attainment dashboards, an approval workflow, and settlement-to-vendor-bill remittance in one policy engine.
Can commission depend on profit margin, not just revenue?
Yes. A policy can compute on net revenue, tax-included total, or profit margin, and every policy can enforce a minimum-margin floor so deeply discounted deals earn nothing.
How are refunds and returns handled?
Crediting an invoice automatically creates a negative counter-entry linked back to the original, so the ledger always reflects the net amount actually owed.
How do commissions actually get paid out?
Approved entries are collected into a settlement batch for a date range, locked to prevent retroactive changes, and remitted with a single vendor bill covering employees and external agents alike.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
A multi-basis Sales Order, invoice, and payment commission engine with tiered rules, hierarchy rollup, settlement workflow, and vendor-bill remittance for Odoo 19.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Sales (sale_management) |
| Lines of code | 1472 |
| Technical Name |
cerevantix_advanced_sales_commission |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module