IssueTracker

Description

Context: The current BigQuery billing export schema lacks a dedicated "Invoice ID" column, forcing users to rely on the "invoice.month" field for invoice identification. This makes it difficult to directly access and track invoice information within the exported data.

Impact: The absence of a dedicated "Invoice ID" column hinders:

- Improved Cost Tracking and Reconciliation: Users cannot easily link specific costs to individual invoices, making cost tracking and reconciliation challenging.
- Integration with Tools Like Cloudability: Integration with third-party cost management tools like Cloudability is hindered due to the lack of direct access to invoice IDs.
- Direct Access to Invoice IDs: Users are unable to directly access invoice IDs within the exported data, limiting their ability to perform detailed analysis and reporting.
- Clarity and Efficiency: The current approach leads to confusion and inefficiency when attempting to identify and manage invoices.