# Make cloud commitments traceable before advising

**Cloud Waypoint can apply FinOps Foundation allocation, invoicing and review practices through five advisory artifacts, using existing client-approved evidence.** Keep invoice liability, internal cost allocation and enterprise commitment recognition as three linked but separate views. A matched billing ledger proves neither contractual eligibility nor provider-confirmed drawdown. FOCUS supplies common datasets and semantics, **not a billing mechanism**. Federal applicability requires separate contracting, finance, security and data-handling decisions. This extends existing Foundations and Enterprise Architecture & Operations conversations; it creates no standalone offering, tooling installation, purchase recommendation or ROI claim. ([FinOps invoicing practice](https://www.finops.org/framework/capabilities/invoicing-chargeback/), [FOCUS purpose](https://focus.finops.org/what-is-focus/))

Technical advisory research • **6 October 2026** • Proposed practices and roles, not accepted client policy. Public-source findings; no client billing records or agreements inspected. Source notes below preserve versions and limitations.

## Ownership must survive resources and incomplete tags

The Foundation combines account hierarchies, resource metadata and shared-cost rules. Recommend a small dictionary: `service_id`, `owner_team_id`, `environment`, protected `financial_ref`, plus `lifecycle_class` and conditional `expires_at`. Map the financial reference to cost center and, where applicable, fund/year and contract/CLIN inside the approved boundary. These are proposed keys, not a Foundation or federal mandate. ([Allocation guide](https://www.finops.org/wg/cloud-cost-allocation/))

**Tags do not cover every invoice charge.** Annual SaaS, shared licenses and unsupported resources need account/agreement mappings and explicit residuals. AWS Marketplace supports particular inherited or vendor-metered tags, but upfront contract commitments lack that metered-tag evidence. Verify activation, propagation and backfill rather than assuming historical coverage. ([AWS tagging](https://docs.aws.amazon.com/marketplace/latest/buyerguide/cost-allocation-tagging.html))

For ephemeral resources, recommend durable request/run, parent service, resource identity, creation/deletion timestamps and effective-dated ownership records. Attribute late charges to the service-period owner; preserve storage, network and other surviving dependencies. Missing history remains unallocated. Expiry triggers review, not deletion authority. This adapts the Foundation’s treatment of continuously changing resources. ([Allocation guide](https://www.finops.org/wg/cloud-cost-allocation/))

Start with showback unless existing approved practice dictates otherwise. Finance decides whether chargeback posts expenses into official budgets; it is not an inevitable maturity upgrade. Specify direct/shared/central/unallocated treatment, cost basis, allocation driver, effective date, disputes and corrections. Allocated amounts plus residual must conserve the chosen source total. ([Invoicing and chargeback](https://www.finops.org/framework/capabilities/invoicing-chargeback/))

## Common data enables comparison, not common contract rights

**FOCUS 1.4, ratified 4 June 2026**, adds Invoice Detail and Billing Period datasets; 1.3 introduced Contract Commitment. Record the specification release separately from the actual provider export/schema version, supplied datasets, optional fields, transformation and gaps. Publication does not prove implementation or entitlement. ([Release history](https://focus.finops.org/what-is-focus/), [Conformance FAQ](https://focus.finops.org/faqs/))

Use billed cost for invoice reconciliation and effective cost for a separately labeled consumption view; never add both. Preserve currencies, native identifiers and correction semantics. FOCUS’s marketplace pattern compares service provider, host provider and invoice issuer, but its sample query is only a starting point: retain currency separation, adjustments and unknown provider identities. Neither normalized eligibility fields nor ledger matching establish enterprise drawdown. Enterprise minimum-spend agreements remain distinct from **Savings Plans, Reserved Instances and CUDs**. ([Marketplace pattern](https://focus.finops.org/docs/use-cases/v1-4/track-marketplace-purchases-across-providers/), [Cost semantics](https://focus.finops.org/docs/specification/v1-4/columns/cost-and-usage/effective-cost/))

## Provider rules require transaction-level evidence

| Provider | Billing evidence for advisory reconciliation | Enterprise commitment boundary |
|---|---|---|
| AWS | Existing CUR/CUR 2.0: billing entity, payer, invoice issuer/ID, seller of record, product, charge type, currency; validate agreement/offer joins. Blank invoice IDs are provisional. ([CUR bill fields](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2-bill.html)) | **No universal percentage established.** Apply the executed agreement’s products, accounts, deployment, cap and timing rules; seek AWS confirmation. Government eligibility and commitment treatment require the receiving organization’s executed agreement and procurement authority. |
| Azure | Marketplace cost details and invoices, then MACC balance/events; direct EA/MCA tracking has billing-role requirements. ([Cost details](https://learn.microsoft.com/en-us/marketplace/cost-management-for-azure-marketplace-purchases), [MACC tracking](https://learn.microsoft.com/en-us/azure/cost-management-billing/benefits/macc/track-consumption-commitment)) | Eligible offer, linked agreement/subscription, Azure-portal purchase and active term: **100% pretax when invoiced**. Hybrid/on-premises license use is excluded; Marketplace presence alone is insufficient. ([Benefit rules](https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit), [FAQ, 24 July 2026](https://learn.microsoft.com/en-us/marketplace/macc-frequently-asked-questions)) |
| Google Cloud | Billing exports: account/project, invoice month, SKU, transaction type, seller where supplied, credits/adjustments; seek agreement-specific Google confirmation. ([Detailed schema](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage)) | **100% eligible-spend rate is not unlimited:** published policy caps cumulative contribution at **25% of the corresponding minimum commitment**, with no excess rollover. Exclusions, channel and installment rules apply, subject to actual governing agreement/policy. ([Rates](https://docs.cloud.google.com/marketplace/docs/commit-drawdown), [Policy, 27 May 2025](https://cloud.google.com/terms/marketplace/commit-policy)) |

Recommend a monthly sequence: reconcile finalized invoices and revisions; allocate under the approved rule; assess each candidate’s agreement, offer, channel, period and cap; compare with provider-confirmed recognition; retain unresolved differences. Keep signature, activation, service, invoice, payment and recognition dates separate. Unknown eligibility stays outside confirmed totals; renewals and refunds reopen review. This is an advisory control inferred from the provider rules, not a universal posting timetable.

## Five process artifacts fit the existing advisory scope

These are recommended designs, not new contracted deliverables. All roles below are **proposed, not accepted**; Charlie facilitates and interprets, while client authorities supply decisions and evidence.

| Artifact | Minimum content and proposed receiving roles |
|---|---|
| Dictionary | Field purpose, values, sensitivity, required conditions, native tag/label equivalents and verification gaps. Service/platform stewards propose; finance/security review. |
| Allocation policy | Cost basis, shared pools, drivers, residuals, corrections and dispute/chargeback approval. Finance proposes policy; service owners confirm beneficiaries. |
| Mapping | Versioned source-to-common-field crosswalk, account/agreement-to-financial reference, effective-dated lifecycle ownership and missing-field register. Platform/data stewards supply; finance validates meaning. |
| Reconciliation/eligibility worksheet | Invoice variance, native lineage, agreement/version, offer/channel, period, rate/cap, recognition evidence and candidate/confirmed/excluded/unknown states. Finance and contracting review; provider confirms drawdown. |
| Exceptions/review cadence | Named issue owner, evidence gap, due date, disposition and correction history; monthly close plus renewal/policy-change review. Proposed client FinOps coordinator convenes finance, procurement and operations. |

Federal application requires evidence of the buyer, contract vehicle, funding/period, product/plan, cloud partition and authorized deployment, applicable agency/FedRAMP/DoD requirements, and permitted billing-metadata handling. **Commercial eligibility, Government availability and workload authorization are separate determinations.** GovCloud documentation warns against export-controlled metadata; Azure Government documentation has dated catalog/private-offer limits; Google’s commercial policy establishes no agency entitlement. ([AWS GovCloud](https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/govcloud-marketplace.html), [Azure Government](https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-manage-marketplace-partners), [Google policy](https://cloud.google.com/terms/marketplace/commit-policy))

Use these artifacts within existing FIN-1–FIN-5 evidence and the four reports. A later, separately authorized tabletop can test a deleted resource, corrected invoice and unconfirmed commitment contribution. Adequate existing client practice should replace proposed templates; missing authority or evidence narrows the advice. The current rehearsal, code and SOW remain untouched.

## Source notes and limits

### Basis, dates and unresolved authority

Read all four notes in `research_notes/FinOps marketplace commitment planning/` (`finops.md`, `aws.md`, `azure.md`, `google.md`), the prior `reports/FinOps and AI economics extension.md`, and its four notes (`repository.md`, `federal-finops.md`, `ai-economics.md`, `tools-and-scope.md`). Marketplace notes govern this extension where they differ. Current portfolio P-48’s **6 October 2026 consolidation** supersedes older module counts: Foundations plus four extensions; operations-focused AI workshops sit within Service-AIOps. This report proposes no change to that suite, the four reports, or **30 requests / 51 positions / 10 domains / 53 workstreams**. ([Portfolio authority](https://github.com/chas450g-beep/portfolio/blob/main/PORTFOLIO.md#p-48--charlies-sustainable-consulting-roadmap-through-retirement-2026-10-03), [Canonical FIN definitions at the prior inspected revision](https://github.com/chas450g-beep/cloud-waypoint/blob/ef9ae5877e8ae784ed2344ddc89a65a285141918/src/domain-workstreams.js#L99))

Research cutoff/retrieval is **6 October 2026**. Policy-sensitive release/rate/eligibility claims were selectively rechecked against primary sources during synthesis; this is not comprehensive policy or provider certification. Google’s rates endpoint failed in the web reader but its official HTML was retrieved directly. Dates below are publisher dates recorded in the notes or rechecked page, not retrieval dates substituted for publication. No provider export version or client conformance was established. No contracts, entitlement, government authorization or actual drawdown were examined.

| Source family | Version/date and material qualification |
|---|---|
| FinOps Foundation | [Allocation guide](https://www.finops.org/wg/cloud-cost-allocation/) and [invoicing capability](https://www.finops.org/framework/capabilities/invoicing-chargeback/): living advisory guidance. Notes disagree on whether a March 16, 2026 update was visible for the guide; use the retrieval cutoff, not a certified revision. |
| FOCUS | [Release record](https://focus.finops.org/what-is-focus/): 1.4 ratified June 4, 2026; 1.3 December 5, 2025. The page still describes 1.4 validator support as forthcoming in Q3; elapsed time does not prove delivery. [FAQ](https://focus.finops.org/faqs/) requires version-specific conformance and allows configured dataset subsets. |
| AWS | CUR and Marketplace documentation are rolling pages without established update dates. [Procurement dashboard article](https://aws.amazon.com/blogs/awsmarketplace/centralized-software-and-ai-agent-procurement-visibility-with-aws-marketplace-single-pane-of-glass-dashboard/) published October 29, 2025. Customer-specific commercial contract example omitted from this federal edition; no government eligibility is inferred. |
| Microsoft | [Benefit guidance](https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit) and [cost management](https://learn.microsoft.com/en-us/marketplace/cost-management-for-azure-marketplace-purchases): September 25, 2025; [FAQ](https://learn.microsoft.com/en-us/marketplace/macc-frequently-asked-questions): July 24, 2026; [MACC tracking](https://learn.microsoft.com/en-us/azure/cost-management-billing/benefits/macc/track-consumption-commitment): March 20, 2026. [Government page](https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-manage-marketplace-partners): December 31, 2021; verify current offering before reliance. |
| Google | [Commitment policy](https://cloud.google.com/terms/marketplace/commit-policy): last modified May 27, 2025; [rates](https://docs.cloud.google.com/marketplace/docs/commit-drawdown) and [private offers](https://docs.cloud.google.com/marketplace/docs/offers/accepting-private-offer): September 30, 2026 in notes. [Export overview](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery): October 6, 2026; [detailed schema](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage): October 5, 2026 in notes. These dates do not establish a client’s incorporated policy edition. |

### Reconciliation needs native fields and separate evidence states

For AWS CUR 2.0, preserve `bill_billing_entity`, `bill_invoice_id`, `bill_invoicing_entity`, `bill_payer_account_id`, `line_item_legal_entity`, `line_item_product_code`, `line_item_line_item_type`, cost/currency and usage-period fields. Net unblended cost is conditional; resource IDs can be missing. Seller of record, invoice issuer, publisher and listing ID are different identities. Validate mappings against actual legacy CUR or CUR 2.0 headers; no export migration is recommended. ([Bill fields](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2-bill.html), [Line-item fields](https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2-line-item.html))

Azure EA uses PartNumber/PublisherName/PlanName/ChargeType; MCA supports InvoiceId/PublisherName/ChargeType. MACC events provide invoice/decrement/balance evidence, but this research establishes no universal per-line join or posting-lag SLA. Google’s `transaction_type` can be missing on nonregular costs; `seller_name` is not universal. Its `THIRD_PARTY_RESELLER` value describes Google reselling third-party services, not proof of the customer’s authorized-reseller route. Google CUD subscription fields describe discount coverage, not enterprise minimum-spend retirement. No authoritative enterprise drawdown API was established in this bounded review; that does not mean none exists. ([Azure details](https://learn.microsoft.com/en-us/marketplace/cost-management-for-azure-marketplace-purchases), [MACC events](https://learn.microsoft.com/en-us/azure/cost-management-billing/benefits/macc/track-consumption-commitment), [Google schema](https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage))

Proposed worksheet controls: identify invoice issuer/account/ID/period/currency; retain original evidence, row identity, source revision and mapping version; aggregate invoice and usage records independently before joining; preserve taxes, support, discounts, credits and refunds. Apply replacement, delta or reversal/re-entry semantics explicitly, avoiding duplicate imports and provider/reseller double counting. Finance sets tolerances and accepts close. Maintain **eligibility** (confirmed eligible/excluded/unknown) separately from **recognition** (candidate/awaiting confirmation/confirmed/reversed), with evidence and reviewer for each. A matched invoice can remain unknown for commitment purposes. ([Invoice Detail](https://focus.finops.org/docs/specification/v1-4/datasets/invoice-detail/), [Correction handling](https://focus.finops.org/docs/specification/v1-4/attributes/correction-handling/))

### Eligibility qualifications must travel with every estimate

AWS: confirm account, region, eligible-fee, tax/credit and annual-period conditions in the receiving organization’s executed agreement; no reusable percentage is established. Marketplace now includes externally hosted SaaS; a deployment badge is screening evidence, not contractual approval. Upfront recognition and posting lag remain agreement-specific unknowns. ([AWS procurement article](https://aws.amazon.com/blogs/awsmarketplace/centralized-software-and-ai-agent-procurement-visibility-with-aws-marketplace-single-pane-of-glass-dashboard/))

Microsoft: benefit guidance says exclusively Azure use while the FAQ says primarily hosted in Azure; both exclude hybrid/on-premises deployment. Do not resolve that wording difference by broadening eligibility. Credit-card Marketplace checkout does not qualify. Final-month rules, SaaS activation, subsequent installments and refunds require review; earlier ineligible spending is not retroactively eligible. Partner benefit purchases cannot consume Azure prepayment; Microsoft credits and purchased prepayment have separate MACC treatment that must not be counted twice. ([Benefit guidance](https://learn.microsoft.com/en-us/marketplace/azure-consumption-commitment-benefit), [FAQ](https://learn.microsoft.com/en-us/marketplace/macc-frequently-asked-questions), [Credit/prepayment treatment](https://learn.microsoft.com/en-us/azure/cost-management-billing/benefits/macc/track-consumption-commitment))

Google: the rate applies at procurement/renewal. Payments covering installments longer than 12 months are prorated; the cap applies across the corresponding commitment, not independently per product. Post–June 8, 2025 reseller purchases require customer association and exclusion from reseller-held commitments. Excluded spend includes Maps, Ads, non-Google-hosted services, nonparticipating resale, purchaser/affiliate-owned services and professional services. Contract scope, amendments, currency, refunds and taxes still require actual evidence. Private-offer activation timing is not drawdown timing. ([Policy](https://cloud.google.com/terms/marketplace/commit-policy), [Exclusions](https://docs.cloud.google.com/marketplace/docs/commit-drawdown), [Offer mechanics](https://docs.cloud.google.com/marketplace/docs/offers/accepting-private-offer))

### Federal applicability remains an evidence dependency

AWS documents a restricted GovCloud catalog and commercial-account dependencies, not blanket federal drawdown eligibility. Azure’s dated Government page supports private plans but says private offers are unsupported; this warrants current confirmation, not either blanket eligibility or blanket exclusion. Its publication requirements do not establish workload authorization. Google’s cited commercial sources establish no federal contract vehicle or agency entitlement. ([GovCloud limits](https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/govcloud-marketplace.html), [Government publishing](https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-manage-marketplace-partners), [Google agreement dependency](https://cloud.google.com/terms/marketplace/commit-policy))

The earlier research retrieved only partial passages from GSA’s February 2, 2022 tagging guide, filename v3.1; the DoD Cloud FinOps Strategy endpoint returned 403. Their full contents and current component applicability are not newly verified here. No universal DoD tag schema or appropriation rule is asserted. Client-controlled policies, acquisition/funding decisions and approved handling govern later use; billing metadata itself can be sensitive. ([GSA guide](https://www.cio.gov/assets/resources/Cloud%20Tagging%20Strategy%20Guide_v3.1.pdf), [DoD endpoint](https://dodcio.defense.gov/Portals/0/Documents/Library/DoDCloudFinOpsStrategy.pdf))

Framework concepts are paraphrased and adapted from the FinOps Foundation and FOCUS project under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/); attribution implies no endorsement. The dictionary, worksheet, proposed roles and cadence are Cloud Waypoint recommendations. Detailed source notes retain retrieval gaps and field-level depth; neither this report nor its offline rendition installs or operates billing tooling, authorizes real-data admission, changes the current rehearsal, or accepts a client commitment.