Hosting invoices get paid. They rarely get checked, and the reason is reasonable: the number is plausible, the machines are running, and nobody has an obvious way to test it. The rate was negotiated carefully, and then every month after that the arithmetic is taken on trust.
Our guide to the hosting cost breakdown explains what makes up the rate, and our piece on reading a hosting agreement covers the contract. This is the monthly question neither answers: the invoice is in front of you, so how do you tell whether it is right.
Start by knowing which model you are on
Most disagreements are not arithmetic errors. They are two parties using different models and both believing the invoice is self-explanatory.
Hosting is usually billed one of a few ways. A rate per kilowatt-hour actually consumed. A rate per kilowatt of contracted capacity, whether or not you use it. A flat fee per machine. Or a profit-share arrangement. Some deals combine them, with a capacity floor and consumption above it.
The practical consequence is that the first check is not a calculation. It is confirming that the structure on the invoice matches the structure in the agreement, because if those differ nothing downstream will reconcile. A capacity-based invoice will not track your consumption no matter how carefully you measure it, and an operator who expects it to will conclude they are being overcharged every month.
What to compare it against
An invoice can only be checked against an independent number. If the only record of what happened is the one that produced the invoice, you are not verifying anything.
Your own fleet data is that independent record. Our guide to fleet monitoring and dashboards covers the tooling; the point here is narrower, which is that the data you already collect is enough for a monthly sanity check.
- Machine-hours. How many units were online, for how long. This is the single most useful figure, and it is the one that catches billing for machines that were down.
- Your own power estimate. Units multiplied by their draw multiplied by hours gives an approximation you can compare to billed kilowatt-hours.
- Observed downtime. When your monitoring shows units offline, and for how long, with timestamps.
- The machine count you believe is installed. Checked against the count being billed, which is a surprisingly common place for drift.
None of this needs to be exact. You are not producing a competing invoice. You are establishing whether the billed figure is in the neighborhood of what your own data implies, and investigating when it is not.
Differences that are normal
This matters as much as the checks, because an operator who treats every discrepancy as an error will raise disputes that go nowhere and spend credibility they will want later.
Billed power exceeds the sum of what your miners report. This is expected, not padding. A machine reports what it is doing; the meter records what was drawn at the wall, which includes power-supply losses and anything else on the circuit. Expect billed consumption to run above the sum of self-reported figures.
Facility overhead is included. Depending on the deal, cooling, lighting, networking and ancillary load may be allocated to customers rather than absorbed. That is a legitimate structure. What matters is whether it is the structure you agreed, and whether the allocation method is stated.
Months differ in length. A three-day swing between billing periods is a meaningful percentage, and it accounts for a good share of invoices that feel wrong on first glance.
Rates move with the underlying market. Where a contract passes through energy cost, the rate is supposed to vary. Our note on demand charge management covers why a bill can rise without consumption rising, which is one of the least intuitive parts of industrial power.
Differences worth raising
A smaller set of findings justifies a conversation.
- Billing for machines that were demonstrably offline. This is the most common real error and the easiest to evidence, provided your monitoring retains the history.
- A machine count that does not match your manifest. Particularly after a swap, a repair return, or a partial deployment.
- Consumption that cannot be reconciled with physics. If billed kilowatt-hours exceed what your installed units could draw running continuously at full power for the entire period, something is wrong regardless of explanation.
- A rate that does not match the agreement, including escalations applied earlier than the contract allows or a promotional rate that ended without notice.
- Charges with no contractual basis. New line items appearing without a corresponding clause.
- SLA credits that should have been applied and were not. Credits are frequently claim-based rather than automatic, which our guide to hosting SLAs and uptime guarantees covers. An outage you absorbed without claiming is money the agreement said you were owed.
Ask how it is measured, once
The question that resolves most future ambiguity is simply where the meter is and what it measures.
Whether billing comes from a meter on your specific circuits or from an allocation of a larger facility meter changes what the number means. Allocation is normal and workable, but the method should be stated: what is divided, by what, and how your share is derived. Our overview of metering and sub-metering covers how facilities build this, and reading it from the supply side makes it much easier to ask a precise question.
It is worth asking once, early, while nothing is in dispute. A provider who can describe their metering clearly is straightforward to work with later. One who treats the question as suspicious has given you useful information at no cost.
Raising a discrepancy without burning the relationship
How a question is asked largely determines whether it gets resolved, and this is a relationship you depend on daily. The goal is an answer, not a win.
What works is specificity. One period, one line item, your figure, their figure, and the data behind yours. A message that says the invoice looks high invites a defensive reply. One that says your monitoring shows eleven units offline from the fourteenth to the seventeenth while the invoice bills the full fleet for the period is a question somebody can actually check.
A few things make the difference in practice:
- Ask before asserting. Open by asking how a figure was derived rather than stating it is wrong. A good proportion of apparent errors turn out to be a structure you had misunderstood, and discovering that after accusing someone is an avoidable cost.
- Keep it to one period. Raising six months at once converts a correctable error into a negotiation about the whole relationship.
- Send the evidence, not a summary of it. Timestamps and the underlying monitoring export, so the other side can verify rather than take your word.
- Put it in writing, even after a phone call. A short confirming email of what was agreed is what makes the outcome real.
- Pay the undisputed part. Withholding an entire invoice over one line gives the facility a reason to treat you as delinquent, and in most agreements an outstanding balance has consequences well beyond the amount.
If a provider cannot explain how a figure was produced, that is itself the finding. Billing you cannot verify is a risk you are carrying whether or not this month’s number happened to be correct.
Make it a habit rather than an investigation
The reason this goes unchecked is that it is only ever done in anger, when a bill looks wrong and the review becomes an accusation.
Done monthly as routine it takes very little. Record billed amount, billed consumption or capacity, billed machine count and the period. Put your own machine-hours and downtime beside it. Over a few months the normal relationship between those columns becomes obvious, and the value is that a genuine anomaly then announces itself rather than needing to be hunted.
That record is also what makes a dispute work. A specific, evidenced claim about one period gets resolved. A general sense that the invoices seem high does not, and it is the version most operators are left with because nobody kept the columns.
It matters at the end of the relationship too. As our guide to getting your miners out of a hosting facility notes, an outstanding balance changes the balance of power in an exit considerably. Knowing precisely what you owe, and what you do not, is worth more then than at any other time.
If you want straight answers about how hosting is metered and billed before you sign rather than after the first invoice, talk to us. It is a better conversation to have while nothing is in dispute.
Explore Rax Mining
- Bitcoin Miner Hosting — Tiered rates from $0.085/kWh, NatGas from $0.055/kWh
- NatGas MDU Units — 1MW modular datacenter containers
- Mining Profitability Calculator — Estimate your mining returns
- Our Facility — Tour our mining infrastructure

