A receiving clerk reports a physical discrepancy to the operations team

Guide

Partial supplier invoices: check cumulative quantities across invoices

Two invoices can each look reasonable while their combined quantities exceed the receipts. Keep a trace of which receipt each invoice uses.

Read the guide

Published

Order, delivery, acceptance and invoice records with one discrepancy

A partial invoice covers part of an agreed order or service. To check it, identify the relevant lines, the receipts supporting them under your rules and the quantities already allocated to earlier invoices. An invoice can look reasonable on its own and exceed the available quantity when you consider the total.

This article covers operational checks for purchased goods. Advance payments, construction progress billing and tax rules require their own configuration with the responsible teams.

Keep three different balances

The quantity still to deliver concerns goods you are waiting to receive. The quantity still to invoice concerns eligible receipts not yet covered by the invoices included in your tracking. The outstanding payment balance concerns entries and payments maintained in accounting.

A partial payment does not create a new receipt. A partial invoice does not prove that an order has been fully delivered. Keep these statuses separate so a paid record does not close an unresolved logistics task.

For successive deliveries and rejected goods, use the partial delivery guide. Here, the question is which receipt quantities each invoice uses for matching.

A cumulative quantity that exceeds the receipts

Fictional example, excluding tax and additional charges to isolate the mechanism. A purchase order covers 100 units at MAD 50 each. Receipt R1 confirms 60 accepted units; receipt R2 confirms another 40.

Invoice F1 covers 60 units, or MAD 3,000, and is allocated to R1. Invoice F2 arrives for 50 units, or MAD 2,500. It has a different invoice number, so it is not necessarily a duplicate invoice.

After F1, only 40 accepted units remain available for a new match. F2 requests 50. The cumulative quantity reaches 110 units against 100 accepted units. The additional ten units represent MAD 500 to clarify in this example.

The check should not alter F2 to make it fit. It preserves the requested 50 units, shows the 40 available units and presents the difference to purchasing and finance. The decision may require a supplier correction, further evidence or an authorised exception.

Keep an allocation record for each invoice line. It connects supplier, purchase order, item, unit, receipt and quantity used for matching. An invoice may cover several receipts; a receipt may support several invoices within the eligible quantity.

Calculate availability for the same order line, unit and confirmed scope. Handle cancellations, returns and credit notes according to their actual effect. A credit that adjusts price does not automatically make quantities available again.

Do not subtract the quantity twice when an invoice moves from proposed to recorded. If the workflow reserves quantities during review, the reservation must become a confirmed allocation or be released after cancellation. Concurrent records must account for these reservations so they cannot claim the same balance.

Check price without hiding the quantity check

An eligible quantity does not prove that the price is correct. Compare unit price, discount, currency and agreed charges separately. Retain the purchase order version applicable to the line.

Microsoft Dynamics 365 documents matching invoiced quantities to selected product receipts, alongside separate price and charge checks. It also describes specific behaviour for total price matching during partial invoicing. Verify your ERP's exact behaviour. Source: accounts payable invoice matching.

Avoid rebuilding the entire check from the purchase order's overall amount. One invoice can cover a fully delivered line and another that is still open.

Handle corrections, credits and cancellations without losing history

When an invoice is replaced, connect the new document to the invoice it corrects. The replacement must not consume the receipt quantity a second time.

When a credit note arrives, identify whether it changes quantity, price, charges or the entire invoice. Have its allocation and accounting entry confirmed. Receiving a credit note PDF does not prove it has been posted.

Duplicate invoice detection remains useful, but answers a different question. Two invoices with different numbers can still cover the same received quantity.

Test the cases that break cumulative matching

Before automating, test at least these situations:

  • two invoices under review claim the same receipt;
  • an invoice arrives before its corresponding receipt;
  • a credit note changes price only;
  • an invoice is cancelled after a provisional allocation;
  • an invoice uses cartons while the receipt uses individual units;
  • an import succeeds but its confirmation is delayed.

For each case, define the expected status and who can resolve it. First check your software's native functions for receipts, allocations and partial invoices.

Keep accounting responsible for the payment balance

Document checks prepare evidence and discrepancies. The accounting system maintains the entries, payments and balances for which it is responsible. Matching documents does not itself authorise payment.

Kaliits can examine purchasing, receipt and invoice matching within your existing process. Prepare an authorised purchase order, its receipts and two successive invoices. Discuss your partial invoice workflow.

All articles

Related reading