Skip to main content

Payout lineage

Every number Lokom produces traces back to the deal and the rule that produced it. This is the feature that makes a disputed payout a five-minute lookup instead of an afternoon.

The chain​

Statement          one participant, one period
  └── Component    the contribution of one rule
        └── Deals  the deals that fed it
              └── Field values  what was read from Pipedrive

A statement total is never a bare figure — it decomposes down to specific deals.

Working a dispute​

A rep says their commission is wrong. In order:

1. Open their statement for the period. Look at the components. Often the answer is visible here: an expected bonus is missing because a quota rule did not fire.

2. Check attainment. High attainment with a small payout usually means a cap. Low attainment with a large payout usually means a rule firing that should not.

3. Expand the component and read the deals. Is a deal they expected absent? Then either it fell outside the period, it was excluded during deal review, or it is attributed to someone else.

4. Check attribution. A deal owned by the wrong person in Pipedrive pays the wrong person in Lokom. Lokom surfaces attribution issues during review — check them before assuming a rule is broken.

5. Check which plan version applied. If the plan changed during or after the period, the statement used the version active at the time — which may not be the plan the rep is reading today. This is a common source of "the plan says 6%".

6. Check for manual adjustments. A previous correction may be doing exactly what it was meant to do.

Most disputes are three things​

In rough order of frequency:

  • Attribution — the deal is owned by the wrong person in Pipedrive.
  • The amount field — the plan pays on a different field than the rep assumes (total contract value rather than annual, gross rather than net).
  • Timing — the deal closed just outside the period, or arrived late and the period was not re-computed.

Actual rule bugs are rarer than any of these, which is why the lineage view is worth walking through in order rather than jumping to the plan.