Commissions
Partner commission accounting for MSPs who resell Solidlio: what you earn on the clients you bring in, what you owe in platform fees, and one netted payout.
The problem
You have been putting clients onto the platform for eighteen months and you have no idea what you are owed. The rate was agreed in an email. The number arrives as a figure on a remittance advice with no working shown, so when it looks light there is nothing to check it against — you raise it in a thread, someone goes through a spreadsheet, and three weeks later you get a different number and no explanation of which one was wrong.
Meanwhile the fees run the other way. Your support-package sales carry a platform cut, your escalation work carries another, and those land somewhere else entirely. Reconciling the two directions is a manual exercise you do once a quarter and never quite finish.
What Solidlio does about it
Every commission is booked against a rule — a rate, an optional fixed amount, optional per-transaction floor and ceiling, a scope and a date window — and the earning stores the whole calculation, not just the total. You can see that a $200.00 subscription produced $25.00 because a 12.5% rule applied, and which rule that was. Rates are set by Solidlio and shown to you read-only, because a partner setting its own rate is not a rate. Approved earnings batch into a payout for a period; platform fees you owe for that same period are netted off before it is paid. If a figure is wrong you contest that specific earning, and the dispute carries a reason, a priority and a recorded resolution.
Capabilities
| Capability | What it does |
|---|---|
| Rule-driven accrual | Books each commission against a named rule: percentage rate, fixed amount per sale, floor, ceiling, scope, effective dates. |
| Auditable arithmetic | Stores base amount, rate, percentage amount, fixed amount and total on every earning, so the partner can recompute the figure. |
| Per-transaction caps | Applies a minimum and a maximum per sale, and records which cap moved the number. |
| Dated terms | A rule added later supersedes an older one automatically; historic sales keep the terms that were live on the day. |
| Scoped rules | Targets specific tiers or product categories, with scoped rules beating blanket rules. |
| Approval before payment | Every earning is approved by a platform administrator before it can enter a payout batch. |
| Period settlement | Batches every approved unpaid earning for an account and a date range into one payout with a payment method and reference. |
| Fee netting | Subtracts pending platform fees from approved commissions to give the amount actually payable for a period. |
| Earning-level disputes | One open dispute per earning, with LOW/MEDIUM/HIGH/URGENT priority and a recorded resolution, resolver and timestamp. |
| AI dispute triage | Assesses legitimacy from the earning, the rule and the account’s dispute history; drafts a reply in one of three tones. |
| Read-only partner view | Shows an MSP its earnings, payouts, net payout and the exact terms that will apply to its next sale — and nothing it can edit. |
| CSV and PDF reporting | Exports earnings, payouts or rules, filtered by account, status and date, as a spreadsheet or a branded PDF document. |
Built for MSPs and their clients
A managed client is a separate Account with its own books. Commissions sit between Solidlio and the MSP, and never touch the client’s ledger.
| MSP | Solidlio (platform) | |
|---|---|---|
| Commission terms | Reads the rate, caps and dates that will apply to its next sale. | Authors the rule. Terms are negotiated, not self-served. |
| Earnings | Sees its own, with the full calculation and the rule behind it. | Sees all accounts’, approves each one before it becomes payable. |
| Payouts | Sees its own history and the payment reference. | Creates the batch and records the settlement. |
| Marking paid | Not permitted — settling your own commission is self-dealing. | Platform administrators only. |
| Disputes | Opens one against a specific earning with a written reason. | Sets priority, triages, resolves or rejects, records the outcome. |
| Platform fees | Sees the outstanding balance that will be netted off its payout. | Records and settles fees; nets them against the payout. |
Access is floored at MSP administrator. Commission figures are revenue-bearing, so an MSP technician does not see the firm’s ledger — and the navigation reflects that rather than offering a link that is then refused.
How it works
- Terms are set. A platform administrator creates a rule against the MSP’s account: a rate as a decimal fraction, optional fixed amount, optional floor and ceiling, and the date it takes effect.
- A client subscribes. An MSP’s managed client moves onto a paid plan, either through a plan upgrade or a plan sold from the MSP portal.
- The commission is booked. The engine picks the rule that governs that sale — most specific first, latest effective date wins — applies it, and writes an earning in
PENDINGwith the full arithmetic and the rule id. - It is approved. A platform administrator reviews the base amount, the rate applied and the resulting figure, and approves it.
- A period is settled. Every approved unpaid earning in the window batches into one payout. Platform fees owed for the same period are netted off.
- The payout is processed. Payment method, reference and a settlement note are recorded, and every earning in the batch flips to
PAID. - Anything contested is disputed. The MSP raises a dispute against the specific earning; the platform triages, resolves and records the outcome.
Compliance and audit
Every administrative action writes a platform audit log entry with the actor’s person id and email, the resource type and id, and the before and after state: rule creation and update, earning approval, payout creation and processing, dispute creation and update, platform fee creation and settlement.
The reconstruction that matters to a partner is available without an audit query: an earning permanently records its base amount, the rate applied, the percentage and fixed components, the total, and the rule it was calculated under. Editing a rule never rewrites a booked earning — the figure you were paid last March still shows the terms that were live last March.
Dispute resolutions record the resolving administrator and the resolution timestamp. AI triage output is stored on the dispute with the time it was generated, so a decision informed by an assessment can be traced back to that assessment.
Editions
Commission earning is a paid-plan capability of the MSP’s own Solidlio plan.
| Capability | Free | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|---|
| Earn commission on client subs | — | ● | ● | ● | ● |
| Commission ledger and payouts | — | ● | ● | ● | ● |
| Effective-terms visibility | — | ● | ● | ● | ● |
| Earning-level disputes | — | ● | ● | ● | ● |
An MSP on the Free plan does not accrue commissions. Rule authoring, approval, payouts, platform fees and AI triage are platform-administrator functions and are not sold as plan features.
AI triage, response drafting, rule recommendation and quick categorisation consume the account’s AI credit allowance and are refused once that allowance is exhausted.
A commission figure you can check is a commission figure you can trust.