DEV Community

Ava Torres
Ava Torres

Posted on

How Commercial Lenders Verify Borrower Entities Before Closing

Before a commercial lender funds a loan, the credit team needs to verify that the borrowing entity actually exists, is in good standing, and is controlled by who claims to control it.

This sounds trivial. It is not.

Borrowers form LLCs in one state, register in another, and operate in a third. Officers change. Entities dissolve and reform. The Secretary of State portal in each state has a different interface, different search syntax, and different data fields.

For a single loan, a credit analyst might need to verify entities across 3-5 states. For a portfolio lender doing 50 loans a month, that is 150-250 manual SOS searches -- plus SEC checks, UCC searches, and good standing certificate requests.

What lenders actually verify

The pre-closing entity verification checklist typically includes:

  1. Entity existence -- Is the LLC/Corp actually registered where the borrower claims?
  2. Good standing -- Is the entity active, not dissolved, suspended, or administratively revoked?
  3. Officer/member verification -- Do the signing parties match the entity's recorded officers or managing members?
  4. Authorized signatory -- Does the operating agreement or corporate resolution authorize this person to sign?
  5. Foreign registrations -- If the entity operates in a state other than formation, is it registered there?
  6. Related entities -- Are there parent companies, subsidiaries, or guarantor entities that also need verification?
  7. Litigation and liens -- UCC filings, tax liens, judgment liens against the entity

Steps 1-3 and 5-6 can be automated with SOS data. Steps 4 and 7 require additional sources.

The data sources

Secretary of State databases

Every state maintains a business entity database. The critical fields:

  • Entity name and type (LLC, Corp, LP, LLP)
  • Status (active, inactive, dissolved, suspended)
  • Formation date and state of formation
  • Registered agent (name and address)
  • Officers/members/managers (names, sometimes addresses)
  • Annual report filing dates (indicates ongoing compliance)

SEC EDGAR

For borrowers with securities filings:

  • 10-K annual reports list subsidiaries
  • 8-K filings show material changes
  • Beneficial ownership filings (Schedule 13D/13G)

UCC filings

Secured transaction filings show existing liens. A borrower with 15 UCC filings against the same collateral is a different risk profile than one with zero.

Automating entity verification

Instead of manual portal searches, lenders can query SOS databases programmatically:

Input: Entity name + state(s)
Output: {
  entityName: "Acme Holdings LLC",
  status: "Active",
  formationDate: "2019-03-15",
  stateOfFormation: "Delaware",
  registeredAgent: "CT Corporation System",
  officers: [
    { name: "John Smith", title: "Managing Member" },
    { name: "Jane Doe", title: "Member" }
  ],
  lastAnnualReport: "2025-12-01",
  foreignRegistrations: ["California", "New York"]
}
Enter fullscreen mode Exit fullscreen mode

This structured data feeds directly into credit decisioning systems, loan origination software, or compliance checklists.

Multi-state search at scale

For portfolio lenders, the volume economics matter:

Manual approach:

  • 5 minutes per state per entity (optimistic)
  • 3 states average per borrower
  • 50 loans/month = 750 minutes = 12.5 hours of analyst time
  • At $75/hr loaded cost = $937/month just for entity verification

Automated approach:

  • Programmatic SOS queries across states: seconds per entity
  • Structured JSON output feeds directly into LOS
  • Cost: $5-20 per loan depending on scope
  • 50 loans/month = $250-1,000/month

The cost is comparable, but the speed and consistency are transformative. Manual searches miss things. Automated searches with standardized output don't.

Tools for programmatic SOS access

Integration patterns

Most commercial lenders use one of these integration approaches:

Batch verification: Upload a CSV of borrower entities and states, run verification overnight, review exceptions in the morning.

Real-time lookup: Embed API calls in the loan origination workflow. When an analyst enters the borrower entity, automatically pull SOS data and flag discrepancies.

Scheduled monitoring: For existing portfolio, run weekly checks on borrower entity status. Alert if any entity becomes inactive, dissolved, or if officers change.

What to watch for

Common red flags that automated verification catches:

  • Entity was formed less than 90 days before loan application
  • Entity is not in good standing (delinquent annual reports)
  • Officers on the loan docs don't match SOS records
  • Entity is dissolved or suspended in its formation state
  • Multiple recent officer changes
  • Registered agent is a mail drop, not a law firm or CT Corp

These are exactly the flags that get missed when a junior analyst is rushing through 10 manual SOS portal searches at 4pm on a Friday.


Building data automation tools for financial services. More at avabuildsdata on dev.to.

Top comments (0)