How FCA financial promotions rules apply to fintech SaaS

What to take away

This site is about marketing for SaaS companies. FCA financial promotions rules are not just a legal topic for regulated firms; they are a marketing constraint for any SaaS business selling into UK financial services. They affect positioning, landing page claims, sales decks, webinars and case studies. They also change the proof you need before a campaign goes live.

For a SaaS marketing team, this is a worked example of regulated demand generation. It shows how to turn a compliance constraint into a positioning advantage, with claims mapped to proof and review built into the campaign workflow. The same method applies when your ICP includes any regulated buyer.

If you work in-house, read references to a SaaS marketing team as your own team or your external partner. The goal is the same: create demand with claims that survive compliance review. The rest of this guide shows how to do that without losing the commercial message.

When FCA financial promotion rules catch fintech SaaS

The Financial Conduct Authority regulates conduct across UK financial services and sets the promotion rules firms must follow. Its remit covers banks, insurers, brokers and the firms that sell software into those businesses.

The FCA is a public body, not an industry club, and its rules bind regulated firms and, in some cases, their suppliers. You can read the FCA's own description of its role on the Financial Conduct Authority - GOV.UK page.

When made in the course of business, a financial promotion is an invitation or inducement to take part in investment activity. That definition is deliberately wide. It catches a landing page, a webinar, a sales deck and a LinkedIn post if the content invites someone to buy or use a regulated product or service.

Fintech SaaS often sits one step away from the regulated product. A fraud detection tool, an onboarding platform or a lending decision engine may not itself be a regulated activity, but marketing it to a bank can still be a financial promotion if the bank uses it to deliver regulated services.

Ask one question early: does this message invite a regulated firm to engage in regulated activity? If yes, the FCA financial promotion rules apply. If no, other regimes still apply, including the advertising codes that fintech SaaS marketing must comply with, as set out in the Advertising codes - ASA | CAP.

The B2B misconception

Many software marketers assume B2B means no consumer rules. That is wrong for fintech. A bank's compliance team will ask how your claims affect its own regulatory position. A claim that misleads a bank about how a model performs can become a misleading financial promotion once the bank repeats it to customers.

The FCA does not need to regulate your software directly to care about your marketing. It regulates the firm that uses your software. That firm will push its obligations down the supply chain through contracts, due diligence and sign-off.

Where the boundary sits

Pure technology marketing, such as cloud hosting or internal HR software, usually falls outside financial promotion rules. Marketing that touches credit, payments, investments, insurance or claims handling usually falls inside. The boundary is the regulated activity, not the label on your product.

If you are unsure, map each claim to the regulated activity it supports. A claim about faster loan decisions supports credit broking or lending. A claim about lower fraud losses supports payment services. That mapping is the first compliance artefact your client's team will ask for.

The financial promotion gateway and approval routes for B2B software

Approval routes for B2B software promotions depend on who is communicating. An authorised firm can approve its own promotions. An unauthorised firm generally cannot, unless an authorised person approves the content under section 21 of the Financial Services and Markets Act 2000.

Section 21 is the gateway. It says a person must not communicate a financial promotion unless they are authorised, or the content is approved by an authorised person, or an exemption applies.

For fintech SaaS, that means the route is usually one of three: the client is authorised and owns the promotion; an authorised partner approves it; or an exemption covers it.

Exemptions exist for certain B2B communications, but they are narrow and fact-specific. A sales deck sent to a regulated firm's procurement team is not automatically exempt. The exemption depends on the audience, the product and the nature of the communication.

The three practical routes

Each route changes your production timetable. Approval can add days or weeks. Build that into campaign planning rather than treating it as a launch-week problem.

What the gateway means for SaaS marketers

A SaaS marketing team cannot approve a financial promotion unless it is authorised to do so. That authority usually sits with the client or a specialist approver.

The marketing team's job is to prepare content that is capable of approval. That means clean claims, sourced figures, clear caveats and a record of the evidence behind every statement. It also means knowing when to stop writing and ask for a compliance review.

For a wider view of how these rules interact with campaign planning, see SAAS marketing rules and ethics.

Consumer Duty and what it means for software sold to banks

Consumer Duty obligations require firms to act to deliver good outcomes for retail customers. The duty has four outcomes: products and services, price and value, consumer understanding, and consumer support. It applies to firms across the distribution chain, including those that supply software used to serve retail customers.

Software sold to banks is in scope when it affects a retail customer's experience. A decisioning engine, a collections platform or a claims portal can all influence whether a customer gets a fair outcome. The bank remains responsible, but it will expect its suppliers to help it meet the duty.

That expectation shows up in procurement. Banks now ask suppliers for evidence on how a product supports consumer understanding, how it handles vulnerable customers and how it avoids foreseeable harm. Marketing claims that ignore these questions look naive to a compliance buyer.

The four outcomes in software terms

A marketing page that claims a tool improves customer outcomes needs evidence. That evidence may be a test result, a model validation report or a pilot outcome. Without it, the claim is a liability for the bank and for you.

Vulnerability and foreseeable harm

Consumer Duty obligations put extra weight on vulnerable customers. If your software screens applications or sets limits, the bank must show it does not cause foreseeable harm to those customers. Marketing that ignores vulnerability will fail a compliance review.

Practical steps include documenting how the software handles edge cases, what human oversight exists and how errors are corrected. These are not marketing extras. They are the substance behind a compliant claim.

For the regulatory backdrop that sits alongside FCA rules, see SAAS marketing UK regulations.

Named FCA sourcebooks and the rules that matter most

Named FCA sourcebooks are the rulebooks that sit under the FCA's handbook. For financial promotions, the most relevant are COBS 4, PERG and SYSC. Each does a different job, and each creates a different obligation for fintech SaaS marketing.

