Your Israeli customer says the invoice was paid. Your accounts team still shows it as outstanding. Sending the same reminder again will not explain the mismatch. Before either side escalates, someone needs to connect the invoice, the claimed transfer and the money actually received.
This is a practical record-reconciliation guide for foreign suppliers and service providers dealing with an Israeli business customer. It does not decide whether payment legally discharged an obligation, who bears a loss, or which procedure applies. Those questions need a separate review of the documents and current law.
Start with the invoice, not the accusation
Choose the exact invoice in dispute. Record its number, issuing entity, customer entity, currency, face amount and the balance your own ledger currently shows. Keep the original invoice and any later credit note together. If several invoices are bundled into one customer account, separate them before discussing a total.
A customer saying “we paid you” might be referring to a different invoice, an earlier deposit or a combined transfer. Treat those as questions to test, not explanations already proved. Ask your finance team to identify what it searched and what it found.
An invoice balance, a transfer confirmation and a bank receipt are different records. The practical task is to connect them before treating them as the same event.
Ask for a specific payment reference
Ask the customer to identify the transfer date, amount, currency, payer name, intended beneficiary and bank transaction reference. Request the original confirmation through an agreed secure channel, rather than a cropped screenshot forwarded through several people. Do not ask for banking passwords, authentication codes or unrelated account activity.
Keep the wording factual. You are checking the payment against your records, not confirming that the account is settled. If the customer says another company paid on its behalf, record that explanation and ask which invoice the transfer was meant to cover. Do not silently replace the contracting customer in your file with the payer’s name.
Build a matching table
A small reconciliation table is more useful than a long email chain. Use one row per disputed invoice and these columns:
- Invoice: number, currency, amount and issuing entity.
- Customer’s payment claim: date, amount, payer and reference, with the source file.
- Your bank record: amount actually located, currency, receipt date and reference, or “not yet matched”.
- Allocation: which invoice your ledger credited and any remaining difference.
- Open question: the single fact needed to connect the records.
Label a customer’s claim as a claim until checked. If no matching receipt has been located, write that. Avoid changing it to “no payment was made” merely because the first search returned nothing.
Separate a missing transfer from a short-payment dispute
Check whether there is no located receipt at all, a receipt allocated elsewhere, or a smaller receipt than the amount under discussion. Possible differences to investigate include currency conversion, bank charges, a credit note or a deduction the customer says it applied. None should be accepted automatically as the correct explanation.
If the customer combines a payment claim with a complaint about delivery or service, keep two separate lists: the claimed money movement and the commercial complaint. This helps the people reviewing the file see what is actually disputed. Whether a deduction is justified is not an accounting conclusion.
Changed bank details need an independent check
If the confirmation points to unfamiliar bank details, stop using that email thread as your only verification channel. IC3 advises using a secondary channel to verify requests to change account information. Contact the relevant person using an independently known number or other established channel, not a new contact detail supplied in the disputed message.
If a suspected fraudulent transfer emerges, contact your financial institution promptly. IC3 recommends contacting the originating institution as soon as fraud is recognized to request recall or reversal. That is a response step, not a promise that money can be recovered. Do not ask the customer to make a second transfer to newly supplied details before the situation is checked.
Give the lawyer the unresolved difference, not just the inbox
For a focused review, prepare the full agreement and amendments, invoice and credit notes, the customer’s payment claim, relevant bank evidence and a short reconciliation table. Include the messages about disputed bank details or deductions. Keep originals; use clearly marked working copies for your notes.
State the commercial decision you need help with: clarifying correspondence, handling an unexplained shortfall, discussing a settlement proposal or assessing whether to escalate. This guide does not supply a demand-letter template or select a legal route. A polished email can still be the wrong response if it rests on an untested payment assumption.
For the separate commercial decision about a disputed receivable, see our Israeli debtor assessment page.
Need a review of a payment dispute with an Israeli customer?
RNC Group can review the payment correspondence and supporting documents before the next substantive response. Start with the invoice amount and currency, the customer’s explanation and the unresolved difference. Do not send bank statements or other sensitive documents in the first WhatsApp message; agree on the document-transfer route first.
Ask about reviewing the payment dispute on WhatsApp
Source and scope
Fraud-response and independent-verification points checked against IC3: Business Email Compromise on October 27, 2026. The reconciliation steps are practical preparation recommendations, not statements of Israeli law. No outcome or response time is promised.
This article is for general information only and does not constitute legal advice. Laws and their application depend on the facts and jurisdiction and may change. Although we aim to keep this information accurate and current, we do not guarantee that it is complete or up to date. The article may contain omissions or errors. Reading this article does not create an attorney-client relationship with RNC Group. Before making a decision or taking action, seek advice from a qualified lawyer in the relevant jurisdiction.