Commissions your sales lead can close without a spreadsheet
Invoices sync nightly from QuickBooks, get stamped with rep and territory, and close monthly in Salesforce against a runbook one person can run.
- Salesforce
- QuickBooks
The problem
Commissions lived in one spreadsheet. Every month meant exporting invoices, matching them to reps by memory, applying four plan types by hand, and hoping nobody asked how a number was reached.
What we built
A commissions engine inside Salesforce for a manufacturer with a dealer network. Invoices sync nightly, each is attributed to a rep and territory, a monthly freeze locks the period, four plan types calculate in the org, and a one-page runbook lets the sales lead close alone.
No AI in this build. Here's why that was right: commission rules are contracts. They need to be exact, explainable, and identical every month.
Invoice sync, rep and territory stamping, plan calculation, the accrual freeze, a parallel run against the old spreadsheet until the two matched, and a watchdog. Every payout traces back to an invoice.
Outcome
Attribution went from 15 percent to 90 percent of the year's revenue in one day, and the first close tied to the sales lead's spreadsheet rep-for-rep.
Who this fits
- Commissioned sales orgs closing the month in a spreadsheet
- Finance teams who can't trace a payout back to an invoice
- Companies with more than one plan type and more than one person who can explain them