Aristo's read Grounded in page evidence

Generated reports preserve the figures and basis that existed when each record was filed.

Why it matters: A circulated decision can be reproduced instead of silently changing with the dashboard.
Recommended action: Open or generate the frozen record needed for the next decision.

Chargeback reports

Formal, reproducible records of what the estate cost and who consumed it — generated on demand or on a monthly schedule, and frozen so the copy you send stays the copy they read.

Investigate in Analytics

Reports heldcounted

frozen documents in this library

one page

Ready to opencounted

complete, with their figures frozen

1 not finished

Schedules runningcounted

monthly run generating on its own

0 sponsors named in Settings

Types not builtcounted

named with the reason, rather than hidden

one kind is built

This is the illustrative organisation. Its report below is built on every request and never written.

What that changes, and what your own tenant does instead

Because nothing is written, the sample report always carries the same date. Generating and scheduling are refused here in words rather than hidden — in your own tenant both write, and every run appears in this library with its own fingerprint.

Saved views none yet on Chargeback reports

Why this workspace keeps none

This is the illustrative organisation — it is never written to, so there is nothing here to save. In your own tenant, naming a filter set keeps it for everyone who can open this workspace, and answers it with the numbers as they stand each time somebody opens it.

Generate a report

Choose the period and scope, and freeze today's counted figures into a document that keeps them.

counted

No filter applied Showing: every month Aristo holds (6) All departments All productsChange

No filter applied Showing: every month Aristo holds (6) All departments All products

Monthly department chargeback — covering March 2026 – August 2026, scoped to Every department.

What this report contains, and what generating actually does

What the estate cost, which teams consumed it, how much of what they hold is being used, and what is recoverable — with every figure carrying the word for how it is known.

Generating freezes today's figures onto a document and stores the scope above with them. Opening that document later re-reads those figures — it never recomputes them, which is what makes the copy you send still the copy they read next quarter.

Source: The counted chargeback composition behind the Overview and Analytics workspaces As of: 2026-08-29

Report library

Every report this organisation has generated, newest first. A report is a record: opening one re-reads its frozen figures and never recomputes them.

Scroll sideways for the remaining columns.

Every report generated for this organisation, newest first, with the period and scope it covers, who generated it, and the fingerprint of its frozen figures.
Report	Period	Scope	Generated	By	Status	Figures	Open
Monthly department chargeback — March 2026 – August 2026 Monthly department chargeback	March 2026 – August 2026	Every department	2026-08-29	A leader here	Complete	cceba17c11dd	Open Scope
Monthly department chargeback — July 2026 Monthly department chargeback	July 2026	Every department	2026-08-26	Aristo, on a schedule	Complete	f06f29841735	Open Scope
Monthly department chargeback — June 2026 (Engineering) Monthly department chargeback	June 2026	Engineering	2026-07-29	A leader here	Complete	e640aaeed58b	Open Scope
Monthly department chargeback — May 2026 Monthly department chargeback	May 2026	Every department	2026-07-26	Aristo, on a schedule	Complete	42652362d7f4	Open Scope
Monthly department chargeback — April 2026 Monthly department chargeback	April 2026	Every department	2026-06-28	A leader here	Failed	—	Open
The directory read that supplies the per-team headcount was not authorised when this run happened, so the department sections had nothing to divide by. Nothing was half-written: the run stopped and this row is the record of it.

The Figures column is each report's fingerprint. Two reports carrying the same one carry the same figures — unless the evidence itself changed, which is the case where the newer report is the stronger one.

Schedules

A monthly run that generates the report on its own, at the scope chosen above.

Every month on day 1, covering the most recent month Aristo holds, on its own, scoped to Every department.

The period is worked out on the morning it runs, never stored — a schedule carrying fixed months would generate the identical report every month for the rest of the tenancy, and each run would look perfectly correct on its own.

Scroll sideways for the remaining columns.

