How to Match Split Invoice Lines to One Purchase Order Line

To match several invoice lines to one purchase order line, first establish that they refer to the same ordered item and scope. Then compare their combined quantity and amount with the PO, while checking each row’s price, unit and delivery reference. Repeated item codes alone do not establish duplicate billing.

The worked example below uses DX-400 from our downloadable fictional documents. It illustrates a manual review method, not a live LineRecon processing result.

Match split invoice lines in five steps

1. Identify the PO line and every invoice row proposed for the group.
2. Check the item, order, destination, unit and currency before grouping.
3. Add the invoice quantities and printed amounts separately.
4. Compare each row’s unit price with the PO; do not rely on the average.
5. Save the source rows, calculation and open questions together.

Use section 1 of the free exception-review worksheet to record your check. It is a plain-text worksheet you can copy into a review note, with no signup required.

Example: one PO line becomes two invoice rows

The PO orders 20 each of DX-400 at $15.00 each. The invoice contains two rows for that item:

Source	Quantity	Unit price	Line amount
PO DX-400	20 each	$15.00	$300.00
Invoice DX-400, first row	12 each	$15.00	$180.00
Invoice DX-400, second row	8 each	$15.00	$120.00
Combined invoice rows	20 each	Check both source prices	$300.00

The quantities add to 20 and the amounts add to $300.00. Both row prices agree with the PO. This explains the arithmetic of the split; it does not prove receipt, authorization or the absence of earlier billing.

In the downloadable pack, the source references are PO-1042 line 40 and INV-8821 lines 4 and 5. Keep all three references with the result so a colleague can reconstruct the group.

Establish the group before summing

Check the supplier and buyer, order reference and revision, item identity, unit and currency. Where an order has repeated items, also check the PO line number, destination, delivery stage or other business context.

For example, two PO lines can both order DX-400 but send it to different sites. Combining every occurrence of DX-400 would hide an allocation error. Likewise, similar descriptions can refer to different sizes or specifications. Use the different-SKU matching guide when item identity needs evidence.

Mark an uncertain group as unresolved. Do not choose the grouping that happens to make the total balance.

Check prices as well as totals

A separate hypothetical variation makes the risk clear: 12 each at $16.00 is $192.00, while eight each at $13.50 is $108.00. The total is still $300.00, but neither price matches the PO’s $15.00.

The first row has a +$12.00 price effect and the second a −$12.00 effect. Netting them to zero conceals two changes that need explanation. A weighted average of $15.00 would conceal them too.

This variation is not in the downloadable PDFs. It shows why a balanced total is only one check, alongside row-level prices and quantities.

Separate split rows from duplicate invoices

A repeated SKU within one invoice can be an intentional split. A second file containing the same invoice can be a duplicate upload. Two different invoice numbers may still bill the same delivery twice. These are different questions.

To investigate repeat billing, compare invoice identities, delivery references, previously recorded quantities and any correction documents. Do not delete one row simply because the description repeats. For billing across several documents, use the partial-invoice running balance.

If the question is whether goods were received, obtain receiving records. Microsoft’s invoice-matching overview distinguishes PO price checks from checks that also use product receipts. A PO and invoice alone do not provide that receipt history.

Copy a split-line review note

PO-1042 line 40 compared with INV-8821 lines 4 and 5: DX-400, 12 + 8 = 20 each, $180.00 + $120.00 = $300.00. Both invoice prices are $15.00 per each. Quantity, price and amount agree for these selected rows. Receipt and prior billing were not checked.

The review checklist provides a place to record evidence and follow-up. If units differ, resolve that question using the case-versus-each guide before comparing quantities.

Common questions

Can I group rows by SKU in Excel?

Yes, after checking the grouping scope and uniqueness. A SKU-only sum can combine different orders, sites or deliveries. Keep source rows and count the records included in each group. The existing Excel guide explains the workbook’s checks and manual-review limits.

Does an exact total mean I can approve the invoice?

An exact total establishes arithmetic agreement for the selected rows. Authorization, receipt and previous billing may still require separate evidence and your organization’s review process.