Configured budgets and estimated spend
Configured budget scope and reporting estimates, with shared accounting and allocations explicitly proposed.
Configured limits
A budget record defines its configured scope, cap, window, soft threshold, action, and enabled state. Conditions and membership exclusions are part of the record's scope. Use the values supported by the managed deployment; do not infer a parent budget or inherited allocation from the reporting chart.
Estimated spend
Estimated spend is captured activity priced over a stated reporting window. The total depends on visibility, filters, capture coverage, and available pricing. Keep unpriced activity visible: unknown cost is not zero.
Estimated spend is not an authoritative admission balance. Do not calculate an enforced remaining balance or budget-used percentage by subtracting captured reporting spend from a configured cap. Reporting and admission can have different scope, freshness, and windows.
See AI spend for the reporting contract.
Proposed shared accounting
Organization-wide protection requires shared accounting for the exact budget scope and window across devices and services. Define admission handling for concurrent requests, reserved usage, in-flight spend, final settlement, retries, cancellation, unknown cost, and unavailable accounting.
A sum of local device budgets does not by itself establish a company-wide spending ceiling. The enterprise acceptance check must exercise multiple devices and concurrent requests against the same applicable limits and verify the resulting provider usage.
Proposed allocations and forecasts
A parent-to-child allocation contract must define ownership, overlapping Team membership, unallocated amounts, direct-member limits, and what happens when a parent cap changes. Do not add overlapping caps or overlapping Team reporting totals into an organization total.
Forecasts require a published calculation and a stated sample/window. A forecast is a reporting estimate, not enforcement evidence or a remaining balance.
Target contract
The following describes planned enterprise behavior. Current behavior remains defined above.
Proposed allocations
Company owners could set a monthly allocation and assign amounts to child scopes and direct members. The contract would need to define shared reservations, settlement, overlap and ownership before it could establish a company-wide ceiling.
Proposed forecasts
A forecast would require a stated sample and calculation window. It would remain a reporting estimate and would not trigger admission enforcement.