An InvoiceReconciliation property references documentation explaining how an API provider's billing data maps to issued invoices — including how to match billing export rows to invoice line items using invoice identifiers. FOCUS 1.2 introduced dedicated Invoice ID columns specifically to enable this reconciliation. For enterprise API consumers, the ability to tie API usage records to financial invoices is a compliance and audit requirement. Linking reconciliation documentation makes this mapping discoverable alongside the API.

Also known as: Invoice Mapping, Billing-to-Invoice Reconciliation, Invoice Line Item Matching

Example

- type: InvoiceReconciliation
  url: https://developers.example.com/billing/reconciliation

Standards

• FinOps Foundation FOCUS — FinOps Open Cost and Usage Specification
• FinOps Foundation FOCUS Specification (latest, Invoice ID columns)
• ISO ISO 20022 — Financial Services Universal Message Scheme
• ASC X12 ASC X12 EDI 810 — Invoice
• CEN EN 16931 — European e-invoicing semantic data model
• OpenPeppol Peppol BIS Billing 3.0
• OASIS UBL 2.1 — Universal Business Language
• schema.org schema.org Invoice

Media Types

• application/xml — Common for UBL, Peppol BIS, and EN 16931 invoice payloads.
• application/json — Used by API-delivered invoice and reconciliation endpoints.
• application/pdf — Human-readable invoice delivery; reconciliation typically requires a structured companion file.
• text/csv — RFC 4180 — Common for FOCUS billing export rows that join to invoices by InvoiceId.

Governance Rules

• invoice-id-present (FOCUS Specification) — Billing rows must include the InvoiceId field to enable reconciliation to a specific invoice document.
• invoice-issuer-identified (FOCUS Specification) — The InvoiceIssuer should be identifiable so resellers and marketplace flows are unambiguous.
• billing-period-aligned (FOCUS Specification) — BillingPeriodStart / BillingPeriodEnd must align with the invoice period for one-to-one reconciliation.
• currency-matches-invoice (FOCUS Specification) — BillingCurrency on the row must match the currency of the issued invoice.

Risk & Compliance

Compliance:

• SOX — invoice reconciliation is a financial control surface
• SOC 2 — billing accuracy assertions rely on reconciliation evidence
• EU VAT Directive — e-invoicing mandates apply to many cross-border flows
• GDPR — invoices typically contain controller-identifiable data

Security: Invoice documents disclose negotiated pricing, account identifiers, and sometimes contract terms; restrict access to billing administrators.

Tools

• FOCUS Specification — Specification
• Peppol — e-invoicing network
• UBL — Document standard
• GoBD-compliant archivers — Regional archive tooling
• FOCUS Validator — Conformance validator (Apache-2.0)

Suggested Metrics

• reconciled_rows_pct — Percentage of billing-export rows successfully matched to invoice line items.
• invoice_variance_value — Aggregate monetary variance between summed billing rows and invoice totals.
• unmatched_invoice_lines — Count of invoice line items with no corresponding billing-export rows.
• reconciliation_lag_days — Days between invoice issuance and availability of fully reconciled detail rows.

Example Implementations

• AWS — AWS Cost and Usage Report includes invoice_id and bill_invoicing_entity for reconciliation.
• Microsoft Azure — Azure billing exports expose invoice number on each charge row.
• Google Cloud — Cloud Billing BigQuery export includes invoice.month and invoice metadata.
• Stripe — Stripe Invoicing exposes invoice IDs and line items via the Invoices API.

Related Properties

• Focus billing export
• Focus conformance report
• Focus contract commitments
• Finops framework
• Billing
• Pricing

Tags

• Invoice
• FinOps
• Billing
• Reconciliation

All Community Properties