No Receipt, No Commission

Most of the time that works, because most people are honest and most memories are decent. But "most of the time" is a terrible standard for money. The failure mode is not fraud. It is a demo that got counted twice, a referral nobody can trace back to a source, an upfront bonus paid on a deal that quietly fell through the week after. Nobody stole anything. The record just never existed, so nobody can prove anything either way, and the ledger fills up with entries that are probably fine.

Probably fine is not a ledger. It is a rumor with a dollar sign.

The rule we just shipped into our own payroll

This week we armed a new rule in Vex Books, the money tool VizyPay runs its own commission cycles on. Starting with the next pay cycle, three commission types cannot enter the approval queue without an attached receipt: the ticket, the activation record, the artifact that proves the event happened.

No receipt, no commission. Not "flagged for review." Not "approved with a note." Refused, out loud, at the door.

The receipt requirement is not new thinking. Every finance leader already believes in it. What is different is where it lives. A policy in a handbook depends on a human remembering it on a busy Friday. A policy in the software refuses on that same Friday without being asked. The rule does not get tired, does not know whose deal it is, and does not make exceptions for anyone, including the people who built it.

Boundary-gated, because fairness is a design decision

One detail we care about: the rule takes effect at the next cycle boundary, never mid-cycle. Anything submitted under the old rules finishes under the old rules. Nothing in flight gets stranded by a policy that did not exist when it was filed.

That sounds small. It is not. Retroactive rules are how teams learn to distrust their own tools. If the software can change the deal on work already submitted, people stop trusting the queue and go back to hallway agreements. A money tool earns trust the same way a person does: by being predictable about the rules and loud about changes before they bite.

Not every payment needs a receipt, and the tool knows the difference

Residuals in Vex Books are system-computed from processing data, so demanding a receipt for them would be asking the software to prove itself to itself. Those stay exempt by design. A couple of newer commission types get watched for one full cycle first, and flip to required only if the receipts prove routine. The point is never paperwork for its own sake. The point is that human-attested money carries human-attested proof.

Why we run it on ourselves first

VizyPay runs its own payroll cycles through Vex Books before any of this reaches anyone else. That is the whole VEXIS model: our book is the test book. When a rule like this one has a sharp edge, it cuts us first, and we fix it before it ever touches a partner.

The takeaway for anyone running an ISO today: look at your last commission run and ask how many line items could survive the question "show me the receipt." If the honest answer is "most of them, probably," you do not have a commission problem yet. You have a records problem, and records problems become commission problems on the worst possible day.

Software should hold the standard your busiest Friday cannot.

Field Notes publishes regularly from the VEXIS build floor. Sign up at getvexis.ai for early access and new dispatches.