Odoo ERP implementation 19 for UK insurance brokers provides CRM, policy renewal automation, ICOBS-compliant document generation, and FCA audit trails at 20-30% of the cost of Acturis or Open GI. For a 3-15 person UK broker writing £2m-£15m GWP, implementation costs £8,000-£22,000 and takes 8-14 weeks. Softomate Solutions configures Odoo 19 for FCA-authorised insurance brokers with UK data hosting.
Last updated: 18 May 2026
Published 18 May 2026For the past two decades, Acturis has been the default choice for UK commercial insurance brokers. It is deeply embedded in the market, integrated with Lloyd's and the London Market, and trusted by thousands of brokers across the country. For a £50m GWP brokerage with a large insurer panel and complex bordereaux obligations, Acturis justifies its cost. But for the 3-15 person broker writing £2m-£15m in gross written premium, the maths no longer stacks up.
A typical Acturis licence for a brokerage of this size runs between £15,000 and £40,000 per year in platform fees alone, before implementation, customisation, or additional module costs. Open GI sits in a similar bracket. Applied Epic, which is more commonly associated with the US market but has a growing UK footprint, commands comparable fees. For a broker whose total revenue might be £300,000-£600,000 a year, spending 5-10% of gross income on a single software platform is a significant overhead that limits what can be invested in staff, marketing, and client service.
The second pressure is functional mismatch. Acturis was built for brokers who need deep insurer EDI connectivity, automated policy issuance across a large panel, and bureau submission workflows for Lloyd's. Many smaller brokers do not need that level of insurer integration. They work with a handful of MGAs and insurers, issue policy documents themselves, and manage renewals through a mix of spreadsheets, email, and diary reminders. They are paying for infrastructure they do not use while still fighting against manual processes that a modern CRM system could eliminate.
The third pressure is the FCA's Consumer Duty, introduced under PS22/9, which came into full effect for new business from 31 July 2023 and for closed book products from 31 July 2024. Consumer Duty requires brokers to demonstrate that they are acting to deliver good outcomes for retail customers, with documented evidence of demands and needs assessments, fair value analysis, and ongoing monitoring. This is a data and documentation challenge as much as a conduct challenge. Brokers need systems that can generate, store, and retrieve compliance documents reliably - and many smaller brokers are doing this in Word templates and shared drives.
Odoo 19 addresses all three problems simultaneously. It is open-source at its core, which means no per-seat insurer connectivity fees. Its modular architecture means you pay only for the capabilities you deploy. And its document, signing, and audit trail features can be configured to meet ICOBS and Consumer Duty requirements without purchasing a separate compliance platform. For sub-£20m GWP brokers, it represents a genuinely viable alternative - not as a like-for-like replacement of Acturis, but as a right-sized system that does what smaller brokers actually need.
Odoo 19 is a modular ERP platform, which means you deploy the applications that match your operational needs and leave the rest unused. For an insurance broker, the relevant modules form a coherent operational stack covering client management, document handling, premium administration, and e-signatures. The following breakdown explains how each module maps to brokerage functions.
The Odoo CRM module handles the client acquisition and renewal pipeline. Each prospect or client is a lead or opportunity, tracked through stages that you define to match your process - for example: Enquiry Received, Quote Requested, Quote Sent, Placed, Declined. Renewal opportunities can be created automatically from expiring policies and assigned to account handlers. Activity reminders ensure nothing drops through. The CRM integrates with the Contacts module so every client communication is logged against their record, creating the kind of interaction history that supports Consumer Duty monitoring.
The Contacts module holds your full contact database: clients, insurers, MGAs, loss adjusters, and introducers. Each contact record holds company type, address, regulatory reference numbers (FRN for FCA-authorised entities), terms of business agreement status, and any bespoke fields your team needs. For insurers and MGAs, you can record panel appointment dates, TOBA reference numbers, and commission rates - information that sits in folders or spreadsheets in most smaller brokerages.
The Documents module creates a structured, searchable file store for every document your brokerage generates or receives. Policy schedules, certificate of insurance PDFs, demands and needs statements, TOBA copies, complaints correspondence, and Consumer Duty fair value assessments all live in tagged, permission-controlled workspaces. Documents can be linked directly to client records and opportunity records, so a compliance audit of a specific client's file is a single click rather than a multi-folder search. Version control ensures you can see which version of a document was sent and when.
Insurance brokers operate on an agency or broker model with distinct cash flows: client premium receipts, insurer premium remittances, and commission income. Odoo's Invoicing module handles all three. You can create premium invoices to clients, record insurer remittances against them, and track commission statements. The chart of accounts can be configured to the FCA's client money rules under CASS 5, with separate ledger codes for client premium accounts and office accounts. For brokers using Xero as their primary accounts package, Softomate builds a bi-directional sync so Odoo holds the insurance-specific transactional detail while Xero manages management accounts and VAT returns.
The Odoo Sign module enables legally binding electronic signatures on documents. For brokers, this applies to demands and needs statements requiring client sign-off, TOBA acknowledgements, SECCI documents for premium finance, and mandate forms. Each signed document generates an audit certificate recording the signatory's email address, IP address, timestamp, and document hash - evidence that meets the requirements of the Electronic Communications Act 2000 and satisfies FCA expectations for documented client consent.
| Module | Broker Function | Key Benefit |
|---|---|---|
| CRM | Client pipeline, renewal tracking, account handler assignment | No renewal slips through; Consumer Duty interaction log |
| Contacts | Client, insurer, and MGA records with FRN and TOBA data | Single source of truth for panel management |
| Documents | Policy schedules, compliance files, TOBA copies | Searchable, versioned, linked to client records |
| Invoicing | Premium invoicing, commission tracking, CASS 5 ledger codes | Clear separation of client money and office money |
| Sign | E-signatures for demands and needs, TOBAs, mandates | Audit certificate meets FCA documentation requirements |
| Email Marketing | Renewal invites, risk management newsletters | Automated sequences triggered by renewal dates |
The combined monthly licence cost for this module set on Odoo.sh (cloud-hosted, UK region) for a team of up to 15 users typically falls between £350 and £600 per month, depending on the hosting tier and the number of Sign credits consumed. This compares with Acturis fees that can run to £3,000 per month or more for a brokerage of similar size.
The Insurance: Conduct of Business sourcebook, known as ICOBS, is the FCA's primary rulebook for insurance brokers distributing non-investment insurance contracts. Compliance with ICOBS is not optional - it is a condition of FCA authorisation. The key chapters that affect broker operations and therefore broker systems are ICOBS 2 (communications), ICOBS 4 (advising and selling standards), ICOBS 6 (pre-contract disclosure), and ICOBS 8 (claims handling). The FCA's Consumer Duty (PS22/9) layered additional obligations on top of ICOBS from July 2023.
ICOBS 2.5 requires that all communications with customers are fair, clear, and not misleading. In an Odoo context, this means every outbound email template, renewal invite, and policy summary letter must be reviewed and approved before use, with version control showing when each template was last updated and by whom. Odoo's Documents module supports this through template workspaces with approval workflows. A compliance officer can approve a template before it enters the live email sequence, and the system records that approval against the document version.
ICOBS 6 requires brokers to specify the demands and needs of the customer before conclusion of the contract, and to provide a statement in a durable medium explaining why a recommended product meets those demands and needs. In Odoo, this is implemented through a custom form linked to each opportunity record. The form captures the client's stated requirements across standard fields - business type, turnover, number of employees, previous claims, specific cover requirements - and generates a PDF demands and needs statement using Odoo's report engine (QWeb). The PDF is automatically stored in the client's Documents workspace and can be e-signed by the client via Odoo Sign before policy inception.
The FCA's Consumer Duty requires brokers to monitor and demonstrate good outcomes across four outcome areas: products and services, price and value, consumer understanding, and consumer support. For a smaller broker, the practical requirements are systematic: you must be able to show that your recommended products are appropriate for your customers' needs, that your charges represent fair value, that your communications are understood, and that customers receive adequate support when they need it.
Odoo supports this through a combination of CRM activity logging (every client interaction recorded), custom fields on opportunity records (e.g. fair value assessment completed: yes/no; date), document linking (fair value assessment PDF attached and dated), and a scheduled report that pulls all renewal opportunities where Consumer Duty fields are incomplete. A broker principal can run this report at any time and produce a list of files requiring attention - the kind of management information the FCA expects to see during a supervisory visit.
ICOBS requires brokers to retain records for a minimum of three years (or longer for certain categories). Odoo's database stores all records permanently unless explicitly deleted, with no automated purge. Softomate's implementation includes a data retention policy document and, optionally, a custom archiving workflow that moves records older than a configurable threshold to an archive state - still queryable but excluded from active views. All changes to client records, document uploads, email sends, and CRM activity completions are timestamped and tied to the user who made them, creating the audit trail that FCA supervisors look for during desk-based reviews and skilled persons reports.
Renewal management is where most smaller brokerages lose the most time and carry the most risk. A missed renewal - whether because a diary reminder was not set, an account handler left, or a client's email address changed - creates a coverage gap that can result in a claim being declined and a professional indemnity claim against the broker. Industry estimates suggest that manual renewal management in a 5-10 person brokerage consumes 30-45 minutes of account handler time per renewal cycle per client, across the various touch-points of initial contact, chasing, confirmation, and document dispatch.
Odoo 19's combination of CRM, email marketing automation, and scheduled actions eliminates the manual diary-keeping element and standardises the renewal process across your team.
When a policy record is created in Odoo with an expiry date, a scheduled action creates a renewal opportunity in the CRM pipeline 90 days before expiry. The opportunity is assigned to the account handler responsible for that client. An automatic activity is logged: 'Begin renewal - request renewal terms from insurer/MGA.' This gives the account handler their work queue each morning without requiring a separate diary system or manual tracking.
At 60 days before expiry, if the renewal opportunity is still at the 'Terms Requested' stage (i.e. no quote has been issued), an automated email is sent to the account handler as an internal nudge. If terms have been received and the opportunity is at 'Quote Ready', an automated renewal invite is sent to the client. The renewal invite email template includes the current cover summary (populated from policy fields on the opportunity record), the proposed renewal premium, and a call to action linking to a secure online acceptance form or asking the client to confirm by return.
When a client accepts the renewal - either by clicking the acceptance link or by the account handler updating the CRM stage to 'Renewal Accepted' - an automated workflow triggers policy document generation. Odoo's QWeb report engine renders the policy schedule, certificate of insurance (where applicable), and updated demands and needs statement as PDFs. These are stored in the client's Documents workspace and sent to the client as email attachments. The Odoo Sign module can be triggered automatically to request e-signature on the demands and needs statement before the documents are dispatched.
If the renewal opportunity reaches the expiry date without progressing to 'Renewal Accepted' or 'Not Taken Up - Client Cancelled', an automated alert is sent to the account handler and their line manager. A follow-up email sequence (configurable: 7 days, 14 days post-expiry) checks whether the client has arranged cover elsewhere. This is not just a commercial safeguard - it is a Consumer Duty obligation. Brokers must be able to demonstrate that they made reasonable efforts to ensure clients did not face unintended coverage gaps.
The net time saving from this automation is estimated at 25-35 minutes per renewal cycle per client, based on eliminating manual diary management, email drafting from templates, and document assembly. For a broker with 200 active commercial clients, this represents approximately 80-120 hours of account handler time recovered per year - the equivalent of two to three weeks of full-time capacity that can be redirected to new business or client service.
Choosing a broker management system involves assessing fit across several dimensions: the GWP scale the platform is designed for, insurer connectivity depth, bordereaux and MGA reporting capability, FCA compliance features, implementation cost, and ongoing licence cost. The table below provides a structured comparison based on publicly available information and Softomate's implementation experience as of May 2026.
| Criterion | Odoo 19 | Acturis | Applied Epic | Broker Buddha |
|---|---|---|---|---|
| Target GWP range | £1m - £20m | £5m - £500m+ | £20m - £500m+ | £500k - £10m |
| Insurer EDI connectivity | Manual / API (custom) | Deep (100+ insurers) | Deep (UK panel growing) | Limited |
| MGA bordereaux reporting | Custom report builder | Native | Native | Limited |
| FCA ICOBS compliance features | Configurable (via Softomate) | Built-in templates | Built-in (US-first) | Basic |
| Consumer Duty reporting | Custom dashboards | Developing (2025-26) | Limited (UK adaptation) | Not available |
| Implementation cost | £8,000 - £22,000 | £25,000 - £80,000+ | £40,000 - £120,000+ | £3,000 - £8,000 |
| Monthly licence (15 users) | £350 - £600 | £2,000 - £5,000+ | £3,000 - £7,000+ | £300 - £500 |
| UK data hosting | Yes (Odoo.sh) | Yes | Yes (Azure UK) | Yes |
Sole trader to 3-person broker (GWP under £2m): Broker Buddha offers the lowest barrier to entry and the fastest setup. Odoo is worth considering if you anticipate growth or need a platform you can expand without migrating later.
3-15 person broker (GWP £2m-£15m): Odoo 19 offers the best cost-to-capability ratio. The absence of native insurer EDI is a genuine limitation if you need automated policy issuance across a large panel, but most brokers in this segment place business manually via MGA extranet or through a small number of insurer relationships. Odoo handles this segment well.
15-50 person broker (GWP £15m-£50m): Acturis becomes genuinely competitive at this scale. The insurer connectivity and bordereaux reporting capabilities are difficult to replicate in Odoo without significant custom development. Acturis's total cost of ownership is higher but may be justified by the operational efficiencies at scale.
50+ person broker (GWP £50m+): Acturis or Applied Epic are the natural choices. Odoo is not designed for this level of complexity, volume, or insurer integration depth.
Softomate Solutions has delivered Odoo implementations for professional services businesses and regulated industries across London and the UK since 2019. Our insurance broker implementation package is built specifically around FCA authorisation requirements, ICOBS compliance obligations, and the operational patterns of 3-15 person commercial brokers. We do not offer a generic Odoo deployment - every insurance broker engagement begins with an FCA compliance mapping session that translates ICOBS obligations into specific Odoo configuration requirements.
FCA compliance mapping: A structured workshop session mapping your specific ICOBS obligations to Odoo modules and configuration options. Output is a written compliance configuration document that you can show to your compliance officer or FCA supervisor.
Odoo configuration: Installation and configuration of CRM, Contacts, Documents, Invoicing, Sign, and Email Marketing modules. Custom fields for insurance-specific data (policy type, expiry date, insurer/MGA, premium, commission rate, FRN references). Custom CRM pipeline stages matching your renewal and new business processes.
ICOBS document templates: QWeb report templates for demands and needs statements, renewal invite letters, policy cover summaries, and TOBA acknowledgement letters. Templates are drafted to meet ICOBS 2.5 fair communications standards and reviewed by your team before go-live.
Xero integration: Bi-directional sync between Odoo Invoicing and Xero, covering premium invoices, commission credit notes, and payment reconciliation. Client money and office money ledger codes configured to CASS 5 requirements.
E-signature workflow: Odoo Sign configured for demands and needs statements, TOBA acknowledgements, and any other documents requiring client sign-off. Audit certificates stored automatically in the client's Documents workspace.
Renewal automation setup: Scheduled actions and email sequences for 90-day, 60-day, and 30-day renewal touch-points. Lapsed policy alert workflows. Account handler activity queues configured.
Staff training: Half-day remote training session for account handlers and a separate session for management covering reporting and compliance monitoring. Training materials provided as a written reference guide.
Implementation cost: £8,000 to £22,000 depending on team size, the number of active clients being migrated from your existing system, and the complexity of document template requirements. Projects run over 8 to 14 weeks from kick-off to go-live. Ongoing support is available on a retained basis from £350 per month, covering platform updates, template revisions, and helpdesk access for your team.
UK data hosting is on Odoo.sh in the EU (Ireland) region, which meets UK GDPR requirements. On-premises deployment to a UK-based server is available for brokers with specific data residency requirements from their PI insurers or Lloyd's market obligations.
The FCA does not approve or endorse specific software platforms. What the FCA requires is that your systems support your ability to meet your regulatory obligations - ICOBS compliance, Consumer Duty, CASS 5 client money rules, and record keeping. Odoo 19, configured by Softomate with insurance-specific templates and workflows, supports all of these obligations. Responsibility for compliance always rests with the FCA-authorised firm, not the software vendor.
For brokers with deep insurer EDI requirements, automated policy issuance across a large panel, or significant bordereaux reporting obligations, Odoo is not a direct like-for-like replacement for Acturis. For brokers writing £2m-£15m GWP through a small number of MGA and insurer relationships, placing business manually via extranet, Odoo handles the CRM, compliance documentation, renewal automation, and invoicing functions that matter most - at a fraction of the cost.
Odoo does not have a native bordereaux module equivalent to Acturis. However, Odoo's custom report builder (Odoo Studio) and its Excel/CSV export capabilities allow you to produce bordereau-format data exports that can be uploaded to MGA portals or formatted to MGA specifications. For brokers with complex or high-volume bordereaux obligations, this is a manual step rather than an automated one - a genuine limitation worth factoring into your decision.
A sole trader broker can start on Odoo's single-user plan at approximately £25-£35 per month (Odoo Online, Standard plan). Softomate's insurance broker configuration package starts at £8,000 for a sole trader or micro-broker setup, covering the core modules, ICOBS document templates, and a half-day training session. The total first-year cost including platform fees is therefore significantly lower than any of the dedicated broker management systems.
Yes. Softomate builds and maintains a bi-directional integration between Odoo Invoicing and Xero as part of the standard insurance broker implementation package. Premium invoices raised in Odoo sync to Xero as sales invoices. Commission credit notes sync as purchase invoices. Payment records reconcile against the appropriate ledger. Chart of accounts configuration covers CASS 5 client money segregation requirements. The integration uses Xero's OAuth 2.0 API and runs on a scheduled sync cycle, typically every 15 minutes.
Odoo 19 hosted on Odoo.sh runs in the EU (Ireland) region by default, which is within the UK GDPR adequacy framework following the UK's post-Brexit data bridge arrangements with the EU. For brokers requiring explicit UK-soil hosting - for example, due to PI insurer requirements or Lloyd's market data obligations - Softomate can arrange deployment to a UK-based VPS or dedicated server. All data is encrypted at rest and in transit. A Data Processing Agreement is available from Odoo S.A. on request.
Odoo implementation costs for UK SMEs in 2026 range from £8,000-15,000 for accounting and CRM only (4-6 week timeline) to £20,000-60,000 for full ERP including inventory, manufacturing, and HR (12-20 week timeline). Annual Odoo Enterprise subscription for 10 users with accounting, CRM, and inventory modules costs approximately £7,200-9,600/year. UK implementation partners typically charge £600-900/day. Total first-year cost of ownership for a UK SME deploying Odoo mid-market ERP is £30,000-70,000 including software, implementation, and training.
UK insurance brokers writing £2m-£15m GWP face a clear system choice in 2026: continue paying £15,000-£40,000 per year for platforms built for brokerages ten times their size, or deploy a right-sized Odoo 19 stack configured specifically for ICOBS compliance, Consumer Duty documentation, and renewal automation. Softomate Solutions has delivered Odoo for regulated businesses since 2019. Implementation for a broker of this size costs £8,000-£22,000 and goes live in 8-14 weeks - with FCA compliance mapping included from day one. Contact us to discuss your current system costs and what a transition would look like for your firm.
View our Odoo ERP implementation service or contact Softomate Solutions to book a discovery call.
Rakesh Patel, Softomate Solutions, Barking, East LondonSources:FCA ICOBS Handbook | Odoo 19 Documentation | British Insurance Brokers' Association (BIBA)
More from the blog
Let us help
Talk to our London-based team about how we can build the AI software, automation, or bespoke development tailored to your needs.
Softomate Solutions Limited
Deen Dayal Yadav
Online
