Home/Products/Sales Performance
Sales performance management platform

Commissions your reps can see and your auditors can trace.

Sales Performance turns a company target into quotas for every region, team and rep. Your business team builds incentive campaigns with rules, tests them before launch and sends approved amounts to payroll and accounting. Every figure traces back to a rule, a data set and a timestamp.

Sample screens. All names and figures are fictional.

The problem

Sales teams live with at least one of these.

commission_final.xlsxcommission_final_revised.xlsxcommission_final_LAST.xlsx
#REF!#REF!

Excel calculations

Version chaos, broken formulas and thousands of rows moved by hand.

Campaign changeWaiting
Campaign changeWaiting
Campaign changeWaiting
Campaign changeWaiting
Campaign changeWaiting

The IT queue

Every campaign change waits its turn in a ticket queue.

Quarter closesResults arrive
JulAugSepAfter

No foresight

Management sees performance too late. Action comes after the quarter has closed.

My calculation is wrong.Which rate did you use?Can you check it again?My calculation is wrong.

Month-end disputes

Every month end, “my calculation is wrong” turns into overtime.

Setting up a campaign is the easy part. The hard part is calculating it correctly, handling payouts on time and getting it through audit.

Sample screens. All names and figures are fictional.

How it works

Follow one commission from target to payroll.

Deniz A. is a sample rep on a sample plan. Scroll down and the same number moves through the whole cycle.

01

The company target becomes a rep’s quota.

Split the target level by level: business unit, region and channel, team, rep. The split comes from data, such as past performance, forecast or portfolio size.

02

The business team writes the plan as rules.

Pick a data set, chain conditions with AND or OR, add reward tiers. Campaigns are built on screen, without code.

03

See what it costs before launch.

Simulation shows who qualifies, the total pool and the average payout. Change one condition, run it again and watch the pool move.

  • A budget limit raises an alert when the pool goes over it
04

Calculation shows who matched which campaign state.

Pick the campaign period and calculate. Each row shows the reward, the matched state, the minimum reward check and whether the rep is out of scope. Review it, then finalise.

05

Exceptions stay on the record.

Cancellations and refunds are recalculated automatically. A manual extra payment goes in with its type, amount and reason.

06

Amounts move through approval.

Approval is role-based and can run through several steps, following your organisation. Each row shows where it stands.

07

Approved amounts reach payroll and accounting.

Calculated, additional and net amounts travel together. Each figure keeps its link to the rule, the data set and the timestamp behind it.

Sample screens. All names and figures are fictional.

Modules

Every part of the cycle, screen by screen.

Set the levels from company to rep, pick the KPIs and break them down by product group, customer segment and geography. Quotas are distributed using data.

A rule runs on a data set: rows of parameter, control and value, joined with AND or OR. It reads as one sentence and needs no code.

Name, dates, period, calculation timing and minimum reward amounts. Then add states: each one pairs a condition with a reward.

For one rep and one reward: last year’s production, this year’s, the minimum increase and the commitment.

Rep, manager and executive read the same figures, each from their own seat.

Every figure traces to a rule, a data set and a timestamp. Rule versions and the change log stay on record, and the trail can be exported.

Sample screens. All names and figures are fictional.

More in the product

The work around the calculation.

Sales channel list

Filter by campaign, period and directorate, sort any column and export the list to Excel.

Field messages

SMS, e-mail and push notifications carry campaign news to the field.

SMS
E-mail
Push notification
SMSDeniz, Q3 Cross-sell ends on 30 Sep.
E-mailQ3 Cross-sell results are approved.
Push notificationDeniz, Q4 Cross-sell is open.

Early warning

Three questions to answer before a target is missed.

Who is about to miss quota?Selin T.
Which region is drifting mid-month?Akdeniz
Which channel wins on which product?Agency · Motor

Channel league

Challenges, achievements, milestones and a league between channels.

Budget limits

Define the budget and get an alert as a campaign nears its limit.

Q3 Cross-sellWithin budgetLimit alert: 95% used
Calculated€84,420
Additional payment€1,200
Budget€90,000

Reward structures

Fixed, tiered or custom, paid as commission, gifts or a performance bonus.

FixedTieredCustom
Commission
Gifts and gift vouchers
Performance bonus

Groups

Group reps by title, region, tenure, performance or portfolio, each group with its own rule.

TitleRegionTenurePerformancePortfolio
DAMKSTCBEYZKOY
Marmara repsOwn rule · own target

Role-based access

Permissions for campaigns, lists and actions, set by role.

Business teamManagerAudit
Campaigns
Lists
Actions

Sample screens. All names and figures are fictional.

Connections

It connects to what you already run.

Data comes in from your databases, message queues and APIs. Approved amounts go out to payroll and accounting.

Data in
PostgreSQL MSSQL DB2 Redshift
Kafka RabbitMQ ActiveMQ IBM MQ Redis
REST Webhooks Event triggers
Batch import and export Scheduled jobs
CRM ERP Policy system Call centre

