Security
Payee data, corrections, and statements stay in a workflow with access you can account for.
Founded 2026 · New York
A security and data-engineering team
CompDay runs sales commissions from source data to a statement. The inputs are pay data, and the plan changes. The same inputs have to produce the same payout, and someone has to be able to see why. That is the work this team already does.
No implementation required. Connect it today, not in a month.
The team
Security and data engineering, on both sides of the product
The people building CompDay come from security and data engineering. One side of the work is the product: how a commission run moves from import to a statement a rep can follow. The other side is the system: a payout that stays deterministic, versioned, and reviewable.
Why that background
Pay data has to be controlled. The calculation has to be reconstructable
A commission run is pay data, a plan that changes, and a statement someone will question.
Data engineering
Imports, mapping, and the plan version are the inputs. The same inputs produce the same payout, and the previous version is still there when the plan changes.
A result you can inspect
Audit history and the statement sit with the calculation. A question about a payout can be followed back to the inputs, the adjustments, and the plan version.