Actual versus amortized cloud cost

Choose a basis for the question

Actual and amortized cost answer different financial questions. In Azure Cost Analysis, actual cost shows usage and purchases as they accrue in the billing view. Amortized cost spreads reservation and savings plan purchase costs across the applicable term and associates costs with usage. Select the basis before comparing periods or assigning a workload cost to a team.

Use actual cost as the starting point for investigating invoice-related charges, while checking the account offer and excluded items. Use amortized cost when examining commitment utilization or the cost of consuming committed capacity over time. Microsoft documents that these views can have different monthly totals. A change of reporting basis can create a trend break even when resource usage stays the same.

Understand what moves between periods

An upfront reservation purchase creates a charge in the actual-cost purchase period. Amortization distributes that purchase over its term. Microsoft gives a one-year, non-leap-year example of a USD 365.00 purchase allocated as USD 1.00 per day. Monthly payment schedules have their own allocation periods. Verify the provider data before applying a simplified daily example to a real agreement.

Amortized costs can be assigned to resources that used the commitment. Unused reservation cost remains visible in the amortized view, so a covered resource with little apparent actual usage cost is not necessarily free to the organization. Include the unused portion when reviewing the commitment. Microsoft limits this amortization behavior to reservations and savings plans; Azure Marketplace purchases are outside that behavior.

Read a purchase spike without claiming savings

The illustrative example uses only one reservation purchase and ignores all other charges. On the purchase date, USD 365.00 in actual cost and USD 1.00 in amortized cost describe different timing treatments of the same purchase. The USD 364.00 gap reflects the portion allocated to other days under the example assumptions. It must not be presented as a saving.

After switching the metric, record the change in the report heading and refresh every comparison using the same basis. Avoid comparing a purchase-month actual total with a later amortized total. For a commitment decision, check coverage eligibility and unused cost separately from cash timing. A smoother chart does not show that the workload became more efficient or that a purchase delivered its expected value.

Scroll the table sideways on smaller screens. Keyboard: focus the table and use the arrow keys.

Keep discount and list-price questions separate

Actual versus amortized cost concerns when and where commitment purchase costs appear. Net versus list price concerns the price basis. Azure usage costs can already reflect negotiated pricing and commitment discounts. Applying a discount again to a provider-reported net amount understates cost. A catalog list-price estimate should remain labeled separately from actual billing evidence, even when the values are shown together.

Use the net and list price guide when assessing a quoted discount or interpreting an estimated opportunity. For a savings comparison, state both the timing basis and the price basis where relevant. Document the selected charge categories too. Commitment purchases, refunds, or invoice adjustments can change the comparison independently of resource efficiency. Ask finance to resolve unclear categories before presenting a single savings amount.

Reconcile the scope and preserve currency

Actual cost is useful for reconciliation, but a Cost Analysis total is not automatically the full invoice payable. Microsoft documents exclusions such as taxes, support charges, and credits, with differences by agreement type. Match the billing scope and period first, then explain excluded items and adjustments in a reconciliation note. Retain the source amounts before rounding them for a meeting or report.

Keep each native currency separate throughout the comparison. EUR 500.00 and USD 500.00 cannot be added into an unlabeled total. If a reporting tool offers a normalized currency view, retain the original amounts and document its conversion basis. Distinguish that management presentation from native provider billing. Also check whether the current period is open, because provisional cost records can change before the invoice is issued.

Record the basis your tools actually provide

A report definition should name its question, source metric, dates, selected scope, currency, and known exclusions. Store the same definition with its export so that finance and engineering can reproduce the result. For recurring meetings, agree a default basis and require an explicit note when it changes. This prevents an unexplained improvement caused solely by selecting a different metric.

This guide explains Azure financial concepts; it does not promise an amortized-cost selector in Costframe. Costframe cost comparisons must use the basis disclosed by the available source. Do not relabel an ActualCost result as amortized or manufacture commitment allocations from a list-price estimate. Consult the cost calculation documentation for product boundaries and request the provider view or export when your analysis needs a basis the product does not expose.

Related guidance