| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 67 |
| Technical Name |
amadio_sales_commission_tracker |
| License | OPL-1 |
| Website | https://amadio.io |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 67 |
| Technical Name |
amadio_sales_commission_tracker |
| License | OPL-1 |
| Website | https://amadio.io |
Sales Commission Tracker
Configure commission rules by rep, team, product category, or customer — auto-calculate commissions on paid invoices and manage monthly statements through approval to payment.
The Challenge
Why organizations need Sales Commission Tracker
Without a transparent, rules-based system, sales reps don't trust commission calculations. Disputes consume management time and damage motivation.
Finance calculates commissions in Excel every month — matching invoices to reps, applying rates, handling exceptions manually. It takes days and errors happen.
When a rep questions their commission, there's no system record showing exactly which invoices contributed, at what rate, and who approved the statement.
What Sales Commission Tracker Does
Six capabilities built specifically for this problem
Flexible Commission Rules
Commission plans support rules by sales rep, team, product category, minimum order amount, and calculation basis (invoiced or paid) — any combination your business requires.
Paid-Invoice Trigger
Commissions calculate on invoice payment — not invoicing — eliminating commission payments on uncollected revenue. The trigger is automatic and audit-logged.
Monthly Statements
The monthly cron generates commission.statement records per active rep — listing every qualifying invoice, amount, rate, and commission line for full transparency.
Approval Workflow
Statements move through Submit → Approve → Mark Paid. Each state change is date-stamped with the acting user — creating a clean approval audit trail.
Rep Notifications
Reps receive automatic email notifications when their statement is generated and when it's approved — keeping them informed throughout the process.
Payroll Export
Approved statements can be exported for payroll processing — providing the net commission amount per rep in a format ready for your payroll system.
How It Works
Operational in minutes — not weeks
Define Commission Plans
Go to Sales → Commission Plans → New. Create rules specifying rep/category/amount conditions and the applicable rate. Assign plans to sales reps.
Statements Generate Monthly
At month end, the cron job creates statements for all active reps — calculating commissions on payments received during the period.
Review, Approve, Pay
Reps review their statements. Sales managers approve. Finance marks as paid after payroll processing. Every step is timestamped and logged.
Perfect For
Industries and organizations that rely on Sales Commission Tracker
Sales-Driven Organizations
Any B2B business with a commissioned sales force — technology, manufacturing, distribution, professional services — benefits from a transparent, automated commission system.
Multi-Rep Teams
Sales teams with complex commission structures (tiered rates, team commissions, category-specific rates) need a rules engine that handles complexity without spreadsheet gymnastics.
Multi-Currency Operations
International sales teams with commissions in different currencies need a commission system that handles multi-currency invoicing correctly.
Technical Specifications
Compatibility and deployment details
| Odoo Version | 18.0 |
|---|---|
| Platform | Odoo.sh & On-Premise |
| License | OPL-1 |
| Author | AMADIO |
| Support | info@amadio.io |
| Website | amadio.io |
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