Sales Performance

  • Targets and quotas
  • Rule engine
  • Simulation
  • Calculation
  • Approval
  • Audit trail
Payment
Payroll
Accounting
Third-party payment systems
The field
SMS
E-mail
Push notification
Audit
Excel export
Audit trail export
Who uses it

One set of figures, four seats.

Business team

Builds and runs the campaign.

Data sets, rules and campaigns are set up on screen. The team runs simulation and calculation and adds additional payments.

Sales rep

My target. My progress. My commission.

Own attainment, commission status, leaderboard position and open campaigns.

Manager

Where the team stands, where to step in.

Team summary, target deviation, individual comparison and reward distribution.

Executive

Channels and regions in one view.

Growth rate, channel and region breakdown, success ratios and a KPI summary board.

The payee can also be an agent, a broker or a dealer. Payroll and accounting receive the approved amounts, and audit receives the exported trail.

Details

All the details.

Why it exists
Why it exists

Every enterprise runs incentives; many run them on spreadsheets.

The commission workbook has a formula that was not updated for the new plan. The distributor rebate file has a lookup on a stale range. A sign error turns a clawback into a payable and nobody notices until the rep does. Reconciliation eats analyst time every cycle, and when internal audit asks how a number was produced, the honest answer is “somebody’s laptop”.

Sales Performance replaces that with three things: plan logic as versioned configuration, calculation as a deterministic engine, and settlement with an audit trail that finance can read. The same inputs produce the same payables; every change has an author, an approver and a date.

One platform spans the four programme families — direct incentives, partner and channel, trade promotions and sales performance management — so the logic, the data and the governance stop fragmenting across departments. It is built and operated by the same Odeontech engineers, to SLOs agreed with you according to your needs.

Modules
Modules

Four programme families, one engine.

Each family is a module with its own screens and rules, but they share the plan designer, the calculation engine, the dispute flow and the settlement ledger. A transaction credited once is credited the same way whether it feeds a rep’s commission, a dealer’s rebate or a retailer’s promotion claim.

01

Direct sales incentives

Commission plans, quotas, accelerators and SPIFFs for your own salesforce. Reps see attainment and projected payout after every run; finance sees the same numbers with the calculation behind them. Plan changes are versioned and approved, so a mid-year change is a decision rather than a scramble.

CommissionQuotasSPIFFs
02

Partner & channel programmes

Tier bonuses, MDF and sell-through incentives across distributors and dealers. Claims are validated against POS evidence before they are paid, and partners see their standing, rebate pipeline and fund balances in a portal instead of asking at quarter end.

TiersMDFSell-through
03

Trade promotions

Planning, budgeting and settlement of retail trade spend, closed with a post-event analysis that shows lift against baseline. Promotions are measured, not just funded; deductions are matched against agreed terms so leakage is surfaced rather than absorbed.

CalendarClaimsLift analysis
04

Sales performance management

Territories, quotas, crediting rules and the dashboards reps and leaders run on. The upstream inputs to every incentive plan are put under governance too, so the engine downstream calculates on foundations that hold through a reorg.

TerritoriesCreditingAnalytics
Features
Features

What it does, in detail.

01

A calculation you can replay.

The engine runs over governed transaction feeds and produces payables deterministically: the same inputs, the same plan version, the same result. Runs are logged with their inputs, so an auditor can pick any figure and walk back to the CRM record that produced it. That is what turns “trust us” into “check for yourself”.

  • Daily or intraday batch by configuration
  • Every run stored with plan version, feed snapshot and actor, so each payout carries a complete audit trail
  • Parallel-run mode calculates alongside your spreadsheets until the numbers agree, then takes over
02

Disputes with a queue, not an inbox.

When a rep or a partner thinks a number is wrong, they raise a structured query against the specific line, from the dashboard. It goes to the right owner with an SLA, the adjustment — if one is made — is logged with a reason and an approver, and the corrected figure flows into the next run. Nobody edits a cell.

  • Queries link to the transaction and the plan clause, so they can be answered by showing the calculation
  • Adjustments are separate records with their own approval; the original run is kept as it was
  • Dispute volume and resolution time reported per plan, which is where plan-design problems first show
03

Settlement that finance reconciles once.

Payout files, accruals and GL postings come out of the same ledger the calculation wrote to. Payroll gets a file per entity and currency; accounting gets accrual and reversal entries by cost centre; treasury gets the partner settlement schedule. They already match, because they are the same number viewed three ways.

  • Multi-entity and multi-currency by configuration — rates, calendars and posting rules per unit, consolidated reporting on top
  • Accrual and true-up entries generated per period with the run they came from
  • Payout files per entity and currency, released from the same run finance reviewed
By role
By role

One record, four readers.

Sales rep

Standing during the period, not at month end.

