When the expected Nostro debit is missing

Payment Series | Episode 15

Payment Engine says “Successful.” But the expected Nostro debit never arrived. What now? 🤔

Example: Corporate A sends SAR 250,000 to Beneficiary B.

The engine shows:

Processed successfully ✅

That means our engine released the payment.

It does not mean settlement is complete.

During reconciliation, the SAR 250,000 debit is missing from the Nostro statement.

An internal PMNE (Payment Not Effected) case is created.

PMNE here is an internal investigation status, not a Swift classification. Operationally, it means settlement cannot yet be evidenced from the expected Nostro debit.

The dangerous reaction?

“Expected Nostro debit is missing → re-effect the payment.”

Not yet.

First prove the state of the original payment.

Check:

→ Any Swift enquiry from the correspondent?

→ Held for missing or incorrect information?

→ Insufficient Nostro balance?

→ Rejected, delayed or still pending?

→ Statement entry simply not available yet?

With Cover Method, the pacs.008 may already be with the Beneficiary Bank while the pacs.009 COV is delayed, held or rejected in the cover chain.

If we send another SAR 250,000 and the original settles two days later, the beneficiary could receive SAR 500,000.

💡 The Insight

A missing Nostro debit tells you settlement is unresolved. It does not prove the payment has failed.

First establish the original payment state.

Then decide whether to:

Wait · Chase · Repair · Recall · Re-effect

Never create a second payment before proving what happened to the first one.

One episode. One practical example. One insight.

#Payments #Nostro #Reconciliation #CrossBorderPayments #PaymentOperations