When importing with line items via the API for a custom platform (e.g. STACKIT), the line items do not appear in the Tenant Usage Report (TURP). The TURP generation logic was originally built for native cloud platforms (AWS, Azure, GCP), which already have their own TURPs as a billing source. For custom platforms, a is the only source of billing data, but the current implementation does not use it to populate TURP line items — making consumption-based billing for custom platforms effectively non-functional.

Define a Building Block with a non-zero price (e.g. €0.01) on the custom platform tenant. This triggers TURP generation via a different code path, which causes the imported usage report line items to appear. Note: this is a workaround only and not a viable strategy for actual consumption-based metering.

We are aware of this limitation and are investigating a proper fix. The TURP generation logic needs to be extended to include line items from for custom platforms.

Check in with our customer success team or support@meshcloud.io if you need any help.