19 November editorial batch, prepared for publication on 20 November.
Internal AI cost showback reports what each team consumed and which shared costs it was assigned. Start with direct inference usage by application and owning department. Apply a documented allocation rule to shared charges, and show any unassigned amount separately. Teams can dispute or correct the report before finance uses it for chargeback.
Attribute direct use at the application boundary
Map authenticated workloads to a department and application identifier that the submitting employee cannot change. Keep the department assignment and its effective period so last month’s report remains reproducible after a reorganization. A background document job might belong to the department that commissioned it, even if a central service account submits it. Define that rule before collecting usage.
Record provider account, currency, model, usage class and whether a cost is estimated or billed. Group requests by department, application and period. Reconcile account totals against the provider report before splitting shared amounts. Requests without a recognized owner belong in an unassigned category. The number of rows in that category tells you where to look next. The FinOps Foundation’s allocation guidance describes using metadata and separate strategies for shared costs. FinOps allocation guidance
Choose a driver for each shared expense
Shared model commitments, platform support and general administration need different drivers. You can assign reserved capacity by entitlement and allocate variable platform costs by supported application activity. A simple fixed split can be easier to audit when departments agree who funds the service. Review the driver when capacity or entitlement changes.
AWS Cost Categories documents fixed, proportional and even splits. It also specifies that those split results do not flow into its Cost and Usage Reports or Cost Explorer. If you use that feature, name the reporting surface where finance can actually obtain the allocated results. AWS split charge documentation
Close a hypothetical showback report
Assume Legal consumes $600 of direct inference and Support consumes $1,400. A $300 shared platform fee pays for reserved access. Legal and Support have equal entitlement, so the platform fee is split evenly even though their actual usage differs. There is also $50 of direct usage with missing ownership.
| Cost owner | Direct inference | Shared platform fee | Reported total |
|---|---|---|---|
| Legal | $600 | $150 | $750 |
| Support | $1,400 | $150 | $1,550 |
| Unassigned | $50 | $0 | $50 |
| Total | $2,050 | $300 | $2,350 |
A usage-weighted split would shift $60 from Legal to Support in this example. Either method can be documented, but each answers a different question. Show both the driver and the amount so a team can tell whether a higher report reflects higher consumption or a change to the allocation agreement.
Ask finance to specify which ledger total the report should match. A budget owner may want costs in local currency after credits. An engineering owner may need pre-credit costs to judge whether a feature is efficient. Publish both amounts with labels if the decisions differ, and keep the exchange rate and credit treatment with the report.
Check the report before charging teams
Test an application with a mid-month owner change, a provider adjustment and a central job with no department tag. Recalculate the total from the source records. Check that a credit appears only once and that split allocations sum to the shared amount after rounding. Freeze a version of each closed report and record later corrections alongside it.
Alectura can track estimated spend by organization and feature tags at list prices. Use the platform reference to evaluate what usage your internal applications can attribute at inference time. Keep department mappings, shared allocation and the finance entry in your reporting system. Start with a report for two teams and have both owners review each unexplained charge before moving to chargeback.
Source documents (2)
- FinOps Foundation AllocationChecked
- AWS split charge rulesChecked
Trace a request through Alectura.
Bring a sample prompt and a customer policy. See what reaches the model and which decisions appear in the request record.
