Every difference between your orders and invoices, traced to the source.
Compare purchase orders, confirmations and invoices. Your team makes the call.
100 free credits · No card required
See LineRecon at work
LineReconHHarbor SupplyBatchesTemplatesBillingSettingsSearch or jump to…⌘K240AMBatches / September linen order
- Upload
- Plan
- Review
- Export
Purchase order #207
Delivery date 03/04/2026
| ITEM | SKU | QTY | UNIT PRICE |
|---|---|---|---|
| Bath towels | BT-400 | 120 each | — |
| Cotton sheets | CS-210 | — | USD 18.00 |
| Pillow inserts | PI-080 | 80 each | — |
| Guest soap | GS-010 | 10 boxes | — |
Invoice #904
Delivery date 2026-04-03
| ITEM | SKU | QTY | UNIT PRICE |
|---|---|---|---|
| Bath towels | BT-400 | 40 each | — |
| Bath towels | BT-400 | 80 each | — |
| Cotton sheets | CS-210 | — | USD 18.01 |
| Guest soap | GS-010 | 120 each | — |
Continued on page 2
Invoice 904 is USD 0.01 higher than Purchase order 207.
Same SKU and currency · exact comparison, no toleranceAccepted difference · “Invoice rounding, agreed with the supplier.”
By Alex Morgan · 21 Sep 2026, 17:52Findings 0 of 4 decided1 of 4 decided
Business differences 2
Accepted difference · “Invoice rounding, agreed with the supplier.”
Example data. Open the worked example with the original PDFs
Review the proposed plan, reuse it next time.
You don’t hand-write fields for every batch. LineRecon proposes what to compare, then asks about anything it isn’t certain of, like a missing currency. Save the plan as a template, then choose it for the next batch to reuse those rules.
See a worked example- QuantityNumber
- Unit priceCurrency: USD
- Delivery dateDate
Trace every difference to its source.
Every finding points back to its exact source. Open a difference and see both documents side by side, with the values behind it marked, so your team checks the original numbers, not a summary.
Compare an order confirmation and invoiceHARBOR SUPPLY
Purchase order 207
NORTHLINE TEXTILES
Invoice 904
Your team makes the call.
A difference isn’t automatically wrong. Your team accepts it with a reason, corrects it, or flags it for follow-up. Every decision, and who made it, stays attached to the finding, so the history travels with the report.
Get the review checklistDecision history
Cotton sheets accepted by Alex Morgan
Invoice rounding, agreed with the supplier.
Pricing that follows your workload.
Free
$0
100 one-time trial credits
100 MB storage
Starter
$15/ month
$180 billed yearly
650 credits per month
Rough estimate: about 160 pages/month
1 GB storage
Team
$39/ month
$468 billed yearly
1,700 credits per month
Rough estimate: about 420 pages/month
10 GB storage
Business
$119/ month
$1,428 billed yearly
5,600 credits per month
Rough estimate: about 1,400 pages/month
30 GB storage
Rough guide: about 4 credits per page. A 4-document, 13-page batch used about ⚡54 in our production test with sample documents; dense line items use more.
Annual billing: 2+ months free. One-time credit packs never expire.
See full pricingA few things worth knowing.
Before your first comparison.
What does LineRecon compare?
LineRecon compares purchase orders, order confirmations and invoices for procurement, operations and finance teams. PDF and photo uploads are supported. You choose which fields to compare; orders, confirmations and invoices are examples, not a fixed template. Interpreting contract clauses or judging compliance isn’t part of LineRecon.
Does LineRecon make decisions for us?
LineRecon checks consistency without assuming one source is correct. Your team reviews uncertain relationships and decides whether to accept a difference or follow up. Different units and currencies are never automatically converted, and accepting a difference never erases the original values.
Can we reuse our comparison setup?
Upload a batch, then choose a saved setup while reviewing the proposed plan. Review, adjust and confirm its fields before they apply to this batch. Reusing a setup never copies old document values, learns a permanent rule from a single pairing, or silently approves a new difference.
Do I need to replace my current system?
No. Start with files from your existing workflow. Automatic order entry, ERP posting and external system integrations aren’t part of LineRecon.
How do credits work?
The estimate shows on the button, e.g. Start comparison ⚡12; final credits follow actual usage. Eligible accounts can claim an available trial in Billing. Workspace administrators can buy a subscription or credit pack through Stripe checkout in Billing. If the workspace balance or your member spending limit runs out, work pauses until you choose Continue after the limit is resolved.
Talk to us
Questions, feedback or a workflow we should support? Tell us what you compare.
You can also contact us by email.
Make sense of the details.
Guides for clearer comparisons, plus a worked example with the original PDFs.
Purchase order vs. order confirmation
Check what was requested against what the supplier confirmed.
Order confirmation vs. invoice
Trace price changes, split lines and additional charges.
A reconciliation example, with the sources
Three synthetic documents. Six findings. Every original value preserved.
A checklist for your next review
A free, downloadable worksheet for recording evidence and open questions.
What is business document reconciliation?
Business document reconciliation compares related records across documents to identify consistent values, differences and information that still needs confirmation. A finding records what differs; a person decides what to do next.
Different documents describe different stages.
The OASIS Universal Business Language 2.3 standard defines separate Order, Order Response and Invoice document types. They provide useful context for comparing a request, a supplier response and a bill.
For international trade, the International Trade Administration’s commercial invoice guide describes an invoice as a document between seller and buyer that states the goods sold and the amount the customer pays.
These references explain document terminology. LineRecon’s worked example illustrates our review approach with fictional records; it is not a claim of UBL compatibility or customs compliance.
By the LineRecon team · Updated .