Mapped without semantic loss
The source supplies the required meaning and Ledger preserves it in the FOCUS core.
Supported imports
A FOCUS-first financial core with provider-native evidence.
Ledger supports the formats teams can export today while keeping one normalized contract downstream. Every adapter declares what it supports, derives, preserves as an extension, or cannot safely interpret.
FormatStatusFinancial pathDetail retained
FOCUS 1.2 CSVProvider-neutralSupportedFOCUS suppliedStandard columns and extensions
AWS CUR 2.0 CSVNative adapterSupportedMapped to FOCUS coreAccounts, services, resources, SKU, Savings Plans
Azure Cost Management CSVActual cost exportSupportedMapped to FOCUS coreSubscriptions, resources, meters, regions, tags
Google Cloud detailed billingBigQuery snapshotSupportedMapped to FOCUS coreProjects, services, SKUs, resources, credits
Ledger native v1 JSONLInternal contractSupportedDirect normalized ingestionFOCUS core, origins, evidence, extensions
Parquet and hosted connectorsFuture delivery pathsRoadmapNot yet availableNo current claim
Why FOCUS comes first
A common vocabulary reduces translation without erasing provenance.
Ledger keeps FOCUS column names and meanings for the financial core. It does not invent a competing set of cost terms. Provider-native adapters map into that core and record field-level origins for every reported or derived value.
Read the FOCUS support documentationListCostPublic price before discounts
ContractedCostNegotiated price before adjustments
BilledCostAmount used for invoicing
EffectiveCostAmortized economic cost
Distinct values. Distinct origins. One explicitly selected reporting basis.
Adapter contracts
Support is a report, not a marketing adjective.
Each conversion produces machine-readable findings and a capability report tied to the adapter version.
Calculated by a declared method
The source fields and deterministic derivation method are retained with the normalized value.
Not present in this export
The optional detail remains absent rather than being filled with a misleading default.
Preserved, but blocks a full claim
Unknown monetary semantics are retained as evidence and surfaced for corrective action.
Native provider depth
Use provider detail where it makes a cost more explainable.
Savings Plans remain a calculation concern.
Covered usage, recurring and upfront fees, plan relationships, and unused commitment are normalized before a documented calculator distributes cost.
Export type is part of the evidence.
The supported actual-cost schema is detected explicitly. Billed and effective cost remain distinct, and unsupported variants fail with guidance.
Invoice timing remains visible.
Late-monetized usage, project and SKU context, credits, corrections, locations, labels, and tags retain source relationships.
What an operator sees
No silent drops between upload and report.
- 01Format detected
Source format, schema version, cost basis, object size, and checksum are persisted.
- 02Findings available
Object, row, field, requirement, and evidence locator make validation actionable.
- 03Capabilities declared
Supported, derived, unavailable, and unsupported semantics are counted and inspectable.
- 04Totals reconciled
All supported cost columns agree by currency before calculation begins.
Deliberate limits
Claims stop where support stops.
- FOCUS 1.2 CSV is supported; Parquet remains roadmap work.
- AWS support targets a documented CUR 2.0 configuration, not every historical CUR shape.
- Azure support targets actual-cost CSV, not an implied universe of export variants.
- Google Cloud input is a documented immutable snapshot of detailed billing data.
- Hosted pull connectors and provider credential storage are not currently part of the product.