commission register

Recompute Commission Statements Line by Line — Free

Paste deals with their units and your commission rate, and read which statement lines paid less than the rate you were promised.

The proof surface

Statement totals hide the per-deal arithmetic. Recomputing at your own rate is what turns a vague suspicion into three deal references and two figures.

Inputdeals with units and the commission actually paid on each

Rare devicerecomputes each deal at the reader's own rate instead of trusting the statement's total

Output artifacta register of expected versus paid, with the shortfall ruled at the foot

Cost$0 · local-first · one free run · samples labelled

Sample, not your facts: Sample: Deal 8841, 12 units, $3,456.00 paid, closed 14 Aug 2026, at a promised rate of $288 per unit — four concrete points across four types.

Why the flat version breaks

Adding the total by hand

A statement total can be correct while three individual deals are rated at the wrong tier — the two errors cancel and the total looks plausible.

Chasing it next quarter

Plan documents and payout rules change on annual cycles, so a shortfall raised late is measured against the wrong plan version.

Missing shared deals

Split commissions, when not flagged on the line, look identical to a rate error, and the query goes to the wrong place on the first attempt.

How to work the commission register

Paste the statement

One deal per line with units, paid figure and reference; add split or clawback notes where they apply.

Enter your promised rate

Per unit keeps the arithmetic visible and makes each line checkable against your plan document.

Read the shortfall foot

The foot rules the total shortfall; each line above shows expected and paid side by side.

Query by deal reference

Send the two figures per deal, not the overall total, and ask which tier the payout used.

What the register replaces

Question	Before	On the register
Is the statement right	add deals by hand	expected beside paid on every line
Which deals are wrong	guess from the total	shortfall printed per deal reference
What to send payroll	a paragraph explaining	deal numbers plus two figures each

Splits and clawbacks are shown as your own line notes; the register does not decide whether a split was agreed.

Run it on the samples, right here

FIRST-LOAD

Data note: Everything runs in this browser tab on the commission register: your statement lines and deal notes stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a bound register page

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the ready-to-mail packet, and holds your drafts on this device — one free run, then $ 9 one-time for the layer that keeps filing.

The register and the per-deal comparison are free. The paid layer keeps four statements and prints a dated query sheet.

Open the commission shortfall register companion

Boundary

This commission register works only on the statement lines and deal details you paste you paste. It does not decide whether a plan document is enforceable, does not calculate legal interest on a shortfall, and does not access your employer's CRM. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with your manager in writing, then a payroll or employment adviser before you rely on it.

What this is built on

Every figure comes from the statement lines and deal details you paste you paste; nothing is looked up, scraped or asserted as verified.
Method: expected commission = units × the rate you supply; shortfall = expected − paid, per line, with both figures printed
Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.

Before: the reader accepted the statement total. After: they can see three deals paid at 6% instead of the stated 8%.