LineRecon is being built to compare the fields that matter and trace differences back to their sources. Review quantities, prices and references, with the final decision in your team’s hands.
In development. Try the synthetic demo below.
Select a finding to see its original source on both documents.
Interactive sample.Synthetic documents, prepared findings
Check what was requested against what the supplier confirmed.
A finding is not an approval. The decision stays with you.
AQ-6208 · Line 10 · Page 1
Pack: 10 pieces/carton. Ordered: 12 cartons.
WL-3106 · Line 10 · Page 1
120 pieces = 12 cartons x 10. Less $0.50/piece.
The documents state a pack size, but the recorded quantities use different units. LineRecon preserves both original values and does not convert them into an automatic match.
AQ-6208 · Line 10 · Page 1
Pack: 10 pieces/carton. Ordered: 12 cartons.
WL-3106 · Line 10 · Page 1
120 pieces = 12 cartons x 10. Less $0.50/piece.
The confirmation also records a $0.50 per-piece discount. The purchase order uses a carton price. These are different price bases; no converted or derived net-price equivalence is asserted.
AQ-6208 · Line 30 · Page 1
Item reference and dimensions not supplied.
WL-3106 · Line 30 · Page 1
100 pieces. Confirm item specification with buyer.
The PO does not specify an item reference or dimensions. The supplier has selected a 40 × 60 cm bath mat. Equal quantities and prices do not prove it is the requested product.
Check confirmed items and prices against the supplier’s invoice.
A finding is not an approval. The decision stays with you.
WL-3106 · Line 10 · Page 1
120 pieces = 12 cartons x 10. Less $0.50/piece.
WL-8814 · Line 10A + 10B · Page 1
Batch LIN-A17. 4 cartons x 10 pieces.
Batch LIN-A22. 8 cartons x 10 pieces.
Invoice lines 10A and 10B share the DC-220 item reference and use the same unit and currency as the confirmation. Their quantities and printed line amounts sum to the confirmed values. This sample assumes the record relationship has been confirmed.
WL-3106 · Line 20 · Page 1
300 pieces. Hemmed edges.
WL-8814 · Line 20 · Page 2
Batch LIN-N08. 300 pieces at invoiced unit price.
The napkin item and quantity match, but the invoiced unit price is higher. Each document’s line arithmetic is internally consistent; the difference is between the documents.
WL-3106 · Totals · Page 1
WL-8814 · Totals · Page 2
The invoice adds $85 in freight. Its merchandise subtotal is also $60 higher because of the separate napkin price difference. The $145 total difference must not all be attributed to freight.
Fictional companies and precomputed findings. No files are uploaded or processed here. Hotel linens are one example, not an industry restriction.
Practical guides and a worked example for reviewing business documents, one source at a time.
Check what was requested against what the supplier confirmed.
Trace price changes, split lines and additional charges.
Three synthetic documents. Six findings. Every original value preserved.
A free, downloadable worksheet for recording evidence and open questions.
Quantities, prices, delivery dates, references. Your team decides which fields matter before a batch is processed.
Upload the batch, then review the proposed comparison plan. Adjust the fields, resolve unclear details, or explicitly reuse a saved setup before confirming the plan and starting the comparison.
An illustrative set of fields for a supplier review.
| Field | What to look for |
|---|---|
| Item reference | The product code printed on each source |
| Quantity | The recorded amount and its original unit |
| Unit price | The stated price, currency and pricing unit |
| Delivery date | The date as written, with ambiguity flagged |
Keep the setup for next time.
Reuse field definitions, never last batch’s business values. Review and confirm before applying.
Some differences are errors. Others are agreed changes. LineRecon is being built to make the evidence clear, so your team can make that call.
Review both sources together. A correction or accepted difference never overwrites the original evidence.
Uncertain record relationships need your confirmation. Different units and currencies stay not comparable.
Accept a difference with a reason, or mark it for follow-up. New result versions retain the history.
Keep your existing business systems. The planned workflow starts with files and ends with a review you can trace.
Bring the PDFs or photos you want to compare together. Keep the original files as evidence.
Review the proposed fields and unclear details. See estimated credits before starting paid analysis or comparison.
Follow each finding to its sources. Confirm uncertain pairings and record your decisions.
Planned Excel and PDF reports include unresolved items, so open questions stay visible.
Full document processing and report export are in development. This site demonstrates the review experience with prepared examples.
Planned credit-based pricing, with one-off credit packs and optional subscriptions. See an estimate before processing; final credits reflect actual model usage.
Work pauses if credits run out.
Top up, then choose when to continue.
Packages and prices are still being finalized.
No payment is collected on this site.
What LineRecon is for, and where it is today.
Not yet. The complete processing and review workflow is in development. You can explore the synthetic sample and request early access. This website does not accept document uploads or payments.
LineRecon is being built for procurement, operations and finance teams comparing business documents. PDF and photo inputs are planned. You choose the fields to compare; orders, confirmations and invoices are examples, not a fixed template. Interpreting contract clauses or judging compliance is outside the first version.
The companies, products and transactions in this demo are fictional. Findings are prepared examples, not live AI output. The highlighted pages come from the downloadable sample PDFs, so you can inspect the original values yourself.
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 or currencies are not automatically converted, and accepting a difference does not erase it.
In the planned workflow, upload the batch first, then choose a saved setup while reviewing the comparison plan. Review, adjust and confirm its fields and settings for this batch. Reusing a setup does not copy old document values, learn permanent rules from a pairing or silently approve new differences.
No replacement is planned. Start with files from your existing workflow. Automatic order entry, ERP posting and external system integrations are outside the first version.
Planned pricing uses credits, with one-off packs and optional monthly or annual subscriptions. Page counts help estimate usage; final credits reflect actual model usage. Work pauses on insufficient balance and resumes when you choose Continue after topping up. Prices and packages are not finalized.
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.
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 .
Tell us what your team reconciles. Help shape an early version around the details that cost you the most time.
Early access, built with your input.
No payment. No document uploads.
Share a little about your needs. We’ll use your email to follow up on this request.
You can also contact us by email.
