--- title: "Matching an invoice when the supplier delivers only part of an order | R&D COPILOT" lang: en canonical: https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/ content_version: f5519551857bb8e5b64a6f38252d7fde7d3c8c1178e53947d16d2e3dc1e58f51 contact: https://rdcopilot.com/contact/ --- [RDC](https://rdcopilot.com/) [Insights](https://rdcopilot.com/insights/)ERP ERPWorkflow # Matching an invoice when the supplier delivers only part of an order A partial delivery should create a clear purchasing decision, with the order, receipt and invoice visible together. The useful automation is the connection between those records and the person authorised to resolve a difference. This guide explains how RDC can structure that workflow so a shortage does not disappear inside a spreadsheet or become an unexplained block for finance. By R&D COPILOT6 October 20264 min read In this guide 1. [Separate the supplier’s claim from the goods received](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-1) 2. [Match individual lines using agreed units](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-2) 3. [Give each discrepancy a decision and an owner](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-3) 4. [Handle later deliveries without rewriting the first receipt](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-4) 5. [Keep documents and access close to the workflow](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-5) 6. [Test the exception queue, then measure its usefulness](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-section-6) [Sources & inspiration](https://rdcopilot.com/insights/erp-partial-delivery-invoice-match/#guide-sources) ## Separate the supplier’s claim from the goods received Consider an illustrative order for 100 identical components. The warehouse receives 60, while the supplier sends an invoice for 100. Those three quantities describe different events: an agreement to purchase, a physical receipt and a request for payment. Preserve them independently. Changing the receipt to 100 merely to make the invoice match would remove the evidence the business needs. The receiver should record the delivery reference, receipt date, item identity, quantity and condition. Finance attaches the invoice without treating its arrival as proof of delivery. Purchasing can then confirm whether the remaining 40 are expected later, cancelled or disputed. The workflow supports that decision; it does not choose a commercial or accounting treatment from the numbers alone. ## Match individual lines using agreed units A supplier may invoice boxes while the order uses individual components. Before comparing quantities, establish the conversion for the particular item and packaging version. Do not apply a general conversion inferred from a description. Keep both the supplier’s original quantity and the normalised quantity visible so a reviewer can explain the comparison. Match lines using stable order and item references where possible. Similar descriptions can conceal different variants, and a supplier may split one order line across several deliveries. The matching record therefore needs links to multiple receipts, not simply one delivery number stored on the invoice header. Freight, discounts and service lines need their own agreed handling because they may not correspond to physical goods received at the dock. ## Give each discrepancy a decision and an owner Create a review item for the precise difference. A quantity shortage belongs first with the person who can check receipt and supplier expectations; a price change may belong with purchasing; an incorrect invoice reference may require supplier correction. A single generic blocked state gives no useful instruction to any of them. Set out the decision choices and the evidence each requires. The person reviewing a difference should see previous conversations and know whether another reviewer is already working on it. If approval authority depends on value or business unit, use the company’s agreed rule and record the version applied. - Confirm the physical quantity with the receiving record. - Check whether another receipt belongs to the same order line. - Ask purchasing to confirm the remaining delivery commitment. - Record the supplier’s correction or agreed next action. - Send finance the decision together with the original documents. ## Handle later deliveries without rewriting the first receipt When the remaining goods arrive, add a new receipt. The system can recalculate the unmatched quantity while preserving the earlier decision history. This matters if the second delivery is short again, arrives damaged or belongs to a different order. A reviewer must be able to reconstruct what was known when a previous approval was made. A corrected invoice should also remain connected to the original submission. Decide with finance how replacement documents and credit documents enter the existing accounting process. An integration should not assume that a new file means a new liability, nor silently replace a document already used downstream. Use stable transaction references and display whether the accounting handoff has been requested, accepted or returned for correction. ## Keep documents and access close to the workflow Store the invoice, receipt evidence and approval history where the authorised teams can retrieve them together. The receiving employee may need delivery details without needing every financial field. Purchasing may need the supplier conversation, while finance needs the reviewed outcome. Build these views around real responsibilities and check exported files as well as on-screen permissions. RDC can scope an EU-hosted document workflow or connect a deployment to company-managed storage. Review document retention, support access, backup recovery and the location of any extraction service used to read invoices. If AI assists with reading a document, retain the original page beside extracted fields and require review for uncertain matches. The arithmetic and approval rules should remain explicit and testable. ## Test the exception queue, then measure its usefulness Use a short set of representative cases: one full delivery, two partial deliveries, a damaged quantity, a duplicate invoice and a corrected price. Ask the warehouse, purchasing and finance teams to resolve each case using the proposed screen. A successful rehearsal leaves a clear explanation of the accepted quantity, remaining commitment, responsible person and next action. Measure the age of unresolved differences, repeated document requests, corrections after handoff and cases returned by finance. Separate waiting for a supplier from waiting for an internal decision, because these need different interventions. Do not reward the team merely for closing more exceptions if the same problems reappear later. RDC can connect the order data, document review and accounting handoff, then help the team refine the workflow using its own operating evidence. Inside the product ## ERP [![Purchase order with goods, ownership and approval steps.](https://erp.rdcopilot.com/product-demos/erp/gallery-overview-en.png)View full size](https://erp.rdcopilot.com/product-demos/erp/gallery-overview-en.png) Purchase order with goods, ownership and approval steps. [![Corrected supplier invoice matched to a partial receipt and approved for finance.](https://erp.rdcopilot.com/product-demos/erp/gallery-detail-en.png)View full size](https://erp.rdcopilot.com/product-demos/erp/gallery-detail-en.png) Corrected supplier invoice matched to a partial receipt and approved for finance. Swipe or use the arrows to explore. Image 1 of 2 Follow the references ## Sources & inspiration ### [AntWMS](https://devpost.com/software/antwms) Devpost project by Mohammad Rafaquat Alam Independent inspiration for workflow design. This independently created project is credited as inspiration. The workflow and implementation guidance in this article are RDC’s analysis. - [Odoo official control policies and three-way matching](https://www.odoo.com/documentation/saas-18.3/applications/inventory_and_mrp/purchase/manage_deals/control_bills.html) Put the guide to work ## Start with your workflow. Tell us what your team needs to do, which systems are involved and where the current process slows down. [Discuss your project](https://rdcopilot.com/contact/?product=erp) [Explore ERP](https://erp.rdcopilot.com/en/products/erp/) ERP ## Keep exploring. [All guides](https://rdcopilot.com/insights/) Workflow ### [From sales invoice to SAF-T: keeping ERP, e-Factura and D406 consistent](https://rdcopilot.com/insights/erp-efactura-saft-consistency/) A practical workflow that keeps one sales invoice consistent from the ERP through e-Factura, period close and the D406 SAF-T file, with a differences queue for review. [Read guide](https://rdcopilot.com/insights/erp-efactura-saft-consistency/) How-to guide ### [Roles, permissions and change history when several companies share one ERP](https://rdcopilot.com/insights/erp-multi-company-roles-permissions/) How to set company boundaries, task-based roles, approval limits and a reviewable change history when a group of companies runs on one ERP, plus a quarterly access review. [Read guide](https://rdcopilot.com/insights/erp-multi-company-roles-permissions/)