Reps see attainment, the pipeline of earnings and the plan terms in plain language on their own dashboard. They can project what closing a specific deal does to their payout. Trust comes from being able to see the calculation.

  • Attainment and projected payout refreshed after every run
  • What-if projection on open pipeline
  • Plan clauses shown next to the numbers they drive
Sales operations

Plan changes, with a trail.

Ops designs and maintains plans, hierarchies and crediting rules in the designer instead of a workbook. A change is modelled, simulated on real data and routed for approval. When the reorg comes, territory and quota impacts are simulated before they are applied, with effective dating.

  • Versioned plans with simulation before approval
  • Hierarchy and crediting rules as configuration
  • Dispute queue with SLAs per plan
Finance

Accruals that match the payout file.

Finance gets payout files, accruals and postings from the same ledger the engine wrote, with the run hash that produced them. Close moves from manual reconciliation to checking that the parallel run still agrees. Internal audit can pick any payable and replay it.

  • Entity- and currency-specific payout files
  • Accrual, reversal and true-up entries per period
  • Replayable runs for audit
Partner

The quarter-end number, before quarter end.

Distributors and dealers log in to see tier standing, the rebates their validated sell-through has earned and their MDF balance. Claims are submitted with evidence and tracked to payment. Disputes are structured, with an SLA, instead of an email thread.

  • Live tier qualification against targets
  • Rebate pipeline built from validated claims
  • Fund balances with every draw-down visible
Architecture
Architecture

Feeds in, one governed record, outputs for every reader.

Sources
CRMERP / order managementPOS & claimsHR hierarchyPayroll
Ingestion
Governed feed contractsPer-source mappingsValidation & quarantineKafka
Core
Plan designerCreditingCalculation engineDispute & adjustmentSettlement ledger
Outputs
Rep & leader dashboardsPartner portalPayout & GL filesAudit replayBI export
Capability matrix
Capability matrix

What ships, what is configured.

CapabilityIn the platformConfigured per client
Plan designer with versioning and simulationPlan library
Deterministic, replayable calculation engine—
Crediting: splits, overlays, team creditRules
Dispute & adjustment workflow with SLAsOwners, SLAs
Rep, leader and partner dashboardsBranding, KPIs
Settlement: payout files, accruals, postingsEntities, GL mapping
Feed contracts (CRM, ERP, POS, HR)Per-source mappings
Custom connectors and extensions—
Integrations
Integrations

Governed contracts, not point-to-point files.

Salesforce

Opportunities, accounts and hierarchies in; attainment and standing back

ERP

Invoices, credit notes and order lines; GL postings and accruals out

POS & distributor claims

Per-partner mappings normalised into one validated sell-through model

HRIS

Roles, managers and effective dates for crediting and hierarchy

Payroll

Per-entity, per-currency payout files on the payroll calendar

Data platform

Run outputs and ledgers exported to your warehouse and BI

Workflow & Procurement

Approval flows for plan changes and MDF claims

Implementation
Implementation

Parallel run first, source of truth second.

01

Plan capture

We read the spreadsheets with the people who own them and rebuild each plan in the designer. Ambiguities become explicit rules with an owner.

02

Feeds and crediting

CRM, ERP and hierarchy feeds land under governed contracts. Crediting rules are configured and validated against last quarter’s records.

03

Parallel run

The engine calculates alongside your current process until the numbers agree. Every difference is explained.

04

Cut-over

Dashboards go live for reps and managers, settlement files go to payroll, and the workbook is retired. Disputes move into the queue.

05

Operated

The Odeontech team that built the platform runs it to SLOs agreed with you, adds programme families as you need them, and supports each plan-year change.

Module pages
FAQ

Frequently asked questions

The plan designer covers tiered, blended, split-credit and gate conditions, plus caps, accelerators, clawbacks and effective dating. Genuinely exotic logic can get an extension built by the product team, not a workaround in a spreadsheet next to the platform.
Parallel run. The engine calculates alongside your spreadsheets until the numbers agree — differences are investigated — and then it becomes the source of truth with a clean cut-over date.
Their own dashboard: current standing, the pipeline of earnings, what-if projection on open deals, and plan terms in plain language next to the numbers they drive. Trust through transparency.
Feeds from CRM and ERP arrive via governed contracts with per-source mappings. Batches run daily or intraday by configuration. Payout and GL files go out on your payroll and close calendars.
No. Each family deploys independently, so you can start with one and add the others on the same record when the programme is ready.
We do. The same Odeontech team that builds the platform runs it, to SLOs agreed with you according to your needs, and supports each plan-year change.
On infrastructure we operate to SLOs agreed with you according to your needs, GDPR and KVKK compliant. Hosting and region are agreed per deployment; the controls are described on the security page.

See it on your own data.

A guided demo with an engineer who operates the platform — configured toward your programme, not a canned deck.

✓ No pitch deck✓ Reply from an AI-native engineer✓ Written follow-up