Cloud budget planning for 2027 works from usage data, not from last year's total plus a flat uplift. You need four pieces: a cleaned baseline from twelve months of billing data, a cost driver for every budget line, the changes already known for 2027, and a range instead of a single number. Each line gets an owner who explains it against actuals in the monthly review.

Build the baseline from twelve months of billing data

Use the last twelve closed billing months; in October 2026 that is October 2025 to September 2026. The current month still lacks late adjustments, credits and tax lines, so leave it out. Use the same cost basis as your monthly cloud cost review. For consumption, amortised cost works best, because upfront commitment payments are spread over their term. Keep the invoiced amounts alongside as a separate cash view. AWS Cost Explorer shows up to 13 months of history, enough for a first look; for the line-by-line split below, use the export.

Cleaning the baseline does not mean deleting data. Split the charges like this and carry everything outside the baseline as its own line:

ChargeTreatmentCUR 2.0: line_item_line_item_typeFOCUS: ChargeCategory
Usage, including commitments and discountsbaselineUsage, DiscountedUsage, SavingsPlanCoveredUsage, SavingsPlanNegation, RIFee, SavingsPlanRecurringFee, Discount, BundledDiscountUsage, Purchase via EffectiveCost
Upfront paymentsnot as one month's usage; amortised over the termSavingsPlanUpfrontFee, FeePurchase with EffectiveCost = 0
Creditsremove, track with expiry dateCreditCredit
Refundsremove, find the causeRefundinside Usage, Purchase or Tax, no own category
Taxremove, budget netTaxTax
One-off eventsremove, document the reasondepends on causedepends on cause

The FOCUS specification has no refund category: Usage, Purchase and Tax each include refunds. To take them out of the baseline on AWS you need the CUR column. One-off events include a finished migration with parallel running, a one-time data export or a load test. Plan the budget net of tax and agree the treatment of tax lines with your accountant; checking EU reverse charge on AWS and Azure invoices shows what to look for on the invoice.

Query: twelve months by account and service

With a FOCUS export (on AWS, the FOCUS_1_2_AWS table from Data Exports), this query returns the raw data. Because EffectiveCost is zero on upfront purchases and the amortised share sits on the usage rows, summing Usage and Purchase gives the amortised view:

SELECT
  BillingPeriodStart  AS billing_month,
  SubAccountId        AS account,
  ServiceName         AS service,
  ChargeCategory      AS category,
  SUM(EffectiveCost)  AS amortised_cost,
  SUM(BilledCost)     AS billed_cost
FROM {focus_table}
WHERE BillingPeriodStart >= TIMESTAMP '2025-10-01 00:00:00'
  AND BillingPeriodStart  < TIMESTAMP '2026-10-01 00:00:00'
GROUP BY 1, 2, 3, 4
ORDER BY 1, 2, 3, 4;

In CUR 2.0, group by bill_billing_period_start_date, line_item_usage_account_id, line_item_product_code and line_item_line_item_type instead. AWS CUR 2.0 or FOCUS 1.2 explains which AWS export fits. Azure's cost details export carries the same dimensions, and on Google Cloud the BigQuery billing export does.

Use cost drivers, not a flat uplift

A percentage uplift explains nothing in July when actuals drift. Give each line a measurable driver and separate fixed from variable cost:

Budget lineDriverWhere the driver volume comes fromBehaviour
Production computeactive customers or requestsproduct metrics, sales planmostly variable
Non-productionenvironments × running hoursaccount structure, infrastructure as codestepped
Data and storageGB stored at month endstorage metricsgrows cumulatively
Data transferoutbound GBnetwork metricsvariable
AI servicestokens or requests per modelprovider usage datavariable, price-sensitive
Platform and supportcontract or share of totalcontractfixed or derived

Cost per unit is the line's baseline cost divided by the driver volume over the same period. Storage is a special case: what you stored in 2026 keeps costing money in 2027 until a lifecycle rule removes it.

Add the changes you already know for 2027

List everything that is decided or dated, each as its own line:

  1. Expiring commitments. Savings Plans, Reserved Instances and Azure reservations have an end date. After it, usage they no longer cover returns to on-demand rates unless you renew.
  2. Credits ending. Startup or migration credits lower the bill, not the workload. Plan gross from the month they expire.
  3. Price changes. Only announced changes with a source and date belong in the base case; suspected ones go into the high case.
  4. Migrations and launches. A move means several months of parallel running; a launch shifts a driver.
  5. EUR/USD. If invoices arrive in USD, or USD prices are converted to euros, the exchange rate moves your euro budget without any technical change. Fix a planning rate with a source and a reference date, such as an ECB reference rate.

The budget template with formulas

The template holds no amounts, only the rule for each column, one row per budget line:

