Important: This article is general information for education only. It is not legal advice and does not recommend any bank, payment platform or security product. If a payment has been diverted, contact your bank and report to 1930 without delay.


More IT professionals now earn outside a salary: freelance development, cloud consulting, test automation contracts, design work or advisory fees after leaving a full-time role. Many of these clients are overseas and pay by international transfer against emailed invoices. That combination of email, invoices and large cross-border payments is exactly what business email compromise (BEC) fraud targets.

In the most common version, a fraudster gets into your mailbox or your client’s, reads the conversation, and sends a perfectly timed message saying your bank details have changed. The client pays. The money goes to a mule account. You discover it weeks later when you chase an “unpaid” invoice.

How the fraud works

  1. Access. The attacker phishes the password for your email, or your client’s, or registers a look-alike domain that differs by one character.
  2. Reconnaissance. They read past threads to learn invoice formats, amounts, project names and who approves payments. Some set forwarding rules so they keep seeing new mail.
  3. The switch. Just before a payment, they send an invoice identical to yours except for the bank details, often with a plausible reason such as “our bank is under audit”.
  4. Delay. They may reply to your follow-ups pretending to be the client, buying time while the money is moved on.

Government agencies have flagged the trend. The Indian Cybercrime Coordination Centre has warned about impersonation of senior executives and regulators over email and messaging apps, and SEBI issued a caution to regulated entities in July 2026 about a related “boss scam” pattern. The tactics overlap heavily with invoice redirection.

Who bears the loss?

There is no simple rule. It depends on your contract, whose system was compromised, and the law that governs your agreement. Often the client argues they paid in good faith to details sent from your address, and you argue you were never paid. Either way, the dispute damages the relationship and your cash flow. Prevention is far cheaper than any argument about liability.

A worked example

Neha, a former SDET, now runs test automation projects for a UK start-up. She invoices £4,000 for a milestone. At an assumed exchange rate of ₹112 to the pound, that is about ₹4,48,000. Her personal email account, reused for client work, had a password exposed in an old breach. A fraudster logs in, sets a rule to hide replies from the client, and emails the client a “corrected” invoice with a new account.

The client pays. Three weeks later Neha chases payment and the truth emerges. The client’s bank initiates a recall request, but most of the money has already moved. Her contract says nothing about bank detail changes. Recovering even part of the ₹4.48 lakh now depends on bank recall success and how the two sides negotiate.

Control Neha lackedEffect it would have had
Unique password plus app-based two-factor loginLikely blocked the mailbox takeover
Contract clause: bank details never change by email aloneClient would have verified, and liability would be clearer
Bank details fixed in a signed vendor formAny change would need a new signed form and a call
Regular check of mail rules and forwardingHidden rule would have been spotted

Prevention checklist for freelancers and consultants

  1. Use a separate business email account with a unique password and app-based or hardware-key two-factor authentication.
  2. Put a clause in every contract and on every invoice: “Our bank details will never change by email. Always confirm by phone on a number already known to you.”
  3. Share bank details once, in a signed document, at the start of the engagement.
  4. Check your email settings monthly for unknown forwarding rules, filters and connected apps.
  5. Send invoices as password-protected files or through an invoicing tool, and confirm receipt of large invoices on a call.
  6. Watch for look-alike domains in replies, especially when tone or urgency changes.
  7. Track expected payment dates; chase within a few days, not weeks.

If a payment has been diverted: the first hours

  • Tell the client immediately so their bank can request a recall of the transfer. Speed matters most here.
  • If the receiving account is in India, report on 1930 and at cybercrime.gov.in so that holds can be attempted.
  • Secure your email: change the password from a clean device, revoke sessions, remove rules, and turn on two-factor login.
  • Preserve evidence: email headers, the fake invoice, payment confirmations and timestamps.
  • Inform other clients that your account may have been accessed and that your bank details have not changed.

Tax and compliance side effects

If you raised an invoice but never received the money, keep careful records for your accounts and any GST reporting, and take professional advice on how to treat the unpaid amount. Our guide on tax for freelancers and consultants covers presumptive taxation and GST registration. If you also hold a salaried job, check your employment terms before taking side work; see moonlighting rules.

Common mistakes

  • Using a personal email with a reused password for client billing.
  • Trusting an email because it came from the right address. Compromised accounts send genuine-looking mail.
  • Waiting weeks to chase payment. Recall chances fall quickly.
  • Arguing liability before acting. Act on recovery first, discuss responsibility after.
  • Not fixing the root cause. Attackers often return to the same mailbox.

FAQ

Can the client’s bank reverse an international transfer?
It can send a recall request, but success depends on whether the funds are still in the receiving account and on the receiving bank’s cooperation. Early action improves the odds.

Is this only a risk for big companies?
No. Small freelancers are attractive because they often lack formal controls and use personal email accounts.

Should I stop sending invoices by email?
Not necessarily. Email is fine if bank details are fixed by contract and any change requires verbal confirmation through a known number.

Sources


Last reviewed: 11 November 2026. This article is general information, not legal or financial advice. For a specific incident, contact your bank, the cybercrime helpline and a lawyer as needed.

Leave a Reply

Trending