Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →

Consultant payouts: transparency is retention

Doctors leave over payout mystery more than payout size. The fix is a statement, not a raise.

BLOG · DEPARTMENT REVENUE
● Format mechanism table
● Invented stats 0
● Figures worked arithmetic
✓ no figure without its working

The mystery tax

A consultant who cannot reconcile their statement against their own case list discounts every number on it. The suspicion costs more goodwill than any calculation error ever did — and it compounds monthly.

Case-level or nothing

A lump figure invites doubt; a statement listing each case, the billed head, the share rule applied, and the resulting line lets the doctor audit themselves in five minutes. Disputes shrink to specific lines, which is what resolution looks like.

What a trustworthy payout statement contains
ItemStandardConsequence / owner
Statement granularityPer case, per billed headSelf-auditable
Share rulesWritten, versioned, applied by systemNo discretionary drift
Payer deductionsSource shown: claim + groundPass-through with provenance
Pending casesListed as pending, not droppedNothing vanishes
Dispute channelLine-level query, trackedResolution, not resentment

Deductions need provenance

When a payer deduction flows through to a consultant’s share, the statement must show the source: claim, ground, amount. Pass-through pain with provenance is accepted; without it, it reads as skimming.

What to do on Monday

Worked examples on this page are illustrative arithmetic on stated assumptions, not measured market statistics.

Read the mechanism. Now check your own numbers.

Bring twenty settled claims, advices only, patient details redacted. We name the clause behind each reduction and you keep the findings.