## TL;DR
Fix this in Oracle Payables by acting on the exact problem first: compare the shipment schedules on the order in Oracle with the receipt history, move the distribution to the shipment with received quantity available, and confirm quantity billed on the wrong shipment returns to zero. Do not resubmit the same invoice or rerun the same match unchanged, because the same inputs produce the same failure. Prove the fix on one invoice distribution on the wrong shipment first, then rerun the full scope and reconcile the results.

```text
how to fix Oracle payables matching error invoice distribution matched to wrong PO shipment fails error
```

## Use this when
- The operation in Oracle Payables fails with this exact problem: how to fix Oracle payables matching error invoice distribution matched to wrong PO shipment fails error.
- The same failure repeats on retry with unchanged inputs.
- An invoice match, hold release, approval or payment run is blocked until this is resolved.

## Not for this skill when
- The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
- The operation completes and you only disagree with a price, tolerance or eligibility judgement. That is a finance owner decision, not this failure.

## Steps
1. Reproduce the failure on one named invoice, purchase order line or receipt in Oracle Payables and record the full problem text plus the invoice, order and receipt numbers involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: compare the shipment schedules on the order in Oracle with the receipt history, move the distribution to the shipment with received quantity available, and confirm quantity billed on the wrong shipment returns to zero. Verify: the single failing invoice, line or receipt now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring invoices, order lines or receipts that share the same supplier, tolerance rule or template, because this class of failure rarely affects only one record. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Oracle Payables on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the purchase order, the goods receipt or the invoice record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the match log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

## Variant phrasings

### how to fix Oracle payables matching error invoice distribution matched to wrong PO shipment fails error
The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single record proof, then the full rerun.

### Oracle payables matching error invoice distribution matched to wrong PO shipment
The alternate phrasing for the same failure in Oracle Payables. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### Oracle Payables troubleshooting for this failure
The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

## Why it happens
Orders with multiple shipments split by date or location look identical at line level in Oracle, so a distribution can attach to a shipment with no receipt while the receipt sits on another shipment of the same line.

## Edge cases
- The order, receipt or tolerance rule changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
- The single record proof passes but the full rerun still fails on other invoices. Treat each remaining failure as its own scope, because a shared supplier, rule or template can hide more than one cause.
- The source systems disagree on the correct value. The purchase order governs price and quantity ordered, the receipt governs quantity received, and the invoice governs amount billed; record which source won and why.

Compatibility: Oracle Payables at current versions, plus the purchasing, receiving or finance system the query names; no extra tooling beyond access to the source records needed to verify results.

## Provenance

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