Free tool · No login · OpenAI invoices

AI Invoice
Reconciliation

Reconcile your AI invoices against recorded usage. Compare costs, identify model-level differences, and uncover gaps in your usage data.

Files stay in your browserNo API key neededDownload your findings

Comparison typeProviderAccount / project scopeUse the same scope for both files and invoice figures. This label is not verified.Usage cost basis

01 / Recorded usage

Add your usage costs

Prepare a CSV with record_id,date,cost_usd. Use unique IDs and dates in YYYY-MM-DD format. Costs must be before invoice credits and adjustments. Optional columns: model and customer_id. Use exact matching model names across both files.

Choose usage CSVUp to 2 MB / 50,000 rows. Processed locally; contents are not uploaded.

No file selected yet.

record_id,date,cost_usd,model,customer_id
usage-001,2026-08-01,24.50,model-a,customer-a
usage-002,2026-08-12,35.25,model-a,customer-b
usage-003,2026-08-28,40.25,model-b,customer-a

Use pseudonymous record and customer IDs. Do not include prompts, API keys, or customer contact details. The report contains totals and checks, not individual records.

02 / OpenAI invoice

Enter the invoice figures

Period startPeriod end (inclusive)Usage charges before credits (USD)Only the usage charges covered by your CSV.Credits to subtract (USD)Positive amount. Enter 0 if none apply.Other adjustments (USD)Positive adds a charge; negative reduces it. Exclude tax.Invoice net subtotal (USD)After credits and adjustments, before tax. Not the amount paid or credit top-up.

When selected, your next real-file comparison saves usage and invoice totals, differences, period length, coverage counts, and missing-data flags to our research database. No raw files, dates, account labels, model names, or customer IDs are sent. Sample financial figures are never saved.

Files and form entries stay in this page unless you share a summary or submit the pilot form. We record usage actions, comparison mode, and error stages with a random browser-session ID in our database. Google Analytics receives categorical actions only, not financial summaries or contact details. Reloading clears the form, not previously submitted records. See our Privacy page for details.Research session reference: available after loading

What reconciliation tells you

A clear comparison, with the gaps visible.

Same account. Same period.

Use USD usage costs for the same OpenAI account, projects, and services as your invoice. Dates are UTC and both selected dates are included. Prepare your export using the template; raw token exports and invoice PDFs are not supported yet.

Costs, not token estimates.

Each row supplies an existing usage cost before credits. This tool sums those costs; it does not calculate token prices or verify negotiated rates. Use either request-level records or daily totals, never both for the same usage.

Differences need context.

Late records, different account scopes, rate changes, rounding, or invoice adjustments can explain a mismatch. Missing days do not prove missing usage. Matching totals do not establish completeness or validate every charge.

Expected net subtotal = recorded usage costs − credits + signed adjustments. Compare against the invoice subtotal after these items, excluding tax, prior balances, and payments. A $0.01 tolerance is applied to each comparison. This tool does not assess revenue recognition or compliance.