CoreFinOps Docs
On this page

Reports and Exports

Share migration and FinOps results without losing financial provenance.

CoreFinOps reporting is intended for migration leadership, FinOps teams and finance partners. Reports should preserve the period, currency, measure, scope, source freshness and approval or verification state behind every figure.

Core report catalog

ReportIntended decision
Migration EconomicsCompare source, transition and target costs, TCO and payback.
DecommissionProve technical and financial exit and explain residual stranded obligations.
Value RealizationShow expected, realized and verified amounts with evidence lineage.
Application Financial SummaryConsolidate allocated cost, legacy/target/transition context and outcomes for one application.
Migration Portfolio Financial SummaryReview wave and portfolio economics, overlap and source exit exposure.
CoreFinOps ROICommunicate attributable/verified value without unverifiable ROI claims.

The repository implements CSV and XLSX export paths for supported reports; availability and columns should match the installed release.

Reports are not new evidence

Report generation time is different from the timestamp of CUR ingestion, inventory observation or verification. Exporting a record to a spreadsheet does not upgrade an estimated figure to realized savings.

Financial reconciliation

For comparable scope/period/currency/measure, totals must agree with the authoritative Overview/Explorer allocation or verified Value Ledger result. Avoid mixing historical calculated values with current application labels as though they were historical evidence.

Sharing and access

Reports can contain account identifiers, application ownership and financial information. Use authorized workspace access and approved sharing channels. Export permissions, plan quotas and retention rules are enforced by the server where configured.

Suggested review checklist

  • Report date, period, measure and currency are all visible.
  • Scope, missing sources and overlap handling are documented.
  • Verification provenance is labeled for each figure.
  • No modeled target run rate is presented as an observed bill.

Important

Never present a modeled target run rate as an observed AWS bill. The two must remain labeled differently in any export or presentation.