When is custom sales commission software worth it?

A shared client, with the split recorded outside the program

Say the company's standard plan gives commission to the person who manages the client. One client, though, is served jointly. The company agreed that in the current period commission on its sales is split between two named reps by an agreed share. The program in use still runs the standard rule, so someone in finance recalculates this case in a spreadsheet.

Before you order an app, establish why this particular split stayed outside the system. Maybe nobody has configured the right rule yet. Or information about the joint account may be missing from the data taken from the CRM. Only checking this with the administrator or the vendor will show whether a new feature is needed.

If the agreed exception were part of the calculation, the finance person would not have to correct the standard rule's result each time. The sale would record whom the split concerns and for what period it applies. A rep could open their line and see that the result reflects the joint account. The explanation would lead to the specific sale and agreement, so nobody would have to rebuild it from comments in a spreadsheet.

The app therefore needs more than a field for typing in a corrected total. It has to apply the agreed split to later sales covered by the exception, and let you check how it reached the result. The company still sets the commission rules and approves their changes. The software project turns them into working calculations.

If the calculation itself works, and the problem is explaining differences in a finished statement, the separate article on reconciling sales commissions will help. Here, the decision is about the tool that should calculate the commissions.

What happens when the sales commission plan changes

In the next period, the company may end the joint account and go back to the standard rule. New calculations should use the new arrangements. The person reviewing an earlier settlement still needs to see the split that applied then, and the sales data used to calculate it.

This matters when you design your own system: recording only the result is not enough if, in a few months, someone has to rebuild where it came from. The settlement has to keep the version of the rules applied and the data it worked on. The client's current assignment in the CRM may already differ from the month being settled.

If an older sale has to be corrected later, an employee should be able to show what changed and why. The earlier calculation and the correction have to stay linked. Otherwise the rep sees a new result with no explanation, and finance goes looking for answers in old copies of the spreadsheet. The company sets the rules for making such corrections; the app should let you apply them and read their history.

Check these features in SaaS first

Ready programs have mechanisms for handling plan changes. Salesforce Spiff lets you set start and end dates for assigning a plan to a user. That is a feature worth seeing when you compare solutions for successive settlement periods (effective dates of plan assignments in Spiff).

Spiff also describes freezing statements, which protects them from change during recalculation. That does not make the whole history unchangeable (recalculating and freezing statements in Spiff). In the conversation with the vendor, show a specific plan change and ask them to reproduce an earlier calculation.

Configuring your current program is a good choice if it lets you record the split, its period and the explanation needed. The work may then also include tidying the data from the CRM. Compare the available modules, or another ready product, before you treat the spreadsheet as proof that you need your own system.

An extension may be enough when the program counts standard commission well, and one kind of exception keeps recurring. It could store the agreed splits and pass them to the calculation. You need to check whether the current product will take such information and keep the link to the specific sale. An extra screen from which finance still retypes totals would leave much of the manual work in place.

Your own app becomes a sensible candidate when the company has several recurring rules whose handling in the available tools needs many workarounds. Its first scope can cover one plan and the exception for jointly served clients. The CRM can keep supplying sales data, and the other finance processes keep running in the current systems.

The calculations will need upkeep

With your own software, it matters who changes a rule when the company agrees a new plan. The person responsible for commissions has to explain the rule and confirm the result on known sales. The app's supplier is responsible for the agreed scope of changes to the program and upkeep of the data connections. How this cooperation works affects the tool's later cost as much as its build.

Moving settlements out of the spreadsheet also needs decisions. For the current plan you will need working rules and the open exceptions. Past periods can stay in an accessible archive, if it holds the information needed to explain the results. Before switching, reproduce a known period in the proposed solution and check the split on a specific sale too. Matching the overall total alone could hide a different allocation between reps.

Also agree on exporting the data and the history of rules, and on ownership of the code. If another company is to take over upkeep one day, it needs access to the app and information on how your arrangements were implemented. Include these points in the comparison with the terms of your current SaaS.

Syntalith builds custom apps. A possible project here calculates one plan with jointly served clients and shows the rep how the split affected their result. Start the conversation with the exception that goes back to the spreadsheet at every settlement. Tell us what the program already calculates and what an employee has to correct outside it. From that you can compare a configuration change, an extension and your own app. Syntalith's apps start from €3,000 net, and we set the scope after a free process review (pricing).

What a commission system costs and when it pays back

Where to start

In the free process review we choose one process and count the team's volume and working time, and within 2 working days you get a written summary with a price. We build as part of AI apps, and we price maintenance separately.