If you have sat through more than one surplus lines software demo, you have heard "we cover all 50 states" from every vendor in the room. It is a claim that survives the demo and falls apart in month two, because it papers over the question that actually decides how much work your team still does: in which states does the software file, and in which states does a human still have to log into a portal?

Both are legitimate. Neither is a scandal. But they are not the same product experience, and you should know which one you are buying before your renewal, not after.

There is no such thing as a single "surplus lines filing system"

Surplus lines is regulated state by state, and each state chose its own mechanism. What exists today is roughly four different worlds:

  • States with a real machine interface. Texas exposes the SLTX SMART API. California has SLIP. Florida's FSLSO takes a SOAP batch. Illinois has SLAI, Georgia runs OCI SLASuite, North Carolina has NCSLA, New York files through ELANY. Software can transmit directly and get a confirmation number back.
  • Clearinghouse states. A group of states file through the SLIP+ clearinghouse under a shared schema, which is why a vendor that builds one integration can light up several states at once.
  • Portal-only states. The state has an online portal for humans and no public API at all. Kentucky, Minnesota, Nevada, Ohio, Oregon and Washington are in this category. Software can drive that portal, but it is automation on top of a screen, not an interface the state supports.
  • Batch and form states. Arizona wants a monthly Excel form. Indiana wants a monthly NAIC OPTins workbook with an affidavit. South Carolina takes a batch upload behind a login that shows an image CAPTCHA every single time, which is precisely the kind of thing that cannot run unattended no matter what anybody's brochure says.

And then there is everywhere else: the remaining 23 states, plus the District of Columbia, where there is no channel open to a vendor at all. In those jurisdictions the filing is prepared and a person submits it under the broker's own credentials. There is no software on earth that changes that today.

What "automated" should mean when you hear it

A useful test on any demo call, ours included: ask the vendor to name the states where their software transmits the filing and receives the state's confirmation number back without a person touching a portal. Then ask what happens in the other states. A straight answer to both questions tells you more than any coverage map.

The reason this matters is not pedantry. It changes three concrete things:

  1. Where your staff time goes. Direct filing states genuinely disappear from the workload. Portal states become faster but not invisible.
  2. How fast you learn about a rejection. This is the one that costs money, and it deserves its own section below.
  3. Who holds the credentials. In every model, the licence and the portal login stay with the broker. Software files under your authority, never instead of it.

The rejection problem, which is the expensive one

Several states are asynchronous. You submit, the system accepts the upload, and the actual pass or fail arrives later, sometimes days later, sometimes only visible inside a portal nobody re-opens once the filing is marked done. Florida, Georgia and the SLAS clearinghouse states all behave this way.

That means a filing can sit in your system labelled "filed" while the state considers it never received. You find out at the deadline, or during an audit, or when a penalty notice arrives. The gap between "we sent it" and "they accepted it" is where surplus lines compliance actually goes wrong.

Here is a real example of what that looks like from the inside. On 1 July 2026, FSLSO retired batch schema version 2.3. Filings built to the old schema started failing validation. The failure is not loud: the submission goes out, and the rejection comes back later as a schema validation error inside the response. If nothing is watching for that, a month of Florida filings quietly are not filings. We shipped the v2.4 cutover the same day because a rejected filing surfaced as an error in front of a person, not as a silent status.

So when you evaluate any platform, ask what it does between submitting and confirming. "We submit to the state" is half a product. The half that matters is what happens when the state says no.

How SLTax360 handles each category

We publish our own map rather than rounding it up to fifty, because a compliance buyer who catches an overclaim is right never to trust the rest of the pitch.

  • Direct electronic filing, 23 states. Seventeen through state APIs (Texas, California, Illinois, Utah, Florida, Georgia, North Carolina, New York, and the SLIP+ states Alabama, Colorado, Kansas, Louisiana, Montana, Oklahoma, South Dakota, Tennessee and Wyoming), plus portal automation in Kentucky, Minnesota, Nevada, Ohio, Oregon and Washington. Confirmation numbers land back in the platform automatically and rejections are re-checked every minute.
  • Generated state files, 4 states. Arizona's monthly form, Indiana's OPTins workbook, South Carolina's batch upload, and Pennsylvania's PASLA EFS route which is built but not yet activated. The platform produces the file the state wants; submission happens in your portal account.
  • Prepared filings, everywhere else including DC. Rates, rules, deadlines, the report itself, the confirmation and the payment record all live in the platform. The submission is made through your own portal account, by your team or by ours depending on plan.

Each state page states which of these applies to that state, including the ones where the honest answer is "we prepare it, you file it."

The part that is the same in all 51 jurisdictions

Filing is the visible step, but it is not most of the work. What actually eats the month is everything around it:

  • Getting the tax and fee math right, including which fees are inside the taxable base in that particular state, and which rate was in force on the transaction's effective date rather than today.
  • Knowing what is due, in which state, on which day, and what is still outstanding.
  • Being able to produce the filing, the payload, the state's response and the confirmation number when an auditor or stamping office asks eighteen months later.
  • Knowing whether the tax you filed was actually paid, because a filed-but-unfunded obligation still becomes a penalty.

That layer is uniform across all 50 states and DC, and it is the part that turns a filing tool into a compliance system of record. Direct filing is a labour saving on top of it, state by state, wherever the regulator makes it possible.

Three questions worth asking any vendor

  1. Which states do you transmit to directly, and which do your staff key into a portal? Ask for the list, not the number.
  2. What happens between submission and confirmation, and how quickly would I know that a Florida or Georgia filing had been rejected?
  3. If a state changes its schema or its rate mid-year, how do I find out, and how did you handle the last time it happened?

You can check our arithmetic before you ever talk to us: the public tax calculator is free, needs no account, and runs the same rate engine we file with. If the numbers match what your stamping office invoices, that is a better reference than anything we could say about ourselves.