Commission statements for building-supply dealers.
Lunica computes each rep’s commission from invoiced gross profit under your plan and drafts the statement; your controller approves it.
Sales & estimatingUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
| Rep | Invoiced GP | Rate | Commission | Status |
|---|---|---|---|---|
| Mike Brennan | $71,420 | 8% · splits applied | $5,713.60 | 1 dispute |
| Counter · Main St | $48,310 | 6% | $2,898.60 | Ready |
| Counter · Route 9 | $39,890 | 6% | $2,393.40 | Ready |
| House accounts | $24,640 | 0% | $0.00 | Excluded by plan |
Invoiced gross profit from your ERP, net of returns, under the plan. One dispute waiting.
The problem.
Commissions at a dealer are a spreadsheet the controller builds on the third of the month from the sales-by-rep report in your ERP, with a column for the split on one job, a row deleted for the house account, and a note about the return that came back after the statement went out. A paid-only plan means waiting on the cash receipts too.
Every rep checks the number against their own list, and the ones that disagree come to the controller’s door. The dispute is about a ticket from six weeks ago that nobody can find the split agreement for. The plan that was supposed to drive behavior is a monthly argument instead.
How it works.
- 1
The plan is written down once
Rates by category or account, splits by job, house accounts, what happens on a return, whether commission is earned at invoice or at payment. A spec your controller edits in plain English, with history and revert.
- 2
Every ticket, computed
Each invoice from your ERP with its cost and gross profit, assigned to the rep on the ticket or the split on the job, with returns and credits netted in the month they hit and paid-only plans waiting on cash. The arithmetic is from your ERP; a model is not involved.
- 3
A statement per rep, drafted
The month’s commission with every ticket behind it: invoice, customer, gross profit, rule, rate, amount. A rep opens their statement and sees the ticket, not a total. The controller sees all of them before anyone else does.
- 4
Disputes to the controller, who approves
A rep flags a ticket with a sentence. It lands on the controller with the plan rule beside it. The controller decides, approves the statement, and the payroll figure goes to your payroll system, or to your ERP keyed by your team.
How it connects to your ERP.
Lunica reads invoiced tickets, credits, cost and the customer file through its database or data warehouse, under an account that can only read: sold price and cost per line, the rep and job on each ticket, returns and credit memos, and cash receipts where the plan is paid-only. Splits and house accounts come from the plan spec and the customer file.
Nothing lands in your ERP without a person and nothing is sent on its own. Statements go to reps when the controller releases them. The approved figures go to payroll or back to your ERP as an import file where your ERP takes one, or keyed by your team from what Lunica prepared; Lunica does not post a journal entry or a payroll line itself.
What a week looks like.
- Every rep’s commission on the first, with every ticket behind it.
- Splits, house accounts and returns handled the way the plan says, every month.
- Disputes that point at a ticket and a rule, not at a spreadsheet.
- A controller who approves statements instead of building them.
Questions
Does it write to your ERP?
No. It reads invoices, cost and receipts. The approved figures go to payroll or are keyed into your ERP by your team.
Does it pay anyone?
No. It computes and drafts. The controller approves, and payroll runs where you run it.
What about paid-only plans?
Commission on an invoice is held until cash is applied in your ERP, and shows on the statement as earned but not yet payable, with the invoice and its balance.
How are splits handled?
By job or account in the plan spec: fifty-fifty on one job, seventy-thirty on a handed-off account, whatever was agreed. A split is written down once and applied every month until it is changed.
What if a rep disagrees?
They flag the ticket from their statement with a sentence. It lands on the controller with the plan rule beside it. The decision is logged against the ticket.
Can reps see each other’s statements?
No. Each rep sees their own. The controller sees all of them.
Available for.
Each version is written in that system’s own terms: its screens, its files, its codes.
Own your AI. Own your software.
Thirty minutes with the people who build it. Bring your ERP.