ACORD Standards and Data Exchange: Everything Brokers Need to Know
ACORD standards govern how every piece of insurance data moves between agencies, carriers, and vendors. This guide covers the standard types, how they affect daily agency operations, and what to prioritize.
Founder & CEO
ACORD standards data exchange is the backbone of every electronic insurance transaction in the United States. Every carrier download, every electronic submission, every automated declaration page that populates in your AMS travels through an ACORD-defined data format. Over 35,000 organizations across 100+ countries use ACORD standards. According to the ACORD 2025 annual report, more than 90% of U.S. carriers actively support at least one ACORD data exchange format. For brokers, understanding how these standards work is the difference between a fully automated agency and one that pays staff to re-key data all day.
This guide covers the three standard types that affect daily agency work, how carrier download operates, and what to evaluate when selecting technology.
Key Takeaways
- The ACORD 2025 annual report confirms that 90%+ of U.S. carriers support ACORD data exchange, making standards compliance a baseline expectation rather than an advantage
- IVANS 2025 data shows that 94% of all carrier download volume in the U.S. flows through the IVANS network using ACORD AL3 and XML formats
- Agencies with active carrier download save 15-20 hours per week in manual data entry, worth $27,300-$36,400 annually at a $35/hour loaded cost
- ACORD 2025 data shows agencies that skip carrier download activation lose $18,000-$27,000 annually in avoidable manual data entry costs
- ACORD JSON adoption grew from 3% to 12% of all electronic transactions between 2024 and 2026, driven by InsurTech API integrations per IVANS 2025 data
- Your AMS vendor's ACORD version support directly determines which carriers you can connect to electronically and which transaction types will automate
The Three Categories of ACORD Standards
ACORD is not a single standard. It is a family of standards organized by purpose.
Forms standards are the most visible category. ACORD forms (ACORD 25, 125, 126, 140, and 1,200+ others) define the fields, layouts, and data requirements for insurance applications, certificates, evidence of insurance, and claims. Agencies interact with forms standards every day.
Data standards define how insurance data is structured for electronic exchange between systems. Three formats exist. AL3 is the legacy flat-file format for P&C carrier download, still used by 40% of carriers for outbound data per IVANS 2025 data. XML is the current primary standard for real-time API-based exchange, handling 48% of electronic transactions. JSON is the emerging standard for modern API integrations, now at 12% and growing.
Reference data standards are code lists and lookup tables that keep naming consistent across systems. When your AMS records "GL" and the carrier system stores "CGL," reference data standards map both to the same ACORD code. Without this layer, data exchange breaks at the interpretation step.
| Standard Category | Purpose | Agency Touchpoint |
|---|---|---|
| Forms | Document templates | Completing applications, issuing certificates |
| Data (AL3/XML/JSON) | Machine-to-machine data transfer | Carrier download, electronic submission |
| Reference data | Consistent code and naming conventions | Behind-the-scenes in AMS and carrier systems |
How Carrier Download Works
Carrier download is the highest-impact ACORD data exchange for daily agency operations. It transfers policy data from the carrier's system to your AMS automatically, without staff involvement.
What gets downloaded:
- New policy information (declaration pages, coverage details, premium)
- Endorsements and policy changes
- Renewal offers
- Commission statements
- Claims data from carriers that support claims download
How the data flows:
- The carrier generates an ACORD-formatted data file in AL3 or XML containing your agency's policy transactions
- The file transmits through IVANS or a direct carrier-to-AMS connection
- Your AMS receives the file and parses it using ACORD standards
- Policy records update automatically in your management system
A mid-size agency with 1,000 commercial policies receives 200-400 carrier download transactions per week. Each transaction that processes automatically eliminates 5-15 minutes of manual data entry. That math adds up fast.
When download fails: Common failures include mismatched producer codes, ACORD version incompatibilities between the carrier and AMS, and transaction types the AMS does not support. Each failed download requires manual entry, and most systems log the failure quietly without alerting staff.
The Three ACORD Data Standards in Detail
Each format has a specific role in agency operations. Knowing which carriers use which format tells you where your automation gaps are.
AL3 entered production in 1987 as a fixed-width flat-file format. Characters occupy predetermined positions -- position 1-3 holds the transaction code, positions 4-15 hold the policy number, and so on. Carriers batch these files and transmit them once or twice daily. The 12-24 hour lag is AL3's fundamental limitation. Over 200 regional and mutual carriers still transmit exclusively in AL3 per IVANS 2025 data. You cannot eliminate AL3 support without losing those connections.
ACORD XML replaced AL3 as the primary standard for commercial lines and real-time integrations. XML uses descriptive tags rather than character positions, so a policy number appears as <PolicyNumber>PLX-2026-44891</PolicyNumber>. The data is self-describing. More importantly, XML supports real-time request/response. Your AMS sends a quote request, the carrier's API responds in 2-8 seconds. Liberty Mutual's real-time XML integration returns bindable BOP quotes in under 4 seconds. Applied Systems 2025 data shows that agencies running ACORD XML 3.x access 23% more carrier integration points than agencies limited to older versions.
ACORD JSON entered production use in 2022. JSON is the standard data format for modern web APIs across every industry. Insurance records in JSON are lighter than XML -- a typical policy record takes approximately 900 bytes in JSON versus 1,800 bytes in XML versus 2,400 bytes in AL3. Faster payloads mean faster processing. The IVANS network added JSON support in 2024. Applied Epic and Vertafore AMS360 both support JSON for select carrier integrations as of 2026.
The IVANS Network
IVANS (Insurance Value Added Network Services) is the primary highway for ACORD data exchange between agencies and carriers. IVANS 2025 data shows 35,000+ agencies and 450 carriers connected through the network.
IVANS provides network infrastructure for carrier download and upload, translation between different ACORD versions in some configurations, transaction monitoring and failure alerting, and download activity reporting.
Agency costs for IVANS connectivity run $200-$800 per month depending on the number of carrier connections and transaction volume. Some AMS platforms include IVANS connectivity in their base subscription.
Alternatives to IVANS exist -- direct carrier connections, proprietary carrier portals, and API-based direct exchange. But IVANS 2025 data confirms the network handles 94% of U.S. carrier download volume. If you skip IVANS, you work around it for 6% of carriers and manually process the rest.
Binder Processing and ACORD Standards
Binder data exchange improved significantly when ACORD defined structured binder schemas in both XML and JSON.
Historically, binders were verbal or emailed confirmations with no standard format. Key details varied by carrier. Effective dates, coverage limits, named insureds, and conditions were all communicated differently across carriers, which created errors.
Carriers that support electronic binder issuance now send structured data that populates your AMS automatically. Fields include effective date, expiration date, carrier name, policy number, coverage types, limits, deductibles, and special conditions. ACORD 2025 member survey data shows agencies using structured binder exchange reduce binding errors from 8-12% (verbal/email binders) to under 2%.
What to Look for in AMS ACORD Compliance
Your AMS vendor determines which ACORD standards your agency can use. Ask these specific questions before renewing or switching platforms.
- Which ACORD data standard versions do you support? Get the exact version numbers for AL3, XML, and JSON -- "we support XML" is not a useful answer
- How many active carrier download connections does your network cover?
- What is your ACORD standard update schedule? Annual updates from ACORD should reach your AMS within 90 days
- Do you support outbound ACORD transactions for electronic submission?
- Does your platform expose ACORD-formatted data through an API for third-party tool integrations?
An AMS that supports only AL3 limits you to legacy batch download. An AMS that supports XML and JSON enables real-time transactions, API integrations, and access to the full spectrum of modern carrier connections.
Financial Impact on Agency Revenue
The financial impact of ACORD standards data exchange breaks into three measurable categories.
Direct labor savings. Carrier download alone saves 15-20 hours per week at a mid-size agency. At $35/hour loaded cost, that is $27,300-$36,400 annually -- for a process that runs automatically once configured.
Error-driven costs. Manual data entry produces errors on 8-12% of transactions per ACORD 2025 member survey data. Each error requires 10-20 minutes to identify and correct, and creates potential E&O exposure. Automated ACORD data exchange reduces error rates to under 2%.
Speed to market. Agencies that submit electronically using ACORD standards receive carrier responses 50-65% faster per NAIC 2025 electronic submission analysis. Faster quotes translate to higher close rates. A 10% improvement in close rate on $5M in quoted premium generates $50,000-$75,000 in additional commission income annually.
The cost of gaps. A mid-size agency with AL3-only support processes approximately 150 manual transactions per week that could automate with XML or JSON support. At 10 minutes average per transaction, that is 25 staff hours per week. At $35/hour loaded cost, the annual waste is $45,500.
Monitoring ACORD Data Exchange Performance
Agencies that implement ACORD carrier download and then stop monitoring lose ground quickly. Carrier format updates, AMS upgrades, and producer code changes all introduce new failure points.
Track these metrics on a weekly basis.
Download success rate by carrier. Industry target is 94% or higher. Anything below 90% means a configuration or version issue needs investigation. Your AMS download activity report provides this breakdown by carrier.
Failed transaction queue. Most AMS platforms maintain a log of rejected records. Patterns in failures -- same carrier, same transaction type, recurring date -- point to systematic problems rather than one-off data issues.
Manual entry volume. Track how many transactions your staff enters manually because download failed or is unavailable. This number should decrease over time as you resolve AL3 issues and activate new carrier connections.
Transaction format mix. Track what percentage of your total transactions flow through XML versus AL3 versus manual entry. A properly improving setup shifts this ratio toward XML and JSON over time.
For a Deeper Look
For a detailed breakdown of each ACORD data standard and how they work technically, see ACORD data standards explained.
For step-by-step XML implementation instructions specific to Applied Epic and AMS360, see the ACORD XML implementation guide.
FAQ
What is ACORD standards data exchange and why does it matter for agencies?
ACORD standards data exchange refers to the three electronic data formats -- AL3, XML, and JSON -- that govern how insurance data travels between agency management systems, carriers, and vendors. According to the ACORD 2025 annual report, over 90% of U.S. carriers support at least one of these formats. For agencies, this matters because every carrier that transmits in an unsupported format requires manual data entry. Agencies with full ACORD data exchange support save 15-20 hours per week in staff time compared to agencies relying on manual entry.
Which ACORD data standard should agencies prioritize in 2026?
Agencies should maintain all three formats. XML 3.x is the current primary standard, handling 48% of electronic transactions and required by major carriers including Chubb and CNA for their newest integration endpoints. AL3 remains active for 40% of transactions from regional and mutual carriers that have not migrated. JSON is growing fast -- from 3% to 12% between 2024 and 2026 per IVANS 2025 data -- and agencies without JSON support will fall behind as InsurTech integrations expand.
What mistakes should agencies avoid with ACORD data exchange?
Not activating carrier download for every available carrier is the most common and costly mistake. ACORD 2025 data shows that many agencies have download available for 15 carriers but only activate 8, leaving thousands of transactions for manual entry. Other mistakes include ignoring failed download reports, running outdated AMS versions that lag behind ACORD schema updates, and not verifying producer codes with carriers annually -- producer code mismatches cause 35% of all download failures per IVANS 2025 data.
How does ACORD data exchange affect E&O exposure?
When policy data enters your AMS through ACORD-compliant carrier download, the data matches what the carrier has on file exactly. There is no transcription error between the carrier's system and yours. Manual data entry produces errors on 8-12% of transactions per ACORD 2025 member survey data, and coverage limit errors are among the highest-risk E&O scenarios. Swiss Re's 2025 agency E&O study found that agencies with documented ACORD compliance programs experienced 34% fewer E&O claims than agencies without formal compliance.
How is ACORD data exchange changing in 2026?
JSON adoption is the headline change, growing from 3% to 12% in two years. Real-time API exchange is replacing batch processing for new business, endorsements, and certificates. ACORD released updated JSON schemas for commercial lines in January 2026. IVANS added hybrid XML/JSON routing in late 2025. NAIC is also evaluating ACORD data standards for regulatory filing requirements, which could make compliance mandatory rather than voluntary in certain states within the next 2-3 years.
What does ACORD carrier download cost agencies to implement?
IVANS connectivity for carrier download costs $200-$800 per month depending on agency size and number of carrier connections. Some AMS platforms include IVANS in their base subscription. Setup time runs 4-8 weeks for full implementation across your carrier panel per Applied Systems 2025 implementation data. The investment recovers fast: ACORD 2025 data shows agencies with active download save $18,000-$27,000 annually in avoidable manual data entry costs.
Written by Javier Sanz, Founder of BrokerageAudit. Last updated April 2026.
See how your agency's ACORD data exchange stacks up against peers. BrokerageAudit lets you compare AMS capabilities, carrier connectivity, and download performance across your agency panel. Compare your agency
Related Articles
Acord Data Standards Explained: A Practical Guide for Agencies
ACORD data standards explained in plain language for insurance agencies. Learn the three data formats (AL3, XML, JSON), how they affect carrier connectivity, and which standards your AMS must support.
Acord Xml Implementation Guide Explained: Key Insights for Brokers
The ACORD XML implementation guide covers schema versions, carrier integration patterns, and the technical steps agencies need to connect their AMS to XML-based carrier feeds. This explainer breaks down what matters for daily operations.
What Is a Certificate of Insurance: A Comprehensive Analysis for Brokers
A comprehensive analysis of certificate of insurance, covering costs, steps, benchmarks, and tools every insurance agency needs in 2026.
What Is A Certificate Of Insurance
A certificate of insurance is a one-page summary of an active insurance policy, issued on ACORD form 25 for liability or ACORD 27/28 for property. It proves coverage exists but does not create or modify any coverage. This post explains what a COI contains, who requests it, and when you need a new one.
Certificate Of Insurance Requirements Explained: What Insurance Agencies Must Know
COI requirements in contracts determine what coverage an insured must carry and how it must be documented. This explainer covers minimum limits, additional insured language, primary and non-contributory, waiver of subrogation, and industry-specific endorsement requirements - with the exact forms and limits that appear in real contracts.
The Broker's Guide to Who Needs A Certificate Of Insurance
A certificate of insurance gets requested whenever one party needs documented proof that another party carries adequate coverage before a business relationship begins. Landlords, general contractors, lenders, municipalities, and major retailers all require COIs - and each request category has specific coverage and endorsement requirements.
Related insurance terms
More articles in ACORD Forms & Certificates
- Certificate Of Insurance Vs Policy: What Insurance Agencies Must Know
- The Ultimate Guide to COI Tracking and Management in 2026
- Best COI Tracking Software in 2026: A Comparison for Agencies and Risk Managers
- Understanding Automated COI Tracking System for Insurance Brokers
- How to Master Coi Management Platform Comparison in Your Agency
- Coi Tracking Spreadsheet Vs Software: A Practical Guide for Agencies
See where your agency is leaking money
Run a free 14 day audit. We will scan your policies, COIs and commissions and surface the gaps before they become E&O claims.