Why No FMO Software Gets the HEAP Model Right
Twenty-five years of Medicare distribution has produced one consistent frustration: no off-the-shelf commission platform actually handles HEAP correctly.
What HEAP actually is
HEAP — Health, Education, Accident, Property — is not a quirky edge case in Medicare commission structures. For FMOs operating across multiple product lines, HEAP is the backbone. And it has properties that break generic commission software reliably.
HEAP is hierarchical. A downline agent's production flows up through one or more layers of override compensation. The override amounts depend on the product, the agent tier, the contract year, and sometimes the specific payer — and those rules can differ within a single agent's book.
Generic commission software assumes flat or two-level hierarchy. HEAP regularly has four.
Where generic platforms fail
Every major commission platform has the same ceiling: they were designed for direct sales compensation, possibly with one manager override. Apply them to HEAP and you hit walls immediately:
Override cascade calculation. When Agent A sells under Manager B, who is under Director C, who is under Regional D — and each level has a different override percentage depending on product and contract year — most platforms either flatten this (wrong) or require manual entry per transaction (unusable at volume).
Mid-year tier changes. An agent who moves from bronze to silver tier in June needs their January-May commissions to stay at bronze rates and June-December at silver. Some platforms recalculate everything retroactively. Most FMO finance directors have at least one horror story from this.
Variance reporting. The actual commission check vs. the calculated commission — the variance — is the number every FMO finance director lives in. Good HEAP software surfaces it by agent, by product, by payer, by period. Bad software makes you reconcile it in Excel.
The spreadsheet trap
Most FMOs solve this the same way: two to three spreadsheets, built and maintained by one or two people who understand the business deeply, backed by tribal knowledge.
This works — until it doesn't. The risk isn't that the spreadsheets are wrong (though they often develop errors). The risk is that the knowledge is concentrated. When the person who built the model leaves, or is sick, or the model grows more complex than a spreadsheet can handle, the FMO's commission function becomes fragile in ways that show up as payment errors that damage agent relationships.
We built compLAB specifically to encode what the best FMO finance director already knows — not to replace them, but to make that knowledge permanent and auditable.
What correct implementation requires
A correct HEAP commission engine needs:
1. Hierarchical override cascade — configurable depth, configurable rate tables per product per tier per contract year. 2. Period-locked rates — tier changes apply forward, not backward. Historical commission calculations are immutable. 3. Agent-level variance reporting — calculated vs. actual, by product, by payer, by period, drillable to the transaction. 4. Payer feed reconciliation — import payer commission statements, match to calculated amounts, surface exceptions. 5. Model simulation — before any compensation change goes live, run it against the last 12 months of production data to see the financial impact.
This is not a feature list for a generic platform. It's the minimum for an FMO running real HEAP production. compLAB was built against this spec, from a finance director who had built the model in spreadsheets and knew exactly where every generic platform had failed her.
compLAB — FMO commission engine
Built for HEAP. Handles override cascade, period-locked rates, variance reporting, and payer feed reconciliation. Waiting list open with 2-year price lock.
Content matched to your domain — no general AI hype, no mass distribution. Each send is personalized to what you told us about your work.