When Proof of Debt Is Insufficient: How Companies Protect Themselves When Accepting Third-Party Bank Transfers
Companies routinely accept incoming bank transfers from parties other than their direct clients whenever an outstanding debt exists. The funds are credited directly to the client’s account as debt satisfaction, and the transaction proceeds as a routine financial operation without raising immediate concerns.
However, a Commercial Court judgment recently ordered a company to refund SAR 290,000 to a third-party account holder, despite the fact that the underlying debt of the client whose account was credited remained undisputed.
The significance of this judgment lies not merely in its outcome, but in highlighting a fundamental distinction that many corporate finance departments treat as one and the same: establishing the underlying debt versus establishing the legal cause of the fund transfer.
The Dispute Was Not About the Underlying Debt
The company received two bank transfers totaling SAR 290,000 from a bank account that did not belong to its debtor client, but to a third party. The company credited the amount directly to the client’s ledger to satisfy part of his outstanding balance. Before the court, the company argued that the debt was undisputed and that the transfer was initiated at the client’s explicit request.
Conversely, the third-party account holder brought an action to recover the funds, denying any intent to satisfy the client’s debt.
The Commercial Court ordered the company to refund the full SAR 290,000 because the evidentiary record contained no documentation proving that the third-party account holder had allocated these transfers to satisfy that specific client’s debt. The Court of Appeal affirmed the ruling.
The rationale was not that the Court denied the existence of the client’s debt, but rather that the company failed to prove the legal cause for transferring funds from a third party’s bank account into its own.
While seemingly subtle, this distinction carries profound implications for corporate collection policies.
Establishing the Debt Does Not Prove the Cause of the Transfer
Contracts, tax invoices, statement of accounts, and balance confirmations establish a company’s legal right against its direct client, enabling it to demand payment or initiate litigation upon default.
However, these corporate documents do not prove that a third party intended to use their personal or corporate assets to discharge that debt.
They prove the legal relationship between creditor and debtor, but they do not prove the distinct legal relationship arising from transferring funds from a third-party account.
Consequently, a debt may be indisputably established, yet courts will order the return of transferred funds if there is no written proof that the account holder intended to allocate those funds toward the debtor’s liability.
[Contract / Invoice] ──> Proves Right Against Client (Debt Exists)
[Bank Statement / Voucher] ──> Proves Funds Received (No Legal Cause Established)
[Third-Party Written Consent] ──> Proves Legal Cause (Protects Retained Funds)
In short, debt documentation proves why the client owes the company, but it does not prove why the company is entitled to retain money received from someone else.
Financial Management Logic vs. Judicial Logic
This case reveals a critical divergence between accounting practices and judicial standards regarding bank transfers:
- Accounting & Financial Perspective: Views an incoming transfer as liquid capital to be allocated against an open balance. If a client has an outstanding liability, the transfer is credited, reducing the debt balance.
- Judicial & Statutory Perspective: Views a third-party transfer as an independent legal act (waqi’ah qanuniyyah) requiring formal proof of its underlying cause (sabab).
Under judicial scrutiny:
- Bank Statements: Prove the physical arrival of funds, but do not prove the intended legal purpose.
- Receipt Vouchers: Prove how the receiving company categorized the payment, but do not prove the third-party sender consented to that allocation.
- Accounting Entries: Reflect internal book treatments post-receipt, but do not independently establish the legal cause of the transfer.
This creates a dangerous gap between what satisfies internal accounting reconciliation and what constitutes admissible evidence before commercial courts.
Performance by a Third Party: What Remains to Be Proven?
The issue is not whether performance by a third party (al-wafa’ min al-ghayr) is legally permissible. Article 222 of the Saudi Civil Transactions Law explicitly permits third-party debt performance, reflecting commercial realities where sister entities, guarantors, or financiers routinely discharge obligations on behalf of others.
However, the legal permissibility of third-party performance does not mean every incoming transfer from a different account automatically constitutes debt satisfaction.
The core fact that remains subject to proof is that the sender genuinely intended to use their funds to discharge the debtor’s liability.
If contemporaneous email correspondence, transfer instructions, or written notices issued by the sender show that the transfer was intended to satisfy a specific debt, performance is legally perfected. Subsequent disputes between the sender and the debtor cannot compromise the creditor’s right to retain the funds.
Conversely, if the legal cause remains unproven, the mere existence of a debt owed by a client does not entitle the company to retain third-party funds.
Mapping Internal Operational Risks
These disputes rarely arise from poorly drafted sales contracts or missing commercial invoices; they stem from operational disconnects across corporate departments:
[Sales Team] ──> Verbally aware a third party will pay on client’s behalf.
↓
[Finance Team] ──> Receives incoming transfer and credits client account directly.
↓
[Legal Team] ──> Reviews file post-dispute, relying solely on client instructions.
These informal practices appear sufficient during stable commercial operations. However, when litigation arises, the company discovers it holds zero documentation issued by the third-party account holder proving consent or debt allocation.
The legal issue is no longer proving the client owes money, but justifying why the company should not refund the third party under unjust enrichment (ithra’ bila sabab).
Risk Management Starts Before Collection
Risk management does not begin at litigation; it begins when accepting a bank transfer.
Companies that regularly accept third-party payments must integrate transfer-cause verification directly into their credit and collection policies, rather than treating it as a post-dispute remedy.
This does not require cumbersome procedures. It simply requires a clear, written instrument issued directly by the transferring party confirming the purpose of the transfer, such as:
- A formal third-party payment authorization letter;
- Official email instructions from the sender’s corporate domain; or
- Explicit banking remittance remarks referencing the specific contract number, invoice number, or debtor name.
The true value of this documentation emerges when a dispute arises years later regarding the transfer’s legal cause.
Summary
Disputes often center not on the validity of a debt, but on the evidence establishing how it was discharged.
A client’s proven liability does not eliminate the requirement to prove that a third-party sender intended to satisfy that liability, nor does an internal accounting entry establish the legal basis for retaining incoming funds.
Documenting the legal cause of incoming transfers upon receipt is not a administrative formality; it is a vital legal risk management tool designed to protect corporate bank accounts from clawback claims.
Collection is not complete when funds hit your bank account—it is complete when your company can legally prove why it is entitled to keep them.
