
Rules and ethics
Financial email campaign compliance checks
Financial email campaign compliance covers consent, promotions, claims, suppression, rendering and post-send review, alongside email deliverability.
What to take away
- Email deliverability sits alongside the financial campaign compliance checks covered here.
- Keep recipient records that show the source, wording, date and scope of consent.
- Before release, classify the content, check financial claims and risk warnings, apply suppression, and test rendering and the unsubscribe path.
- After sending, review bounces, complaints and unsubscribes.
Financial campaign compliance checks
The campaign checks span personal data and electronic marketing, financial promotions, and advertising claims. The ICO, FCA and ASA each see a different slice.
Three regulators, three slices
ICO
- Polices
- Personal data
- Rules
- UK GDPR, PECR
- Email view
- Data processing
- London base
- Headquartered
FCA
- Polices
- Financial promotions
- Rules
- FCA Handbook
- Email view
- Promotion
- London base
- Canary Wharf
ASA
- Polices
- Advertising claims
- Rules
- CAP Code
- Email view
- Advertisement
- London base
- Codes and rulings
London is the setting for this guide. For the local angle, see London matters. Compliance advice is easy to find and easy to get wrong.
Overlap is the practical problem. One email can be a data processing activity, a financial promotion and an advertisement at the same time. Each regulator sees a different slice.
The rules sit in UK GDPR and the Data Protection Act 2018, PECR, the FCA Handbook and the CAP Code.
Start from the UK rules that touch an email campaign before choosing a sending platform. The order of checks decides the build.
Recipient records and consent checks
PECR governs electronic marketing to individuals. Consent must be specific, informed and freely given, and the ICO expects records that survive an audit.
Consent or soft opt-in?
Is the recipient an existing customer?
Soft opt-in may apply
Consent required
The ICO's guidance on direct marketing and regulatory communications draws the line that most financial firms blur. Marketing needs consent or soft opt-in. Regulatory communications do not.
Soft opt-in is narrow. It applies to existing customers, at the point of sale, for similar products, with an opt-out in every message. A wealth manager emailing a prospect about a new fund cannot use it.
Choosing the basis is a documented decision, not a default. The ICO's page on choosing your lawful basis sets out legitimate interests, consent and contract, and the balancing test each requires.
Consent records need the source, the wording shown, the date and the scope. A tick box that covers "financial products" will not cover a pension transfer campaign.
Remember that email compliance is never just a configuration setting. The platform stores consent; it does not create it.
What a consent record should hold
| Field | Example | Why it matters |
|---|---|---|
| Source | Website form, 12 March | Shows how consent was captured |
| Wording | "Send me investment updates" | Defines the scope |
| Basis | Consent | Distinguishes from soft opt-in |
| Proof | Timestamp and IP | Supports accountability |
| Withdrawal | Unsubscribe link and date | Closes the record |
Reviewing financial promotions before sending
A financial promotion is an invitation or inducement to engage in investment activity, communicated in the course of business. Most marketing email from an authorised firm is one.
FCA promotion checks
- Fair, clear and not misleading
- Balanced view of risks and benefits
- Identifiable as a financial promotion
- Risk warnings prominent, not buried
- Section 21 gateway satisfied
- Approval owned on every edit
The Handbook of rules and guidance holds the rules. COBS 4 covers form and content: fair, clear and not misleading, with a balanced view of risks and benefits.
Section 21 of the Financial Services and Markets Act 2000 is the gateway. An unauthorised person cannot communicate a promotion unless an authorised firm approves it or an exemption applies. Email forwarded to a friend can breach this.
Financial promotions must be identifiable as such. A subject line that reads like a personal note, with the promotion buried below, fails the clarity test.
Risk warnings must be prominent, not appended in six point type. Past performance warnings and capital risk statements belong where the reader sees them.
The FCA's consumer protection objective sits behind these rules. It gives the regulator grounds to act where a promotion could mislead a retail client.
Approval is not a one off. If a firm approves an email template, it owns the content every time a sales team edits it.
Where promotions go wrong
- Returns shown without a risk warning.
- A comparison to a competitor that cannot be substantiated.
- A headline rate that omits the qualifying conditions.
- A call to action that implies capital cannot fall.
Checking financial claims before sending
The ASA administers the advertising codes that apply to financial claims in email. The CAP Code covers non broadcast advertising, which includes marketing email.
ASA claim checks
- Claims substantiated before they run
- Endorsements genuine and representative
- Comparisons compare like with like
- Qualifications do not contradict headline
- CAP Code and Handbook both checked
Claims must be substantiated before they run. "Best performing fund" needs evidence the firm holds, not a ranking it once saw.
Endorsements and testimonials must be genuine and representative. A client quote about a returns figure needs the same substantiation as the claim itself.
Comparisons must compare like with like. An ISA rate against a savings account rate, without stating terms, invites a ruling.
Prominence matters as much as accuracy. A qualification in a footnote that contradicts the headline claim does not fix it.
The ASA and FCA overlap here. A promotion can breach the CAP Code and the Handbook at once, and the ASA will refer FCA regulated firms to the regulator.
Before release, run a check on claims, endorsements and permission. It catches the wording problems that survive legal review.
Worked example: a wealth manager's campaign
A London wealth manager plans an email to 4,000 opted-in contacts about a new multi asset fund. The team drafts a subject line, a returns table and a client quote.
The compliance officer checks three things. Consent records show the contacts opted in to "investment updates" in the last 18 months. The returns table carries a past performance warning above the figures. The client quote is genuine and the client has given written permission.
The FCA angle is approval. The firm is authorised, so it can communicate its own promotion, and the approver signs off the final HTML rather than the Word draft.
The ASA angle is the headline. "Beat the market" is dropped because the evidence does not support it for this fund. The revised line describes the objective instead.
The ICO angle is the send list. Contacts who opted in to a different product line are excluded, and the suppression file is applied at send time.
Keeping regulatory communications separate from marketing
Regulatory communications are messages a firm must send to meet a legal or contractual duty. They are not marketing, and PECR treats them differently.
Regulatory vs marketing email
Regulatory
- Purpose
- Legal duty
- Consent
- Not required
- Examples
- Terms change, statement
- Suppression
- Still applies
Marketing
- Purpose
- Promotion
- Consent
- Required or soft opt-in
- Examples
- New fund offer
- Suppression
- Objection blocks send
Examples include a change to terms, a statement of account, a risk disclosure or a service interruption notice. They can be sent without consent because the law requires them.
The test is purpose, not format. If the same email adds a promotion for a new product, the whole message risks becoming marketing.
Keep the two streams separate. A regulatory email with a promotional banner at the bottom is the classic mistake, and it undermines the exemption for the rest of the message.
Suppression rules still apply. A customer who has objected to marketing can still receive a contractual notice, but not the offer beside it.
Document the classification. When the ICO asks why an email went to a non consented address, the answer must be a specific legal duty, not a preference.
A send workflow for financial email campaigns
Work through the campaign in the order below. Each step produces evidence for the next check.
Seven-step compliance map
- Map the data and record sources
- Choose the lawful basis and document it
- Classify the content type
- Draft against COBS 4, CAP Code, PECR
- Approve and record with named approver
- Build send list with consent filters
- Review bounces, complaints and unsubscribes
- Map the data. Record where each contact came from, what they agreed to receive and when. Use the method in drawing the email data path.
- Choose the basis. Decide consent, soft opt-in, legitimate interests or regulatory communication, and write the reasoning down.
- Classify the content. Decide whether the email is a financial promotion, an advertisement, a regulatory communication or a mix.
- Draft against the rules. Apply COBS 4 for form and content, the CAP Code for claims, and PECR for consent.
- Approve and record. A named approver signs off the final HTML, and the approval is stored with the send record.
- Build the send list. Apply consent filters and suppression files, then test the rendering and the unsubscribe path.
- Review after send. Check bounces, complaints and unsubscribes, and log any ruling or query.
Pre-send checklist
- Consent source, wording and date recorded for every recipient.
- Lawful basis documented, including any soft opt-in reasoning.
- Financial promotion status decided and approval recorded.
- Risk warnings and past performance statements prominent.
- Every claim substantiated and evidence filed.
- Endorsements genuine, permitted and representative.
- Suppression list applied and unsubscribe link tested.
- Regulatory and marketing content kept in separate emails.
Check suppression before release as part of the financial email send workflow.



