Read your OVHcloud invoices as a month-to-date and a forecast

Where do you find your OVHcloud invoices and usage?

The OVHcloud Control Panel keeps invoices and usage in separate views. Your invoices for every service are on the My bills page, which can also export all of them as a CSV file. Inside a Public Cloud project, Billing has a History tab of that project’s past bills and a Current usage view of the month in progress. Current usage has an “Already billed” part for resources charged at the monthly rate, and a “Future bills” part that lists pay-as-you-go usage “from the first of the month up to that day”, next to OVHcloud’s projection of the invoice due on the 1st.

Usage OVHcloud has metered but not yet billed stays in Current usage until the invoice is written.

How does OVHcloud bill (and when does an invoice arrive)?

Most OVHcloud charges reach you on invoices issued on the 1st, but the lines on them cover different periods. The lines come in three kinds.

• Pay-as-you-go (hourly) resources are billed after use. Public Cloud counts hourly instances by the second, and OVHcloud US shows that time on the invoice as decimal hours. They are “paid for on the first day of the following month”. Each Public Cloud project gets a separate bill for the month, generated on that day.
• Commitments are billed in advance. Commitments are “billed on a monthly basis and payable in advance”, so the invoice issued at the start of a month carries that month’s commitment fee.
• Renewals land on the 1st. Services set to renew are renewed on the first day of the month, though how often depends on the service. The renewal charge pays for the period ahead.

Those charges do not always share one invoice. OVHcloud US also notes that since 1 April 2026 Public Cloud invoices are issued separately from Bare Metal and Hosted Private Cloud ones. The 1st can bring more than one invoice, each with its own total.

Here is what the 1st can bring, whether it arrives as one invoice or several. The figures are invented for illustration and carry no currency.

Part of that is October and part of it is November, yet all of it carries one date.

Why does OVHcloud spend jump on the 1st?

OVHcloud spend jumps on the 1st because CostCompass records it on the day the invoice is issued, and the 1st is when OVHcloud usually issues the invoices that carry most of the month’s charges. The usage timeline and the billing timeline run side by side.

• The usage timeline is when your resources ran: the October days your hourly instances were up.
• The billing timeline is when OVHcloud turned that into a charge: the invoice dated 1 November.

Each row in CostCompass keeps the service period OVHcloud gives its line, but it stays on the invoice date: the date printed on the invoice in My bills.

So, across the month:

1. On the 1st, month-to-date steps up. The invoices issued that day hold last month’s pay-as-you-go usage and this month’s commitments and renewals.
2. For the rest of the month it stays flat. Nothing new appears until OVHcloud issues another invoice.
3. This month’s hourly usage shows up next month. It is on the next 1st’s invoice, so it belongs to next month’s month-to-date.

If you want to watch the current month’s hourly usage build up before it is invoiced, OVHcloud’s Future bills view is the place for that.

Is the OVHcloud cost exact or estimated?

The OVHcloud figure is a reported cost. OVHcloud states the money on every invoice line, and CostCompass records that amount as it is, with no rate table in between. That is a different source from Sentry, where CostCompass prices usage counts into money, and from RunPod, which reports a cost for each day from a prepaid balance.

CostCompass also checks every invoice against itself before storing it:

• The lines must add up to the invoice’s pre-tax total.
• The pre-tax total plus the tax must equal the invoice total.
• Every amount on the invoice must be in one currency.

If any check fails, or an invoice or one of its lines does not come back, the refresh stops with an error and stores nothing for that window. Tax is kept as a separate Tax row for each invoice that carries it, so the card’s total is what OVHcloud charged with tax included. A refresh that sees an invoice it already holds updates those rows in place, so clicking Refresh again never counts an invoice twice.

There is one size limit: a single refresh reads at most 6 invoices of up to 14 lines each across the two months it covers, and an account past that gets a plain error saying so rather than a partial total. For scale, the OVHcloud US account we connected on 19 October 2026 held 3 invoices and 16 lines across those two months. In the same run we set off each failure the connector handles (a wrong secret, a computer clock out of step, an expired consumer key, a key from the wrong region, a key missing its rights), and each one came back as a separate message instead of an empty card.

How do you forecast next month’s OVHcloud bill?

CostCompass forecasts next month’s OVHcloud spend as the total of OVHcloud invoices issued in the last complete calendar month, added to the one forecast for all your providers.

The usual method, described in the guide to forecasting AI spend, scales the last seven days of spend up to a month. That suits providers whose spend grows a little every day. OVHcloud spend does not: a seven-day window holds nothing in most weeks and a whole month of invoices in the week of the 1st.

Put numbers on it with the illustrative figures above, and suppose every 1st brings the same lines, 87.96 in total. In a November week that includes the 1st, the seven-day method projects December at 87.96 ÷ 7 × 31 ≈ 389.54, about 4.4 times what OVHcloud will bill. In any other November week it projects 0. The last complete month gives 87.96 all month. A complete month of invoices holds one full cycle: a month of pay-as-you-go usage plus a month of advance charges, which is what the next 1st will bring too.

Two details follow from that choice. When a card has no invoices from last month yet, because its first invoice arrived this month, CostCompass uses this month’s invoices instead. And because the input is a closed month, a sharp change in your usage reaches the forecast one billing cycle later.

How does CostCompass track your OVHcloud costs?

CostCompass reads your OVHcloud invoices through OVHcloud’s API with a read-only key, splits each invoice into its lines by service, and adds them to your month-to-date figure each time you click Refresh. Setting it up takes four steps.

1. Pick your region on the OVHcloud card. The connect form offers Europe, Canada and United States. Choose the one your OVHcloud account belongs to.
2. Open that region’s key page. For Europe it is https://eu.api.ovh.com/createToken/, for Canada https://ca.api.ovh.com/createToken/, and for the United States https://api.us.ovhcloud.com/createToken/.
3. Create the key with two rights. Give it a name and a description, then add GET /me/bill and GET /me/bill/* and nothing else. OVHcloud also lets you set a validity period; once it runs out, the consumer key stops working and you create a new key.
4. Paste the three values and refresh. The page gives you an application key, an application secret and a consumer key. Paste all three into the card and click Refresh.

A key belongs to the region it was created in. If you paste a European key into a card set to Canada, OVHcloud does not recognize it, and CostCompass asks you to check that the key was created in the region the card uses. A mistyped application secret gets a different message, asking you to paste the three values again.

Each line becomes a row named after the service OVHcloud bills on it, such as a Public Cloud project, a VPS or a domain, with one Tax row per invoice.

Amounts stay in the currency OVHcloud invoiced them in, with no exchange rate applied.

Each refresh reads this month’s and last month’s invoices. That keeps last month’s total complete, which is what the forecast is built from, even when the invoice for last month’s usage arrived only this morning. Nothing runs between your clicks: the numbers change when you refresh.

OVHcloud then counts alongside compute providers such as Cloudflare and RunPod, and alongside your AI providers, in one view; the tracking guide covers how that rollup works, and the guides index lists every provider.