Most teams are live on Prowi in about two weeks. What decides the timeline is rarely the software. It is how quickly you can write down your commission rules, give access to the data the plans pay on, and check one period you have already paid. This guide answers the questions buyers ask before they sign: how long an implementation takes, how much effort it needs from finance, sales and IT, and what to prepare.
How long should a commission software implementation take?
For a sales team with one CRM and written commission plans, about two weeks from kickoff to go-live is a realistic target, and it is what most Prowi customers see. It takes longer when the rules exist only in a spreadsheet or in someone's head, when the numbers a plan pays on live outside the CRM, or when several companies, countries or currencies are involved.
Ask any vendor what "live" means. A useful definition: reps can see their statements, and one real period has been calculated, approved and passed on to payroll. Anything before that is a demo with your data.
Week-by-week implementation timeline
The table shows a typical two-week plan. The stages overlap in practice, and the order matters more than the exact days.
| When | What happens | Who is involved on your side |
|---|---|---|
| Before kickoff | Collect the written plans, a list of everyone who gets paid, the last paid statements and the access details for your systems | Sales leader, finance |
| Week 1, days 1 to 2 | Kickoff. Walk through every plan and write each rule down in plain words, including the edge cases: what counts as closed, which date decides the period, splits and clawbacks. Sign off the written version | Sales leader or plan owner |
| Week 1, days 3 to 5 | Connect the CRM and, if needed, the accounting or billing system. Choose the fields the plans need. Check that a closed period has the same number of deals and the same total as the source | CRM admin |
| Week 2, days 1 to 3 | Set up people, teams, plans and the approval chain. Calculate a past period | Plan owner, for questions |
| Week 2, days 4 to 5 | Compare the calculated period with what you actually paid and explain every difference. Give reps access | Finance, sales leader |
| First period close | Statements move to awaiting approval, are approved and go on to payroll | Approvers, payroll |
The one step not to skip is the written sign-off on the rules before anything is built. Building on a guess, sending numbers, hearing they are wrong and starting over is what turns two weeks into two months.
How much implementation effort should finance expect?
Finance mainly supplies data and checks results. It provides the last paid period, the payroll format and wage codes, and reviews the comparison between what was paid and what the system calculates. Most of the setup questions go to whoever owns the commission rules, usually the sales leader.
| Role | What they do | When |
|---|---|---|
| Sales leader or plan owner | Explains the plans, signs off the written rules, answers questions that come up during setup | Weeks 1 and 2 |
| Finance | Provides the last paid statements or spreadsheet, reviews the comparison, usually becomes an approver | Week 2 and every period close |
| CRM admin | Grants access, explains what the fields mean, fixes gaps such as missing owners or close dates | Week 1 |
| HR or payroll | Confirms wage codes and how approved commission should arrive in payroll | Before the first payout |
| Reps | Open the app, check their first statement and flag anything missing | Go-live |
IT is rarely needed beyond the CRM admin, because the integrations are set up by granting access, not by building anything.
What do you need to prepare before implementation?
Prepare the rules, the people and the data. If you can hand over the items below at kickoff, the two-week timeline is realistic.
- Every commission plan in writing, in the version the reps signed. If you do not have one, start from a commission plan template.
- Everyone who gets paid, with their manager, the person who approves their commission and a fallback approver for holidays.
- The last paid statements or spreadsheet, ideally a full quarter, because quarterly targets, caps and tiers only show their behaviour over a full cycle.
- For each number a plan uses, the system and field that holds it: deal value in the CRM, invoiced revenue in accounting, recurring revenue in billing.
- Access to the CRM and accounting system, or the name of the person who can grant it.
- Payroll details: which system you use, the wage codes for commission and bonus, and who receives the payroll file.
- Known edge cases: deals that reopen, cancellations, credit notes, reps who change team mid-period.
Unsure whether your plan is ready to be automated? The free commission plan health check scores clarity, rules, process and data in a few minutes.
How do I set up data integrations when moving off spreadsheet commissions?
Start from the plan, not from the CRM. List every number the plan pays on, find the system and field that holds it, connect those systems, and then prove the data by checking one closed period against the source. Import only what the plans need.
CRM: deals, owners and close dates
Prowi reads won deals from HubSpot, Pipedrive, Salesforce, Podio and Microsoft Dynamics 365. Before connecting, decide which pipeline and stage count as won, which date decides the period, which field holds the amount, and how a deal owner in the CRM maps to a person on a plan.
Accounting and billing: invoices and recurring revenue
If commission is paid on invoiced revenue, margin or payment rather than on the deal, connect the accounting or billing system too. Prowi has integrations with e-conomic, Dinero and Fenerum.
Payroll: getting approved commission paid
When a statement is approved, the amount is added to the rep's balance in Prowi and passed on to payroll. With Zenegy, Prowi pushes it directly. For Danløn, Visma Dataløn, Lessorløn and Visma Enterprise, Prowi produces a payroll file that is imported into the payroll system.
Systems without an integration
If a system is not on the list, its data can still be loaded into Prowi as a CSV file. That works well for data that changes once a month, such as targets or a list of active customers.
| Data | Typical source | What to decide |
|---|---|---|
| Won deals | CRM | Which stage counts as won, which date decides the period, which field holds the amount |
| Deal owner and splits | CRM | How owners map to people, and where a shared deal's split is stored |
| Invoices and credit notes | Accounting | Whether commission follows the deal, the invoice or the payment, and how a credit note reduces it |
| Subscriptions | Billing | Whether commission is based on MRR or ARR, and what counts as churn |
| Wage codes | Payroll | Which code each type of pay goes to, and the file format |
Before anyone relies on the numbers, check one closed period: the same number of deals and the same total in the source and in the system. Differences usually come from deals in another pipeline, a missing owner or a missing date.
What is the implementation effort for complex splits and clawbacks?
The effort sits in writing the rules precisely and in having the data that triggers them, not in the software. A split needs to know who shares a deal and by how much. A clawback needs to know which event triggers it, how far back it reaches and how the amount is deducted.
Splits
Write down who can share a deal, whether shares are fixed or depend on the role, and whether an overlay role such as a specialist is paid on top or out of the same pool. Then make sure the CRM holds that information on the deal, for example as a second owner field or a percentage field. A split agreed in a hallway cannot be automated. The split commission calculator is a quick way to test a rule before you write it into the plan, and the glossary explains split commission and crediting rules.
Clawbacks and retroactive adjustments
Write down what triggers a clawback (a cancellation, a credit note, a customer who never pays), the window in which it applies, how it is deducted, any limit per period, and what happens if the rep has left. In Prowi, when a deal changes after payday, the old period is recalculated with the rules that applied then, and the difference is applied to the next open statement. You can see how that works in the clawback and correction calculator, and the clawback guide covers the rules to put in the agreement.
What happens during onboarding and go-live?
Onboarding moves through the same steps whichever system you choose: agree the rules in writing, connect the data, build the plans, check a period you have already paid, and then run one real period through approval and payroll.
- Kickoff. Name who decides how commission works, who will run the system day to day, who owns the CRM and who receives the payroll file.
- Rules signed off. Each plan is written in plain words and approved by the person who owns it.
- Data connected and checked. A closed period matches the source.
- Plans built. People, teams, plans and approvers are set up, and a past period calculates without errors.
- Checked against a paid period. Every difference is explained. It is either a rule that was misunderstood, a field that means something else, a timing difference, or an error in the old spreadsheet.
- Go-live. Reps get access. Each rep's statement updates live through the period. When the period closes, it moves to awaiting approval, and once approved, the amount is added to the rep's balance and passed on to payroll.
How do you avoid commission disputes during go-live?
Disputes at go-live come from surprises, so remove them. Check the numbers against a paid period before reps see anything. Give reps access before the first period closes, so a missing deal is flagged while it can still be fixed. Explain in advance where the new numbers will differ from the old spreadsheet and why. And let the approval flow do its job: a statement awaiting approval is the place to raise an objection, before the amount reaches payroll. The guide to avoiding commission disputes has more on the process.
What usually slows an implementation down?
| What slows it down | How to avoid it |
|---|---|
| Rules that are not written down | Write and sign off every plan before setup starts |
| A number the plan pays on lives outside the CRM | Map every number to a system before you sign, not during setup |
| No approver, or the only approver is away | Name an approver and a fallback for every plan |
| The CRM changes during setup, for example a new pipeline | Freeze the structure for two weeks, or tell the vendor first |
| Redesigning the plan while migrating | Move the current plan first and change it later. See rolling out a new commission plan |
What to read next
If you are still choosing between tools, read commission calculator vs commission management system. To work out whether the switch pays off, see how to calculate commission software ROI. And for the errors an implementation should remove, see why commission is calculated wrong. The commission management page shows the whole flow from CRM to payroll.
FAQ
Can we implement commission software in the middle of the year?
Yes. Start at a period boundary, such as the first of a month or quarter, and move the plan you already have. Plan changes are easier to introduce at the start of a new plan year.
Do we need our IT department?
Usually not. The CRM admin grants access and explains the fields. Integrations are set up by connecting accounts, not by writing code.
Should we keep the spreadsheet running in parallel?
Run one paid period in both and compare the results person by person. Once every difference is explained, the spreadsheet can go.
What if our CRM or payroll system has no integration?
Data can be loaded as a CSV file, and approved commission can go to payroll as a file. Check the list of live integrations before you sign.
How do we know the numbers are right?
Calculate a period you have already paid and compare it with what each rep actually received. A difference is either a rule, a field, a timing issue or an old error, and each one should be written down and resolved before go-live.
Want to see what a two-week implementation looks like with your own plans? Book a demo.