Customer cloud · usage and invoices

Make cloud consumption understandable before the invoice.

Customers see current usage, project and service breakdowns, budget position and issued invoices from the same metering record your commercial teams use.

Discuss your requirementsCustomer cloud overview
Metering · tenant Meridian AGInstance hours1,284 hAccelerator hours312 hBlock storage18.4 TBEgress2.1 TBAPI requests1.8 MPlansyour pricesInvoiceNº 2026-0912Total€8,420reconciled · paidAPI · EVERY ACTION IS A CALLGET /v1/tenants/meridian/usage?period=2026-09POST /v1/plans { "name": "gpu-hourly", "price": 2.40 }GET /v1/invoices/2026-0912 → 200 · total 8420.00 EURPOST /v1/projects/erp/instances { "size": "m.large", "count": 4 }
Visibility
Current usage
Before period close
Breakdown
Project & service
Costs in operating context
Control
Budgets
Position and alerts
Record
Invoices
Usage-backed documents
Scope

Commercial transparency inside the customer workflow.

Usage is not separated from the resources, projects and plans that explain it.

Consumption view

Follow measured usage by resource type and billing period.

Project breakdown

Understand which teams and services are driving consumption.

Budgets and forecast

Compare current position with an agreed customer budget.

Invoice history

Access issued invoices and the usage context behind them.

Operating workflow

Keep customers informed throughout the billing cycle.

The portal presents the commercial record as it develops, not only after invoicing.

  1. 01

    Measure services

    Capture consumption against tenant and project resources.

  2. 02

    Show current position

    Present usage, budget and forecast during the period.

  3. 03

    Close the period

    Apply plans and commitments to the final record.

  4. 04

    Issue and retain

    Publish the invoice with historical usage context.

Two connected responsibilities

Operator control and customer action stay explicit.

Operator responsibility

What commercial teams publish

  • Metered service units
  • Plans and commitments
  • Budgets and periods
  • Invoice and export records
Service consumer

What account teams can inspect

  • Current and historical usage
  • Project and service costs
  • Budget position
  • Invoices and supporting detail
Operational outcome

What this changes in the working model.

Outcome 01

Fewer surprises

Customers can follow spend before the invoice arrives.

Outcome 02

Shared numbers

Portal and operator console use the same usage record.

Outcome 03

Better internal allocation

Projects make consumption accountable inside the customer organisation.

Return to customer cloud overview →
Continue in this section
Partner with us

Make usage part of the customer experience.

We will map plans, projects, budgets and invoices into a transparent account workflow.

Book a briefingCustomer cloud overview