What Is IVANS and How Do Carrier Downloads Work?

The short version

IVANS is a data-exchange network that sits between insurance carriers and agencies. Carriers publish information about the policies you write with them (new business, renewals, changes, cancellations and in some cases documents) and the network delivers it to your agency management system. That delivery is what agencies call a download. The goal is that a change made at the carrier shows up on your client's record without anyone retyping it. See our glossary for other terms.

What a carrier download can contain

What arrives depends on the carrier and on how the connection was set up. Common categories include:

Policy information: insured details, coverages, limits, premiums and policy periods
Transactions: renewals, endorsements, cancellations and reinstatements
Documents: declarations pages and other policy documents, where the carrier supplies them
Commission information: in some cases, though commission statements often arrive separately

Ask each carrier what they send. Not every carrier supports every category, and some are more complete than others.

How the flow works

The carrier publishes data to the network for the agencies it has activated.
Your agency's connection receives it, using the agency and producer codes the carrier has on file for you.
Your management system imports it and matches each item to an existing client and policy, or flags it as something new.
Someone reviews the exceptions. Anything the system couldn't match goes to a queue for a person to resolve.

How an agency gets downloads set up

Make sure your agency has a network account and that your agency management system can receive downloads. Ask your vendor whether this is supported.
For each carrier, confirm your agency code and the producer codes that are on file with that carrier.
Ask each carrier to activate downloads for your agency and to confirm which categories they will send.
Test with a few policies. Confirm that new activity on a known policy appears where you expect it.

Allow time. Carriers handle these requests on their own schedules, which is why we suggest starting integrations early in your implementation checklist.

Where downloads go wrong

Matching problems. The same insured can appear with a name in a different order, a nickname, a changed policy number at renewal, or a slightly different address. A good system matches on more than one field and shows you the near-matches instead of silently creating duplicates.
Code mismatches. If the carrier has an old agency or producer code on file, data can arrive for the wrong person or not at all.
Gaps in coverage. Some carriers don't send everything. Know which carriers you must still check at the carrier's own portal.
Unreviewed exceptions. A queue nobody works means your records slowly drift away from the carrier's.

Downloads and your other carrier documents

Downloads cover part of the picture, not all of it. Many carriers also let agents retrieve documents from their own portals, and a document harvester can collect those and file them to the correct client. DarkHorse AMS supports IVANS downloads and document harvesting as part of the core platform; the agency management system overview lists what else is included.

How downloads relate to commissions

When policy data and commission statements both reach the same system, matching a commission line to a policy is a lookup. When they don't, you rebuild the link by hand each month. Our guide to reconciling commission statements walks through that process.

A worked example

Imagine a carrier renews a client's auto policy with a new policy number and a changed premium. The renewal arrives through the network overnight. A well-built system looks for the existing policy by more than the number: it considers the insured, the effective dates and the prior number the carrier supplies. If it finds a confident match, it updates the existing record and keeps the history. If it finds a possible match, it places the item in the exceptions queue for a person to confirm, rather than creating a second, duplicate policy. The difference between those two outcomes is why matching quality is worth testing during a demo.

Questions to ask any vendor about downloads

Does your system receive IVANS downloads, and is that included in the price?
How does it match incoming records to existing policies, and what happens to the ones it can't match?
Who sets up the carrier connections, and how long does it usually take?
Can I see the exceptions queue and work it myself?

Put those next to your answers on pricing and migration in the comparison guide. Not sure how your carriers fit? Book a demo and bring your carrier list.

What is IVANS, and how do carrier downloads work?