FOCUS 1.4 and invoice reconciliation: matching cloud cost data to what accounts payable pays

In brief

Why cloud cost data rarely matches the invoice, what FOCUS 1.4's Invoice Detail and Billing Period datasets add, and a month-end routine for controllers.

Steve Elliott

Steve Elliott · · 7 min read


On this page
  1. Why don't cloud cost totals match the invoice?
  2. What do the Invoice Detail and Billing Period datasets add?
  3. How does the rounding variance tolerance work?
  4. What changed from FOCUS 1.2's InvoiceId?
  5. Which providers support FOCUS 1.4 invoice data?
  6. A month-end reconciliation routine
  7. An illustrative reconciliation
  8. Sources

Cloud cost data and the invoice disagree for ordinary reasons: the data is pulled before the billing period closes, tax usually sits only on the invoice, and millions of six-decimal rows don't sum to a two-decimal total. FOCUS 1.4, ratified on June 4, 2026, gives controllers the missing half of the match: an Invoice Detail dataset, a Billing Period dataset with open and closed status, and a formula for how much rounding difference to accept.

The catch, as of November 2026: the AWS, Microsoft, Google Cloud and Oracle documentation we checked shows no FOCUS 1.4 export; the newest version named is 1.2 (Microsoft's and Google's as previews). The 1.4 routine below still works today with each provider's native invoice data.

Why don't cloud cost totals match the invoice?

The causes the FOCUS spec and providers describe are mostly timing and scope:

  • The period is still open. FOCUS 1.4 marks a billing period Open or Closed. While it is open, "records may continue to be added or revised." Microsoft says Customer Agreement pending charges are estimates that exclude tax.
  • The invoice comes later. The FinOps Framework says invoices typically arrive "between 3 and 12 days after the end of the previous month," so teams may need to close on incomplete data, estimate, and reconcile with journal entries later.
  • Some charges are calculated after usage is final. AWS says it may update a finalized cost report for refunds, credits or support fees, and that support fees based on final usage appear on the sixth or seventh of the following month.
  • Tax sits on the invoice. The FOCUS Invoice Reconciliation feature notes that tax is typically excluded from the Cost and Usage dataset.
  • Corrections arrive after close. In 1.4, ChargeClass "Correction" flags a correction to a previously closed billing period, such as refunds and credit modifications.
  • Rounding. The FOCUS Billed Cost definition notes that cost data may carry six or more decimal places while invoices use two.
  • Some rows are billed by someone else, or not at all. BilledCost must be 0 for charges fully covered by one or more covering charges, such as a commitment purchase, and for charges from entities not responsible for invoicing. Reconcile on BilledCost, the column FOCUS ties to the invoice, not EffectiveCost; the FOCUS-to-TBM crosswalk explains the difference.

What do the Invoice Detail and Billing Period datasets add?

Before 1.4, FOCUS described only the cost side of the match. The FinOps Foundation calls 1.4 "the first FOCUS release that lets FinOps teams interface with accounts payable."

DatasetWhat the spec says it holdsColumns a controller will useWhen it must be present
Invoice Detail (new)The financial record of charges as they appear on invoicesInvoiceId, InvoiceDetailId, BilledCost, ChargeCategory, InvoiceIssueStatus, ReferenceInvoiceId, PaymentDueDate, PaymentTerms, PurchaseOrderNumber, PaymentCurrencyBilledCostWhen the invoice issuer supports payable invoices
Billing Period (new)The intervals and status of an invoice issuer's billing cyclesBillingPeriodStart, BillingPeriodEnd, BillingPeriodStatus, InvoiceIssuerNameWhen the invoice issuer supports payable invoices
Cost and Usage (changed)Granular chargesInvoiceId, new InvoiceDetailId, BilledCost, ChargeCategory, ChargeClassThe core FOCUS dataset
  • Invoice Issue Status is Open (provisional, subject to change), Issued (a valid financial obligation with final data) or Voided (retracted). It must not move from Issued back to Open unless the customer requested or approved it.
  • Billing Period Status works the same way: a closed period can be reopened only to apply corrections, with customer request or approval. The spec says corrections are typically recorded in a later open period instead.
  • Reference Invoice ID is never null. On a line that adjusts an earlier invoice, it carries that invoice's ID, which gives credits, refunds and corrections a traceable link to the original bill.

