Cost Allocation & Showback Platform  ·  View 08 of 22  ·  3 · Structure

Integration Surface

Five read surfaces, three write surfaces, and nothing written back to the estate it measures.

Editable source SVG draw.io All views
Read (the platform never writes back) Provider billing exports AWS CUR · Azure · GCP Licence & SaaS invoices file + API Cluster metrics 60 s samples Catalogue & org system effective-dated Business driver feeds team-owned Cost Allocation & Showback Platform Cost Allocation & Showback read-only to the estate Tell and act ERP general ledger chargeback only Collaboration digest Teams BI & team tooling Power BI, budget gates daily monthly streamed ownership daily push postings alerts marts, API Integration Surface — Five Things It Reads, Three It Tells External / third party Application we own batch event / async synchronous Five read surfaces, three write surfaces, and nothing written back to the estate. The provider invoice API is read once per period to reconcile. A platform that measured cost and also changed resources would be disbelieved by the teams it measures. v 1.0 · owner Platform Architecture · date 2026-09

The rule

  • Billing credentials are scoped to export read only and cannot reach the workloads themselves
  • A platform that measured cost and also changed resources would be disbelieved by the teams it measures
  • The GL posting is the only integration that moves real money, and it reads frozen statements only

Failure behaviour per surface

  • A missing export publishes the period as incomplete with the provider named
  • A drifted export schema quarantines the partition and blocks that provider for the period
  • A stale driver feed suppresses the unit cost rather than carrying the last value forward

Accepted clutter

  • The route checker reports two label-proximity warnings on this view; the edges and labels are correct and the alternative is an unlabelled boundary crossing