Domain 4 · Manage the FinOps Practice
Invoices teams read on day one.
Invoicing and Chargeback is where FinOps meets finance. CloudMonitor produces per-cost-group invoices, GL-ready exports, and a showback-first workflow — because the Foundation framework's order is showback, then chargeback, not the other way round.
The problem
Chargeback that nobody trusts.
Invoices land month-end-plus-five.
By the time the cost team has shaped the data into per-team invoices, the period is closed and the conversation is academic.
Journals hand-keyed.
Finance hand-keys GL entries from a CSV. Errors are inevitable; the next month opens with reconciliation work the team didn't budget for.
Chargeback before showback.
Chargeback gets imposed without weeks of showback first. Engineering reads the invoice as a tax, not a signal. Adoption rolls back inside a quarter.
How CloudMonitor answers
Invoices the GL recognises.
Per-cost-group invoices.
A per-team, per-product, per-BU invoice ready the day after close. Same numbers as the master bill — they just roll up the right way.
GL-ready exports.
Journal-ready CSV or API push for the GL — accounts, cost centres, departments mapped to the same allocation tree as the report.
Showback first.
Showback workflow as the default — teams see what they're spending before any journal entries move. The order the Foundation framework actually recommends.
Acceptance workflow.
Cost-group owners review and accept the invoice before journal posting. Disputes land before the GL, not after.
Outcomes
Chargeback engineering actually accepts.
Day +1
Invoices ready after close
GL
Export, not hand-key
Showback
Before chargeback, always
See a per-team invoice and a GL export.
The demo tenant ships a closed-period invoice run and an acceptance workflow.