A plan exists in three places at once

Almost every company runs its compensation on three representations of the same plan. There is the plan document that participants sign, written in prose. There is the configuration inside the calculation engine, written in a vendor's own format. And there is the spreadsheet an analyst maintains to reconcile the first two when someone disputes a payment.

Nothing keeps the three in sync. They drift the moment a plan is amended mid-year, and the drift is usually discovered by a salesperson who was paid the wrong amount.

What that costs

Changing vendors becomes a rewrite rather than a migration, because the only complete statement of the plan lives inside the system being replaced. Auditing requires that vendor's tooling and that vendor's staff. A disputed payment cannot be traced back to the sentence in the plan document that governs it. And nobody can answer a question as ordinary as what changed between last year's plan and this year's, because there is no artifact to compare.

What a shared definition buys back

A vendor-neutral, machine-readable plan definition makes the plan itself the durable artifact. The same file can be handed to competing vendors during an evaluation and mean the same thing to each of them. Two plan years can be diffed. And because every fact in the schema carries its own effective dates, the plan as it stood on any given day can be reconstructed — which is what an audit or a dispute actually requires.

What this standard is not

The standard describes the plan. It is not a transaction format, and it does not carry orders, bookings, or payments. It is not a results format, and it does not carry calculated commission amounts. It is not a calculation engine, and it does not specify how a system should compute attainment.

Those boundaries are deliberate. A plan definition that also tried to be a data interchange format would be adopted by nobody, because it would collide with every system already doing that job.