Skip to content

Commission tracking software for SDR teams

Commission computed from the booking itself — one row per booking, approve and pay — with cancellations resolved by a defined compensation matrix.

Updated 9 October 2026ForOperations and finance leads who own the payout
commissions · october2 selected · €190
SDRBookingStateAmount
Ricky RomaNorthgate Ltd · 7 Octpending€70
Dave MossKestrel Ltd · 7 Octpending€120
Shelley LeveneHarbor Group · 6 Octwithheld€90
Jordan BelfortNorthgate Ltd · 3 Octapproved€70
Ricky RomaKestrel Ltd · 1 Octpaid€120
one row per booking Approve 2
Illustrative example — sample data, not a customer screenshot.

What this gets you

One commission row per completed booking, enforced by a unique database constraint

A duplicate or retried job cannot double-pay — the database rejects it

Cancellation and no-show outcomes resolved by a stored policy, applied identically every time

The same billable set drives both the payout and the client invoice

Historical payouts stay reproducible after a price change

Why commission spreadsheets fail at month end

The problem is not discipline. A spreadsheet has no constraints.

Commission spreadsheet

  • The same booking can be pasted twice and paid twice
  • No rule for whether a no-show or cancellation is commissionable
  • A price change silently recalculates last quarter

With Dialbrew

  • One commission row per booking, enforced by a UNIQUE (booking_id) constraint
  • Cancellations resolved by a stored compensation matrix
  • Prices frozen onto billing records when they are created

How a commission is created and paid

  1. 1

    Product

    Each client product carries a client price and an SDR commission. One is the default.

  2. 2

    Booking

    A completed booking creates exactly one commission row. Retries are rejected by the database.

  3. 3

    Approve

    A manager approves pending rows in bulk. No-shows with a reschedule request are withheld.

  4. 4

    Pay

    Approved rows are marked paid. Reverting is possible and recorded.

Products are archived, never deleted, so old rows always resolve to the product that priced them. Each state change is stored, so “has this been paid” is a fact, not a memory.

Cancellations after money has moved

When a cancellation is approved, the compensation matrix checks two things: has the client invoice been sent, and has the commission been paid. Money never moves backward. The client gets a credit on the next invoice if they were already billed. The SDR’s unpaid commission is cancelled; a paid one becomes open work owed.

The invoice and the payout match

Both come from the same billable set. A billing record counts as invoiced only when it is sent or paid, and the client portal and the compensation logic read that same definition, so they cannot disagree.

Employees and contractors

employment_type records ENTREPRENEUR or EMPLOYEE and sets the default permission template at invite. A contractor who should see only their rostered clients is a setting, not a code change.

What you still own

Dialbrew calculates and tracks commission. It does not run payroll. Your payroll or invoicing process pays out, using a number that is correct, counted once, and matches what the client was charged.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run