State filing

An eligible surplus-lines policy booking is reported to the insured’s home state: new business or renewal, each premium-bearing endorsement, and a cancellation return. The policy needs a home state. Underflow files through the InsCipher feed and keeps one filing record per eligible booking, so the compliance register and the file agree on what the state has been told.

​

What gets filed

Each eligible booking creates a filing keyed on its ledger row, so a booking that re-runs never files twice: Ledger reversals, including a reinstatement reversal, do not create a state filing. A cancellation with no unearned premium creates no return row and therefore no filing. The filing carries the figures the booking used: premium, agency fee, and each tax and fee line as the state titles it. The feed checks those against its own engine and flags a mismatch rather than accepting it silently.

​

How a filing moves

When InsCipher is configured, filings are queued after the booking and sent in the background. Without credentials, the filing remains Pending. Each one shows where it sits:

• Pending: waiting to send, or back in the queue after a failure the feed or the network caused.
• Submitted: with the feed, which shows its own word for the stage (saved, submitted, flagged, in the e-file queue).
• Filed: the state has accepted it, with the date filed and, where the state issues one, the SLA transaction number.
• Failed: the feed refused it, with the reason on the record. Fix the file, then retry from the policy.

The feed reports back two ways. Its webhooks land the filed status, the SLA or countersignature number, and the dates each tax was paid to the state. A daily sweep asks after every filing still with the feed and sends anything that was waiting. On the file, Check status is available for a Submitted filing that has an InsCipher transaction ID. A Failed or attempted Pending filing offers Retry instead.

​

Paper on the filing

Stamping offices file on the policy paper, not only the figures. Once the opening filing is with the feed, Underflow attaches the desk’s paper to it:

• The binder, after bind
• The declarations page, after issue
• Each signed state form, under the state’s code for it, when its condition is received with the signed copy

Each document is answered for on its own. A document the feed saved shows as saved on the filing; one it turned away shows the feed’s reason, and stays put until a person sends it again. A document under a code the feed does not know is kept on the transaction as an attachment but left out of the state filing until it is mapped in the feed’s portal. Paper the state sends back (a stamped declarations page, for instance) appears on the filing with a link to it.

​

Where to look

On a file, the State filings block lists every filing on the file’s policies with its figures, its stage, the SLA number, and the paper with the feed. Failed filings offer a retry; submitted filings offer a status check and a paper resend. Under Accounting > State filings, the compliance register lists every filing on the desk, newest first, beside the carrier bordereaux.