FOCUS 1.4: invoice reconciliation and commitment detail
Published and reviewed: 1 October 2026
Scope my cloud cost reviewFOCUS 1.4 was ratified on 4 June 2026 and adds the Invoice Detail and Billing Period datasets.

On this page
What FOCUS 1.4 contains
The FOCUS Steering Committee ratified version 1.4 on 4 June 2026. The FinOps Foundation introduced it on 10 June 2026 and counts 2 new datasets, 47 columns, 6 attributes, 17 glossary entries and 2 supported features. The parts that affect a buyer:
- Invoice Detail dataset: the charges as they appear on issued invoices, including payment currency, payment terms, due date and purchase order number.
- Billing Period dataset: billing period boundaries and status that follow the invoice issuer, for periods that do not match calendar months.
- Contract Commitment grows from 13 to 30 columns, and a new Commitment Program Eligibility Details column on Cost and Usage records which charges could be covered by a commitment program.
- One recognition rule for covering charges (for example a reservation prepayment) and covered charges (the usage that draws on it), so that billed cost and effective cost sum to the same total.
- Four integrity attributes: correction handling, delivery handling, dataset completeness and dataset configuration.
The release also removes the Provider Name and Publisher Name columns that version 1.3 had deprecated. The Foundation describes the upgrade as having zero incompatible changes. Its article also said that validator support for 1.4 would come later in the third quarter of 2026, so the publication of the specification and a generator that implements it are two different events, and the status of the validator is worth checking.
Joining usage to invoices
The new Invoice Reconciliation feature joins Invoice Detail to Cost and Usage on the invoice identifier. Invoice Detail ID allows line-by-line matching, and a Payment Currency Invoice Detail ID links records when billing and payment currencies are tracked at different levels of detail. Finance also gets tax lines, which are typically excluded from Cost and Usage.
The specification adds a Rounding Variance Tolerance entry, which defines how to compare costs held with many decimals against invoice totals rounded to two. Agree the tolerance with your accounts payable team before acceptance, otherwise a reconciliation will fail on cents and lose the trust of the people who use it.
| Question for finance | Where the answer sits in FOCUS 1.4 |
|---|---|
| Does this charge appear on an issued invoice? | Invoice Detail dataset, joined to Cost and Usage on the invoice identifier |
| Which period does the invoice cover? | Billing Period dataset |
| Could this usage have been covered by a commitment? | Commitment Program Eligibility Details column on Cost and Usage records |
| What does the commitment cost, and when does it end? | Contract Commitment dataset, now 30 columns |
Commitment detail and eligibility
With 30 columns, the Contract Commitment dataset can answer questions that used to require a portal or a contract PDF: the payment schedule, whether the commitment is usage based or spend based, the discount rate it carries. The Contract Applied column also receives a formal JSON schema.
Eligibility matters for decisions about new purchases. The Foundation's example is coverage: you can now compute how much spend could have been covered, as well as how much was. Ask any provider proposing a commitment review to show the eligible spend and the coverage rate from the export itself, and to state what happens to the figure if demand falls. The commitment break-even calculator helps test that downside case.
Corrections and deliveries
Correction handling has three documented styles: replacement (a full snapshot overwrites the previous one), delta (records carry the net change) and ledger (explicit reversals and re-entries keep an audit trail). Delivery handling distinguishes overwrite from append, and a provider can overwrite an open period and append once it closes. The specification bars any implementation that would force practitioners to deduplicate records.
What to prepare and to ask
- Request Invoice Detail and Billing Period exports from each provider, or a written statement that they are not available yet.
- Compare one closed month: invoice total, sum by invoice identifier, difference, explanation.
- Keep the previous export next to the new one until effective cost baselines match.
- Write the dependency into the scope if a required dataset is missing, instead of describing the whole pipeline as upgraded.
The FOCUS implementation checklist supplies acceptance wording for each of these tests.
Primary sources
The FinOps Foundation article introducing FOCUS 1.4, read in full for this page:
Continue your review
Get support on my project
A specialist in the subject reviews your request and sends you a quote.
Get support on my project