The RMAR: stop
dreading it.
The Retail Mediation Activities Return is an annual FCA submission. Sections B, D, E, G, and H. For most firms it means two weeks of chasing advisers for data that should already be in the system. Amaea pre-populates it from your live data.
Five sections, pre-filled from your live data.
Sections B, D, E, G, and H are the ones Amaea populates automatically. Each exports as CSV ready for GABRIEL upload.
Section B · Complaints
Drawn from the complaint log. Cross-checked against DISP 1.6: FOS rights communicated, 5-day acknowledgement, 8-week final response. Mismatches surface as draft-time warnings, not post-submission queries. Where firms fail: complaint records sit in email threads; the DISP 1.6 timestamps were never captured.
Section D · Financial resources
Pulled from the firm's connected platform feed (Intelliflo etc.). Revenue, regulated activity split, and capital position aligned to the FCA's GABRIEL data dictionary. Where firms fail: the regulated / non-regulated revenue split is manually estimated; the split changes month to month and gets stale.
Section E · PII renewal
Pulled from the policy schedule you upload at renewal. Limits, exclusions, and renewal date checked against the SUP 9.2 minimum. Schedule expiry triggers an in-app reminder 60 days out. Where firms fail: the renewal date is in a calendar; nobody cross-checks the schedule's exclusions and limits against the SUP 9.2 floor.
Section G · Adviser roster
Pulled from the live roster table. Only currently-active advisers are counted; SMCR roles tagged correctly; leavers excluded from headcount as of the reporting cut-off. Where firms fail: the roster includes ex-advisers because nobody marked them as leavers; SMCR roles drift out of sync with HR.
Section H · Training records
Drawn from the T&C record set against each adviser. CPD hours, attainment, SPS evidence. Gaps surface as flags before submission, not after the FCA queries the return. Where firms fail: CPD is tracked per adviser; the firm-wide aggregate gets calculated the day before submission, with gaps surfacing too late.
The most common RMAR errors
The most-repeated RMAR errors across the 27 compliance officers we interviewed in 2025. Every one of them prepared the return manually before talking to us.
- ✕ Complaint data inconsistent with FCA's own Register; firms submit different numbers than FCA already holds
- ✕ Business volumes don't reconcile to Intelliflo data; manual extraction introduces errors under deadline pressure
- ✕ Vulnerable client percentage can't be verified; no single system tracked it across the year
- ✕ Submission made late or with known errors because data gaps couldn't be resolved in time
Amaea pre-fills sections B/D/E/G/H from Intelliflo + SharePoint, runs the DISP 1.6 cross-check, and exports a CSV ready for GABRIEL.
Book a demoRMAR submission, the honest version.
What we ship pre-filled, what we cross-check before submission, what the GABRIEL-ready CSV actually looks like, and what the first quarter really costs you in reconciliation time.
The first time you run Amaea's RMAR draft, expect to spend an afternoon reconciling discrepancies between what Intelliflo says and what the spreadsheet you've been using says. From the next quarter onwards, the same run takes under an hour.
Section B is checked against DISP 1.6: was FOS notified, was the 5-day acknowledgement sent, did the final response arrive inside 8 weeks? Where any of these are missing, the system tells you in the draft. Not after the return is submitted and the FCA queries it.
Run the gap report 30 days before submission. It lists every incomplete data point with the underlying record, so you have a real list to work through. Not "Section G is empty" with no context. Each gap links straight to the client or document that needs an update.
Each section exports as a CSV in the column layout GABRIEL expects. The CSV header is the same field-name format as the FCA's own data dictionary. Paste into GABRIEL, validate, submit. No manual re-keying.