Get started
01 / 03Invoice reconciliationBounded arithmetic · zero retention
FinOps & Audit

Reconcile a closed bill against the prices that stood over it.

Zero retention · Bounded when list prices moved mid-month · Evaluating a forward vendor quote? Check single-rate terms at /quote →

02 / 03Billing window workbookIn-memory POST · historical periods
Zero retention invoice reconciliation

Usage counts and stated vendor invoice totals are reconciled in memory against historical Witness price periods and never written to disk, database, or logs.

Sample invoice windows
Window Reconciliation

At list, the 100,000 priced units of this window cost $800.00, covering every unit that ran. The stated spend of $960.00 is 20 percent above list.

Window: 2026-09-01 to 2026-09-30Units: 100,000Coverage: 100.0%
1. Derived Witness List CostExact period match
$800.00across 100,000 priced units over 2026-09-01 to 2026-09-30
2. Stated Invoice ComparisonStated: $960.00
20% above published listcomparing $960.00 stated invoice against $800.00 list
3. SKU Line Breakdown1 line
SKUUnitsList Per UnitWindow List Cost
anthropic/claude-sonnet-5100,000$0.008000$800.00

List prices only: what was actually paid is whatever the bill says. A supplied spend line is compared here and stored nowhere.

Cost only, where no production success rate is recorded at or before the window's end. Cost per successful unit is derived only from a measurement somebody entered, never assumed at 100.

Reconciled in memory with zero retention; supplied vendor invoice lines and usage counts are never stored.

03 / 03Three refusalsBounds · whole-window coverage · no retention
Three Refusals

Bounded arithmetic rather than interpolated guesses.

01 / 03

Bounds instead of interpolation

When a vendor changes list prices mid-month and your usage export carries only a monthly total, Vitna reports the exact minimum and maximum list cost bounds rather than assuming uniform daily traffic.

02 / 03

Whole-window coverage rule

A SKU with a coverage gap inside the billing dates is marked unpriced and excluded from the sum rather than silently priced at zero, and whole-window discounts are refused unless 100% of units are covered.

03 / 03

Zero retention by construction

Realised spend and monthly token volumes are bilateral operational data. Both this page and POST /api/v1/reconcile compute in memory and discard the payload on return.