Start with a specific discrepancy
Write the exact question: a missing usage item, an unexpected quantity, a collection difference or a timing mismatch. These require different evidence. Record the account and transaction references privately, but keep sensitive payment details out of a general investigation note. Do not ask the client to pay again simply because one dashboard has not yet reflected another record.
Match like with like
Align service category, unit definition, currency and time interval. Separate gross usage, adjustments and collected amounts. HighLevel billing documentation distinguishes the agency funding path from client rebilling, so matching two totals without understanding their roles can be misleading. A supplier charge and a client invoice may legitimately differ; the point is to explain the difference rather than assume it is an error.
A synthetic investigation
A fictional statement shows 120 units while your plan sheet anticipated 100. First confirm that the estimate was not mistaken for a limit. Then compare the observed unit definition and period. If the 20-unit difference remains unexplained, preserve both records and ask a narrow support question. Do not rewrite historical estimates to match the bill, because that destroys the evidence needed to improve the next estimate.
Close only with an explanation
Record whether the discrepancy was resolved, remains pending or requires an authorized correction. Name the record that supports the conclusion. If a correction would charge, refund or change access, obtain the applicable authority separately. Update the future planning assumption only after understanding the cause. A reconciled total is useful operational evidence; it is not proof that the service is profitable or that all clients will behave similarly. Keep the original discrepancy and the eventual explanation together. The useful output is a traceable reason for the difference, not merely a revised total that happens to match your initial expectation.
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
- Stripe subscription lifecycle — Merchant documentation · docs.stripe.com · Merchant-controlled · checked 2026-09-27