Cost Category data is not available in Billing Export CUR 2.0

There are a few potential reasons why your newly created Cost Category is not appearing in the CUR 2.0 Data Export:

1. Processing time: After creating a new Cost Category, it can take up to 24 hours for the cost and usage information to be processed and categorized. If you've only recently created the Cost Category, you may need to wait a bit longer for it to appear in your CUR 2.0 export.

2. Export timing: CUR 2.0 exports are typically generated on a schedule (e.g., daily or monthly). If your export was generated before the Cost Category was fully processed, it may not include the new category data. You might need to wait for the next scheduled export to see the new Cost Category.

3. Data timeframe: Cost Categories are only applied to data from the time they were created moving forward. They don't retroactively categorize historical data. Make sure you're looking at data for periods after March 30th, 2025, when you created the Cost Category.

4. Export configuration: Ensure that your CUR 2.0 export is configured to include Cost Category data. Check your export settings to confirm that the necessary columns are included.

5. Permissions: Verify that the IAM permissions associated with your CUR 2.0 export are sufficient to access the Cost Category data.

6. Status check: In the AWS Billing console, check the status of your Cost Category. If it shows as "Processing" instead of "Applied," the updates are still in progress.

If you've accounted for these factors and are still not seeing the Cost Category data in your CUR 2.0 export, you may want to contact AWS Support for further assistance in troubleshooting your specific configuration.
Sources
Organizing costs using AWS Cost Categories - AWS Billing
Migrating from CUR to Data Exports CUR 2.0 - AWS Data Exports
Cost Explorer, Cost Category Reports | AWS re:Post