## TL;DR
Drop-ship goods never enter your warehouse, so a warehouse goods receipt can never exist. The receipt event is delivery to the customer, proven by the carrier proof of delivery. Configure or process the drop-ship PO as a special order where the vendor invoice plus POD completes the match, post the delivery confirmation from the POD, and the perpetual GR missing clears. Chasing the warehouse for this receipt wastes everyone's month end.

```text
drop-ship PO: vendor invoice arrived before the warehouse receipt, perpetual "GR missing" error
```

## Use this when
- The PO is drop-ship: vendor ships directly to the customer.
- The vendor invoice arrived and the match demands a GR that receiving cannot create.
- Carrier tracking shows delivery to the customer address.

## Not for this skill when
- The order was supposed to come to your warehouse and was misrouted. That is a logistics exception, not a drop-ship match setup.
- No proof of delivery exists and the customer denies receipt. Do not pay yet; resolve delivery first.

## Steps
1. Confirm the PO type and ship-to address show drop-ship to the customer, not to your warehouse. Verify: the order structure explains why no warehouse GR exists
2. Obtain the carrier proof of delivery with delivery date and recipient from the vendor or the carrier portal. Verify: POD exists and matches the customer address and the invoiced items
3. Confirm with the customer or the sales order record that the goods were accepted, where your process requires it. Verify: acceptance is recorded on the sales side
4. Post the drop-ship receipt or delivery confirmation from the POD, or process the match as two-way invoice plus POD if your ERP supports it. Verify: the GR missing flag clears on the PO
5. Fix the drop-ship PO template so future drop-ship orders are created with the POD-based match path from the start. Verify: a new test drop-ship PO shows the correct match type

## Variant phrasings
### drop ship PO GR missing vendor invoice match
The drop-ship phrasing.
### drop shipment three way match proof of delivery
When POD is the receipt evidence.

Compatibility: Drop-ship and third-party order processing in NetSuite, SAP, Dynamics 365, and Oracle special orders.

## Why it happens
Standard match logic assumes custody: you pay after you receive. Drop-ship breaks the custody assumption while keeping the payment obligation. Systems handle it with a distinct order type whose receipt is a delivery confirmation, but if the order is raised as a normal PO, the match engine applies warehouse rules to a warehouse event that is structurally impossible. The error is permanent until the order type or the evidence path changes.

## Edge cases / pitfalls
- Sales tax and revenue recognition on drop-ship follow delivery to the customer, so the POD date matters beyond AP. Use the real delivery date.
- Vendors sometimes invoice at shipment, days before delivery. The POD path still requires waiting for delivery before payment.
- If the customer returns drop-ship goods, the return goes to the vendor; make sure the credit process mirrors the original POD-based flow.

## Provenance

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