Insurance integration

CNA Financial EDI and data integration

A guide to exchanging policy, billing, commission, claim and payment data with CNA Financial: company facts from its website, what property and casualty insurers typically exchange, and what to confirm before setup.

Overview

Understanding CNA Financial integration

Who this is for: Agencies, brokers, managing general agents, administrators, repair and service vendors, and finance teams that exchange data with CNA Financial.

CNA offers customized business insurance. Its website is cna.com.

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

Property and casualty insurers exchange policy, billing, commission and claim data with agencies, brokers, managing general agents, third-party administrators and service vendors. Much of it runs as ACORD data, XML, agreed flat files or spreadsheets rather than X12, and each insurer implements the formats a little differently. Payments between the parties usually move as bank files. 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 CNA Financial's own pages is general practice, not CNA Financial's published requirement; confirm each point with CNA Financial before you build maps or test.

Workflows

Typical CNA Financial business workflows

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

Typical data exchange

  1. 1Agree formats and delivery
  2. 2Map policy and billing data
  3. 3Exchange files or messages
  4. 4Reconcile payments
  5. 5Correct rejected records

Documents and APIs

CNA Financial documents by program

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

DocumentNameDirectionProgramStatusPurpose
ACORD ACORD policy and agency data Both directions Not stated General guidance Typically carries policy, endorsement, billing and commission data between agencies, brokers 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, administrators and vendors.
Bordereaux Premium and loss reports To CNA Financial Not stated General guidance Typically reports premium and losses for business that an agency or administrator handles on the insurer's behalf.
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 CNA Financial 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 partner

    Each insurer implements ACORD data and agreed files a little differently, so one source record is mapped separately for every partner.

  • 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

    Policy, billing and payment records must agree across the agency, insurer and bank files, or the gaps surface as unmatched payments.

  • Confirm the current requirements

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

How ECOM helps

How ECOM can support your CNA Financial integration

ERP integration options

ECOM connects the files CNA Financial 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 CNA Financial 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 CNA Financial program

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

  • Review CNA Financial's requirements

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

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

    Plan testing and certification

Typical requirements

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

Agency and broker downloads

Agencies and brokers typically receive policy, billing and commission data from the carrier, often as ACORD data or an agreed download from the agency management system, and send new business and changes back. This is separate from claims and from invoices for services.

Claims and vendor exchanges

Claim notices, status and payments move between the carrier, adjusters, administrators and repair or service vendors. Vendors that invoice for their work usually do so through the carrier's own procurement or payment channel; confirm with CNA Financial which channel applies.

Regions, states and affiliates

CNA Financial 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 CNA Financial entity and region applies to you before you build or test.

Typical onboarding checklist

  1. Confirm the legal entity, line of business and region you exchange data with.
  2. Ask for the current file layouts, versions and any companion guide.
  3. Agree the connection method and who receives the files.
  4. Map your policy, billing or claim records to the layout.
  5. Test with sample files and review rejected records.
  6. Plan payments and reconciliation, then monitor from the first live file.

CNA Financial integration FAQs

Which documents or files do partners of CNA Financial usually exchange?

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

Where do the requirements for connecting with CNA Financial come from?

From CNA Financial 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 CNA Financial'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 CNA Financial and start from there.

What is not covered on this page about CNA Financial?

Which documents and file layouts CNA Financial 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 CNA Financial?

Yes. Once CNA Financial 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 CNA Financial.

Sources and accuracy

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

Request CNA Financial integration assistance

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