The report schedules on this organisation's record, when each next runs, and what its last run produced.
Scope	Runs	Covers	Next	Last run	Audience	Action
Every departmentReference: Illustrative enterprise monthly close · read-only	Day 3 of each month	the most recent month Aristo holds, on its own	2026-09-03	2026-08-26 Complete	0 sponsors
Every departmentReference: Illustrative finance cut · paused · read-only	Day 15 of each month	the most recent month Aristo holds, on its own	Paused	2026-07-26 Complete	0 sponsors

In-app delivery. A scheduled run generates the report, files it in this library, appears in Notifications for every leader, and rings the bell. Its audience is the 0 sponsors named in Settings when it runs. Nothing is emailed and nothing is posted to Teams.

Why email is not wired, and what the audience count resolves to

Since slice 11 a run also appears on Notifications and on the bell in the top bar, which is what in-app delivery looks like when it is real rather than promised. Nothing is emailed and nothing is posted to Teams. Why not, precisely: this product's one piece of outbound machinery is the weekly sponsor digest — an adaptive card, sent to the sponsors named in Settings, on a per-tenant daily send budget, behind the organisation's quiet-mode gate — and riding a report into it needs three things that do not exist. A card design for a report (the digest card is built around the weekly reading and has no shape for a document). A decision about whether a report competes for the same daily send budget every nudge is metered against, or gets its own — nobody has made it, and guessing would mean a monthly report silently suppressing somebody's activation nudge. And an answer for what a person does with a card about a document they must leave Teams to open. A schedule here will never promise a message that does not arrive. The audience column is the 0 sponsors named in Settings: a count resolved when the run happens, never an address book stored on the schedule, so removing somebody in Settings removes them here with nothing else to remember.

Report types this build does not have

Named with the reason, because a missing feature that is explained is a boundary and a hidden one is a hole. 8 of them.

Quarterly executive summaryBudget variance reportCost optimization reportAnnual true-up reportFinance allocation detail and department leader summariesDetailed license analysisCopilot usage analysisShare, email, duplicate and archive

Why each of these 8 is not built

Quarterly executive summary. The executive summary is a live workspace rather than a filed document: it reads the current counted run and moves with it. Freezing a QUARTERLY one needs a composition over three months, which Aristo holds for no tenant yet — so it would be this chargeback report with a wider date on it and a different heading.
Budget variance report. Variance against a BUDGET needs departmental budgets, which this product does not yet hold — the variance section in this report compares months, runs and the consumption cap, which are the endpoints that genuinely exist.
Cost optimization report. The optimization workspace is live and is where these recommendations are read; this report already carries the same ranked list inside it. A separate document would be a second copy of one composition, which is how two surfaces start disagreeing about the same money.
Annual true-up report. A true-up compares what was charged against what was consumed across a full contract year. Aristo keeps every month it measures and does not yet hold a year of them for any tenant, so the report would be mostly labelled estimates wearing an annual title.
Finance allocation detail and department leader summaries. These are the same figures cut for a different reader, and Aristo holds no audience to cut them for: a report carries no audience field and the roles surface grants access to pages rather than scoping a document to a reader. Issuing them now would mean maintaining three copies of one composition with nothing to distinguish them.
Detailed license analysis. A per-SKU analysis needs each product's bought-and-assigned figures over time, and no document in this store carries a SKU name and a period key together: the licence record is a single CURRENT snapshot, and the persisted run keeps aggregate seat counts with no per-SKU breakdown. The report would have one real column and a row of months it could not fill.
Copilot usage analysis. What every run persists is aggregate: how many seats were active, how many were cold, and the activation share. There is no per-person or per-feature usage record behind them, and there deliberately never will be one that this product would print — team figures are reported at a five-person floor and below it they are merged. A usage analysis in the ordinary sense is a person-level document, which is the one thing the covenant does not permit.
Share, email, duplicate and archive. Sharing a report is its link — every one of them is a URL a leader can send, and a second sharing mechanism would be a permission model nobody asked for. Email is not wired and the schedules panel says so rather than offering a control that quietly does nothing. Duplicating is generating again at the same scope, which is the button already on this page. Archiving hides a document a leader asked for, and a register with a hidden row is the one state it may not have.