PDF Invoice Matching for Small Teams

Check the invoice before a difference becomes another email thread

You have the purchase order. The supplier has sent an invoice PDF. Now someone has to check that the quantities, prices and extra charges belong to the same agreement.

LineRecon is being built for this document-checking step: comparing business records, showing the differences and keeping the source evidence close to the review.

Early access: the production upload and processing workflow is still in development. You can explore the example below and express interest today. This page does not provide a live invoice checker.

See the worked example · Explore LineRecon early access

A familiar problem: two PDFs, several questions

Perhaps the invoice uses the supplier’s product descriptions instead of yours. A box price appears beside an each price. One order line becomes two invoice lines. Freight appears at the bottom even though your purchase order says it is included.

A useful review needs to answer more than whether the grand totals agree. It should show which records belong together, which values differ, which differences can be explained and which need a person to investigate.

The planned LineRecon workflow is focused on that review. It is intended for teams that already have the documents and want a clearer way to compare them, without turning the comparison itself into a separate accounting-system migration.

A lower invoice total can still contain higher charges

Consider a fictional purchase order for $1,640.00 and an invoice for $1,512.00, both before tax. The invoice is $128.00 lower. That fact alone does not settle the line-by-line check.

Item	Purchase order	Invoice	Question to review
AX-100	100 each at $4.00	100 each at $4.20	Was the $20.00 price increase accepted?
FX-600	10 each at $12.00	12 each at $12.00	Were the additional two units ordered and received?
Freight	Included	$28.00 added	What supports the extra charge?
EX-500	30 each, $180.00 total	Absent from this invoice	Is this a partial invoice or is another document missing?

Other lines explain the remaining difference. One price is lower, one case quantity is expressed in eaches, and one order line is split across two invoice rows.

These are fictional teaching documents. The table is an editorially prepared comparison, not output from a released LineRecon processing engine. No receiving record or buyer approval of amended terms is included, so the example cannot establish whether payment is due or whether goods arrived.

Download the sample document pack or walk through the full comparison.

What LineRecon is being designed to help you review

Prices and quantities. Compare the values associated with the same business item. Preserve the original units and flag the evidence needed to explain a difference.

Document references. Check the order and invoice identifiers before treating two records as a pair. An identical total does not establish a relationship.

Added or missing items. Surface invoice rows with no corresponding order item, and order items that do not appear on the supplied invoice. A missing line may require another invoice or delivery record.

Supporting evidence. Keep original values and their document locations available when someone has to make a decision or contact the supplier.

Uncertainty. Leave unclear pairings and unsupported conversions for review. A plausible explanation still needs evidence.

These are product-design goals for early access. Supported formats, volume limits, exports and commercial terms must be confirmed when a production offer is available.

Where this fits in your process

Use a document comparison to prepare the review. Continue using your existing approval and payment controls to make the financial decision.

In a straightforward workflow, your team gathers the relevant documents, checks their relationship, reviews the differences and records a decision for each unresolved item. A buyer may confirm a revised price. A receiving colleague may explain a quantity. The finance team may ask for a corrected invoice.

Comparing a PO with an invoice does not establish receipt of goods. Microsoft’s invoice-matching documentation distinguishes checks against the order from checks that also use receipt information.

Is this the right problem to bring to LineRecon?

This direction is relevant when your work begins with existing supplier documents and ends with a checked comparison or a list of questions. You might work in purchasing, operations, a small finance team or a business where one person covers all three.

A wider system may be more appropriate when the main requirement is purchase approvals, goods receipt, inventory control, payment execution or a specific ERP integration. The invoice-matching software guide explains how to compare those options.

For a task you need to complete immediately, the free Excel matching template provides an available starting point.

Questions before you try a document-checking workflow

Can I upload invoices here today?

The production checker is still in development. The sample documents and educational resources are available without uploading your own records. Use the early-access details on the homepage to express interest.

Does a matching total mean the invoice is correct?

No. In the sample, higher and lower prices partially offset one another. A total is one control, while the individual lines still need attention.

Can a document comparison approve payment?

A comparison can inform a decision. Your authorized reviewer still needs to apply purchasing terms, receipt evidence and internal approval rules.

Do I need to connect an accounting system?

The product direction begins with existing documents. Do not assume a named accounting integration is available; confirm the released workflow and its supported inputs before adopting it.

Spend less time explaining what needs checking

Bring the problem you actually have: the documents you compare, the difference you struggle to find and the output your colleague needs next.

Explore LineRecon and request early access.