Salesperson configuration and commissions in Business Central

Business Central has built-in salesperson / purchaser master records and a basic commission calculation tied to them. The functionality covers simple flat-percentage commissions cleanly; complex incentive compensation needs an external tool.

The salesperson master. A salesperson / purchaser code is a Dataverse-like record representing an internal salesperson or buyer. Each carries:

• Code — short identifier.
• Name — human-readable.
• Commission % — flat percentage for simple commission calculation.
• Email — for routing notifications.
• Team / Phone / Job Title — operational fields.
• Dimension defaults — financial dimensions to attach to transactions where this salesperson is involved.

The salesperson code is not a Microsoft 365 user account — it's a sales-team-role record. A salesperson can map to a user account through configuration, but doesn't have to.

Assignment to customers. Each customer card has a Salesperson Code field — the default salesperson responsible for that customer. New sales documents (quotes, orders, invoices) default the salesperson from the customer; users can override at the line level if needed.

Per-document overrides. Documents can carry a salesperson different from the customer's default — useful for splits, joint sales, internal handovers. Each posted document records the salesperson at posting time, locked for audit.

Commission calculation. The basic approach:

• Each salesperson has a flat Commission %.
• Posted sales documents accumulate commission based on the salesperson code and the percentage.
• The Salesperson Statistics view shows commission earned per period.
• Commission amounts can be posted to GL accounts through the General Posting Setup.

Limits. Real-world commission schemes are usually more complex:

• Tiered rates — different % at different revenue bands.
• Product-specific rates — higher commission on strategic products.
• Margin-based commission — commission as % of gross margin, not revenue.
• Splits — multiple salespeople sharing a deal at configured percentages.
• Accelerators — commission rates increase above quota attainment.
• SPIFs (Sales Performance Incentive Funds) — one-time bonuses for specific products / campaigns.
• Clawbacks — commission reversed if the customer doesn't pay or returns goods.
• Multi-currency — different rates per region or currency.
• New-vs-renewal — different rates for new business vs renewal.

The built-in BC commission engine handles none of this beyond the flat percentage. For complex schemes, the options are:

1. External commission engines integrated with BC — Spiff, Performio, CaptivateIQ, Iconixx, regional ISVs. These pull sales data from BC and compute commission externally; payouts feed back to payroll or AP.
2. Custom AL extensions — for moderate-complexity schemes that don't justify external tools.
3. Excel models outside BC — for small organisations where formality isn't worth the tool cost.

Multi-salesperson allocation. Some businesses split sales between two salespeople (inside seller, field seller, or by territory ownership). BC's built-in supports a single salesperson per document; splits typically use custom fields and reporting logic in Power BI.

Reporting. Salesperson-keyed reports cover:

• Revenue by salesperson.
• Margin by salesperson.
• Open opportunities (if using BC's Relationships module).
• Commission earned (basic flat-rate calculation).

Power BI dashboards extend with team views, attainment-vs-quota, trend analysis.

Operational reality. For very simple commission schemes (single flat rate, no splits, no tiers), the BC built-in suffices. The moment the scheme has tiers, products, or splits, plan for an external commission engine. Trying to bend BC's flat percentage into complex logic creates fragile customisations.