Sales Commission Management for ERPNext

ECOSIRE builds a proper Frappe app — sales_commission_management, a real installable app with its own module, not a pile of loose customisations — that gives ERPNext a first-class commission engine. At the centre are new DocTypes: a Commission Plan (the rule set), Commission Rule child rows (per Item, per Item Group, or per Customer Group, each with its own rate and basis), Commission Slab rows for target-based tiers, and a Commission Entry ledger that records every calculated payout with a link back to the source Sales Invoice or Sales Order. Splits are modelled as a child table of contributors with weightings that must sum to 100%, so a single sale can pay multiple reps and their managers from one document.

Calculation is driven server-side through hooks.py document events. On Sales Invoice (or Sales Order, per your scope) on_submit, a server script walks each line item, matches it to the applicable rule, resolves the rate — flat, tiered against the rep's period-to-date attainment, or profit-based using item valuation for margin — applies any split weightings, and writes immutable Commission Entry rows in draft state. A scheduled event (scheduler_events in hooks.py) runs nightly or monthly to roll individual entries into period accruals and recompute slab attainment as new invoices land. Nothing is paid until a reviewer moves entries through a Frappe workflow (Draft → Pending Approval → Approved → Paid), and every state change is captured in the standard ERPNext audit trail. Whitelisted methods expose the numbers to the Frappe REST API so a rep portal, Power BI, or payroll integration can pull live commission balances, and role profiles keep reps scoped to their own entries while managers see the team.

Because this is built to your commission policy rather than a generic template, delivery is build-to-order. We start with a short scoping call, confirm the exact rules — rate tables, slab thresholds, profit vs net basis, split logic, approval chain — in a written specification, then build, test on a staging bench, and run UAT with your data before go-live. Typical delivery is 2–4 weeks from confirmed scope depending on rule complexity, and you receive the full source in a git repository so nothing is locked to us. The app targets Frappe/ERPNext v15 and v16 and is written to Frappe app conventions so it survives bench update cleanly.