COBS 4 is the conduct of business sourcebook chapter on financial promotions. It requires promotions to be fair, clear and not misleading. It sets rules on risk warnings, past performance and the balance of benefits and risks. If your claim appears in a promotion, COBS 4 is the standard it will be judged against.

PERG is the perimeter guidance manual. It helps firms decide whether an activity is regulated and whether a communication is a financial promotion. PERG is where you check whether an exemption applies. It is guidance rather than a single rule, but it is the first place a compliance team will look.

SYSC is the senior management arrangements, systems and controls sourcebook. It covers governance, outsourcing and record-keeping. SYSC matters because it explains why the bank needs evidence from you and why it will keep that evidence.

Other sourcebooks worth knowing

COBS 2 covers the client's best interests rule and communications with clients. It reinforces the fair, clear and not misleading standard. BCOBS covers banking conduct and matters when software touches retail banking communications. MCOB covers mortgages and home finance, relevant if your software supports mortgage decisions.

ICOBS covers insurance conduct, relevant for insurtech SaaS. CONC covers consumer credit, relevant for lending and collections software. Each sourcebook adds specific rules on top of the general promotion standard.

How to use the sourcebooks without a law degree

You do not need to memorise the handbook. You need to know which sourcebook your claim touches and who in the client's team owns it. Build a simple map: product, regulated activity, sourcebook, owner. That map turns a vague compliance conversation into a specific one.

When a claim is challenged, the sourcebook gives you the language to resolve it. COBS 4 gives you the fair, clear and not misleading test. PERG gives you the perimeter question. SYSC gives you the evidence question. Those three questions cover most day-to-day disputes.

A SaaS marketing team that can speak this language becomes easier to approve, not harder. It also reduces the risk of late-stage rewrites.

For the contractual side of these arrangements, see SAAS marketing commercial contracts.

Examples of compliant and non-compliant software marketing claims

Worked examples make the rules concrete. The difference between a compliant and a non-compliant claim is usually not the product, but the promise. Compliant claims describe what the software does and the evidence behind it. Non-compliant claims promise an outcome the software cannot deliver.

The table below sets out common pairs. Each non-compliant claim would breach the fair, clear and not misleading standard in COBS 4. Each compliant version keeps the benefit while removing the promise of a certain result.

A worked example

Imagine a fintech SaaS firm selling an affordability tool to a UK bank. The draft headline reads: "Our tool ensures every borrower can afford their loan." That claim fails on two counts. It promises a regulated outcome, and it implies the bank can rely on the tool instead of its own assessment.

A compliant rewrite reads: "Our tool helps affordability teams apply the bank's lending policy consistently, with an audit trail for every decision." This version describes the function, respects the bank's responsibility and avoids a promise of a certain result. It is also easier to evidence.

A checklist before you publish

Run this checklist on every campaign asset, not just the main landing page. Webinars, case studies and sales decks all carry the same risk. The ASA's advice for businesses on compliant claims, available at Advice for businesses - ASA | CAP, is a useful cross-check for the advertising side.

Working with a client's compliance team on sign-off

Sign-off is a process, not an event. The best time to involve a client's compliance team is before the first draft, not after the campaign is built. Early involvement turns compliance into a source of accurate claims rather than a blocker.

Start with a scoping call. Ask which sourcebooks apply, who owns approval and what evidence the team expects. Ask whether the promotion needs section 21 approval and who will provide it. Record the answers in writing.

Then agree a review cycle. Compliance teams rarely turn around a full campaign in a day. Build two review rounds into your timeline, with a named reviewer on each side.

What compliance teams actually want

They want claims they can defend. That means a source for every figure, a caveat where the evidence is limited and no implied endorsement by the FCA. They also want to see that you understand the bank's own obligations, including Consumer Duty.

They dislike surprises. A new claim introduced late in the process causes more work than a claim raised early. Share the full asset list, including social posts and email sequences, at the start.

Handling disagreement

When compliance pushes back, ask which rule or sourcebook is engaged. That moves the conversation from taste to test. If the concern is a comparative claim, check whether you can substantiate it. If the concern is an implied outcome, rewrite around the function.

Escalate only when the rule is unclear. Most disputes resolve once the sourcebook is named and the evidence is produced.

For the diligence questions that sit alongside sign-off, see SAAS marketing vendor due diligence. The Competition and Markets Authority - GOV.UK also matters here, because its work on market conduct shapes how banks buy and use software.

Evidence and record-keeping for financial promotions

Evidence is what turns a claim into a defensible statement. Under SYSC, firms must keep records that show how they meet their obligations. When your software supports a bank's regulated activity, your evidence becomes part of the bank's record.

Keep evidence for every material claim. That includes model performance data, test results, pilot outcomes, customer research and the date each item was produced. Store it where the client's compliance team can retrieve it quickly.

Version control matters. A claim approved in March may be unsupported by June if the underlying data changes. Set a review date for each claim and retire it when the evidence expires.

A simple evidence log

Pair the log with a sign-off record. Note who approved the wording, when and under which route. If section 21 approval applies, keep the approver's confirmation. If an exemption applies, record the reasoning.

Audits and retrospectives

Expect periodic reviews. A bank's internal audit may ask for the evidence behind a claim it repeated to customers. An FCA review may ask the bank to show how it controlled the promotion. Your log is the fastest way to answer both.

After each campaign, run a short retrospective. Note which claims were challenged, which were changed and which evidence was missing. Feed the lessons into the next campaign brief.

This discipline is also good marketing. A SaaS marketing team that can show evidence wins trust with compliance buyers and shortens sales cycles. It also supports the service standards clients expect; see SAAS marketing service standards.

Common questions