Market

Munich reinsurance: DACH treaty, BaFin flavour, and NatCat that is not Florida

Munich is a DACH treaty market: BaFin-flavoured reporting, German and Austrian cedents, and NatCat programmes that are not a London slip with a Bavarian adjective. Reinsured.AI is software for wordings and bordereaux. This page does not invent a German authorisation or a climate-model accuracy figure.

Munich is a treaty city. DACH cedents — German, Austrian, and the Swiss programmes that still talk to Bavarian desks — send automatic capacity, not a daily pile of London facultative MRCs. BaFin supervises German (re)insurance undertakings and flavours the reporting stack, often beside Solvency II. This page uses that flavour. It does not invent a BaFin authorisation for Reinsured.AI, and it does not put us on Königinstrasse as a licensed writer.

Placing customs are relationship and programme, not box and stamp. A German primary insurer renews a 1 January quota share and a per-risk plus cat XoL with a Munich writer, sometimes with a London following market on the same structure. The wording may be German. The broker summary may be English. The English summary loses. Hail, Elbe and Danube flood, and winter storm are the NatCat conversation. They are not Florida wind with a pretzel. The Accumulation Agent is the named worker for zone files, clash, and TIV that must still open the SOV cell — not for inventing a climate score.

Treaty reinsurance is the home hub for quota share, surplus, and XoL administration. Facultative reinsurance appears when a Bavarian plant or an Austrian dam sits outside class. The brokers hub is how that leftover pack should be built. Do not quietly absorb it into the treaty bordereau because the cedent number matched.

BaFin flavour without a fake permission

BaFin expects the undertaking to administer the contract it signed. That is why a placing email that moved the attachment after the wording PDF was circulated is a conflict, not a convenience. Solvency II QRTs, where they apply, are the undertaking's. This product does not file them. The honest connection is cited inputs: share, territory, peril, reinstatement, hours.

German accounting habits leak into ops. A bordereau that follows local booking calendars, or that restates prior quarters after a late close, needs a bridge. If the covering email's total matches a subtotal row in the German sheet and not the grand total, that is a conflict. Flag it. Do not "translate" the sheet into last year's English mapping because the cedent is a long relationship.

Events such as Baden-Baden matter for European follow-through after Monte Carlo. Munich desks live on that calendar. A meeting note is not a signed share.

NatCat that is not a US wind collar

DACH NatCat is flood, hail, convective storm, and winter storm, with earthquake in some Alpine and Rhine contexts. Hours clauses and event definitions still govern. A 72-hour winter-storm clause is not a 168-hour flood clause. If the cat XoL uses one and the per-risk XoL uses another, a single weather week can be two events or one, depending on which wording you open. Show the page.

Zoning files — CRESTA, postal, or a cedent's own flood zone — are documents with as-at dates. A broker heat map without a file date is a chase item. The reinsurance AI hub is the argument against inventing TIV so a map looks complete. Accumulation that cannot open the cell is a story.

The illustration of Munich peril-and-accumulation work, labelled as an illustration and not as customer proof, is the Munich reinsurer climate-risk illustration. It is not a climate-model accuracy claim and not a logo wall.

Documents a Munich treaty desk actually posts

Typical files:

• German or bilingual treaty wordings and endorsements
• Structure charts that must lose to the wording if they disagree
• Subject premium and large-loss listings, often in EUR
• Premium, claims, and commission bordereaux from DACH cedents
• NatCat zoning and SOVs with as-at dates
• Special-acceptance letters for occupancies the treaty excludes
• Association or GDV statistical exhibits as documents, not as a pasted ratio
• Facultative slips when a risk is thrown out of the treaty

Year of account still bites. Premium written in December and reported in January is this treaty or next according to the wording, not according to when the German spreadsheet was emailed. If the inbound file mixes years without a column you can cite, stop.

ACME Construction Ltd in Bavaria

Walk a fictional file. ACME Construction Ltd, domain acme.example, is building a plant outside Augsburg and a riverside warehouse on the Danube in Passau. The 1/1 quota share is EUR, class construction, territory Germany and Austria, flood sublimit in clause 12. The cat XoL attaches at EUR 20,000,000, 72-hour hail and storm, flood as a named peril with a different hours clause in endorsement 2. The SOV codes Passau to a flood zone the broker summary omitted. The covering email says "flood as standard."

Clause 12 and endorsement 2 are the cover. The email is not. The Passau warehouse is a conflict until someone confirms it is inside the sublimit. A Munich underwriter who prices one TIV for Augsburg and Passau has guessed. The pack should show the two hours clauses and the zone cell. Do not average the river into the plant.

This page will not invent a BaFin licence. It will not publish a climate ROI. It will not display carrier logos. Humans still set appetite for hail and flood. Software can cite the German wording, the Danube zone, and the endorsement the English email skipped.