Three way invoice matching compares a supplier invoice with the approved purchase order and the buyer’s recorded receipt evidence. For hardware importers, a reliable match begins with the same SKU, pack, revision and unit basis across all three records, then reconciles quantities and agreed prices. A receipt entry does not automatically prove inspection acceptance, and a partial delivery does not automatically make an invoice wrong; the buyer must apply the actual contract, payment terms and finance policy.
What does three-way invoice matching check?
Three-way matching is a control used in procurement and accounts payable to compare three related records: what was authorized for purchase, what the buyer recorded as received, and what the supplier billed. The purchase order sets the approved commercial baseline. Receipt records show what the buyer or its receiving agent posted as delivered. The invoice states what the supplier is requesting payment for under the agreed terms.
Microsoft’s Dynamics 365 Finance documentation describes matching invoice prices to purchase-order prices and invoice quantities to selected product receipts, with tolerance behavior configured by the organization. Oracle’s procurement documentation also distinguishes receipt and inspection-related matching options. These are software-specific examples, not universal payment rules or requirements for every importer. See the official Microsoft explanation of invoice matching و Oracle’s receipt and inspection matching options.
For a metal bathroom or home-storage order, the three records can contain different naming conventions. The purchase order may list a buyer SKU; the supplier’s invoice may use an internal product code; a receiving log may identify cartons and pack counts. The buyer needs a controlled mapping that proves these records refer to the same physical item and sellable unit.
Three-way matching is not the same as deciding whether a supplier is trustworthy, whether goods meet quality requirements or whether payment is legally due. It is a reconciliation procedure under the buyer’s accounting controls and contract terms. If records disagree, the discrepancy should be investigated by the responsible owner rather than silently edited to force a match.
How do the purchase order, receipt and invoice differ?
The purchase order records what the buyer authorized under its order process. It may include the product and SKU, quantity, unit, price, finish, packaging, delivery terms, payment milestones and referenced specification. If the order has revisions, the buyer needs to know which revision was accepted and whether later changes were properly approved.
A receipt record is evidence that goods arrived at a receiving point and were recorded. It may represent the whole shipment or a partial delivery. It can identify cartons, quantities and dates. Depending on the buyer’s process, a receipt may be posted before inspection is complete. A receiving record should not be invented from a supplier’s packing list or dispatch notice; those documents can support reconciliation but do not necessarily establish destination receipt.
An invoice is a supplier’s request for payment for goods or services under the agreed commercial arrangement. It may cover a whole order, a partial shipment, an agreed advance, tooling, freight, or another item. The invoice must be interpreted against the actual order and payment terms, not against an assumed rule that every invoice can only be issued after receipt.
| Record | Primary question | Useful hardware fields | Not established by the record alone |
|---|---|---|---|
| Approved purchase order | What did the buyer authorize? | SKU, product revision, quantity, unit, price, finish, pack and terms | What was delivered |
| Receiving record | What quantity did the buyer record as received? | SKU/carton mapping, receipt date, quantity, condition notes and location | Whether goods passed quality inspection or are accepted under all terms |
| Supplier invoice | What is the supplier billing under the agreed arrangement? | Invoice line, product reference, billed quantity, unit price, charges and terms | Whether the quantity was received or whether quality acceptance is complete |
| Inspection record | What was checked and what is its status? | Sample/lot, inspection scope, hold or release status, observed discrepancy | Payment obligation or the accounting match by itself |
Keep inspection records visible but separate. Some systems can make invoice approval depend on inspection acceptance; others may apply receipt-based or order-based rules. The buyer’s configuration and contract determine the procedure. A receiving clerk should not mark an item “accepted” merely because it appears on a packing list, and finance should not infer product quality from a successful quantity match.
Why do SKU identity and unit basis matter?
Matching the wrong item perfectly still produces a bad control. A hardware order may contain a towel bar in two finishes, a matching ring, mounting kits, replacement parts and retail packs. Similar names can conceal different dimensions, BOM revisions or pack contents. The buyer must align the physical SKU and unit across the order, receipt and invoice.
Suppose a buyer orders 100 kits, where each kit contains a pair of hooks and one hardware bag. The invoice says “100 sets,” but the receipt record says “200 pieces.” Those values may be consistent if the piece count refers to hooks, or inconsistent if it counts kits. The mapping must be explicit. A case pack may also contain several retail units, so carton quantity is not automatically the same as sellable-unit quantity.
Use a defined unit conversion if the order and invoice use different units. Record the conversion basis and confirm it is approved. For example, a purchase order may be in sets while a supplier packing list reports individual pieces. The buyer should not add both quantities together or treat the piece count as a second delivery. Reconcile the underlying number of sellable units and the packaging hierarchy.
Product revisions matter too. A revised mounting plate or included screw bag may change the description without changing the buyer’s short SKU. Make sure the order references the correct approved revision and that receipt evidence maps the delivered configuration to it. A name match is not sufficient if the physical product changed.
If the buyer needs help with quantity bases before issuing an order, use the separate guide to MOQ, order multiples and case packs. That article covers pre-order unit and quantity definitions; this guide focuses on matching order, receipt and billing records after the transaction begins.
Track unique receipt events and cumulative balances without double-counting.
How should a buyer reconcile partial deliveries?
A split delivery creates several receipts against one purchase order, or separate approved orders depending on the transaction. The buyer should maintain cumulative received and billed quantities so each new invoice or receipt is compared to the correct balance. A later delivery must not cause the earlier quantity to be counted again.
Consider a purely hypothetical order for 100 bathroom accessory kits. The buyer records 60 kits received on the first delivery and 40 as expected later. The supplier invoices for all 100 kits. That invoice is not automatically an error: the buyer must check whether the agreed terms allow billing at order, shipment, milestone or receipt. If the arrangement requires receipt-based billing, the buyer should reconcile the 60 currently recorded against the invoice and route the balance according to its policy. If the arrangement allows an advance or shipment milestone, the buyer should match the invoice to the agreed trigger and supporting evidence.
When the remaining 40 kits arrive, create a new receipt record linked to the same purchase order and delivery reference. Do not re-enter the original 60. The cumulative receipt should be 100, subject to the buyer’s records. If a second invoice covers the later delivery, match it to the correct order and receipt balance, ensuring the total billed amount does not exceed the authorized commercial basis unless a documented change or charge was approved.
A practical line ledger can include:
| Field | Entry for each order line or receipt event |
|---|---|
| PO number and revision | Approved order record and change reference |
| Buyer SKU / supplier item | Exact mapping of the physical item and pack |
| Unit and conversion | Piece, pair, kit, set or carton; approved conversion if needed |
| Ordered quantity | Authorized quantity at the controlling revision |
| Receipt reference and date | Individual delivery/receiving event |
| Quantity this receipt | New quantity posted for this event only |
| Cumulative received | Sum of unique posted receipt events |
| Invoice reference and billed quantity | Each supplier billing event |
| Cumulative billed | Total billed quantity or value by the agreed basis |
| Inspection status | Separate record: pending, released, held or other buyer-defined state |
| Difference and owner | What does not reconcile and who must investigate |
| Disposition | Corrected record, approved change, claim route or documented exception |
The ledger should distinguish source documents. A packing list says what the supplier says was packed. A carrier record may say what was handed to a carrier. The buyer’s receiving record says what the receiving operation posted at the destination. These documents can be reconciled, but they are not automatically equivalent.
Physical receipt and inspection status should remain separate records.
What should happen when received goods are under inspection?
Receiving and quality acceptance are different statuses. A shipment can be physically present while some units await inspection or remain on hold. The accounting match may use posted receipts, inspection-accepted quantities or another configured basis. The buyer should confirm which process is in force and ensure that receiving and accounts payable do not collapse the statuses.
For example, if 60 kits arrive and 5 are held for inspection, the receipt record might show 60 physically received while the quality record shows 55 released and 5 under review. The exact accounting treatment depends on the buyer’s system, policy and contract. Do not silently reduce the receipt to 55, mark the 5 rejected, or withhold payment solely from this example. Record physical receipt and inspection status separately so the appropriate owner can apply the actual rule.
If the inspection finds a dimensional, finish or packaging issue, route it through the buyer’s established quality and claim process. A correct quantity match does not settle a defect claim. Conversely, an open quality review does not by itself establish that the supplier invoice is incorrect. The supplier and buyer should work from the agreed inspection criteria, evidence and commercial remedy.
Oracle’s documentation illustrates that approval settings can distinguish receipt from inspection acceptance in a configured system. That detail should not be transferred to another ERP, contract or buyer’s process as a universal rule. Ask the buyer’s accounting owner which status drives matching and approval.
Which invoice discrepancies need investigation?
A mismatch should be routed according to its cause. A wrong product or quantity can originate in the purchase order, receipt, invoice or SKU mapping. A price difference may come from a later approved change, currency basis, surcharge, discount or invoice error. A packaging or freight line may be governed by separate terms. Do not assume a single cause before reviewing the source records.
| Observed mismatch | First records to compare | Likely owner to investigate |
|---|---|---|
| Invoice SKU differs from PO | Approved item mapping, quote and PO revision | Buyer and supplier documentation owner |
| Invoice quantity exceeds current receipt | Partial delivery records, payment trigger and contract terms | Receiving, AP and procurement |
| Receipt quantity exceeds PO quantity | Change order, over-delivery approval and count evidence | Buyer purchasing and receiving |
| Unit price differs | Accepted quotation, PO revision, approved change and currency | Procurement and AP |
| Kit/piece/carton totals do not align | Pack definition and approved unit conversion | Product data, receiving and supplier |
| Shipment appears short | Carton records, receipt count and carrier evidence | Receiving/logistics under buyer’s claim process |
| Goods are on quality hold | Inspection record and buyer acceptance procedure | Quality and the designated commercial owner |
| Credit or replacement is pending | Approved claim disposition and related invoice/order | Procurement/AP under the agreed remedy process |
If there is a physical shortage, use a receiving investigation and preserve supporting evidence. Koitor’s existing guide to short-carton and SKU reconciliation covers that problem. If the parties have already agreed a credit or replacement remedy, follow the separate supplier credit-note and replacement-goods process. Three-way matching should route these issues, not repeat or replace those workflows.
Does invoice matching change payment terms?
No. A matching workflow does not rewrite the agreed payment arrangement. A buyer may have advance payment, deposit, shipment milestone, receipt-based billing or another negotiated structure. The invoice should be reviewed against the actual contract, accepted purchase order and applicable payment terms. Do not assume that every invoice must wait for destination receipt or that every discrepancy permits a payment hold.
The buyer’s finance and procurement owners should determine how a match exception affects approval. The supplier should be given a specific question and the relevant order or receipt reference. If the problem is an invoice arithmetic error, request a corrected document through the buyer’s approved procedure. If the issue is a quantity discrepancy, investigate the receiving evidence. If an advance milestone is being invoiced, verify the milestone and contract rather than trying to match it to a receipt that the terms do not require.
This guide does not provide jurisdiction-specific tax, accounting, audit or legal advice. Buyers should use their finance team’s policies, ERP configuration, commercial terms and qualified advisers where needed. Software documentation can explain one system’s behavior, but it cannot establish the requirements for another organization.
How can importers keep records useful across teams?
Procurement, receiving, quality and accounts payable often use different identifiers and timing. A good record set makes the relationship visible. Use the PO number and line as the common key, add the buyer SKU and physical description, preserve the supplier invoice and delivery references, and record receipt events individually. If the buyer has a supplier code or product revision, include that too.
Do not rely only on email subject lines or an invoice file name. Store the actual records in the buyer’s controlled document system, with access appropriate to the commercial information. Maintain a log of changes to quantity, unit price, packaging, finish or shipment scope, and link each change to its authorization.
When suppliers use different item codes, maintain a controlled cross-reference. Do not ask the supplier to change an invoice to a fabricated identifier merely to make a spreadsheet match. Instead, map supplier item, buyer SKU and physical configuration transparently. The mapping should be reviewed when the product, pack or revision changes.
For split shipments, the receipt log should identify each event’s date, quantities and evidence. If the same carton appears in two records, verify whether one is a duplicate posting before summing. If one packing list reports cartons and another report lists units, document the conversion. Keep open balances visible so a later receipt can be matched without re-counting previous deliveries.
What mistakes should importers avoid?
Mistake 1: using the packing list as proof of destination receipt. The packing list helps identify what the supplier says was packed; the buyer still needs its own receiving record or other approved evidence.
Mistake 2: counting the same delivery twice. A supplier packing list, carrier record and warehouse receipt may all describe the same units. Reconcile their relationship rather than adding all numbers.
Mistake 3: matching only the product name. Similar names may represent different finishes, sizes, kit contents or revisions. Use a SKU and configuration mapping.
Mistake 4: comparing pieces with kits or cartons without conversion. State the unit basis and conversion rule. Do not assume “set,” “pair” and “piece” are interchangeable.
Mistake 5: treating physical receipt as quality acceptance. Keep quantity receipt and inspection status separate.
Mistake 6: treating every partial invoice as an error. Check the payment trigger and actual terms. Billing may relate to an agreed advance or milestone.
Mistake 7: treating every mismatch as permission to change the books. Route the issue to the authorized owner and preserve source documents.
Mistake 8: applying an ERP tolerance from an article as a universal threshold. Matching tolerances and approval behavior are system- and organization-specific.
Mistake 9: settling a shortage through invoice matching alone. Use the buyer’s shortage, claim and remedy process with shipment evidence.
How can a hardware supplier help with reconciliation?
A supplier can help clarify the product description, order reference, pack configuration, invoice line, dispatch document and any approved revision within its records. For metal bathroom and home storage products, the product identity may include dimensions, finish, mounting hardware, set contents and packaging. A clear RFQ and purchase order make it easier for both parties to use the same item description.
Koitor Hardware can discuss product and pack details for confirmed OEM scope and refer to the buyer’s order references when responding. That does not mean Koitor uses a particular accounts-payable platform, provides buyer-side accounting services, determines destination receipt, or changes payment terms. The buyer retains ownership of its receipt records, accounting controls and payment authorization.
If a line mismatch appears, state the PO number, invoice line, SKU, unit, quantity and supporting receipt reference. Ask a narrow question: “Please confirm whether this invoice line is for the 100-unit kit at PO revision B or the 60-unit first delivery under receipt R-01.” This is more actionable than “the invoice does not match.” If the supplier confirms an error, the buyer can request the appropriate correction under its document process.
Buyer checklist for three-way matching
- Match the approved PO revision to the invoice line and physical SKU.
- Confirm the unit basis: piece, pair, set, kit or carton.
- Record the approved conversion between units when records differ.
- Link each receipt event to a unique date and evidence reference.
- Maintain cumulative received and billed balances without double-counting.
- Keep dispatch, packing-list, carrier and destination-receipt evidence distinct.
- Record inspection or hold status separately from physical quantity received.
- Compare billed price and charges with the authorized commercial basis.
- Check payment terms and milestone triggers before routing exceptions.
- Assign each mismatch to procurement, receiving, quality, AP or supplier documentation owner.
- Preserve correction, credit, replacement or approved-change records.
- Do not invent a receipt, alter a contract term or apply an unapproved tolerance.
Three way invoice matching for imported hardware needs a stable SKU, pack and unit basis across all three records. A three way invoice matching ledger should track each unique receipt event and the cumulative billed balance. For three way invoice matching, keep physical receipt and inspection acceptance as separate evidence.
الأسئلة الشائعة
Is a packing list the same as a goods receipt?
Not necessarily. A packing list is supplier-side shipment information. A buyer’s receipt record usually reflects what its receiving process posted. The records can be reconciled but should not be treated as identical without the buyer’s policy saying so.
Does a receipt prove that hardware passed inspection?
No. Receipt confirms a quantity or event under the receiving process. Inspection and quality acceptance are separate evidence unless the buyer’s system and procedure explicitly tie them together.
Is every invoice for a partial delivery incorrect?
No. The invoice must be checked against the actual contract and payment trigger. It might cover a receipt, a shipment, an advance or another agreed milestone.
Should AP automatically block every unmatched invoice?
That depends on the buyer’s controls and terms. ERP tolerances and approval routes are organization-specific. AP should follow the buyer’s established policy and involve procurement or receiving as appropriate.
Does three-way matching replace a shortage or quality claim?
No. It can identify an exception and direct attention to the relevant records. Shortage, damage, defect, credit or replacement matters should follow the buyer’s agreed investigation and remedy process.
اعمل مع شركة «كويتور» للأدوات
Keep the comparison assumptions visible in the buyer record whenever the specification changes.
Keep the Hardware SKU and Pack Clear in Your Order Records
Identify the product, finish, set contents, unit basis and approved order reference when discussing an OEM project. Koitor can clarify product and pack details within the confirmed quotation; buyer receiving and payment controls remain with your team.
For a useful three way invoice matching review, record the product identity and the decision the measure is meant to support.
OEM / العلامة التجارية الخاصة
حوّل دليل التوريد هذا إلى موجز منتج
يرجى إطلاعنا على المنتج المستهدف، والحجم، والتشطيب، وكمية الطلب، ومتطلبات التغليف. وسيتلقى فريقك تقييمًا عمليًّا لإمكانية التصنيع قبل تقديم عرض الأسعار.
English 
Español 
Português 
Français 
Deutsch 
العربية