How to run an insurance brokerage on Odoo.

An insurance brokerage does not really sell policies. It sells a renewal book — the accumulated trust of clients who come back every year, and the commission stream that follows them. Walk into most brokerages across the UAE and GCC, though, and that asset lives in a spreadsheet, updated by whoever remembered to update it last. Renewals surface the week a policy lapses, sometimes the week after, when a client calls asking why their cover has stopped. Commissions get booked when someone remembers to book them, and reconciled against the insurer's statement almost never, so nobody can say with real confidence whether what was paid matches what was actually owed.

The rest of the file is just as scattered. Policy documents live across three inboxes and whichever laptop last handled the renewal. Claims follow-up depends on one coordinator's memory of who promised what and by when, and when that person is on leave, the claim simply waits. Receivables age quietly on both sides of the desk at once: clients who have not paid their premium, and insurers who have not paid the commission due on it. And when it comes time to assemble the reporting your regulator expects, someone spends a week piecing it together from whatever records survived the year, instead of pulling it from a system built to hold the answer already. None of this is fixed by hiring another coordinator. It is fixed by making the policy, not the inbox, the centre of the business.

What standard Odoo gives you — and where it needs shaping

Odoo's CRM, invoicing, and accounting are solid raw material for a brokerage: pipelines for new business, recurring invoicing, multi-currency accounting, and real financial reporting all come standard. That is enough for an adviser writing a handful of policies a year, tracked by memory and a diary. It is not enough for a brokerage renewing hundreds of policies across a dozen insurers. Standard Odoo has no concept of a policy as an object with its own renewal clock, no commission logic that knows an insurer pays a different rate for motor than for medical, and no workflow that keeps the premium a client owes separate from the commission an insurer owes back. That shaping — the policy record, its renewal clock, and its commission logic — is what we configure for the insurance brokerages we work with across the UAE and GCC.

The workflow: from quote slip to renewed policy

• 1. Enquiry becomes quote slips, compared side by side. A new enquiry, or an upcoming renewal, goes out to the insurers on your panel as quote slips, and the terms come back to sit against each other on one screen — premium, terms, and commission rate — instead of three tabs and a notepad.
• 2. Policy issued and registered, with its commission terms attached. Once terms are accepted, the policy record captures the client, the insurer, the line of business, the sum insured, and the commission rate agreed for that policy — and the signed schedule and supporting documents attach to the record itself, so the next renewal or claim is a lookup, not a search through old emails.
• 3. Premium invoiced, collection and insurer remittance tracked apart. The client is invoiced for premium and payment is tracked to collection. Separately, what you owe the insurer, or what the insurer owes you, depending on the paper, is tracked on its own schedule, so the two never blur into one unclear balance.
• 4. Endorsements recorded against the policy, not a side email. A change in sum insured, a vehicle added to a fleet policy, a new staff member added to a medical scheme — each endorsement is logged against the policy record with its own effective date and premium adjustment, so the file always matches what is actually covered.
• 5. Claims logged and chased, with status visible to the whole client team. A claim is logged against the policy the day it is reported, with the insurer's reference, its current status, and the next action due — visible to whoever is on the desk that day, not locked in one coordinator's inbox or memory.
• 6. Renewal surfaces 90 days out, and moves through a pipeline. Every policy's renewal date drives a pipeline with stages at 90, 60, and 30 days out, each one triggering a reminder to the client team by WhatsApp or email, so the renewal quote goes out while there is still room to negotiate, not the week the old policy lapses.
• 7. Commission statements reconciled line by line. When an insurer's statement arrives, it is checked policy by policy against what the system says is owed, so a short payment or a missing line is a query raised that week, not a gap absorbed quietly into the year-end numbers.

What management finally sees

Because every quote, policy, and claim sits on one system, a principal sees renewal retention rate by month, not a guess offered at a partner meeting. Commission receivable by insurer shows exactly who is late paying what they owe. Production by line of business and by producer shows who is actually writing profitable business, not just busy business. And claims ageing shows which files have gone quiet and need a call today, not next month. With our AI Connector, a principal can just ask: "which policies renew next month, and who owns them?" — and get the answer from live data, not a scramble through the diary.

How we implement it

We start with your existing policy register, however it lives today — a spreadsheet, an old system, a filing cabinet of renewal notices — and configure the policy record, the renewal pipeline, and the commission logic around your actual panel of insurers and lines of business, not a generic template. Commission rates per insurer and per product are set up before go-live, so reconciliation works from day one instead of being fixed after the fact. Most brokerages go live in six to ten weeks. And it comes with our guarantee: you see the system running on your own book of business before you pay, and if we miss the date we agreed, you walk away.