Explainable AI in commission software: the AI writes, the engine calculates

Every commission statement eventually meets the same question: "Why did I get this number?"

A sales rep asks their manager. The manager asks finance. Finance opens a spreadsheet and hopes the person who built it still works there.

That question is the real test of any commission system. Not how fast it calculates, but whether it can explain what it calculated.

The problem with "the AI said so"

General-purpose AI models are probabilistic. Ask the same question twice and you can get two different answers. That's fine for drafting an email. It's not fine for pay.

A commission is a promise with money attached. If you can't reproduce it, you can't defend it: not to the rep, not to an auditor, and not to yourself.

Our rule: the AI writes, the engine calculates

Evenq splits the work in two, and the line between them doesn't move.

The calculation engine is deterministic. Same sales, same plan, same result, every time, to the cent. There is no AI model, no randomness and no outside service inside a commission calculation.

The AI assistant, Zeke, never computes money. It helps you configure and understand the system. When it drafts a rule from a plain-language description, the draft goes through the same validation as the rule form, and nothing is saved until a person reviews it and confirms.

That keeps AI where it's useful (reading, explaining, drafting) and out of where it's risky (deciding what someone gets paid).

Every number has a way back

Explainability isn't a chatbot feature. It's how the data is designed. In Evenq:

• Each commission is linked to the sale that produced it.
• The version of the rule that was used is frozen with it, so editing a plan later doesn't rewrite the past.
• A recalculation creates a new record and marks the old one as replaced, instead of overwriting history.
• The money cards on the dashboard open the rows behind them, and those rows add up to the same figure.

So "why this number?" has a concrete answer: this sale, this rule, this version.

Asking "where does this amount come from?"

Zeke can answer that with real data: payouts, pay runs and balance entries. It works read-only, with the same permissions as the screens you already use, so it can't show you anything you couldn't see yourself.

And when it can't answer, it says so. It doesn't fill the gap with a guess. A confident wrong answer about someone's pay is worse than "I can't look that up yet."

Why it matters now

Across Europe, rules on pay transparency and on the use of AI are pushing companies to show how pay decisions are made, not just what they are.

But the bigger reason is trust. A rep who doesn't trust their statement rebuilds it in a spreadsheet. A finance team that can't explain a figure holds up payroll. Numbers that explain themselves save both.

The short version

• Deterministic engine: same inputs, same result.
• AI assists, people decide: drafts are validated and confirmed, never saved on their own.
• Traceable numbers: every commission leads back to its sale and the rule version used.
• Honest assistant: when Zeke can't answer, it tells you.

If "explain this number" is a question your team hears every month, request access to Evenq and see it on your own plans.