Does your invoice match what customers used?
Run an example in one click, or use three CSV exports with no technical setup. You'll see each flagged record and why it needs review.
Try an example
Choose a scenario. No file required.
Check your own exports
Upload three CSV files. No JSON editing, no account, no server upload.
Important: when is the invoice comparison valid?
Only if all three files cover the same billing period, quantities use the same unit, and the invoice amounts represent untaxed, undiscounted, linear usage charges. Otherwise, use the audit for event-level diagnostics, not invoice conclusions. This beta cannot validate source completeness.
For safety, use anonymized records only. Each file up to 2 MB, up to 5,000 rows. CSV mapping supports common English header names.
Audit from a link
Paste a public GitHub link to a FIXLAYER JSON export. Your browser retrieves it directly; the data are not uploaded to FIXLAYER.
Use my own JSON instead Advanced
Your file remains in this browser. Use anonymized or synthetic data only. Maximum 2 MB.
Expected fields: usage, metering, credit_ledger, invoices, unit_price and currency. Optional: ingestion_receipts, audit_reference_at, grace_minutes, completed_operations and ai_observations (for AI telemetry correlation). Operation IDs must come from an independently supplied completed-requests register; similar span IDs or token counts alone are not proof. No hidden-token or invoice certification.
Know what's wrong. Know what to do next.
Review what is supported by the data, what still requires evidence, and the next action. Nothing is classified as recovered money.
Confirmed financial recovery
Not verifiedNo vendor-recognized settlement evidence
Cases needing review
0Not proof of incorrect charges
Inconclusive findings
0Missing or insufficient evidence
Source categories supplied
0/4Not verified invoice coverage
Verify the contract, governing price and period, authentic source events, taxes, discounts, credits and final invoice before contacting a provider. This browser audit does not verify recoverable amounts.
Download the redacted Casebook for Case Desk. Full diagnostic JSON contains original data and must be handled as sensitive.
Technical evidence checks and raw diagnostic findings
Complete audit details
Casebook exports omit identifiers and unapproved text. Full diagnostic JSON contains the supplied records; handle it as sensitive.
Is this discrepancy provable?
No amount is classified as verified savings without independent evidence.
Records to investigate
Inconclusive or out of scope
Findings are based on the data you provide; they do not prove money is owed or authorize changes.
Case Desk provides a separate, local investigation journal. Download a redacted casebook above and import it there; data are not silently transferred.
What can this audit check?
Duplicate and missing metering, consumption differences, acknowledged-but-unmetered events, and simple usage-versus-invoice totals. It cannot yet model tax, tiered pricing, discounts, refunds or invoice periods.
Review your operation-to-invoice evidence.
Use the four-ledger tool to compare explicit contract rules, periods and individual invoice lines. It keeps source files local.
Open four-ledger review →Start using FIXLAYER without a waitlist.
Sign in with Google and access the free audit tools immediately. Starter and extra credits are currently available to authorized testers in Stripe Sandbox only. No real payment is collected here.
Email/password accounts, live subscriptions and automatic vendor integrations will open only after their security and billing checks are complete. How it works.