The Overseas Supplier Says the Invoice Is Unpaid: What to Check

A Saudi buyer has paid a German supplier for equipment. The buyer's account shows a debit. The supplier's accounts team still sees an open invoice and asks for payment before releasing the next shipment.

There are several possible explanations. The transfer may still be unresolved. The supplier may have received a credit that was short, converted differently or left unmatched because the invoice reference was missing. A generic “payment sent” screenshot cannot distinguish these cases.

This fictional example uses a 10,000 EUR invoice. It makes no claim about the banks' actual terms or the legal obligations of either country. Its purpose is to separate payment delivery from the supplier's commercial allocation.

Build one case from the original references

Start with the invoice number, supplier legal entity, agreed invoice currency and amount, due date, and the beneficiary details that were approved for payment. Add the buyer's payment instruction reference, bank reference, debit amount and timestamp. Preserve the original instruction rather than replacing it with a later screenshot.

Ask the supplier's authorised finance contact to identify the credit they can see, if any: amount, currency, date and usable transaction reference. Use an established communication route. Share only the records needed to match the payment; a full bank statement can expose unrelated transactions.

Keep the invoice reference and the bank reference separate. One identifies the commercial obligation; the other helps trace a payment. A useful case connects them without assuming they are interchangeable.

Establish which stage is actually confirmed

The buyer's ledger, bank status, beneficiary account and supplier receivables ledger answer different questions. Record each observed state with its source and time.

Swift's Universal Confirmations framework, for payments in its scope, includes beneficiary credit and other outcomes such as rejection, hold or transfer outside Swift. A status that reports onward transfer should not be relabelled as confirmed beneficiary credit. Other payment routes have their own documented statuses. Swift Universal Confirmations

Even confirmed beneficiary credit does not prove the supplier has allocated the money to the intended invoice. The accounts team may have an unidentified receipt, a payment covering several invoices or a disagreement about deductions. That is a reconciliation task with the supplier, not necessarily a failed bank transfer.

These are investigation paths, not diagnoses made from one status label. The last two rows require evidence. An absent notification or an operator's inability to find a record is not proof that no instruction was accepted.

Make the invoice reference survive the handoffs

Structured remittance information can help the receiving business reconcile a credit with an obligation. Swift's corporate ISO 20022 guidance describes richer structured data as a benefit for corporate payments and reconciliation. The fields available in a particular bank channel still depend on that bank's supported message versions and usage rules. Swift ISO 20022 for corporates

For the fictional 10,000 EUR invoice, the buyer should retain the invoice identifier and confirm where it belongs in the bank's supported instruction. If several invoices are paid together, provide an allocation schedule through the agreed business process and preserve its link to the payment reference.

Do not assume that attaching a PDF to an internal approval means the supplier receives that reference with the credit. Test the actual receiving record or ask the supplier what appears. A field can exist in a source system and still be lost, truncated or mapped differently along the route.

If the supplier finds the full credit in an unidentified-receipts account, ask for confirmation that it has been applied to the correct invoice. Keep the original bank trace open only for questions it can answer; use the supplier's receivables record for allocation.

Resolve the original payment before considering another

Treat changed bank details as a separate verification task

An unpaid-invoice discussion can be followed by a message asking the buyer to resend funds to a new account. Do not let the urgency of a shipment release override beneficiary verification.

The FBI's Internet Crime Complaint Center describes business email compromise and recommends verifying changes in account numbers or payment procedures through an independent channel. In practice, use a previously established contact route rather than relying on the contact details supplied in the change request. IC3 business email compromise guidance

Record that verification under the organisation's existing authority controls. Verifying new details does not resolve the first transfer. Both questions must be answered before a replacement payment is considered.

Close with evidence the next operator can use

The final case should say whether the original payment was credited, returned or otherwise resolved, how the supplier allocated it, and what happened to any difference. Include the reference for a separately approved balance payment if one was necessary. Avoid closing the case with “finance confirmed” when the actual evidence is a chat message saying someone will check.

For the quote stage before submission, the recipient-amount comparison explains fee and conversion bases. For a broader supplier transition, the service-handover guide examines operational acceptance. Neither replaces the simple evidence needed here: what reached the supplier, and which obligation it settled.