Invoice Detail must include every invoice line item with a non-zero BilledCost. The two datasets join on InvoiceIssuerName and InvoiceId, optionally InvoiceDetailId, and the spec warns that one or both sides will usually need aggregating first.

How does the rounding variance tolerance work?

A new 1.4 appendix sets how far summed cost data may drift from an invoice before it counts as a break:

Tolerance = MAX(100 × Subunit, SQRT(Rows) × 0.5 × Subunit)

Rows is the number of Cost and Usage rows in the aggregation, scoped by invoice issuer, invoice ID and, where used, invoice detail ID. Subunit is the smallest unit of the billing currency: 0.01 for US dollars, 1 for yen. So the floor is $1.00 or ¥100, and the allowance grows with the square root of the row count.

The appendix doesn't label itself normative, but the Billed Cost column makes it binding: once an invoice is issued, summed BilledCost for an InvoiceId and InvoiceIssuerName must not differ from the payable amount by more than this tolerance.

In the spec's examples, a five-row invoice $5.00 short fails against $1.00: a charge is missing. A million-row invoice $15.00 off fails against $5.00, which the spec attributes to systematic truncation bias.

What changed from FOCUS 1.2's InvoiceId?

FOCUS 1.2, announced in June 2025, introduced InvoiceId so each charge, credit or refund could be traced to its invoice. The table compares its 1.3 rules, the last before 1.4, with 1.4.

FOCUS 1.3FOCUS 1.4
InvoiceId feature levelRecommendedConditional: must be populated when the charge belongs to an issued or pre-generated provisional invoice
Match ruleSummed BilledCost per InvoiceId must match the invoice's payable amountAfter issuance, within the rounding variance tolerance; before issuance, may differ
Line-level linkNoneInvoiceDetailId, unique within an InvoiceId
Invoice side of the matchOutside FOCUSInvoice Detail and Billing Period datasets
Invoice handling rulesInvoice Handling attributeAttribute removed

In our view, an exact-match rule is hard to meet across millions of rows; the tolerance makes the test practical. The spec lets invoice IDs be generated before issuance but doesn't require it, and AWS leaves bill/InvoiceId blank until a line item is final. A blank ID on day two is not necessarily a defect.

Which providers support FOCUS 1.4 invoice data?

As of November 2026, none of the four providers we checked documents it:

  • AWS. The Data Exports user guide lists FOCUS 1.2 and FOCUS 1.0 tables.
  • Google Cloud. Its FOCUS export to BigQuery entered Preview on June 8, 2026, with columns up to version 1.2. The conformance table lists Invoice ID as not provided.
  • Microsoft. The conformance summary covers a FOCUS 1.2-preview dataset and notes that InvoiceId isn't supported for EA accounts.
  • Oracle. OCI's cost report docs say its FOCUS reports conform to the spec without naming a version, and the FOCUS columns they list include no InvoiceId.

Until 1.4 exports arrive, the invoice side comes from native files, such as the bill/InvoiceId column in the AWS Cost and Usage Report. For a Customer Agreement, Microsoft says the usage file is typically ready within 72 hours of the invoice being issued.

A month-end reconciliation routine

