State-by-State Filing Requirements for US Business Entities: The Complete Guide

If you operate, verify, or onboard US business entities, understanding state filing requirements is no longer optional — it's a compliance imperative. Whether you're a fintech underwriter screening merchant applicants, a compliance officer running KYB due diligence, or a legal professional advising clients on entity formation, the patchwork of Secretary of State (SOS) requirements across 50 states, Washington D.C., Puerto Rico, and the U.S. Virgin Islands creates real operational risk. Miss a filing deadline in Delaware, misread a status code from Wyoming, or fail to verify a registered agent in California — and you're exposed.

This guide breaks down what you need to know about state-level filing requirements in 2026, how federal rules like FinCEN's Beneficial Ownership Information (BOI) reporting interact with state records, and how APIs like OpenSOSData can automate the verification layer that manual lookups simply cannot scale. The platform covers all 50 US states, Washington D.C., Puerto Rico, and the U.S. Virgin Islands — over 23 million entities.

Why State Filing Requirements Matter More Than Ever

The regulatory environment tightened considerably with the Corporate Transparency Act (CTA) and FinCEN's BOI rule, which took effect January 1, 2024. While enforcement timelines have been litigated, the underlying compliance expectation is clear: regulated institutions must verify that businesses they onboard are properly registered entities in good standing, and must identify beneficial owners behind those entities.

State SOS records are the foundational layer of that verification. Before you can assess beneficial ownership, OFAC exposure, or BSA risk, you need to confirm the entity actually exists, is active, and matches the information a business applicant provided. This is the core of Know Your Business (KYB) — and it starts with state filing data.

How US Business Entity Filings Work: The Basics

Every US business entity — LLC, corporation, limited partnership, nonprofit, etc. — is registered at the state level. The state of formation (domestic state) holds the primary record, while any state where the business operates but wasn't formed requires a foreign qualification filing. Both matter for compliance purposes.

Key data points held by Secretary of State offices include:

• Entity legal name and any trade/DBA names
• Entity type (LLC, C-Corp, S-Corp, LP, LLP, etc.)
• Entity ID / file number — unique per state
• Status (Active, Good Standing, Dissolved, Revoked, Suspended)
• Formation / registration date
• Registered agent name and address
• Principal office address
• Officers and directors (in states that require disclosure)

Not all states publish the same depth of information, which is why a unified API layer matters enormously for compliance teams working at scale.

State-by-State Filing Requirements: Key Variations by State

The table below summarizes critical filing distinctions across major incorporation states. These are the states most frequently encountered during KYB workflows.

Note: Fees and requirements are subject to legislative changes. Always verify current requirements through the relevant SOS portal or a real-time API lookup.

Federal Overlay: FinCEN BOI, BSA, and KYB Compliance

State filings form the foundation, but federal rules dictate what you must do with that information. Under the Bank Secrecy Act (BSA), financial institutions must implement Customer Due Diligence (CDD) programs that include identifying and verifying legal entity customers. The 2016 FinCEN CDD Rule and its 2024 BOI reporting successor both anchor that verification to state registration records.

Specifically, your KYB workflow should cross-reference:

• State SOS record confirming entity existence and active status
• FinCEN BOI database (for companies subject to CTA reporting)
• OFAC SDN list for entity and beneficial owner screening
• IRS EIN confirmation where applicable

The SOS lookup is step one — and it must happen programmatically at scale if you're onboarding more than a handful of businesses per week. Manual state portal lookups are slow, inconsistent, and not audit-ready.

Common Filing Status Codes and What They Mean for KYB

When you pull a Secretary of State record, the status field is the most compliance-critical data point. Here's how to interpret the most common statuses:

