The invoice was for $800. A new client says they sent $1,800 by mistake. Could you return the extra $1,000 today? Their colleague will send the account details.
You want to be professional. You also want to keep the project. But sending a second payment before you understand the first can turn someone else’s explanation into your loss.
If a client appears to have overpaid, pause any return or onward transfer. Match the payment to the invoice, verify the instruction through an established contact, and ask the original receiving provider how the discrepancy should be handled. A screenshot, an urgent message or a visible balance alone does not settle all three questions.
This guide is for freelancers dealing with an unexpected excess payment. It does not assume every accounting mistake is fraud. It gives you a process that can handle a genuine mistake without making an unverified one more expensive.
Fraud guidance and product references checked on 13 October 2026. Examples below are hypothetical.
Why an overpayment deserves a pause
The US Federal Trade Commission warns that an excess check payment can be followed by a request to forward the difference. Check funds may become available before a forgery is discovered, leaving the recipient liable after sending money away. This check-specific warning does not establish the rules for every payment rail.
The FTC also warns about people being recruited to move stolen money, including through supposed jobs. The story may sound routine while the recipient is being used as an intermediary.
For a freelancer, the first practical question is therefore simple: Why am I being asked to move money that is not payment for my work?
An answer worth investigating might be a duplicate invoice payment from an established accounts team. A story that keeps changing, introduces an unrelated recipient, or demands a different payment method deserves much more scrutiny. Neither a friendly tone nor a familiar company logo replaces verification.
First, work out whether there is an overpayment
Before discussing a return, reconcile the invoice with the money you can independently observe.
Item | What to record | What not to assume |
|---|---|---|
Invoice | Number, amount, currency and supplier | A message refers to the correct invoice |
Expected payer | Client and agreed payment arrangement | Any incoming name belongs to this client |
Incoming record | Provider reference, amount, currency and status | A sender’s screenshot proves receipt |
Existing payments | Deposits, milestones or duplicate invoices | The latest payment is the only relevant one |
Claimed excess | The calculation supplied by the client | Their arithmetic matches your records |
For example, an $800 invoice and a separate $200 deposit do not automatically mean a later $1,000 credit contains a $200 mistake. The contract might treat the deposit differently, the payment might cover another milestone, or the client may have quoted the wrong invoice. Establish the allocation in writing.
Do not compare unlike currencies as though they were the same number. Equally, do not describe unexplained differences as exchange-rate costs. If the issue is that less arrived than expected, our guide to why an international wire can arrive short addresses that separate problem.
A consistent invoice makes this easier. Our guide to invoicing a US client from Nigeria explains the payment instructions and identifiers worth agreeing before a transfer starts.
Verify the request without using the request’s own shortcut
Contact the client through a channel you already used for the project. If you normally work with a project manager, involve the known finance contact as well. Do not treat a new phone number or a new email address supplied in the return request as independent confirmation.
Ask them to confirm the invoice number, the payment they believe was duplicated or overstated, and the intended correction. Record who confirmed it and when. The aim is to reconcile the payment, not to accuse the client.
If the original relationship is new and you have no established contact, there is less history to rely on. That is a reason to involve the receiving provider, not to let urgency stand in for verification.
Here is a neutral reply:
Thanks for flagging the difference. I am matching the payment to the invoice and checking the correction process with my receiving provider. Please confirm the invoice number and original payment reference through our existing project email thread. I will not send a separate payment to a new recipient while that review is open.
Keep your wording factual. Do not promise a same-day return before the provider has explained what can happen to the original credit. Do not send a token amount merely to demonstrate cooperation; that would still be a separate transfer.
Keep the original payment and the proposed return connected
A request to receive by one method and return by another creates a second transaction with its own risks and records. It does not automatically correct the first.
Ask your receiving provider these questions through its official support channel:
Can you identify the incoming payment from this reference?
What is its current status, and are there restrictions or an active review?
What process applies to an accidental excess or duplicate payment on this route?
Can the correction remain linked to the original transaction?
What evidence and authorisation do you need before I take action?
The answer may depend on the provider and payment method. Do not invent a universal waiting period after which every credit becomes safe to forward. Keep the unexplained amount untouched while you obtain instructions, and follow any restrictions the provider gives you.
For ordinary freelance income, walllet.com presents receiving details and ways to manage money after it arrives. The useful fit is a planned income workflow, not a promise that an account prevents fraud. See how walllet.com could fit your regular client-payment setup. Resolve a questionable payment with its original provider before moving it elsewhere.
Check, bank transfer or stablecoin: identify the actual route
An emailed payment image does not tell you which system carried the money. Use the receiving record and provider confirmation.
If it is a check: explain the return request to the bank and ask about that deposit. The displayed balance alone does not resolve the fake-check risk.
If it is a bank or payment-platform transfer: preserve the original reference and ask the receiving service about its correction process. Do not assume the sender’s proposed return account is the appropriate destination. The fact that someone knows the amount does not establish that they control the original payment.
If it is a stablecoin transfer: keep the network, token, transaction hash and receiving address with the invoice. A transaction record can help establish what moved; it does not explain why the client wants you to send value to a different person. Do not automatically send funds back to an address copied from a transaction record without checking the provider’s instructions and the payer’s identity. Address ownership and the business reason still need to be established.
For any route, distinguish the documents you have. A bank statement, account letter and transaction receipt serve different purposes. A document confirming your account details does not prove that this specific payment is legitimate.
Build a short case file
You do not need a complicated fraud investigation folder. You need enough information to reconstruct the sequence without searching several chat apps.
Save:
The contract and relevant invoice.
The original incoming-payment record.
The message first describing the alleged mistake.
Any later change of recipient, amount or payment method.
Your independent confirmation attempt.
The provider’s case number and instructions.
The final outcome and any correction reference.
Keep original records intact. If you prepare a public explanation or ask a community for general advice, use a separate redacted copy. Avoid exposing another person’s account information alongside your own.
Our guide to proof of income and source-of-funds records explains why a clear connection between the work, invoice and incoming payment matters. In this situation, that connection also makes the claimed excess easier to investigate.
If you have already sent the money
Contact the outgoing-payment service immediately, identify the suspected scam and ask what action is possible. Recovery is not guaranteed. Stop further payments and preserve the communication instead of deleting it out of embarrassment.
Record both transactions separately: the questionable incoming payment and the outgoing payment you authorised. If two providers are involved, each needs the reference for its own transaction and enough context to understand the connection.
Do not send another payment to someone claiming they need an activation fee, verification deposit or recovery charge to release the first. Return to the provider through its official channel to check any such request.
For future work, create a written payment-change rule: changes to recipient details and corrections to past payments require verification through the established contact and the relevant provider. Add it to your primary and backup freelance payment plan, alongside your ordinary receiving instructions.
Make your normal payment process easier to verify before the next client pays. Explore walllet.com’s global-income options, confirm the supported route for your account, and keep the invoice and payment reference together.
Related reading
Payment Safety and Troubleshooting: Resolve Problems and Reduce Risk
Virtual Card Refund Not Received? How to Trace Your Money
Microdeposit verification: what those small bank entries actually prove
Bank Statement vs Account Letter vs Transaction Receipt: Which One Should You Send?
