Skip to main content

Supported carriers and what we parse

Which carriers Stateable recognizes, how new ones get added, and what to do when a statement isn't matched.

Written by Stateable

Stateable supports the carriers our customers upload most. New formats get added on demand — usually within a few days of the first statement landing in our queue. This article explains what's covered today, what to do when a statement isn't matched, and how to get a new carrier onto the supported list.

How carrier matching works

When you upload a statement, Stateable's first step is Analyzing. It reads the file's text, layout, and tell-tale signs (carrier logos, the words in the header, how the file is named) and checks them against the library of carrier setups we keep. When it finds a match, Stateable knows the exact spot on the page where each field sits and can pull it out.

If nothing in the library matches, the document gets a No Match status. The file is kept safe; nothing is lost. You forward it to Support and we add the carrier.

What we extract

For every supported carrier, Stateable extracts the same set of standard fields where they exist in the source:

  • Carrier, Policy Number, Insured, Producer

  • Effective Date, Expiration Date, Transaction Date

  • Premium, Commissionable Premium, Commission Rate, Commission Amount

  • Transaction Type (new business, renewal, endorsement, cancellation, chargeback, reinstatement)

  • Line of Business (personal auto, homeowners, commercial GL, etc., where the carrier labels it)

Which fields you get depends on the carrier — some statements leave out commission rate, others leave out transaction date. The Data tab shows whatever the carrier put on the statement; anything that wasn't there shows up as an empty cell rather than a guess.

How to find out if your carrier is supported

The fastest check is to upload a real statement. Either:

  • The file reaches Done with rows in the Data tab — supported.

  • The file reaches No Match — not yet supported; we need to add it.

If you're evaluating Stateable before signing up and don't want to send statements through the trial, contact [email protected] with the carrier names — we'll tell you what's already in the library.

When a statement comes back No Match

This is the normal path for a new carrier. Three steps:

  1. Forward the file. Email it to [email protected] with the carrier name in the subject. Don't black anything out — we need the headers and identifying details to teach Stateable the new layout.

  2. We add the new carrier. A straightforward layout usually takes 2–5 business days. Carriers with several different statement formats can take longer; we'll tell you upfront.

  3. We re-run the file. Once the new carrier is set up, your original upload is parsed again on its own and rows appear in the Data tab. Future statements from that carrier follow the same path.

Carriers with multiple statement formats

Many large carriers send a different-looking statement for each product — personal lines and commercial lines may look nothing alike. Stateable keeps a separate setup for each format. If one product line uploads fine and another comes back No Match, that's normal — forward the unmatched file so we can add the second format.

Scanned vs native PDFs

Native PDFs (the kind a computer creates) parse the fastest and most accurately. Scanned PDFs (paper statements run through a scanner) first have to be read by software that turns the picture into actual text; accuracy drops a little and it takes longer — about 1–3 minutes per 10 pages. We handle both, but if you have a choice, ask the carrier for the native version.

What we don't (yet) parse

A few patterns are still on our roadmap:

  • Screenshots of a carrier portal. If a carrier only shows your commissions on a web page and you take a screenshot, the picture is too fuzzy for us to pull clean rows out of. Download the statement from the portal instead.

  • Direct carrier connections. Pulling commissions straight from a carrier's own system, skipping the statement altogether, is something we plan to offer later — it's not part of how Stateable reads files today.

  • Handwritten notes. Anything someone scribbled on a paper statement before scanning it won't end up in the columns.

If your workflow depends on one of these and a workaround isn't obvious, tell Support what you're trying to do — sometimes we can solve it with a carrier-specific tweak.

Get help

Still need a hand? Start a conversation from the Support button in the app, or email [email protected]. We reply within one business day for most tickets.

Related articles

Last reviewed: 2026-05-27

Did this answer your question?