/

/

Reconcile cloud invoices with billing exports

Reconcile cloud invoices with billing exports

Reconcile cloud invoices with billing exports

Match provider invoices with normalized billing data and flag differences.

Runs in

Claude · Slack

First optimization recommendation

The next day

ROI

Pays for itself with the first recommendation you act on

Reconcile cloud invoices with billing exports

Question

Compare September's AWS invoice total with billed cost in Costory and explain any difference.

Query

Result

Finding

September AWS invoice vs Costory billed cost: €0.4k difference (tax and credits applied after the export).

You decide

Finance resolves differences.

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

An invoice arrives.

Costory investigates

01

Invoice totals

Bring invoice totals.

02

Compare

Against billed cost per account.

03

Flag

Differences above a threshold.

Where you see it

Claude

You decide

Finance resolves differences.

Why it matters

Finance reconciles invoices by hand against exports and spreadsheets.

Who it’s for

Controllers, finance

Where it runs

Claude · Slack

What you get

What lands in front of your team

Faster reconciliation

Automatic comparison.

Flagged gaps

Differences explained.

Audit trail

Saved views.

Sources and assistants

What it connects

The billing data, context and assistants this playbook uses. Each links to its setup page.

The billing data, context and assistants this playbook uses. Each links to its setup page.

Example prompts

Or drive it yourself

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

The agent runs this on its own once set up. These prompts open in Claude, pre-filled, to set it up, review it or dig into a result.

Reconcile

Compare September's AWS invoice total with billed cost in Costory and explain any difference.

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

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