A FocusConformanceReport property references a published document describing how a provider's billing data maps to the FOCUS schema — including any gaps between native fields and the FOCUS column definitions. The FinOps Foundation's certified conformance program requires providers to publish a native-to-FOCUS column mapping and a conformance gap report. Linking this document makes verifiable billing data compatibility discoverable by FinOps tools and enterprise procurement teams.

Also known as: FOCUS Conformance Summary, FOCUS Mapping Report, FOCUS Gap Analysis

Example

- type: FocusConformanceReport
  url: https://developers.example.com/billing/focus-conformance

Standards

• FinOps Foundation FOCUS Conformance Program
• FinOps Foundation FOCUS — FinOps Open Cost and Usage Specification
• FinOps Foundation FOCUS Specification (latest)
• FinOps Foundation FOCUS Conformance Summary template

Governance Rules

• conformance-version-declared (FOCUS Conformance Program) — Report must state the FOCUS specification version it was assessed against.
• native-to-focus-mapping (FOCUS Conformance Program) — Report must include a native-column to FOCUS-column mapping table.
• gap-disclosure (FOCUS Conformance Program) — Any unsupported or partially supported FOCUS columns must be enumerated with rationale.
• optional-columns-listed (FOCUS Conformance Program) — Optional columns supported by the provider should be explicitly listed.

Risk & Compliance

Compliance:

• SOX — conformance evidence supports auditability of billing transformations
• SOC 2 — supplier-management evidence for FinOps tooling vendors

Security: Conformance reports are typically public and reveal billing schema structure; they do not themselves expose customer data but may reveal which discount mechanics a provider supports.

Tools

• FOCUS Validator — Conformance validator (Apache-2.0)
• FOCUS Specification — Specification
• FOCUS Conformance Program — Certification program
• FinOps Foundation — Standards body

Suggested Metrics

• focus_columns_conformant — Number of FOCUS columns the export fully satisfies.
• focus_columns_partial — Number of columns with partial support documented in the gap report.
• focus_columns_unsupported — Number of mandatory FOCUS columns the provider does not yet produce.
• conformance_assessed_version — FOCUS specification version against which the report was assessed.

Example Implementations

• AWS — AWS publishes FOCUS 1.0 conformance documentation for its Data Exports.
• Microsoft Azure — Microsoft Cost Management publishes a FOCUS conformance summary.
• Google Cloud — Google Cloud Billing publishes its FOCUS-aligned mapping documentation.
• Oracle Cloud — OCI publishes a FOCUS conformance summary for its billing export.

Related Properties

• Focus billing export
• Focus contract commitments
• Invoice reconciliation
• Finops framework
• Opencost specification
• Compliance

Tags

• FOCUS
• FinOps
• Conformance
• Billing

All Community Properties