Insurance integration

Munich Re EDI and data integration

A guide to exchanging bordereaux, claim and accounting data with Munich Re: company facts from its website, what reinsurers typically exchange, and what to confirm before setup.

Overview

Understanding Munich Re integration

Who this is for: Insurers that cede business, brokers, managing general agents and finance teams that exchange data with Munich Re.

Munich Re is a global provider of reinsurance, primary insurance and insurance-related risk solutions. Its website is munichre.com. It is also searched for as Munich Reinsurance.

This page is an integration guide. It uses the public pages and documents of Munich Re that are listed under Sources, which we read on November 10, 2026 and summarize in our own words; it does not reproduce them, and no private specification was used. Connection requirements usually come from Munich Re itself, through its onboarding team, its companion guides or its partner portal, and they can differ by line of business, program, state and region.

What Munich Re's own pages say: Munich Re's U.S. non-life client portal offers secure project rooms for real-time electronic data exchange and document management. The page does not say that bordereaux or an EDI standard are exchanged there.

Reinsurers and the insurers that cede business to them exchange premium and loss reports, often called bordereaux, claims data and accounting statements. These move as spreadsheets, agreed flat files, XML or portal uploads, and the layouts differ by treaty and by partner. ECOM can read and integrate ACORD data; the formats and versions a partner uses are confirmed during scoping. Everything on this page that is not attributed to Munich Re's own pages is general practice, not Munich Re's published requirement; confirm each point with Munich Re before you build maps or test.

Workflows

Typical Munich Re business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Munich Re's published process.

Typical data exchange

  1. 1Agree layouts per treaty
  2. 2Map premium and loss data
  3. 3Exchange reports on schedule
  4. 4Reconcile the accounts
  5. 5Correct rejected records

Documents and APIs

Munich Re documents by program

Typical requirements—confirm with your trading partner. We could not verify Munich Re's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Munich Re's confirmed requirements. Confirm the list, versions and programs with Munich Re.

DocumentNameDirectionProgramStatusPurpose
Bordereaux Premium and loss reports To Munich Re Not stated General guidance Typically reports premium and losses ceded under each treaty on a regular schedule.
Claims Claim and loss advice files Both directions Not stated General guidance Typically reports large or notified claims and their progress.
Accounting Accounting statements From Munich Re Not stated General guidance Typically settles balances for each treaty period.
Payments Settlement payments Both directions Not stated General guidance Typically moves as bank files with remittance detail that must match the accounts.

Connectivity

How companies connect

  • AS2 or SFTP

    Many insurers and administrators exchange files directly over SFTP or AS2. Confirm which methods Munich Re accepts.

    General guidance

  • Network or clearinghouse

    Some exchanges run through a value-added network or clearinghouse that translates and routes files to the partner.

    General guidance

  • Portals and APIs

    Some insurers offer partner portals or APIs for enrollment, policy, claims or payment data; access usually requires an account and a login.

    General guidance

Challenges

Common integration challenges

  • A layout per treaty

    Bordereaux and claim files differ by treaty and partner, so one source record is mapped separately for each.

  • Spreadsheets and portals

    Many exchanges still run as spreadsheets and portal uploads, which need validation before they reach accounting systems.

  • Reconciliation

    Premium, loss and settlement records must agree between the cedent and the reinsurer, or the gaps surface as disputes at period end.

  • Confirm the current requirements

    Document sets, versions and delivery rules change, and they come from Munich Re directly, so confirm the current ones before building maps or testing.

How ECOM helps

How ECOM can support your Munich Re integration

ERP integration options

ECOM connects the files Munich Re asks for with your policy administration, claims, benefits and finance systems, so data moves without re-keying and exceptions are shown before a partner reports them.

Visibility and exception management

ECOM can monitor each Munich Re exchange and show late, missing or rejected files and mismatches, so your team can resolve exceptions before they affect payments or coverage.

Next step

Get help with your Munich Re program

Each request goes to an ECOM EDI specialist with Munich Re's name attached, so the reply starts from your program.

  • Review Munich Re's requirements

    Send us Munich Re's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Munich Re to your ERP

    Policy, claim, enrollment, billing and payment data in and out of the policy, claims, benefits and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Munich Re document, then go live with monitoring from the first file.

    Plan testing and certification

Typical requirements

Which Munich Re exchange applies to you

Typical requirements—confirm with your trading partner. This section is general practice for this type of insurer, not requirements published by Munich Re. This guide does not imply approval, certification or a partnership.

Treaties and bordereaux

Reinsurance data is organized by treaty. Cedents send premium and loss reports, often as bordereaux, and receive accounting statements. Layouts differ by treaty and partner.

Claims and settlements

Notified claims and settlement payments are exchanged separately from the reports and must match the accounts.

Regions, states and affiliates

Munich Re may operate through different legal entities, states and regions. Requirements, contacts and connection methods can differ by entity, state, region, line of business and program, so confirm which Munich Re entity and region applies to you before you build or test.

Typical onboarding checklist

  1. Confirm the treaty, entity and region.
  2. Ask for the reporting layout and schedule.
  3. Agree how reports are delivered.
  4. Map your premium and loss data.
  5. Test with sample reports and review rejected records.
  6. Reconcile the accounts each period.

Munich Re integration FAQs

Which documents or files do partners of Munich Re usually exchange?

Partners of reinsurers typically exchange premium and loss reports, claim and loss advice files, accounting statements, settlement payments. That is general practice, not Munich Re's published list; confirm the set with Munich Re.

Where do the requirements for connecting with Munich Re come from?

From Munich Re itself, usually through its onboarding team, companion guides or partner portal. This page does not reproduce them, and they can differ by line of business, program and region.

Do I need Munich Re's implementation guide to start?

No. It helps to share any companion guide or file layout you already have, but if you have none, ECOM can help gather the requirements from Munich Re and start from there.

What does Munich Re publish about EDI and integration?

Munich Re's U.S. non-life client portal offers secure project rooms for real-time electronic data exchange and document management. The page does not say that bordereaux or an EDI standard are exchanged there. Source links are listed on this page; confirm current details with Munich Re.

What is not covered on this page about Munich Re?

Beyond the sources listed on this page, which documents and file layouts Munich Re accepts for your program, the versions it uses, the testing steps and any security or compliance requirements were not reviewed.

Can ECOM help connect with Munich Re?

Yes. Once Munich Re provides its requirements, ECOM can map, test and run the exchanges with your systems. This page is an integration guide and does not indicate a partnership with Munich Re.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Munich Re sets its own requirements and can change them at any time; your Munich Re implementation guide, partner portal or account contact is the authoritative source for your program.

Request Munich Re integration assistance

Tell us about your Munich Re program, documents and ERP. We will outline the connection, mapping and testing plan.