This routine uses 1.4 terms; substitute native equivalents where a provider lacks a column. It is a starting point to agree with your controller, not accounting advice; confirm accrual and restatement treatment with your advisers.

  1. Day 1 to 2: label the data provisional. Pull cost and usage for the month and check Billing Period Status. Figures from an Open period enter the close as estimates, under the controller's accrual approach.
  2. When invoices issue: refresh. Wait for Invoice Issue Status Issued, then pull Cost and Usage, Invoice Detail and Billing Period again. Drop any invoice marked Voided.
  3. Match each invoice, excluding tax. For each InvoiceIssuerName and InvoiceId (the join keys the Invoice Detail dataset names), sum BilledCost on both sides with ChargeCategory not equal to Tax, and full outer join the totals. The spec's example query does this per InvoiceId. An invoice on only one side is a finding.
  4. Test the variance against the tolerance. Inside it, close the invoice. Outside it, look for missing charges first, then systematic rounding.
  5. Reconcile tax separately. Split Invoice Detail into tax, non-tax and total payable, and tie the total to what accounts payable is paying.
  6. Trace credits and corrections. Find ChargeClass "Correction" rows and follow Reference Invoice ID back to the invoice each adjusts. Decide with the controller whether to book them in the current month or restate.
  7. Check currency. Where payment currency differs from billing currency, the spec uses PaymentCurrencyInvoiceDetailId to derive an effective exchange rate. Compare it with the rate you booked.
  8. Watch closed periods. The spec says FinOps tools and reporting engines should detect Billing Period Status transitions and trigger updates to allocation, chargeback and reporting. Rerun chargeback when that happens.

An illustrative reconciliation

The numbers are made up. Take one November invoice from one issuer, billed in US dollars, backed by 2.4 million cost and usage rows. The tolerance is the larger of $1.00 and √2,400,000 × 0.5 × $0.01, which is about $7.75.

StepAmount
Cost and usage BilledCost pulled December 2, period Open$1,171,050.12
Late usage rows added before issuance+$9,820.55
Fees calculated on final usage, billed on this invoice (timing varies by provider)+$11,734.20
Credit rows added at invoicing−$4,500.00
Cost and usage BilledCost after issuance, excluding tax$1,188,104.87
Invoice Detail BilledCost, excluding tax$1,188,108.00
Variance$3.13, inside $7.75: pass
Tax lines on Invoice Detail+$95,048.64
Total payable$1,283,156.64

The December 2 pull was $17,057.88 short of the issued pre-tax total, hence the provisional label. The $3.13 variance would fail a 1.3-style exact match; under 1.4 it passes.

We think invoice data in FOCUS earns its keep when reconciled cost flows straight into the showback and chargeback numbers and the operating model that funding decisions are made from.

Sources

Frequently asked questions

Does the FOCUS Cost and Usage dataset include tax?

Usually not. The FOCUS 1.4 Invoice Reconciliation feature notes that tax is typically excluded from Cost and Usage, and its example query matches invoices with tax left out. Tax lines appear in the new Invoice Detail dataset, so reconcile pre-tax amounts first, then tie tax and the total payable from Invoice Detail to what accounts payable pays.

What is the FOCUS rounding variance tolerance?

It is the largest acceptable gap between summed BilledCost and an issued invoice: the greater of 100 currency subunits and half the square root of the row count, in subunits. For US dollars the floor is $1.00. A million-row invoice gets $5.00. Gaps beyond it point to missing charges or systematic rounding, not noise.

Can we reconcile cloud invoices with FOCUS 1.4 today?

Not fully with the major cloud providers. As of November 2026, AWS, Google Cloud, Microsoft and Oracle documentation shows no FOCUS 1.4 export and no Invoice Detail or Billing Period datasets. You can apply the 1.4 routine and tolerance now, using each provider's native invoice data for the invoice side, and switch as 1.4 exports appear.

How should corrections to a closed billing period be handled?

FOCUS 1.4 marks them with ChargeClass "Correction" and says they are typically recorded in a later open period rather than by reopening the closed one, which needs customer request or approval. Invoice Detail's Reference Invoice ID links the adjustment to the original invoice. Whether to book it currently or restate is a policy question for your controller.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on FinOps & Cloud

FOCUS, commitments, shared cost.