Cost Allocation & Showback Platform  ·  View 20 of 22  ·  6 · Operations

The Monthly Close Loop

Six steps, once per period. The last two are what make next month's number better than this month's.

Editable source SVG draw.io All views
Exports land daily, T+1 Conform & reconcile to the invoice Allocate 3 pinned inputs Freeze & publish 5 business days Dispute & restate 90-day window Review policy & coverage what to fix next Close cycle one per period raw partitions conformed facts allocated facts statements v1 statements v2 next policy version The Monthly Close Loop — Where the Platform Actually Lives Interface / broker Application we own Data store Security / platform The loop is the product. A platform that only runs the first four steps is a report; the last two are what make the next month's number better than this one's. v 1.0 · owner Platform Architecture · date 2026-09

Why the loop is the product

  • A platform that runs only the first four steps is a report
  • Dispute and restatement are how errors are found; policy and coverage review is how they stop recurring
  • Tag coverage, apportionment rules and the remainder strategy are revisited every period, not set once

Cadence

  • Steps 1 to 3 run daily; steps 4 to 6 run per period
  • The correction window keeps step 5 open for 90 days after close (stated assumption)

What closes the loop

  • Every restatement is classified by cause, and the causes rank the next policy and coverage backlog
◀  Observability All views Security Trust Zones  ▶
Solution Architecture v1.0 · Microsoft Azure · Cost & Efficiency Architecture · 2026-0920-monthly-close-loop