Executive Summary: When the same business name appears as a domestic entity in two states, the lender is looking at two legal persons, not one borrower with two registrations. Identify the borrower by state of organization and entity number, never by name, and have the borrower confirm that pairing in writing before loan documents are drawn. This guide shows underwriting and closing leads how to enumerate every candidate, reconcile each one against the loan file, and lock the result.
Why Can the Same Business Name Exist as a Domestic Entity in Two States?
What does a state name rule actually check?
Florida requires an LLC name to be distinguishable in the records of its Department of State from the names of other entities on file there, and it lists the differences that do not count: a suffix, an article, "and" versus an ampersand, a plural, or a punctuation mark.[1] Delaware requires a name that distinguishes the company upon the records in the office of its Secretary of State from names already on those records.[2]
Neither rule looks at another state's records, so one owner can form the same name in two states and each filing stands on its own.
Why does a shared owner not make the two entities one borrower?
The Uniform Commercial Code defines a registered organization as one organized solely under the law of a single state, in the usual case by filing a public organic record with that state.[3] Two filings in two states therefore produce two organizations, even when the same individual signed both.
So "same name plus same person" describes two candidates, not one identifier, and no registry can say which one is borrowing.
What does a same-name conflict look like in a loan file?
Take a file where the application says the borrower is an Ohio limited liability company, the formation documents show a Georgia limited liability company, and both states have a domestic LLC under the same name with the same individual on both records. The file is hypothetical, and later sections return to it.
Only the borrower can say which of the two registrations is signing, so the question goes back to the borrower in writing.
Which Facts Identify a Borrower Entity When the Names Match?
Why is the state of organization plus the entity number the primary key?
The UCC's jurisdiction of organization is the jurisdiction under whose law the organization is formed,[3] and that state's registry assigns the entity number. Cobalt's help center describes sosId as the official registration number assigned by the state Secretary of State, unique within that jurisdiction.[4] State plus number is unique nationally in a way the name is not.
What does the EIN add, and where does it stop?
The IRS states that a business entity should have only one EIN and that an LLC needs one to operate.[5] Two LLCs formed under two states' laws are two entities, so in the ordinary case they carry two EINs and the EIN on the application points at one of them. The documented exception is a single-member LLC that has not elected corporate or S corporation taxation, has no employees, and owes no excise tax, which may use its owner's sole proprietor EIN.[6] There the EIN follows the person, not the filing, and cannot separate two same-name single-member LLCs with the same owner.
IRS TIN Matching lets payers validate TIN and name combinations before submitting an information return.[7] Cobalt's TIN verification takes the EIN and business name together and returns a match status with the IRS code and reason, but no state registration fields.[8] Cobalt's help center describes the IRS test two ways: an exact match on the legal name, suffix included,[9] and a name control, usually the first four characters, under which similar names can both match one EIN.[10] Identical names pass either test, so a match cannot say which state's entity holds the EIN. When the TIN name and the state record disagree, use the escalation workflow for TIN and Secretary of State name conflicts; when they agree, tie the EIN to a state and entity number with another document.
Treat a TIN result as a data-quality check on the name and EIN pairing. The regulation on the TIN matching program, 26 CFR 31.3406(j)-1(c), reads: "The provisions of section 3406(f), relating to confidentiality of information, apply to any matching details received by a payor through the matching program. A payor may not take into account any such matching details in determining whether to open or close an account with a payee."[11] Ask your compliance team whether and how TIN results may be used in underwriting.
What do the formation documents and the signature block contribute?
The articles of organization or certificate of formation are the initial filing in the company's public organic record, which also includes any record filed with or issued by the state that amends or restates them.[3] A filed copy shows which state accepted the filing and, where the state printed one, the entity number. Those two facts identify one candidate. The operating agreement shows who can bind the company, which decides who signs, not which entity signs. A deed or purchase contract that names the grantee with a state qualifier, such as "a Georgia limited liability company," gives a stronger identity signal than the name in front of it.
Record the name exactly as the state shows it, punctuation and suffix included. If the application shows a trade name, resolve that first with the DBA versus legal entity workflow.
How Do You Enumerate Every Candidate Before Choosing One?
Which states have to be searched?
Search at least four places: the state the lender named on intake, the state named on the formation documents, the property state, and any state in the addresses the borrower supplied. When those sources disagree, or when a same-name entity could sit in a state nobody named, search every state.
In Florida, property-state registration is not optional for a rental. A foreign LLC may not transact business there until it obtains a certificate of authority,[12] and owning income-producing real property in the state is transacting business, while owning property "without more" is not.[13] A home-state LLC that owns a Florida rental should therefore appear in Florida's records as a foreign registration; if the only Florida record under the name is a domestic Florida LLC, the reviewer has found a second candidate. Each state writes its own rule, so check the property state's statute.
How do you tell a second domestic entity from a foreign registration of the first?
Cobalt's help center explains that stateOfFormation indicates the business's home state, where it was originally incorporated, and stateOfSosRegistration shows where it is currently registered to do business.[14] Where the two differ, the record is likely a foreign registration, and some states also label entityType as "Foreign."[15]
In the Ohio and Georgia case, a Georgia record showing Ohio as its formation state is the same legal person registered in a second state, and there is one candidate. A Georgia record showing Georgia as its formation state or a domestic entity type is a second candidate, and the same-name review begins. The foreign qualification and multi-state registration guide covers one entity registered in several states; this guide covers two entities.
What should the candidate table capture?
Build one row per candidate from every state searched.
• State and entity number. The jurisdiction of organization and the sosId the state assigned.[4]
• Exact registered name. The name as the state shows it, including the punctuation and suffix that a name rule such as Florida's ignores.[1]
• Entity type and formation state. The entityType value where the state returns one, since not every state does,[16] and the stateOfFormation value that separates a domestic entity from a foreign registration.[14]
• Filing date and status. The state's filing date and status wording, with Cobalt's normalizedStatus beside it.[17]
• Registered agent and officers. The agent for service of process and any officers listed in the filings.[18] Cobalt's help center says nearly all states publish agent details,[19] while officer data depends on the state.
• Addresses. The physical and mailing addresses the state holds.
• Source record and capture. The state's record URL, the screenshot if requested, and the search input that produced the hit.[20]
The lender will need this table if the borrower later disputes which entity signed.
How Do You Reconcile the Candidates Against the Loan File?
Which document goes against which field?
Reconciliation is a field-by-field comparison. The application's legal name and state go against the table's name and formation state. The formation documents' state and entity number go against state and sosId. The EIN confirmation or W-9 name goes against the registered name, subject to the single-member exception. The deed or purchase contract's grantee and state qualifier go against the candidate that will hold title. The operating agreement's members and managers go against the officers or organizer the state shows, where it shows any.
A pair that matches both candidates, such as the owner's name, carries no weight. A pair that matches neither, such as an entity number found in no searched state, means another state must be searched.
What must the borrower confirm in writing?
Put the question to the borrower in a signed statement: which entity is borrowing, identified by state of organization and entity number, and that the same entity holds or will take title to the collateral. A manager's or member's certificate that names the entity the same way, attaches the formation documents, and states who is authorized to sign closes the loop.
A phone answer of "they are the same company" is a business description, not a legal one. If the borrower wants the other same-name entity to guarantee the loan or hold title, that entity is a separate party with its own review, identifiers, and signature block.
What if the documents point to different entities?
Stop and treat the file as an open identity question, not a clerical mismatch. The cause may be ordinary: an owner who formed a new LLC in the property state instead of registering the home-state LLC, a name and state copied from an earlier deal, or a plan to take title in one entity and apply in the other. None is fraud, but each binds the wrong party if the reviewer guesses.
Do not resolve the conflict by filing date, by status, or by which record intake found first. Resolve it by asking the borrower in writing and aligning the deed, the note, the security instrument, and the guaranty to that answer. The alternative-match review before funding covers the within-state version, where several records in one registry look right; the cross-state version is harder, because the names can be identical and the same person can stand behind both records.
What Breaks When the Wrong Entity Is Named in the Documents?
Why does the UCC-1 fail if the debtor name belongs to the other entity?
UCC 9-503(a)(1) sets the debtor-name rule for a registered organization.[21]
"A financing statement sufficiently provides the name of the debtor: (1) except as otherwise provided in paragraph (3), if the debtor is a registered organization, or the collateral is held in a trust that is a registered organization, only if the financing statement provides the name that is stated to be the registered organization’s name on the public organic record of [sic] most recently filed with or issued or enacted by the registered organization’s jurisdiction of organization which purports to state, amend, or restate the registered organization’s name"
Two consequences follow. The first is location: while a debtor is located in a state, that state's law generally governs perfection,[22] and a registered organization organized under a state's law is located in that state,[23] so a financing statement for the Georgia borrower filed in Ohio sits in the wrong office, whatever name it carries. The second is spelling: if the records differ by a suffix or a comma, a statement that copies the wrong record's spelling fails to provide the debtor's name and is seriously misleading unless the filing office's standard search logic under the correct name would still find it.[24] Either way the filing describes a stranger to the loan.
Why does a security interest not attach to property the named entity does not own?
A security interest is enforceable only if value has been given, the debtor has rights in the collateral or the power to transfer them, and, in the usual case, the debtor has authenticated a security agreement that describes the collateral.[25] If the Ohio LLC signs the security agreement but the Georgia LLC owns the equipment or the accounts, nothing attaches. The same logic governs a mortgage or deed of trust: the instrument must be granted by the entity that holds record title, and a same-name entity from another state is a non-owner.
Naming the wrong entity leaves the lender with a note from a company that does not own the collateral and no enforceable lien on the collateral itself. Common ownership repairs neither half.
None of this is specific to real estate. Article 9 also applies to a sale of accounts,[26] so a merchant cash advance funder that buys receivables and files a UCC-1 meets the same name and location rules as an equipment or working-capital lender.
Which Same-Name Patterns Are Routine, and Which Should Raise the Review Level?
What are the ordinary explanations?
A same-name pair can have an innocent explanation. An investor may form one holding LLC per state and reuse a brand name. An owner who moves may form a new entity in the new state rather than registering the old one. The review need not explain why both exist, only which one is borrowing, which one owns the collateral, and why the other was excluded.
Which signals should raise the level?
These observations should move the file to a second reviewer or to counsel.
• Recent formation in the property state. A same-name domestic entity formed in the property state within weeks of the application, while the file's formation documents are older and from another state.
• Different people on the records. An agent, organizer, or officer on one record who appears nowhere in the loan file.
• Status conflict. One candidate inactive, dissolved, or delinquent while the application describes an active company.
• Name drift. Names that differ only by a suffix, an article, or punctuation, which Florida's name rule does not count as distinguishing,[1] but which the application and the deed spell differently.
• Title in the other entity. A deed or contract whose grantee carries the other state's qualifier.
None proves misconduct; each means the identity question is still open.
How should the excluded record be documented?
Keep the excluded candidate in the file with the reason, the date, the reviewer, and the state record as captured. Do not delete it. If the borrower later argues that the other entity was the real party, or a workout raises the question, the file should show that the lender saw both entities, asked, and received a written answer.
How Can an Underwriting Workflow Automate the Enumeration Without Automating the Decision?
By hand, this works at low volume and strains as volume grows, because each state site has its own search rules, field set, and way of expressing the entity number. The alternatives fall into three groups: secondary-source aggregators that compile registry data on their own refresh cycle, full-service verification platforms that bundle decisioning with data, and a direct Secretary of State data API that returns the state record and leaves the decision with the lender. Cobalt is the third kind. The Top 34 questions about the Secretary of State API cover its general behavior; the fields that matter here are narrower.
Which SOS API calls and fields describe each candidate?
A state-specific search takes a business name, an entity number as sosId, or a person's name, plus a required state,[17] so each state on the list is one request. The help center calls it the faster mode when the registration state is known, and describes full verification as a sweep of all 51 jurisdictions that needs only the business name.[27] The help center adds that full verification returns all registrations found, consolidated in one response.[28] In the API reference, the request also accepts a person's name, returns a searchGuid for checking progress, and can send the results to a callback URL once every available state has run.[29]
Use full verification when intake, the documents, and the addresses disagree on a state, or to look for a same-name entity nobody named. Use state-specific searches for the states on the list. The API reference documents sosId as a general search input,[17] but Cobalt's public feature-support spreadsheet marks searchBySosId for Florida and Mississippi only, which leaves out Ohio and Georgia. Search by sosId only in a state where you have confirmed that ID search works, such as one the spreadsheet marks; elsewhere, search by the exact registered name and check the returned sosId against the number on the documents. The searchByPersonFirstName and searchByPersonLastName parameters[17] run a principal's name where the state supports it.[30]
Close matches from a state-specific search come back in an alternatives array of up to about ten records, limited to the state searched,[31] so an Ohio alternatives list will never contain the Georgia entity. The API reference names the array by outcome: a response that returns a record carries possibleAlternatives, and a response with no exact match carries alternativeResults.[17] Cobalt's help center says each candidate also carries a confidenceLevel and an address-match flag.[32] It adds that when a request includes no address, alternatives come back with only what the search page shows, names and URLs, while a request with an address gets fuller details such as status, filing number, and date.[33] Cobalt also publishes a downloadable spreadsheet of which states return which fields, the place to check before a workflow assumes officer or formation-state data for a given state.[34] For Ohio and Georgia, Cobalt's sources disagree. The spreadsheet marks stateOfFormation for Georgia but not Ohio, while Cobalt's own measurement on September 11, 2026, described below, found the field in both Ohio probes that returned a record and in none of the three Georgia probes, where entityType read "Foreign Profit Corporation." Where the field is missing, check entityType for a foreign label and take the home state from the formation documents.
What does a customer-owned candidate record look like?
The record below is illustrative and lender-owned, not a Cobalt API response, and adds no fields to Cobalt's schema. It stores two candidates beside the reviewer's reconciliation.
{
"record_type": "lender_same_name_reconciliation",
"loan_file": "LF-EXAMPLE-0000001",
"application_legal_name": "Example Property Holdings LLC",
"application_state": "OH",
"candidates": [
{
"candidate_id": "cand-oh",
"state": "OH",
"sosId": "OH-EXAMPLE-0000001",
"title": "EXAMPLE PROPERTY HOLDINGS LLC",
"entityType": "Domestic Limited Liability Company",
"filingDate": "2019-04-02",
"normalizedStatus": "Active"
},
{
"candidate_id": "cand-ga",
"state": "GA",
"sosId": "GA-EXAMPLE-0000001",
"title": "EXAMPLE PROPERTY HOLDINGS LLC",
"entityType": "Domestic Limited Liability Company",
"filingDate": "2024-11-18",
"normalizedStatus": "Active"
}
],
"reconciliation": {
"formation_documents": {"state": "GA", "entity_number": "GA-EXAMPLE-0000001"},
"vesting_deed_qualifier": "a Georgia limited liability company",
"borrower_written_confirmation": {"received": true, "state": "GA", "entity_number": "GA-EXAMPLE-0000001"},
"resolved_borrower": "cand-ga",
"excluded": [{"candidate_id": "cand-oh", "reason": "not named in formation documents, deed, or borrower confirmation"}],
"status": "resolved",
"reviewed_at": "2026-09-24T15:10:00Z"
}
}The API can fill candidates; only the lender can fill reconciliation, and resolved_borrower is a human decision recorded against evidence, not a computed field.
What can the SOS data not settle, and what must the lender own?
Cobalt is a data source, not a decisioning engine, and the boundary is sharpest here. Secretary of State data cannot establish which entity signed the loan; both candidates are real, accurate records, and nothing in either says "borrower." The lender reconciles the application, the formation documents, and the borrower's written confirmation, and owns the result.
Cobalt's own measurement on September 11, 2026 searched three large national companies by name in each of the 50 states and DC: 153 probes, each with a 180-second ceiling. All 51 jurisdictions returned status, filing date, sosId, and the registered name, but stateOfFormation came back from 37 and officers from 32. Of the 153 probes, 110 returned a live record in 1.51 to 170.27 seconds, 3 returned Nevada records from the cache while that site was down for maintenance, 19 completed without an exact match, and 21 did not finish inside the ceiling. That was one day and three well-formed names. It shows what a state can return, not what it never returns, and it is not a service expectation.
Cobalt's help center says a lookup that runs past about 20 seconds returns a retryId to poll, or posts to a callbackUrl when ready,[35] so run searches asynchronously. It also describes a common integration pattern that stores the structured payload for audit,[36] and the API reference calls the screenshot a short-lived URL not yet available in all states,[17] so check the field spreadsheet and download each capture into the lender's own file.
What Should the File Contain When the Same-Name Review Closes?
Which identifiers get locked?
Lock, for the chosen entity, the state of organization, the entity number, the registered name exactly as the state shows it, the entity type, the formation date, the status at review, the EIN as confirmed against that name, the downloaded state record capture, and the borrower's written confirmation. Lock the excluded candidate's identifiers and exclusion reason beside them, each dated, because status and name can change before closing.
How should the loan documents name the borrower?
Name the borrower in every document by the exact registered name followed by the state qualifier, "an Ohio limited liability company" or "a Georgia limited liability company," in the note, the security instrument, the guaranty, the closing certificate, and the financing statement. File the financing statement in the state of organization.
When should the review be rerun?
Rerun the recorded searches, by sosId only in a state where ID search is confirmed and by exact name elsewhere, before closing if weeks have passed, when the borrower substitutes the entity that will hold title, and when either candidate shows a name or status change. A rerun compares fresh results with the locked identifiers; it is not a new review. To map the candidate table and the reconciliation record into your underwriting or closing system, schedule a workflow and integration review with Cobalt.
Then the file is closed on identifiers, not on a name.
.jpg){kind=small}
.png)