Why Your Per-Head Invoice Doesn't Match Your Headcount: The 25th Cutoff, Pro-Ration, and Tier Re-Application Explained
- Connie Barrientos-Carey
- Aug 1
- 2 min read
The market rewards the loudest provider. Inspections reward the most documented one.
Nowhere is that gap more expensive than in per-head billing. Most disputes on a per-head invoice aren't pricing disagreements — they're documentation gaps. The client doesn't know why the number moved. The provider doesn't have a file that shows the math. Someone ends up guessing, and guessing erodes trust faster than a bad rate ever could.
Here's the mechanism, in full:
01 — The cutoff. Headcount is locked on the 25th of each month. That figure — not the 1st, not the 30th — becomes the invoice base for the coming cycle. A hire on the 26th doesn't inflate this month's bill. It rolls forward.
02 — Pro-ration. Mid-cycle hires and exits are billed by days active, not a flat monthly rate. Someone active for 12 days pays for 12 days. This i
s arithmetic, not policy — and it should be visible as arithmetic on the invoice, not asserted as a summary line.
03 — Tier re-application. When headcount crosses a volume threshold, the new per-head rate takes effect from the next full billing cycle — never applied backward onto heads already invoiced under the prior tier.
Retroactive tier changes are where most billing anxiety actually lives, and they're avoidable with a documented effective date.
None of this requires trust in a dashboard or a reassuring account manager. It requires a line-item invoice: cutoff headcount, pro-ration calculation, tier basis, effective rate — retrievable, not recited.
That's the structural difference in this market. Providers narrate compliance and billing accuracy. Very few can hand you the file that proves it on request. "We're transparent" is a claim. A reproducible invoice trail is proof.
If your current EoR or per-head arrangement can't show you this math on demand, that's not a minor gap — it's the whole audit trail missing.
Note: cutoff date, tiering, and pro-ration mechanics above reflect Aleph's standard framework and should be checked against your specific service agreement.
Comments