ColumnContent or formula
A Budget linee.g. "Production compute, account prod-eu"
B Ownername, team, cost centre
C Baselinecleaned amortised cost, October 2025 to September 2026
D Baseline driver volumedriver total over the same period
E Fixed portioncost that does not move with the driver
F Cost per unit= (C − E) / D
G 2027 driver volumeplanned value from product or sales planning
H Plan before changes= E + F × G
I Known changessum of the dated individual items
J 2027 base plan= H + I
K Low, L Highformula from J with low and high assumptions
M Assumption and evidencesource, date, open question

Where a line has no reliable driver, leave F empty and carry the line forward with a stated reason rather than an invented driver.

Cleaned baseline: twelve closed months, amortised, without credits, refunds, tax and one-offsCost per unit: baseline minus fixed portion, divided by the driver volumePlan before changes: fixed portion plus cost per unit times the 2027 driver volume2027 base plan: plus the dated known changesLow and high scenarios from named assumptionsMonthly phasing by days and dated items
From baseline to plan: twelve cleaned months and a driver give a cost per unit, the planned driver volume and the dated changes give the base plan, and the scenarios and the phasing follow from it

Scenarios instead of one number

Calculate three scenarios that differ only in named assumptions: driver volume, launch date, commitment renewal and planning rate. Get the base case approved, and let management decide explicitly what the gap to the high case is: a reserve, a re-planning threshold, or knowingly unbudgeted.

Monthly phasing

Do not divide the annual budget by twelve. Cloud cost follows calendar days, launches and payment dates:

  • At constant load, hourly-billed services cost less in February than in March.
  • Launches, migrations and shutdowns take effect from their month.
  • Upfront payments, annual Marketplace licences and support contracts land in a single month.

As a formula: monthly plan = daily run rate of the line × days in the month + dated changes in that month.

An owner for every budget line

Each line needs a person who explains its variance in the monthly review and a cost centre that finance books it to. Engineering team leads are natural owners because they control the drivers. A line without an owner is resolved before approval.

Native budgets as early warning

AWS Budgets supports cost, usage, reservation and Savings Plans budgets and notifies by email or Amazon SNS, including on forecast cost. AWS updates budget data up to three times a day and notes that costs can exceed the threshold before the notification arrives. Budget actions apply an IAM policy or SCP or target specific EC2 and RDS instances, automatically or after approval. None of this caps the bill.

Azure budgets in Cost Management evaluate actual and forecast cost every 24 hours, based on actual rather than amortised cost. Microsoft states that resources are not affected and consumption is not stopped. Azure splits an annual budget evenly across twelve months, so a phased plan needs separate budgets. Under a Microsoft Customer Agreement, a budget at billing account scope is evaluated in USD, while one at billing profile scope uses the billing currency. On Google Cloud, alerts-only budgets do not cap spend. Spend-cap budgets exist only for individual services such as Cloud Run and the Gemini API, and they do not pause ongoing fixed charges for persistent resources.

Provider forecasts are not a plan: Cost Explorer projects historical usage up to 18 months ahead and returns no forecast without enough history; Azure projects up to a year using linear regression. Neither knows your launch plan.

Compare actuals with plan every month

Compare on the same cost basis, in the same currency and with the same conversion method as the plan. Split each line's variance:

  • Volume effect = (actual driver − planned driver) × planned cost per unit
  • Rate effect = (actual cost per unit − planned cost per unit) × actual driver
  • Currency effect, credits and one-offs as separate lines

If a driver changes for good, update the forecast and record why; the budget stays as the reference. Finance sets the variance threshold that triggers re-planning. Handle late charges with the same rule as at month-end close.

Common mistakes

  • Credits left in the baseline, so their expiry looks like a cost explosion.
  • An upfront Savings Plans payment counted as one month's consumption.
  • Budget and monthly report on different cost bases, such as billed versus amortised.
  • The provider forecast adopted as the budget, although it only extends history.

Budgets in Costfluent

In Costfluent you create budgets for a defined scope and period, compare actual cost with the budget and keep the variance history; the docs explain the setup under Budgets. A budget shows where its current period is heading, and a cost report can show a spend forecast. Budget alert notifications are Planned. The data comes from read-only connections to AWS, Azure and Google Cloud.

Sources and method

Checked on 2026-10-10. AWS Budgets, AWS budget actions, Cost Explorer, Cost Explorer forecast, CUR 2.0 line item columns, FOCUS 1.2 with AWS columns, FOCUS 1.4: ChargeCategory, FOCUS 1.4: EffectiveCost, Azure budgets, Azure cost analysis and forecast, Google Cloud budgets, Google Cloud spend caps. The tables, formulas and review steps are Costfluent recommendations, not tax or accounting advice.