Missed Price Checker / free & local

You approved a new price.
Did it get billed?

Compare what you billed with the prices that should have applied. Get a review list with the source and calculation for each difference. Start with one supplier or product group.

For pricing managers and controllers at industrial distributors.

See what your pricing team would receive.Try nine fictional invoice lines, including an exception, a billing correction, and a missing unit match.

01 / choose a manageable scope

Bring two exports. Or start in Excel.

You need invoice lines and the approved customer/item prices for the same period. Already have CSV exports? Keep their column names and match them below. Each input can contain up to 10,000 rows and 2 MB.

Prefer working in Excel?

Download the workbook, paste values into its two input tabs, then copy each tab’s headers and populated rows into the paste boxes below. Instructions, a field guide, and separate fictional examples are included.

No macros or external connections. This page reads pasted cells or CSVs, not .xlsx uploads.

A / actual transactions

Invoice lines

What you charged, on which date, and in which unit.

No file selected.

Paste from Excel instead

B / approved commercial records

Customer prices

The intended price from approved agreements or updates, and when it applied.

No file selected.

Paste from Excel instead

Check the price source. A second export of the same stale ERP price will not reveal an unapplied update. Use the approved agreement or update that should have governed the invoice. A supplier cost increase alone does not establish that selling price.

Export missing currency or document type? Dates in another format?

Selected defaults and date interpretations are recorded in the review CSV. Units and approved prices are never inferred.

What to export, and what this version can check

Prepare the records

  • Dates: YYYY-MM-DD. Numbers: decimal point, no currency signs or thousands separators. Slash dates need an explicit setting above.
  • One customer/item/unit/currency price per applicable date. End dates are inclusive; blank means no end.
  • Use sale, credit, or return as document types. Include branch identifiers in invoice numbers if they repeat across branches.
  • Link known billing adjustments to the original sale in adjustment_amount. Positive means additional billing; negative means a customer credit. Use the same currency, once per sale line. Physical returns need a reviewed quantity.
  • Mark documented authorized exceptions yes; retain the supporting agreement.

Know the boundary

  • This checks an approved price against a transaction. A supplier cost increase alone does not establish the correct customer price.
  • Tiered, matrix, wildcard, and quantity-break prices need to be resolved into the applicable customer/item price before using this version. Compare both prices on the same net-of-discount, tax-exclusive basis.
  • No currency or unit conversions. Supported currencies: USD, CAD, EUR, GBP, AUD, NZD, CHF, MXN.
  • Standalone credits and returns are excluded, not matched automatically. Tax, freight, rebates, and discount policies are outside this check.
  • Unit prices support six decimals and quantities three. Line differences round once to the nearest cent, with halves rounded away from zero.

A check you can explain

The rule and the arithmetic stay visible.

Match

Find the applicable price.

Customer, item, invoice date, currency, and unit must match. Missing or overlapping records are held for review.

Compare

Calculate the difference.

(Approved unit price − invoiced unit price) × quantity, rounded to cents, less the signed billing adjustment. No annual extrapolation.

Decide

Give the finding an owner.

Open a row, inspect its source references, and add a decision, owner, and note. They travel with your downloaded review CSV.