Skip to main content

Model Design

The showback and chargeback model defines how cloud costs are grouped, allocated, and presented to internal or external consumers. A clear model makes bills predictable and fair, and keeps Cost Management aligned with finance practices.

Use this guide to decide who should see or pay for which costs, which cost views to expose, and how Cloudaware allocation data should flow into statements, dashboards, and billing workflows.

Core Questions to Answer​

When designing your model, decide:

  • Who is billed or shown costs?
    • Business units, products, applications, teams, environments.
    • Customers or tenants (for MSPs and resellers).
  • What cost is in scope?
  • How is cost allocated?
    • Tag‑based, account‑based, or hybrid allocation.
    • Treatment of shared/platform costs and commitments.
  • What level of detail is needed?
    • Summary lines vs. detailed service breakdowns.
    • Blended vs. unblended or effective cost views.

Answering these questions up front helps you choose appropriate data structures, reports, and dashboards.

Building on Allocation and Business Mapping​

Most model design work starts from:

  • Allocation — how raw costs are mapped to apps, teams, BUs, customers, and environments.
  • Business Mapping — how accounts, subscriptions, projects, and tags translate into business hierarchies.
  • Shared Costs — how platform, networking, support, and other shared costs are treated.

Your showback and chargeback model should reuse these structures so that dashboards, budgets, and bills all tell the same story.

Rate Types and Views​

Decide which price views to use:

  • On-demand or unblended cost — shows cost before shared-rate averaging or certain discount allocation methods; useful for technical cost understanding and provider reconciliation.
  • Blended — averages rates across accounts in consolidated billing; often used for MSP or reseller roll‑ups.
  • Effective cost — includes amortized commitments and discounts to reflect the true economic cost of usage.

Many organizations:

  • Use effective cost for internal showback/chargeback.
  • Keep on‑demand/unblended views for engineering analysis and provider reconciliation.

Internal vs. External Models​

Cloudaware supports:

  • Internal models — chargeback to BUs, cost centers, or teams inside your organization.
  • External models — invoicing customers in MSP, reseller, or SaaS scenarios.

Differences to consider:

  • Internal bills may emphasize accountability and behavior change more than precision to the cent.
  • External bills often require more detailed line items, tax handling, and alignment with legal/commercial terms (usually managed in external billing systems).

Use Cloudaware as the analytics and FinOps tool, and integrate with finance/ERP or billing platforms for final invoicing, as needed.

Reconciliation and Governance​

For a healthy model:

  • Reconcile total billed/showback amounts with total cloud spend for each period.
  • Track and explain any deliberate differences (for example, costs retained in a central platform bucket).
  • Review the model periodically with finance and key stakeholders to ensure it still reflects how the business is organized.

Changes to the showback and chargeback model should be versioned and communicated in advance so owners understand how their statements may change over time.