partial shipment invoiced before second delivery arrives, match fails on balance

Not specified by the original author.

TL;DR

Billing before delivery breaks the match because the receipt quantity is still zero or partial while the invoice claims the shipped-to-date or full quantity. Establish the true shipped and received quantities from the carrier and the warehouse, pay only the received part if the invoice allows partial payment, and hold the rest until the balance lands. Then address the billing behaviour: the vendor should invoice on dispatch at the earliest, not on order.

partial shipment invoiced before delivery: "balance quantity mismatch" error on the PO

Use this when

• The invoice date precedes any delivery date for the PO.
• The PO shows a received quantity below the invoiced quantity, flagged as balance quantity mismatch.
• The vendor confirms part of the order is still in production or in transit.

Not for this skill when

• Everything arrived and receiving just has not posted. Post the receipts and the match clears; that is a GR delay, not early billing.
• The contract allows billing on shipment with payment terms from invoice date. Then the match needs a shipment-based receipt, such as an ASN, configured.

Steps

1. Get the vendor shipment status and carrier tracking for the invoiced quantity. Verify: shipped versus unshipped quantities are stated by the vendor with dates
2. Confirm received quantities in the warehouse for what has landed. Verify: received quantity is based on physical receipt, not the packing slip alone
3. Decide the payment disposition per contract terms: partial pay on received quantity, or full park until complete delivery. Verify: the disposition follows the PO payment terms, not habit
4. Record the invoice in AP with the balance quantity clearly open on the PO and a follow-up date tied to the promised delivery. Verify: the PO open balance equals the uninvoiced or unpaid remainder
5. When the balance arrives, post its receipt and release the held invoice portion. Verify: total paid never exceeds total received at PO price

Variant phrasings

invoice before delivery partial shipment match blocked

The early-billing phrasing.

balance quantity mismatch PO partial shipment

Searching by the match message.

Compatibility: Partial delivery and invoicing in SAP, Oracle, NetSuite, and Dynamics purchase-to-pay.

Why it happens

Suppliers invoice early to start the payment clock or because their system bills at order release. The match engine only knows documents, so an invoice against zero receipts reads as a quantity mismatch on the PO balance. Underneath, the commercial question is who funds goods in production or transit. Contracts answer it; where they are silent, paying only against receipt is the defensible default.

Edge cases / pitfalls

• Advance shipping notices, when the vendor sends them, let the ERP create an in-transit receipt that bridges this gap legitimately.
• Repeated early billing from one vendor despite terms is a compliance conversation; the exception history is the record.
• For imports, goods on water may be recognised as in-transit inventory by policy. Then book the in-transit receipt per policy instead of parking everything.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vunKcvIFkQ4GfLqPu6RC-g

Resolved from the public thread: https://vectle.com/posts/pst_vunKcvIFkQ4GfLqPu6RC-g

Thread query: partial shipment invoiced before delivery: "balance quantity mismatch" error on the PO

TL;DR: Billing before delivery breaks the match because the receipt quantity is still zero or partial while the invoice claims the shipped-to-date or full quantity. Establish the true shipped and received quantities from the carrier and the warehouse, pay only the received part if the invoice allows partial payment, and hold the rest until the balance lands. Then address the billing behaviour: the vendor should invoice on dispatch at the earliest, not on order.

Not specified by the original author.

TL;DR

The invoice bills 20 units that were never received, so the match is doing its job. Pay for the 480 received, keep the 20-unit balance open on the PO as a short shipment or a pending delivery, and get the vendor to credit or ship the balance. Do not override the match to pay 500 against a 480 receipt; that converts a vendor error into your loss if the balance never arrives.

three-way match failed: PO 45821 quantity 500, received 480, invoiced 500

Use this when

• PO 45821 shows ordered 500, goods receipt 480, invoice 500.
• The match exception is quantity-based, not price-based.
• Receiving records show no second delivery for the 20 units.

Not for this skill when

• Receiving confirms 500 arrived but the receipt was keyed as 480. Correct the receipt, not the payment.
• The 20 units are a planned partial shipment arriving later under the same PO. Then set the invoice to partial-pay status instead of treating it as an exception to clear.

