Map
You confirm which source header supplies each canonical field. Missing required columns stop before money is calculated.
REVENUE CONTROL / BROWSER-LOCAL
Prove every usage dollar before it becomes an invoice.
Choose raw meter events, your pricebook and Stripe invoice lines. MeterProof replays the calculation and shows exactly where the records disagree — without the files leaving this tab.
- No account
- No API key
- Nothing uploaded
- Reproducible ledger
MP-001 · SYNTHETIC2 findings
lineexpectedinvoicedelta
il_tokens$100.00$110.00+$10.00il_reports$35.00$39.50+$4.50Total difference+$14.50 USD
What MeterProof does
MeterProof replays your raw usage events against your effective-dated pricebook and compares the result with Stripe invoice lines, in your browser, without a Stripe key or upload.
YOUR AUDIT
Three files in. One explainable ledger out.
Files stay in memory. Start with the compatible synthetic kit or choose your own exports, then confirm every required join.
NEW · STARTER CSV KITAdapt files that already pass the full audit.
These deterministic downloads are generated from the same source as the worked result.
NEW · AI PRICEBOOK BUILDER
No pricebook.csv? Build one from your pricing document.
Paste an order form, a pricing page or Stripe price JSON. Claude proposes each price row with the sentence it came from; you accept rows one by one, and the deterministic engine does all the arithmetic. Only the text you paste is sent — never your usage or invoice files.
CALCULATING LOCALLY
Validating rows, applying effective prices and building the exact trace…
AUDIT COMPLETE
Reconciliation result
NEW · LOCAL FINDING TRIAGE
Investigate the lines that need attention.
No findings match these filters.
| Line | Status | Quantity | Expected | Invoice | Delta | Calculation |
|---|
WHAT IT CATCHES
The drifts the invoice alone will not show you.
Each finding names its code and the source rows behind it, and every rated line shows its arithmetic. Stripe bills the usage that reached it; MeterProof replays your own event log against your own price rules.
- Usage that was never billed
unbilled_usage - Your events add up to more units than the invoice line bills.
- Billed usage you cannot find
missing_usage - The invoice bills more units than your events record.
- A line with no usage behind it
extra_invoice_line - An invoice line exists for a customer and meter with no events in its period.
- Usage with no invoice line
missing_invoice_line - Events fall in a period no invoice line covers; the line is blocked, never guessed.
- The wrong price revision
stale_price_id - The invoice cites a different price than the rule that governed the usage.
- An amount that does not follow the rule
amount_mismatch - Quantity, tiers, included units and minimums replay to a different amount.
- Events that arrived after close
late_event - Usage ingested after the period ended, flagged for review.
THE CONTROL LOOP
Map. Replay. Explain.
Replay
Events are assigned to half-open UTC periods and rated under every effective price revision that governed them.
Explain
Every result cites source rows, selected rules, exact decimal steps and the declared rounding of each governed segment.
LOCAL BY CONSTRUCTION
Your billing export never becomes our dataset.
No upload endpoint exists. Files are read in this tab, results live in memory, exports use temporary object URLs, and reset or reload removes the run.
BOUNDARIES
Exact where it works. Explicit where it stops.
MeterProof handles flat, graduated and volume usage pricing with effective revisions, included quantities and line minimums. It does not calculate tax, discounts, credits, proration, prepaid balances, revenue recognition or currency conversion.