Matching Invoice Line Items When Supplier SKUs and Descriptions Differ

To match invoice lines with different SKUs, verify that the buyer’s code and supplier’s code identify the same item in the applicable order. Use an approved cross-reference, manufacturer identifier or specific product evidence. Similar wording should identify candidates, not decide the relationship.

A code mismatch can mean two names for one product, different packaging, a substituted product or an incorrect item. Those cases need different outcomes.

Work through an ambiguous description

Consider this fictional example, which is separate from the downloadable sample:

Source	Code	Description	Quantity
Buyer PO	FLT-10-5	Filter cartridge, 10 inch, 5 micron	24 each
Supplier invoice, candidate A	FC105	Cartridge 10in 5µm	24 each
Supplier catalog, candidate B	FC101	Cartridge 10in 1µm	Sold individually

Candidate A is plausible because its size and filtration specification agree. Candidate B is a different specification, even though most of the description overlaps. An equal price would not remove that distinction.

Suppose the supplier’s order confirmation explicitly maps FLT-10-5 to FC105 for this order. Preserve that confirmation and its page reference, then record the pairing. Without a reliable mapping or sufficiently specific product evidence, keep the relationship unresolved and ask the supplier.

Record the supplier part number and buyer SKU together

For the fictional example, an order-specific mapping could look like this:

Mapping field	Entry
Buyer SKU	FLT-10-5
Supplier part number	FC105
Defining specification	10-inch, 5-micron cartridge
Packaging unit	Each
Evidence	The supplier confirmation for this order
Reuse permission	This order only; future reuse not approved

Add the actual supplier identity, order reference and source location before using the record. Section 5 of the free exception-review worksheet provides those fields.

When can an item mapping be reused?

Before reusing a mapping, check its supplier, specifications, packaging and applicable period or revision. Record who confirmed it and when.

Avoid a global rule such as “FC105 always equals FLT-10-5.” Another supplier might use the same code differently. The same supplier might change its packaging or substitute a revised product.

Confirming an item for this order and approving a reusable mapping are separate decisions. Keep both explicit.

Check identity before comparing value

Use this order of operations:

1. Establish the order and buyer/supplier context.
2. Compare the product identifiers and defining specifications.
3. Resolve packaging and units using documented evidence.
4. Confirm the specific row relationship.
5. Compare quantities, prices and other selected fields.

This prevents a common circular argument: “the amount matches, so the items must match; because the items match, the invoice is correct.”

For case-versus-each differences, use the pack-size calculation. For one item spread across several invoice rows, use the split-line method. Each calculation depends on the identity and scope already being established.

Treat substitution as its own decision

If the supplier shipped a one-micron cartridge instead of the ordered five-micron cartridge, do not rename the invoice row to make it look identical. Record the original specifications and the substitution question.

An authorized buyer might accept a substitute for a particular use. That business decision does not mean the source documents originally agreed, and it does not authorize the same substitute next time.

If the invoice has a typographical error but the underlying product is correct, request clarification or a corrected document. Keep the supplier’s explanation linked to the original evidence.

Use fuzzy matching to organize review

Text similarity can help a reviewer find “10in 5µm” when searching for “10 inch, 5 micron.” It can also put “10 inch, 1 micron” nearby. A similarity score measures the tool’s matching signal; it is not evidence that the products are interchangeable.

For evaluating any matching tool, include difficult negatives in a test set: same name with different dimensions, same price with different pack sizes, reused codes across suppliers and superseded product revisions. Record wrong pairings separately from missed matches. This is a suggested evaluation method, not a measured accuracy claim about LineRecon or a competitor.

Make the final explanation specific

For the example, a review note could say: “FLT-10-5 paired with FC105 based on the supplier confirmation for this order; 10-inch, 5-micron specification and each unit agree. FC101 excluded because it specifies 1 micron. Price and quantity checks recorded separately.”

If there is no reliable order reference either, begin with the missing-PO-number guide.

Common questions

Is a matching barcode enough?

Check what the identifier refers to and the packaging level. The matching identifier helps establish identity, but it does not prove the ordered quantity, price, receipt or payment status.

Can I save a mapping after one confirmed match?

You can record it for that case. Reusing it later should be a separate, explicit decision with supplier, product, packaging and revision boundaries.