Month-end close: allocated cloud costs ready for finance
Use Costory's frozen month-end numbers, allocated to cost centers, as the cloud input to your close.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Row
cost_center
cost_eur
1
CC-110 Payments
Acme SAS
71,350.20
2
CC-120 Search
Acme SAS
52,980.75
3
CC-140 Data Platform
Acme GmbH
64,210.40
4
CC-150 Platform
Acme SAS
38,665.10
September (frozen on Oct 10): €331,420 across 9 cost centers, in EUR. Change vs the Oct 2 preliminary view: +€1,180, mostly late Datadog adjustments.
You decide
Controllers book the numbers.
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
Month n-1 freezes on the 10th.
Costory investigates
01
Refresh window
Costory refreshes month n-1 until the 10th of month n.
02
Freeze
After the 10th, month n-1 is frozen so close numbers stay stable.
03
Allocate
Cost centers and entities via virtual dimensions.
04
Export
BigQuery Data Exports or a scheduled report for the close file.
Where you see it
Claude
You decide
Controllers book the numbers.
Why it matters
Cloud bills keep changing after month end as providers adjust them. Finance needs a number that stops moving.
Who it’s for
Finance, controllers, FinOps leads
Where it runs
Claude · Slack
What you get
What lands in front of your team
Stable numbers
Frozen after the 10th.
Allocated
By cost center and entity.
Close-ready exports
Into finance's own tools.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Close
Give me September's frozen cost by cost center and entity, in EUR, ready for the close file.
Check
Which cost centers changed the most between the preliminary and the final September numbers?
FAQ
Questions about this playbook
When are month-end numbers final?
Costory refreshes month n-1 until the 10th of month n, then freezes it so close numbers stay stable.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
The 11th of every month, after month n-1 is frozen.
Monthly chargeback pack by cost center, ready for finance
A monthly, frozen view of allocated cost per cost center, exported to BigQuery or shared as a PDF for finance.
See the playbook
Costory notices
A commitment purchase shifts billed cost between teams.
Stable team costs with contracted cost
Give teams a usage-driven cost view that doesn't swing when Savings Plan discounts are shared across accounts.
See the playbook
Costory notices
Month-end, or when FX moves materially.
Report cloud costs in EUR across USD invoices
Report in your company currency while providers bill in USD, with consistent conversion rules across AWS, Google Cloud, Azure and Datadog.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud