Your invoice and your numbers, side by side.
Billed Periods puts what Azure and AWS actually invoiced next to the cost CloudOptify tracked, period by period, so finance can sign off on the numbers — and you can see straight away which month doesn’t add up.
Invoice against tracked cost
Every closed billing period shows usage, tax, credits, the invoiced total and the difference, per subscription and account.
Only real differences
Periods still running, invoices covering accounts you don’t track, and credits applied on the invoice itself are explained, not flagged.
The VAT your cost data never shows
Azure adds tax when the invoice is issued, so it never reaches an export. Billed Periods reads it from the invoice — for most agreements the only place it exists.
Know how exact each figure is
Every row says whether it comes from your billing data or is an estimate — and whether the official invoice is linked.
Clear next steps
If invoices can’t be read yet, you’re told the exact read-only permission to grant. Nothing else changes.
Does this match the invoice?
Sooner or later, every FinOps report meets that question from finance. It’s a fair question, and a surprisingly hard one to answer. Cost tools and invoices are built from the same billing data, but they rarely line up at a glance: invoices follow billing periods that don’t always run by calendar month, some credits are applied only on the invoice, a reservation bought upfront is billed in one month but usually reported across its term, and one payer invoice often covers accounts nobody asked you to track.
Billed Periods answers the question directly — so the conversations with finance start from numbers everyone already agrees on.
Invoice against tracked cost.
For every closed billing period, Billed Periods shows what CloudOptify tracked — usage, tax and credits — next to what Azure or AWS actually invoiced, and the difference between them.
Rows are grouped by the month they were billed, per Azure subscription and AWS connection. Expand any row to see the invoices behind it, with invoice numbers ready to copy into your finance system.
Red flags you can trust.
A reconciliation view is only useful if its red flags mean something. Billed Periods is careful about when not to compare:
The current period
Shown as in progress — never as a mismatch against an invoice that doesn’t exist yet.
Accounts you don’t track
An invoice covering more accounts than you track is listed, not compared — the gap would just be the accounts you left out.
Credits on the invoice
A credit applied on the invoice itself, such as a Visual Studio subscription’s monthly credit, is recognized and shown as a credit.
Upfront purchases
Reservation and savings-plan purchases count in the month they were billed — exactly as the invoice charges them.
When Billed Periods says a period differs, it’s worth a look.
How exact is each number?
Every row says where its figures come from. Figures from your billing export or Cost & Usage Report are the provider’s own billing data — the same data the invoice is produced from. Figures from the cost APIs are clearly marked as estimates. You always know which numbers you can hand to finance as they are.
Reading invoices needs one extra read-only billing permission. If a connection doesn’t have it yet, Billed Periods still shows your tracked cost and tells you the exact role or permission to grant — and to which identity. New AWS connections include it from the start, and nothing else about your connection changes.