The beneficiary bank is asking for an invoice before releasing funds
The beneficiary bank is asking for an invoice before releasing funds usually means the bank needs to connect the payment to a real commercial transaction before funds are released. Start by matching the payment to the invoice, purpose, sender, beneficiary, amount, currency, and trade context, then respond with one clean document pack instead of disconnected attachments.
LIST · DAY 0
Confirm which documents are missing — invoice, purpose, contract, source of funds — before sending anything.
Do not send a random folder of every file you have.
Illustrative windows. Response times depend on the rail, the jurisdiction and the institutions involved. Instructions to Unicorn Currencies are accepted 24/7 with no cut-off. Settlement follows the receiving rail's operating schedule.
Typical causes in document hold.
Illustrative patterns — not measured frequencies for your corridor.
What it usually means
The beneficiary bank is connecting incoming funds to a commercial transaction before crediting the account. This is common on supplier receipts where the bank needs to see who paid, for what, and whether the amount matches a legitimate trade.
Evidence needed
Prepare invoice, purpose of payment, goods or services description, sender and beneficiary relationship, source of funds or source of wealth if requested, and trade explanation. The invoice amount, beneficiary name, and payment reference must match the wire exactly.
What not to do
Do not send inconsistent or incomplete explanations to different banks or counterparties. Do not send a replacement payment to unblock the supplier while the original funds are still held for review.
Correct next action
Send one structured release pack to the bank path the supplier confirms is active. Ask which bank owns the review and what timeline they were given. Escalate if documents were already supplied and the bank repeats the same request without a clear reason.
How Unicorn Currencies helps
Unicorn Currencies helps organise the payment proof, references, beneficiary details, supplier messages, and timeline so the next action is clear. Depending on the payment state, that may mean waiting inside the rail window, requesting a trace, preparing a proof pack, supporting escalation, coordinating an amendment, or preparing a recall request. Unicorn Currencies does not control SWIFT, correspondent banks, beneficiary banks, or partner banks, and cannot guarantee recall, recovery, release, or bank action.
Match the invoice to the payment: beneficiary name, amount, currency, goods or services, and reference. Build one document pack with invoice, purpose of payment, relationship context, and payment proof. Respond once with consistent facts — not disconnected attachments to different contacts.
Unicorn Currencies does not control SWIFT, correspondent banks, beneficiary banks, or partner banks, and cannot guarantee recall, recovery, release, or bank action. Settlement follows the receiving rail's operating schedule.
The pack you send.
You are in the right place when the beneficiary bank wants an invoice before releasing funds. The payment may already be at the receiving bank — the hold is usually about trade context, not whether your side sent the wire.
Questions on this problem.
The receiving or intermediary bank may still need trade context before releasing funds. The invoice helps connect the sender, beneficiary, amount, currency, goods or services, and payment purpose to a legitimate commercial transaction.
The best version of this page is the one you never need.
Local rails and a named specialist reduce how often these failures appear. Applications open to businesses moving $1M or more a year.