• Active / Good Standing: Entity is current on filings and fees. Generally safe to proceed (subject to other due diligence).
• Delinquent: Annual report or fee is past due. Entity may still operate but is at risk of revocation. Flag for review.
• Revoked / Administratively Dissolved: State has terminated the entity's authority to operate, usually for failure to file or pay fees. High-risk — do not onboard without remediation.
• Voluntarily Dissolved: Owners chose to wind down the entity. Should not be actively conducting business.
• Suspended (California-specific): Entity cannot legally enter contracts or defend lawsuits. Treat as high-risk.
• Merged / Converted: Entity absorbed into or transformed into another entity. Successor entity must be verified separately.

Automating State Verification with the OpenSOSData API

Manual lookups across 50+ state portals are untenable for any compliance program handling real volume. OpenSOSData provides a single REST API endpoint covering all 50 US states, Washington D.C., Puerto Rico, and the U.S. Virgin Islands — returning standardized entity data in milliseconds.

Live lookups start at $0.10 per call (as low as $0.0314 at volume). Cached lookups are available at $0.01 (as low as $0.00314 at volume). Pay-as-you-go — no subscription required. Review full pricing and coverage at the documentation portal.

The example below demonstrates a Python lookup for a Delaware LLC — a common KYB scenario:

import requests

# OpenSOSData API endpoint
API_URL = "https://api.opensosdata.com/v1/lookup"

# Replace with your actual API key from https://app.opensosdata.com
API_KEY = "your_api_key_here"

# Payload: searching for a Delaware entity by name
payload = {
    "state": "DE",                          # Two-letter state code (Delaware)
    "entity_name": "Acme Holdings LLC",     # Legal entity name to search
    "lookup_type": "live"                   # "live" for real-time SOS data; "cached" for $0.01/call
}

headers = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json"
}

response = requests.post(API_URL, json=payload, headers=headers)

if response.status_code == 200:
    data = response.json()

    # Extract key compliance fields
    entity_name   = data.get("entity_name")
    entity_type   = data.get("entity_type")      # e.g., "LLC", "Corporation"
    entity_id     = data.get("entity_id")         # State-assigned file number
    status        = data.get("status")            # e.g., "Active", "Revoked"
    formation_date = data.get("formation_date")   # ISO 8601 date string
    reg_agent     = data.get("registered_agent")  # Registered agent name
    reg_address   = data.get("registered_agent_address")

    # Simple compliance gate: reject non-active entities
    if status.lower() not in ["active", "good standing"]:
        print(f"ALERT: Entity '{entity_name}' has status '{status}' — flag for review.")
    else:
        print(f"VERIFIED: {entity_name} ({entity_type}) | ID: {entity_id}")
        print(f"  Status: {status} | Formed: {formation_date}")
        print(f"  Registered Agent: {reg_agent} at {reg_address}")
else:
    print(f"API Error {response.status_code}: {response.text}")
  

For a full parameter reference including entity ID lookups, bulk queries, and webhook options, visit the OpenSOSData documentation. To get your API key, sign up here — no credit card required to start.

Building a Compliant KYB Workflow in 2026

A defensible KYB program for 2026 should follow this verification sequence:

1. Collect entity details at onboarding — legal name, state of formation, entity type, EIN.
2. Run a live SOS lookup via OpenSOSData to confirm existence, status, and registered agent.
3. Cross-check against BOI records — for reporting companies under the CTA, validate disclosed beneficial owners.
4. Screen against OFAC SDN and consolidated lists — entity name, beneficial owners, registered agent.
5. Assess risk and document findings — retain API response records for audit trail.
6. Set re-verification triggers — annual report deadlines vary by state; schedule status re-checks accordingly.

Frequently Asked Questions

Final Thoughts

State filing requirements in 2026 are more consequential than ever. The convergence of FinCEN's BOI reporting obligations, heightened BSA enforcement, and expanding KYB expectations from banking regulators means that entity verification is now a front-line compliance function — not an afterthought. Building programmatic access to Secretary of State data, standardized across all US jurisdictions, is the only scalable path forward.

OpenSOSData provides that infrastructure at a price point accessible to teams of any size. Whether you're verifying ten entities a month or ten thousand, create your free account and explore the full API documentation to see how quickly you can operationalize compliant business entity verification across every US jurisdiction.