One Purchase Order, Multiple Invoices: A Partial-Billing Worksheet

To reconcile one purchase order against multiple invoices, track each invoice’s allocation to the relevant PO line and maintain a cumulative billed quantity and amount. Compare the running total with the applicable order revision. Do not compare every partial invoice with the full PO and treat the unbilled balance as an error.

The example below is fictional and separate from this site’s downloadable sample documents. It shows a quantity-based order; deposit, milestone and service billing need the agreed billing schedule instead.

Set up a partial-invoice register

Use one row per invoice-to-PO-line allocation. Record supplier, buyer entity, PO and revision, PO line, invoice and version, invoiced quantity/unit, amount/currency, and source reference. Mark superseded documents separately so they do not enter the active balance twice.

Remaining quantity = ordered quantity − cumulative billed quantity. Keep the amount balance separate: a price change can alter the amount without changing quantity. For an amount-based order, use its agreed value and billing schedule instead.

Section 3 of the free exception-review worksheet includes blank register rows and separate quantity and amount adjustments. It is a manual record, not a connection to your accounting system.

Example: reconcile three partial invoices

Suppose PO-720 orders 100 each of item R-10 at $8.00 each: an $800.00 line before tax, with no additional charges in this example.

Billing document	This invoice	Cumulative billed	PO quantity not yet billed
INV-A	40 each / $320.00	40 each / $320.00	60 each
INV-B	35 each / $280.00	75 each / $600.00	25 each
INV-C	25 each / $200.00	100 each / $800.00	0 each

After INV-B, the remaining 25 each is an unbilled order balance. It does not prove that goods are missing or late. They might not have shipped, might have arrived but not been invoiced, or might have been cancelled under a later revision.

If a new INV-D bills another 10 each, the recorded cumulative billing reaches 110 each and $880.00. The extra 10 each and $80.00 need explanation. Check whether INV-D replaces an earlier document or reflects an accepted order increase before concluding it is excess billing.

Keep billed, received and paid separate

Maintain separate columns for ordered quantity, invoiced quantity, received quantity and payment status. Each comes from a different source. An invoice records a billing claim; it does not establish receipt or payment.

Microsoft’s invoice-matching overview describes checks against PO prices and, for three-way matching, product receipts. That distinction matters when a supplier invoices one delivery in several stages.

If receiving records are unavailable, state that receipt was not checked. If payment records are unavailable, do not label an invoice unpaid merely because it appears in the folder.

Decide which documents enter the balance

Before summing, identify each invoice by supplier, buyer entity, invoice number and applicable version. Keep the original documents, including corrections, but establish which documents represent current billing.

Do not count both an original invoice and its replacement as additional purchases. Equally, do not discard a second invoice just because its amount matches the first: two legitimate deliveries may have identical quantities and prices.

For a credit or adjustment, record its reference and the invoice or line it affects. In a separate variation, a $20.00 price-only credit against INV-B changes cumulative billing from $800.00 to $780.00, while billed quantity remains 100 each. The $20.00 amount gap needs its credit explanation; it does not mean more goods remain to be billed.

Keep signed quantity and amount adjustments separate. Do not subtract one credit twice because it appears in both a statement and a separate document.

Handle several orders or rows on one invoice

Oracle’s invoice-line matching documentation explicitly describes both multiple invoices against one PO and one invoice against multiple POs. Keep those relationships visible in your register rather than assuming one file equals one order.

Allocate each source row to its actual PO and line. One invoice total cannot safely be assigned in full to several orders. Keep unresolved allocations outside the confirmed subtotal and disclose them beside it.

If a single row covers several PO lines, request the allocation evidence or record a human-confirmed split with the original row retained. The split-line guide explains why matching totals alone are insufficient.

If no PO reference is shown, follow the missing-PO-number workflow before adding the invoice to an order’s balance.

Make the scope of the balance visible

A useful handoff states the PO revision, documents included, cutoff date, quantity and amount basis, unresolved allocations, and missing records. “All invoices in this folder total $800.00” is narrower than “this order has been billed exactly once and in full.”

Use a note such as: “PO-720, original 100-each line; INV-A through INV-C included; billed quantity 100 each and amount $800.00 before tax. No receipt or payment records reviewed. Later invoices are outside this snapshot.”

To request an explanation for a possible repeat charge, attach the relevant rows from your register and use the factual structure in the supplier email templates.

Common questions

Does the remaining PO balance equal the amount we owe?

No. An unbilled order balance differs from outstanding invoices and from payment obligations. Keep billing and payment records separate and follow the applicable agreed terms.

Can the existing Excel template maintain this history automatically?

Do not assume it does. The Excel template guide describes its supported comparison and limitations. A running order history needs an explicit invoice register, version handling and allocations like those above.