Concepts

Cost amounts

What a Costfluent total counts, how amortization, credits, refunds and tax change it, and why missing data is never shown as zero.

Every total in Costfluent is a sum over the same cost records. What changes between two totals is which amount is summed and which charge categories are counted. A cost report stores those choices, so reopening it shows the same total. You set them under Options on a report's chart card, with the switches below, each with a line under it on what it counts; a change there is unsaved until you select Save changes or Save as new. See Explore cost data. A new report starts from the workspace's report defaults, and a new workspace starts from the defaults below.

Billed or effective cost

Each cost record carries two amounts:

  • Billed cost is what the provider charges on the invoice for that line. An upfront commitment appears in full on the day it is bought.
  • Effective cost spreads commitments such as reserved instances and savings plans over the usage they cover, so a day's cost reflects what that day's usage really cost.

Amortized cost sums effective cost instead of billed cost. It is on by default. Turn it off to reconcile a report against the provider's invoice.

Spread commitment discounts

AWS applies a Savings Plan or Reserved Instance to the usage it matches, account by account, so effective cost shows the whole discount on some accounts and none on others running the same kind of usage on demand. A workspace with Spread commitment discounts on gives that usage an even share of commitment savings instead: on any one day, every eligible line takes the same percentage off. It is a showback view of what each team's usage cost; see Showback for teams. It is off for a new workspace, and an Owner turns it on in the workspace's settings (Organization and workspaces).

The discount is spread within a pool: one AWS connection, billing account, billing currency, service, operation and pricing unit on one day, such as Amazon EC2 RunInstances hours. A pool counts only when a commitment covered some of its usage that day. Its covered lines and its on-demand lines share the pool's effective cost in proportion to their on-demand value, which is the list cost, or the effective cost where that is higher. The rounding remainder goes to the line with the largest on-demand value, so each pool, and so each connection's amortized total, adds up to exactly what it did before.

Everything else keeps its own effective cost:

  • usage no commitment covered in its pool, such as EBS volumes, data transfer and NAT gateways under Amazon EC2;
  • unused commitment, commitment purchases and fees, credits, tax and corrections;
  • Azure, Google Cloud and Kubernetes cost.

Every amortized figure in the workspace carries the spread: cost reports, dashboards, budgets, cost alerts, anomalies and Insights, the forecast, allocation coverage on amortized cost, the native export's Cost and AmortizedCost, and the Public API's costs and summary when they name the workspace, whose commitmentDiscounts then reads blended rather than asApplied. Billed cost never changes. The coverage figures on Commitments stay as AWS applied the commitments, since they say what each commitment covered, so a team's report can show a discount its coverage does not. The FOCUS export's EffectiveCost stays the provider's figure (Explore cost data).

The rate is shared, so a team's amortized cost can move when another team's eligible usage moves, even while its own stays the same.

Charge categories

Every record from a cloud provider has a charge category from the FOCUS specification: Usage, Purchase, Tax, Credit or Adjustment. Usage and purchases are counted, except a correction while refunds are left out, and so are the fee lines a custom provider upload can carry; its discount lines are credits and its refund lines corrections. The other three FOCUS categories are switches:

SettingCountsDefault
Include creditsCredit lines, such as promotional creditsOff
Include refundsRefunds and corrections: the Adjustment category, and every line whose charge class is Correction, such as an Azure refund or a Google Cloud correctionOff
Include taxTax linesOn

Group a report by Charge category to see how much each category contributes.

Credits by source

Include credits counts the credits a provider delivers as lines of their own:

SourceCredit lines
Amazon Web ServicesEvery credit, from the export and, for months the export does not cover, from Cost Explorer (Connect AWS)
Google CloudPromotional credits, such as a free trial. Sustained and committed use discounts, other discounts, the free tier, reseller margin and subscription benefits are part of the price and stay subtracted from the charge (Connect GCP)
Microsoft AzureFor a connection collecting a billing scope, the credits billed at the billing account or billing profile (Connect Azure). None for a connection collecting subscriptions: Microsoft applies Azure credits and prepayment on the invoice, at the billing account or billing profile, which such a connection does not import (Connect Azure)
FOCUS exports and custom uploadsThe Credit lines the file states; a custom upload's discounts too (Upload cost to a custom provider)

The other providers' data states no credits.

To follow how much of a grant of credits is left and when paid usage starts, enter it on its connection; see Credits.

List cost and savings

On a cost report, beside the total, "Saved against list price" shows what the range's usage would have cost at the providers' list prices less what it cost, and that saving as a percentage of the list cost. Negotiated discounts, Savings Plans, reservations and committed use discounts show in it, and credits when the report includes them. Below the figure, "at list price" gives the list cost, and "Always at amortized cost." with "How the saving is counted" links to this section.

The card always reads amortized cost, whatever the report's Amortized cost setting: on billed cost, covered usage costs nothing and the commitment purchase is not usage, so the whole list price would read as saved. It counts the report's own rows, filter and Include credits and Include refunds settings:

  • List cost: each usage line at its list cost, or at its effective cost where that is higher. Unused commitment and commitment fees have no list cost.
  • Cost: the effective cost of the usage, unused commitment and fees included, and the credits and refunds the report includes. Purchases and tax count on neither side.

In a workspace that spreads commitment discounts, the cost carries the spread. A saving can be negative: commitment left unused can cost more than the commitments saved.

Only sources that state a list price count:

SourceList price
Amazon Web ServicesStated on the rows of the export. Months read from Cost Explorer, which the export does not cover, state none (Connect AWS)
Google CloudThe billing export's cost at list price
Microsoft AzureThe pay-as-you-go cost. A line a reservation covers often states none, and counts at its effective cost on both sides, saving nothing
GitHubThe gross amount before discounts
FOCUS exportsThe file's ListCost
Custom uploads, Kubernetes clusters and every other providerNone

The card names each provider in the range that states no list price rather than counting its cost as nothing saved, and reads "List prices not available" when none in the range states one. Dashboard widgets, share links, scheduled deliveries and the Public API do not carry it. The Public API's listCost and totalListCost and the native export's ListCost column hold the list cost as stored, which for a line whose provider states no list price is its billed cost.

Currency

A record keeps the currency it was billed in. A workspace either converts every amount into one currency at a published European Central Bank rate, or shows each billing currency side by side. An amount with no published rate for its date is left out of the total and named beside it rather than guessed. See Currency settings.

Missing data is not zero

Costfluent never shows zero where it does not know the amount:

  • Days your plan's cost history does not reach are cut from the range, and the report says so, naming the date: "Cost history before … is not included in your plan, so this range starts there."
  • Days not collected yet, for example while automatic syncing is off, fill in on the next collection.
  • Between connecting a provider and its first cost, the Overview's "Total cost (30d)" and "Previous period" read "No cost data yet".
  • The last day or two of a range ending today are still arriving, so a change compares only the days through the last settled day with as many days before, never the missing cost as a fall.
  • A budget whose spend has not been computed yet shows "Spend not computed yet".
  • An amount that cannot be converted is excluded from a converted total and listed separately.