Market

Dubai reinsurance: DIFC desks, DFSA flavour, and GCC facultative packs

Dubai's reinsurance conversation often sits in the DIFC under DFSA rules, with GCC facultative packs in USD or AED. This page does not invent a DFSA licence for Reinsured.AI. The ops work is tower SOVs, heat and flood schedules, and slips that still have to match the certificate.

Dubai's distinctive market is the Dubai International Financial Centre, not a generic "Middle East hub" label. DIFC firms sit under the Dubai Financial Services Authority on a common-law framework. Onshore UAE insurance sits on a different statutory path. Abu Dhabi's ADGM is a third address book. This page is DIFC-flavoured. It does not invent a DFSA licence for Reinsured.AI, and it does not put us in a Gate Village office as a licensed intermediary.

Placing customs are facultative-heavy for construction, energy, and towers, with treaty programmes sitting behind regional cedents. Brokers in the DIFC offer GCC and wider MENA risks to London, Bermuda, and Singapore following markets, often in USD, sometimes in AED. A slip that says "UAE" when the SOV is a single Dubai Marina tower is either sloppy territory or a different programme. The Triage Agent is the named worker for inbound packs that must be sorted before an underwriter spends an hour on a file that is still missing the hours clause.

Facultative reinsurance is the home hub for those tower packs. Treaty reinsurance is the automatic cover when a regional insurer cedes a class, not a building. The brokers hub is how the zip should look before it is forwarded from DIFC to EC3. Do not send two versions — one before the Abu Dhabi site was added, one after — and call them one placement.

DIFC is not onshore, and onshore is not ADGM

Ops failures start with the letterhead. A DFSA-authorised intermediary places a facultative slip. The original policy is onshore. The reinsurance certificate uses a DIFC governing-law clause. None of that is illegal on this page; it is three documents that must agree on named insured, period, and interest. If they do not, the claim will be argued in two systems.

Sanctions, vessel, and country screens appear more often on MENA packs than on a Munich hail treaty. Those screens are documents or system outputs you can store. Software should not invent a clearance date to make a completeness ring look green. The reinsurance AI hub is the rule: a field without a span is a gap.

Events still sit on the 1/1 calendar for treaty. DIFC facultative is continuous. A Monte Carlo badge does not bind a Sheikh Zayed Road tower.

Documents a DIFC desk actually files

Typical files:

• Facultative slips in English, USD or AED
• Project SOVs for towers, infrastructure, and energy, with values that can be summed
• Loss runs with as-at dates; undated regional runs are chase items
• Wording excerpts: occupancy, political violence, flood, heat, defective-design exclusions
• Onshore policy jackets that must be joined to the reinsurance slip, not assumed
• Treaty wordings and bordereaux when the DIFC writer is a carrier, not only a broker
• DFSA or DIFC registrar exhibits as documents to extract from, not as filings we submit

Heat and flood are not decorative. A Marina basement and a desert labour camp are different occupancies. If the slip says contractors all risks and the SOV includes a completed tower awaiting handover, you have a period and occupancy conflict. Do not average them into one TIV.

Energy and wet-risk facultative sits in the same DIFC inbox as towers. A marine warranty survey, a wells schedule, or a pipeline alignment sheet is a document. It is not a construction SOV with a desert filter. If the slip occupancy is contractors all risks and the attachment is a drilling programme, stop. That is a different class, a different following market, and a different certificate.

Political violence and terrorism are manuscript more often than in a Toronto condo file. If the clause is missing, it is a chase item. A fluent summary that says "PV as usual" is not a field. Currency conversion between AED slip figures and USD following lines needs a cited rate as-at, not a breakfast print from the DIFC gate.

ACME Construction Ltd on Sheikh Zayed Road

Walk a fictional file. ACME Construction Ltd, domain acme.example, is building a mixed-use tower off Sheikh Zayed Road and a labour camp in Jebel Ali. The DIFC-placed facultative slip names ACME Construction Ltd, interest CAR, period 1 March 2026 to 28 February 2027, limit USD 80,000,000 any one occurrence, deductible USD 2,000,000. The onshore policy names ACME Construction LLC, UAE. The SOV adds an Abu Dhabi fit-out that is not on the slip. The loss run has no as-at. The hours clause is missing. The covering email says "UAE-wide."

That is a name conflict, a territory conflict, a stale history, and a missing hours clause. A following market in London who quotes UAE-wide TIV has guessed. The pack should list four chase items and keep ACME Ltd and ACME LLC visible. Do not clean the name to match a policy admin system.

The illustration of Dubai regional-file work, labelled as an illustration and not as customer proof, is the Dubai reinsurer emerging-markets illustration. It is not a DFSA letter and not a logo wall.

This page will not invent a DFSA or onshore UAE licence. It will not publish a GCC ROI. It will not display carrier logos. Humans still write the line. Software can cite the DIFC slip, the onshore jacket, and the Abu Dhabi site that never made the interest.