Billing and reports

CloudPouch shows your AWS bill as amortized cost — consistently, in every view — with Enterprise Discount Program rows excluded, and lets you drill from a monthly total down to the single UsageType that changed — by service, region, time period, or linked account. Everything is computed locally from AWS cost data; CloudPouch does not upload your cost data to CloudPouch servers.

How CloudPouch treats billing data

AWS billing data is messy: Savings Plans post large up-front charges, discounts appear as negative rows, and the same workload shows up under different region-prefixed usage types. CloudPouch normalizes this so the numbers answer cost questions directly:

Savings Plans and Reserved Instances appear as amortized costs. Commitment spend is spread across the resources that consume it, so a service’s cost reflects what it actually uses rather than showing a spike on the day you bought the commitment.
Enterprise Discount Program discount rows are excluded, so EDP accounting noise does not distort service totals.
One billing model everywhere. Scoped reports and Cost Insights use the same unified billing model, so a number you see in one view matches the same number in another.
Some views show clean usage cost. The Bedrock IAM-tag breakdown, for example, excludes tax, refunds, credits, and EDP discounts so team attribution reflects real usage.

Organizations and linked accounts

Point CloudPouch at a payer (management) account profile and it aggregates costs by linked account across your AWS Organization. When the profile can read account names from AWS Organizations, CloudPouch shows names like prod-payments instead of raw 12-digit account IDs — which is usually the difference between recognizing a cost owner instantly and keeping a spreadsheet of account numbers.

Drilling into UsageTypes

Service totals hide the interesting part. “EC2-Other: $40,000” tells you nothing; EBS:VolumeUsage.gp2 at $38,000 tells you exactly what to fix. CloudPouch exposes AWS UsageType costs beneath each service so you can see the low-level billing drivers, and it can aggregate the same usage type across regions so EUC1-EBS:VolumeUsage.gp2 and USE1-EBS:VolumeUsage.gp2 roll up into one logical cost driver instead of scattering across rows.

This UsageType-level view is how a real 2021/2022 account traced roughly $100,000 of monthly spend to GP2 volume storage — the starting point for an $18,890/month optimization.

Compare reports

Compare reports put two months side by side and highlight what changed: which services grew, which shrank, and which usage types drove each change. Use them to:

Verify that an optimization actually reduced spend, not just shifted it.
Catch month-over-month growth before it compounds.
Find the specific usage type behind a service-level increase.

Compare reports merge region-prefixed usage types by default, so a cost driver that spans several regions shows up as one row with one delta instead of a dozen partial changes.

Timeframes

CloudPouch analyzes the current month and the previous month, and Cost Insights run in both timeframes. One gotcha: on the first day of a month, the previous-month view may show data from two months ago, because the just-completed month is not yet represented consistently in AWS billing data.