Two gates before a dollar is committed. Both owned by the Portfolio Owner.
AWS Budgets gives thresholds and alerts. It does not give a human approval workflow with an estimate-size gate and a recurring spend gate routed to a Portfolio Owner. FinOps Center adds that layer — so every approval is a business decision recorded against the hierarchy, not an engineering threshold that fires after the fact.
WHY DID WE BUILD? ↓
AWS Budgets fires an alert when a threshold is crossed. The spend has already happened. There is no approval before it. There is no record of who was accountable for it.
Governance is a human approval workflow, not an automated alert.
AWS Budgets and Budget Actions give thresholds, alerts, and limited automated responses. They do not give a human approval workflow with an estimate-size gate and a recurring spend gate routed to a Portfolio Owner. The alert fires after the threshold is crossed. The spend is already committed. There is no record of who approved the budget level, who reviewed the actual spending, or whether the organization signed off before the bill arrived.
FinOps Center adds the two-gate approval workflow that native AWS cannot provide. Both gates route to the Portfolio Owner, the person accountable for the product owners beneath them. Every approval is recorded against the hierarchy so approved data is attributable at every rollup level at month close.
THE TWO GATES
Two approval decisions. One before spend starts. One while it is happening.
Estimate-size approval
Before spend is committed
The Portfolio Owner approves how large a budget or estimate may be before spend begins. This gate fires when a Product Owner submits an estimate or budget request. The Portfolio Owner reviews the size against portfolio-level context and approves or rejects before any workload draws from the budget.
- Triggered by: Product Owner estimate or budget submission
- Routed to: Portfolio Owner
- Required for: budget to be active and workloads to draw from it
- Recorded: yes, against the hierarchy for month-end completeness
Spend approval
Recurring, while spend is happening
The Portfolio Owner approves what is actually being spent against an approved budget on a recurring cadence — for example, weekly. Each spend card gives the Portfolio Owner a view of actual spend for the period against the plan. Anomalies surface during the period, not after the bill arrives.
- Triggered by: recurring schedule (for example, weekly)
- Routed to: Portfolio Owner
- Required for: month-end approval completeness
- Recorded: yes, feeds directly into Month Close
Budget thresholds and anomaly alerts from AWS Budgets feed the workflow as signals, not as the approval itself. An alert tells the Portfolio Owner something needs attention. The spend card is where the approval happens.
SPEND CARDS
Every spend period reviewed before it rolls into the bill.
Spend cards are the weekly spending review built into the Portfolio Owner workflow. Each period — typically Sunday to Saturday — the Portfolio Owner reviews actual spending across the Product Owners beneath them, against the estimates and plan. Anomalies surface during the period. The Portfolio Owner can act immediately: flag a workload, question a model choice, or route a budget increase up the chain.
By the time the month-end bill arrives, every spend card has been reviewed and accepted. The accrual is based on numbers the business already owns — not numbers Finance is seeing for the first time. This is how Month Close becomes a non-event instead of a reconciliation crisis.
Put approval before the bill, not after it.
support@finopscenter.com