Start with responsibility
Pass-through and markup describe pricing relationships, not whether costs exist. A pass-through model can still require reconciliation and explanation. A markup can still be inadequate if it ignores support effort or uncollected bills. HighLevel documentation distinguishes rebilling options across plans and services; confirm the exact supported category rather than applying a platform-wide assumption to everything.
Write a transparent usage row
Record the service, billable unit, observed supplier rate, client treatment, collection method and owner of exceptions. For a fictional plan with separately billed communication usage, the client should understand what quantity can change and where to review it. Do not conceal variable exposure behind a fixed monthly headline. The plan description and actual billing configuration should tell the same story.
Check the downside case
Ask what happens if usage occurs but client collection fails. Identify which party was charged first and how long that exposure can remain unresolved. This question matters even when a markup appears attractive. Our recommendation is to define an exception response and an affordable exposure boundary before relying on automated collection; it is not a guarantee that any particular product setting enforces a hard spending cap.
Avoid a false profit calculation
The difference between a supplier line and a client line is not net profit. Omitted labor, fees, adjustments and collection failures may change the result. Use observed costs and keep unknowns explicit. If your clients need predictable bills more than customized pricing, simplify the offered feature set or retain a client-owned service. Revisit the model using actual records rather than increasing the markup to hide an unexplained discrepancy. Before enabling the arrangement, ask a colleague to explain a fictional usage bill from the proposed description. If they cannot identify the unit and payer, improve the explanation before changing billing settings.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- HighLevel billing and wallets — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
- HighLevel pricing — Merchant documentation · gohighlevel.com · Merchant-controlled · checked 2026-09-27