Insurance integration

W. R. Berkley EDI and data integration

A guide to exchanging policy, bordereaux, claim and payment data with W. R. Berkley: company facts from its website, what specialty insurers typically exchange, and what to confirm before setup.

Overview

Understanding W. R. Berkley integration

Who this is for: Managing general agents, brokers, wholesalers, administrators, reinsurers and finance teams that exchange data with W. R. Berkley.

W. R. Berkley operates as Berkley, a commercial lines insurer made up of many specialized businesses, each focused on an industry, product or region. Its website is berkley.com. It is also searched for as Berkley.

This page is an integration guide. It does not reproduce W. R. Berkley's specifications. We looked for public EDI or integration documentation from W. R. Berkley and found none we could verify, so this page stays general guidance. Connection requirements usually come from W. R. Berkley itself, through its onboarding team, its companion guides or its partner portal, and they can differ by line of business, program, state and region.

Specialty insurers work through brokers, wholesalers and managing general agents, and exchange policy, premium and loss reports, often called bordereaux, claims data and payments with them and with reinsurers. These move as ACORD data, XML, agreed flat files, spreadsheets or portal uploads, and the layouts differ by program 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 W. R. Berkley's own pages is general practice, not W. R. Berkley's published requirement; confirm each point with W. R. Berkley before you build maps or test.

Workflows

Typical W. R. Berkley business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not W. R. Berkley's published process.

Typical data exchange

  1. 1Agree layouts per program
  2. 2Map policy and loss data
  3. 3Exchange files on schedule
  4. 4Reconcile premium and losses
  5. 5Correct rejected records

Documents and APIs

W. R. Berkley documents by program

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

DocumentNameDirectionProgramStatusPurpose
Bordereaux Premium and loss reports To W. R. Berkley Not stated General guidance Typically reports premium and losses for each program on a regular schedule.
ACORD ACORD policy and agency data Both directions Not stated General guidance Typically carries policy, endorsement and billing data between brokers, agents and the insurer.
Claims Claim files and status Both directions Not stated General guidance Typically carries claim notices, status and payment details between the insurer and its partners.
Payments Premium, commission and claim payments Both directions Not stated General guidance Typically moves as bank files with remittance detail that must match policy and claim records.

Connectivity

How companies connect

  • AS2 or SFTP

    Many insurers and administrators exchange files directly over SFTP or AS2. Confirm which methods W. R. Berkley 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 program

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

  • Specifications by request

    Format specifications usually reach you through the insurer or through ACORD membership rather than a public download, so scoping starts by collecting them.

  • Reconciliation

    Premium, loss and payment records must agree between partners, or the gaps surface as disputes at period end.

  • Confirm the current requirements

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

How ECOM helps

How ECOM can support your W. R. Berkley integration

ERP integration options

ECOM connects the files W. R. Berkley 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 W. R. Berkley 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 W. R. Berkley program

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

  • Review W. R. Berkley's requirements

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

    Request a requirements review
  • Connect W. R. Berkley 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 W. R. Berkley document, then go live with monitoring from the first file.

    Plan testing and certification

Typical requirements

Which W. R. Berkley 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 W. R. Berkley. This guide does not imply approval, certification or a partnership.

Programs, brokers and bordereaux

Specialty business is usually organized by program. Managing general agents and brokers report premium and losses, often as bordereaux, on a schedule agreed for each program. Layouts can differ by program and partner.

Claims and payments

Claim notices and payments are exchanged separately from premium reporting, and payments usually move as bank files that must match the reports.

Regions, states and affiliates

W. R. Berkley 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 W. R. Berkley entity and region applies to you before you build or test.

Typical onboarding checklist

  1. Confirm the entity, program and region you report under.
  2. Ask for the reporting layout, schedule and any validation rules.
  3. Agree how files are delivered and who receives them.
  4. Map your policy and loss data to the layout.
  5. Test with sample files and review rejected records.
  6. Reconcile premium, losses and payments each period.

W. R. Berkley integration FAQs

Which documents or files do partners of W. R. Berkley usually exchange?

Partners of specialty insurers typically exchange premium and loss reports, ACORD policy and agency data, claim files and status, premium, commission and claim payments. That is general practice, not W. R. Berkley's published list; confirm the set with W. R. Berkley.

Where do the requirements for connecting with W. R. Berkley come from?

From W. R. Berkley 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 W. R. Berkley'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 W. R. Berkley and start from there.

What is not covered on this page about W. R. Berkley?

Which documents and file layouts W. R. Berkley accepts, the versions and companion guides it uses, the connection method, the testing steps and any security or compliance requirements were not found in public sources and are not covered on this page.

Can ECOM help connect with W. R. Berkley?

Yes. Once W. R. Berkley 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 W. R. Berkley.

Sources and accuracy

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

Request W. R. Berkley integration assistance

Tell us about your W. R. Berkley program, documents and ERP. We will outline the connection, mapping and testing plan.