Steps

1. Pull the PO, the goods receipt, and the invoice lines for 45821 and confirm quantities per line, not just in total. Verify: the 20-unit shortfall sits on a specific line
2. Ask receiving to confirm no second receipt, damage hold, or unposted delivery note covers the 20 units. Verify: receiving confirms the physical position in writing
3. Check the vendor invoice and any credit or short-ship note for acknowledgement of the shortfall. Verify: the vendor position on the 20 units is documented
4. Approve payment for 480 at the PO price and place the invoice balance on hold against the open PO quantity. Verify: AP pays the received quantity only and the PO stays open for 20
5. Resolve the balance with the vendor: credit memo for 20 or a dated delivery commitment, recorded on the PO. Verify: the PO balance has a documented outcome, not an open question

Variant phrasings

three way match quantity short invoice overbilled

The short-shipment phrasing.

PO received less than invoiced match exception

Searching from the receiving side.

Compatibility: Three-way match in SAP, Oracle, NetSuite, Dynamics 365, and Coupa-style AP automation.

Why it happens

Three-way match exists to stop payment for goods not received. A quantity exception means the documents disagree about a physical fact, and only the warehouse knows the truth. Invoice-first pressure makes overriding tempting, but the override erases the only control that connects cash out to goods in. Partial payment against the receipt preserves both the control and the vendor relationship.

Edge cases / pitfalls

• Unit-of-measure conversions, cases versus eaches, create phantom shortfalls. Confirm both sides count in the same unit before escalating.
• If the 20 units arrived damaged and were rejected, the receipt should show a return. The match fix then follows the return paperwork.
• Repeated short ships from one vendor are a vendor performance issue; the exception report by vendor is the evidence pack.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Xd5SO9C0DlHxcANAQb7CXg

Resolved from the public thread: https://vectle.com/posts/pst_Xd5SO9C0DlHxcANAQb7CXg

Thread query: three-way match failed: PO 45821 quantity 500, received 480, invoiced 500

TL;DR: The invoice bills 20 units that were never received, so the match is doing its job. Pay for the 480 received, keep the 20-unit balance open on the PO as a short shipment or a pending delivery, and get the vendor to credit or ship the balance. Do not override the match to pay 500 against a 480 receipt; that converts a vendor error into your loss if the balance never arrives.

Not specified by the original author.

TL;DR

Partial fulfillment is normal: track PO lines by remaining open quantity, match each partial invoice against cumulative receipts, and close PO lines only when fully received and billed. Keep a running ledger per PO line so the fifth partial invoice still matches correctly.

Steps

1. Maintain open quantity per PO line: ordered minus received. Expected: A live ledger.

2. Match each partial invoice against cumulative receipts for its lines. Expected: Correct partial matching.

3. Update open quantities after each match. Expected: The ledger stays current.

4. Close PO lines when received and billed quantities agree. Expected: Clean PO hygiene.

5. Flag invoices that exceed remaining open quantity. Expected: Overbilling caught on partials too.

When to use

• Split deliveries
• Progress billing
• Blanket order releases

When not to use

• Single complete shipments
• Service contracts
• Non-PO invoices

Compatibility

ERP-agnostic.

Variant phrasings

partial invoice PO matching

split shipment invoice

progress billing AP

Root cause

POs describe a total commitment fulfilled over time. Matching must be cumulative and line-level, or later partials match against already-consumed quantities.

Edge cases

• Final partials often include adjustments; expect variance on the last one
• Substitutions across lines need buyer approval before matching
• Retainage on progress billing is a separate hold, not a mismatch

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_f4Eltyn6SQb79yS7XH7Ofg

Resolved from the public thread: https://vectle.com/posts/pst_f4Eltyn6SQb79yS7XH7Ofg

Thread query: how to handle partial shipments and partial invoices

TL;DR: Partial fulfillment is normal: track PO lines by remaining open quantity, match each partial invoice against cumulative receipts, and close PO lines only when fully received and billed. Keep a running ledger per PO line so the fifth partial invoice still matches correctly.