Finance & Ops
This is the internal page a platform lead forwards when finance needs to understand reconciliation, chargeback, close timing, and who approves spend exceptions. It is not the discovery page for the underlying cost problem.
If you still need the trigger story, start with AI Cost Control. This page assumes the architecture decision is already in motion and stays focused on the ledger and accountability model finance has to co-sign.
What This Page Is For
Finance usually arrives after platform has already decided Keel belongs in the request path. The remaining questions are narrower:
- How estimated spend becomes reconciled actual spend.
- How usage rolls up into tenant, workload, or internal cost-allocation views.
- How period close handles late provider actuals or cost corrections.
- Who signs off when a workload needs to exceed its normal budget path.
Reconciliation Workflow
- Estimated permit — before execution, the permit stores the expected token and cost shape for the approved request.
- Reconciled permit — after execution, closeout attaches provider-reported actuals to the same `permit_id`.
- Correction entry — when provider actuals diverge from the estimate, the ledger preserves the original decision and books the delta instead of overwriting history.
- Period query — finance can read forecast, actual, and variance by tenant or workload without stitching provider exports back to application logs.
Chargeback And Showback
| Allocation view | How Keel helps |
|---|---|
| Per tenant | Each permit already carries tenant scope, so billed usage can roll up to the customer or business unit that actually consumed it. |
| Per workload or product surface | Usage can be grouped by workload name and model route to show unit cost for one feature, service, or internal workflow. |
| Internal cost allocation | The usage ledger exports cleanly into the warehouse or cost-allocation model finance already uses instead of replacing that system. |
Close-Cycle Integration
Monthly close usually needs three things at once: an open-period accrual posture, a clean true-up when provider actuals settle, and a record finance can explain later without reopening engineering logs.
- During the period — estimated cost on issued permits supports provisional accruals and budget tracking.
- After provider settlement — reconciled actuals and correction entries true up the period when token estimates were off.
- During later review — the same ledger shows the original approval, the final actual, and the variance path without re-keying data between systems.
Budget Ownership And Exception Approval
- Platform sees workload-level alerts, block reasons, and route changes first because the permit is issued in the request path.
- Finance owns material cap changes, chargeback policy, and the approval rules for exception paths that affect spend accountability.
- Workload owners supply the business justification when they need to exceed the default budget path.
- Escalations stay visible because the exception path and later outcome live on the same request record.
If finance wants to validate the operating rhythm, use the contact page and ask for a usage-ledger walkthrough with one sample reconciliation period. That is the right close for this audience, not another architecture pitch.