Skip to workspace
PixelOkayFINANCE WORKSPACE
Tools
LOCAL RECONCILIATION STUDIO No account · No upload

Invoice & Purchase Order Reconciler

Compare what was ordered, received, and billed. Find duplicate charges, price differences, quantity discrepancies and missing items—and document every decision.

Private, in-browser analysis Deterministic matching Exportable audit trail
STEP 01

Bring your records

01

Purchase orders

What you approved

0 rows
No files added
02

Supplier invoices

What was charged

0 rows
No files added
03

Delivery receipts

What actually arrived

0 rows
No files added
Load records or open the demo to begin. Rows remain in your browser.
STEP 02

Matching rules

Adjust before reviewing
PO + invoice required; receipts optional.
STEP 03

Reconciliation results

≡

Your matching report appears here

Import a PO and an invoice, or load the included demo. We’ll separate blocking differences from informational exceptions.

Three-way invoice matching without sending files to a server

PixelOkay Invoice & Purchase Order Reconciler analyzes structured supplier invoice lines, PO lines and goods receipt records. It flags potential duplicate invoice charges, PO price variances, invoiced quantities above received or ordered amounts, missing PO items, missing receipts, and possible duplicate deliveries. Partial deliveries and split invoices are aggregated at the supplier–PO–SKU level.

This version supports structured CSV, TSV, TXT and JSON data, not scanned PDF invoice extraction or OCR. Matching is rule-based and auditable rather than a generative AI inference service. Different units of measure, tax rules, freight and foreign-exchange conversion require review outside this tool.

Reconcile purchase orders, invoices and receipts

Import structured CSV, TSV, text or JSON Lines, map each file’s columns, confirm currencies, units and tolerances, then compare purchase-order, invoice and optional receipt lines. Review exceptions before exporting a decision log or restorable project.

Example workflow

  1. Load the purchase order and invoice, then map item, quantity, unit price, currency and identifier fields.
  2. Set the comparison tolerances and, for three-way review, add a receipt file. Inspect duplicates, unit/currency differences and missing receipts.
  3. Review each exception, record a disposition and export the history CSV or project JSON.

Authored example: Enter fictional purchase-order, invoice and receipt rows for three items. Change one unit and leave one receipt quantity short, then review the separate exceptions before recording any decision.

Limits and privacy: Reconciliation compares supplied records; it does not OCR or extract documents, approve payments or convert FX. Missing receipts leave three-way review incomplete. Changing source rows or tolerances invalidates prior dispositions, and editable history is not signed evidence. Review projects for commercially sensitive data before sharing.

Common questions

Does the tool approve an invoice or payment?

No. It flags record differences for human review; it does not approve payments, authenticate invoices or sign an audit record.

Can it read scanned invoices or convert currencies?

No. It accepts structured text data and does not OCR documents or convert FX. Enter comparable values and currencies before reconciling.

Related tools