Home › Blog › Digital Infrastructure
Digital Infrastructure

Who Pays When a Scammer Impersonates Your Business? The Shared Responsibility Framework Gap

Who Pays When a Scammer Impersonates Your Business? The Shared Responsibility Framework Gap

If a scammer impersonates your company and a customer pays them instead of you, your company almost certainly carries that loss. Singapore's Shared Responsibility Framework, in force since 16 December 2024, requires banks and telecommunications operators to share the cost of certain digitally enabled phishing scams. It was written to protect individual consumers. Business accounts sit outside it, and so does the far more common case where somebody was tricked into making a payment they authorised themselves. For a small Singapore company, that means prevention is not the cheaper option. It is the only option. And the six weeks of December promotions, year-end invoicing and relief staff are exactly when the exposure peaks.

What does the Shared Responsibility Framework actually cover?

The framework, issued jointly by the Monetary Authority of Singapore and the Infocomm Media Development Authority, does not create a general scam refund. It sets out specific duties for two groups of businesses and makes them pay when those duties are breached.

If a duty was breached, losses are allocated down a waterfall: the financial institution first, then the telco, then the consumer. Crucially, the scope is narrow. It covers phishing scams, where somebody was deceived by a message pretending to come from a bank or a government agency and an unauthorised transaction followed. It does not cover authorised payments, where the victim knowingly sent money to someone who turned out to be a fraudster. Almost every scam that hits an SME or its customers is the second kind.

Why is a company account treated differently from a personal one?

The policy reasoning is that a business is expected to have its own controls: segregation of duties, payment approval limits, a finance process, and the option to buy insurance. A sole proprietor with one bank login and no second approver still sits on the business side of that line.

The practical consequence is blunt. When a consumer is scammed there is a defined process and a named party who may have to pay. When a company is scammed, recovery depends on three things that are all uncertain: whether the receiving bank can freeze the money in time, whether your insurance policy includes a social engineering fraud extension rather than just data breach cover, and whether your own records show you followed a documented verification step. Most small companies fail the third test, and that failure is what insurers decline on.

How does a scammer actually impersonate a small Singapore company?

Four patterns account for most of what we see, and none of them require technical sophistication.

What must be in place before the December peak?

These are the controls that matter, in the order they pay back fastest.

What do you do if the money has already gone?

Speed is the only variable you control. Call your bank's anti-scam line immediately, because a recall attempt in the first hour has a materially better chance than one made the next morning. File a police report, and use the ScamShield helpline on 1799 for guidance if you are unsure of the next step. Preserve the original emails with their full headers rather than forwarding screenshots, since that is what any investigation or claim will need. Tell affected customers before they find out elsewhere, and check your policy wording for a social engineering or funds transfer fraud extension rather than assuming cyber cover applies.

What does this realistically cost?

Sender name registration is a small annual fee. Email authentication is free. The verification rule, the approval threshold and the published channel page are procedure changes, not purchases. Set against one fraudulent invoice at the size a small company actually pays, the entire list is cheaper than the first incident, and considerably cheaper than the second one after your insurer has declined the first.

Frequently asked questions

Does the Shared Responsibility Framework apply if my company bank account is scammed?

Generally no. The framework was designed around individual consumer accounts and unauthorised phishing-related transactions. A company that authorises a payment to a fraudster is outside its scope, which is why internal verification and insurance wording matter more for a business than for a consumer.

Can I be held liable if a customer is scammed by someone impersonating my business?

Direct legal liability is unlikely in most straightforward cases, but that is not where the cost lands. The practical damage is the refund you feel obliged to make, the lost customer, and the reputational effect during your busiest selling weeks. Where you had an obvious control missing, such as an unregistered sender name, your position is noticeably weaker.

Is registering an SMS sender name still necessary if we only use WhatsApp and email?

If you genuinely never send text messages, registration is not relevant to you today. Register it anyway if there is any chance you will send order or delivery notifications, including through a third-party platform. Registration takes time, and December is the wrong month to discover that.

Ready to Transform Your Business?

Let Digital Perpetual help you automate, streamline, and grow.

Get Started with Digital Perpetual →
shared responsibility framework scam liability business email compromise sms sender id registry december peak