Executive Summary: A Secretary of State record can tell a closing team that an LLC exists, what the state calls it, whether it is in good standing, and sometimes which people the company reported as managers or members. It cannot, by itself, tell the team who is authorized to sign for the LLC, because signing authority comes from the operating agreement, the consents adopted under it, and the LLC statute of the formation state, not from any field an API returns. This guide covers what state records assert, where they go silent, which documents establish authority, and how a closing or review workflow should store public-record evidence next to the authority determination. It is an evidence and workflow guide, not legal advice.
Why Does the State Record Not Answer Who Is Authorized to Sign for the LLC?
What does a Secretary of State actually record about an LLC?
A state filing office records what its statute tells it to record. In Delaware, the certificate of formation must set forth only the company name, the registered office and agent, and "any other matters the members determine to include therein."[1] Nothing in that list identifies a manager, a member, or a person with signing power. The Delaware Division of Corporations says in its FAQ that "alternative entities are not required to list members and/or managers."[2]
Other states collect more. Arizona's articles of organization must say whether the company is manager-managed or member-managed and must name each manager plus every member holding a twenty percent or greater interest, or every member if the company is member-managed.[3] Florida's annual report must include "the name, title or capacity, and address of at least one person who has the authority to manage the company."[4] California's statement of information lists the managers and the chief executive officer, or each member if no manager has been appointed, and is due within 90 days of formation and every two years after that.[5] These filings disclose management; none grants authority to sign a loan document.
Where does signing authority legally come from?
The LLC statute of the formation state supplies a default rule, and the operating agreement or, in some states, the filed articles can change it. Delaware vests management in the members by their interests in profits, or in a manager where the LLC agreement provides for one, and unless the agreement says otherwise, "each member and manager has the authority to bind the limited liability company."[6] Florida makes a company member-managed unless the operating agreement or articles expressly provide for managers, and the terms "managing member" and "managing members" do not by themselves make a company manager-managed.[7] California and Arizona make a company member-managed unless its filed articles say otherwise.[8][9]
The filed articles therefore settle the structure in California and Arizona and can settle it in Florida, but who holds each position today and any limit on what that person may sign live in the operating agreement, read with every amendment, consent, and resolution adopted under it. On those points a state record can corroborate the agreement but not replace it, except for a filed statement of authority, covered below.
Why do member-managed and manager-managed LLCs change the answer?
Agency rules turn on the management structure. In a member-managed Florida LLC each member is an agent for acts apparently carrying on the ordinary course of business, but in a manager-managed company "a member is not an agent of the limited liability company for the purpose of its business solely by reason of being a member."[10] Where the articles of organization indicate a manager-managed company, California is blunter: "No member acting solely in the capacity of a member is an agent of the limited liability company nor can any member bind or execute any instrument on behalf of the limited liability company."[11] Arizona follows the same split.[12]
So a person listed as a member of a manager-managed LLC may hold most of the equity and still lack the power to sign the note. A person listed as a manager may have authority in the ordinary course and still need a member vote for a transaction outside it.[10] The title on the record starts the inquiry. It does not finish it.
What Do State Records Show About Managers and Members, State by State?
Which states list managers or members in the public record?
Arizona, Florida, and California require the management disclosures described above. Texas works differently. Its Secretary of State's management records come from the Public Information Report filed with the Comptroller as part of the franchise tax report, which lists officers, directors, managers, or members "as applicable."[13] The Comptroller asks for each person's name, title, term expiration date, and address "as of the date the report is filed."[14]
An API returns a narrower map: what each state's system displays. Cobalt's downloadable field spreadsheet[15] marks the officers array for 35 of the 52 jurisdictions it covers, the 50 states plus DC and Puerto Rico.[16] Cobalt's own measurement on September 11, 2026 searched three large national corporations by name in the 50 states and DC, 153 probes with a 180-second ceiling on each, and got an officers array from 32 of 51 jurisdictions on at least one probe. One day and three well-formed corporate names show what a state can return, not what it never returns, and set no service expectation; LLC records still follow each state's LLC filing rules. The two sources mostly agree:
• No officers array in either source. California, Colorado, Delaware, Idaho, Kansas, Maine, Maryland, Missouri, Montana, North Dakota, Ohio, Oklahoma, South Carolina, South Dakota, Tennessee, and Wisconsin.
• Disagreement. New Jersey returned officers in the measurement but is unmarked in the spreadsheet; Illinois, Kentucky, and New Hampshire are marked but returned none.
• Documents instead. Nine of those sixteen, California, Colorado, Idaho, Kansas, Maryland, Montana, North Dakota, Ohio, and South Dakota, are among the 23 jurisdictions the spreadsheet marks for filed documents, so look for names in the filings themselves.[16]
California shows the gap between statute and API. Its statement of information names managers,[5] yet neither source shows an officers array there, as Cobalt's earlier article on officer information in Secretary of State records also noted when it counted 28 states with officer data in May 2025.
Which states show almost nothing about who runs the LLC?
Delaware is the clearest case. Its statute and Division require no manager or member names,[1][2] its management default defers to a private LLC agreement,[6] and the spreadsheet marks neither officers nor documents there, so a lookup returns the name, file number, status, formation date, and registered agent, and no manager or member.[16] The spreadsheet shows the same gap for Maine, Missouri, Oklahoma, South Carolina, Tennessee, and Wisconsin, which describes what the API returns, not everything those states hold. For an LLC formed in these jurisdictions, the public record fixes the entity and its standing; control comes from the borrower's own documents.
How current is a listed name, and who reported it?
Every name in a state record was reported by the company, on a form, at a moment. Texas says so directly:
Please note, the management information maintained by the secretary of state is not necessarily current, but is based on the last information received by this office.[13]
Texas adds that changes after a Public Information Report is filed appear on the next report, and that a person wrongly listed can file an affidavit with the Comptroller.[13] Florida's annual report window runs from January 1 to May 1,[4] and California's statement of information is biennial,[5] so a manager removed in June can remain on the record for months. Cobalt's help center adds that states follow no universal identity-vetting standard, so officer records are public registry information, not validated identity proof, and beneficial ownership data is generally not in state registries.[17]
What Goes Wrong When a Closing Team Treats a Listed Name as the Signer?
What happens when the listed person is a member of a manager-managed LLC?
The failure is quiet. The application names a signer, the state record shows the same name with a title such as member, and the file moves. If the company was manager-managed with someone else as manager, that member had no agency by reason of membership alone.[10][11][12] Under Florida's real property rule, unless a certified statement of authority recorded in the applicable real estate records limits a member's or manager's authority, a member of a member-managed company or a manager of a manager-managed one may sign and deliver an instrument transferring or affecting the company's interest in real property, and the instrument is conclusive in favor of a person who gives value without knowledge of the signer's lack of authority.[10] So even that protection turns on the management structure and on what the real estate records show.
What happens when an amendment or transfer changed control after the last report?
Status alone does not show whether a filed amendment changed control, so read the filing history too. Where a state publishes filings, Cobalt's response can include them as individual documents, such as formation filings, annual reports, and amendments, and Cobalt analyzes their text to flag officer, address, and merger changes.[18] The help center points to those annotations for change history,[19] and some states expose a filing history that Cobalt returns in the documents or history fields.[20] Where the state publishes no filings, ask the borrower for the amendment and the consent that adopted it.
Transfers of membership interests can leave no state filing at all. Delaware's Division of Corporations says alternative entities "are not required to list members and/or managers,"[2] and a Texas LLC may file an amendment to update its management information but is not required to, so a change can wait for the next Public Information Report.[13]
For a lender that funds on a state listing alone, that lag is also a fraud vector: a stale record can present a departed member as the signer, and a recent filing can add a name no operating agreement supports. Cobalt's article on officer and member changes as an early business fraud signal lists patterns worth a second look, such as a new officer roster shortly before a credit application or a dormant entity that suddenly acquires officers. Each is a reason to read the governing documents more closely, not a finding.
What happens when two same-name LLCs in different states share a person?
Take a file where the lender says the borrower is an Ohio LLC, the formation documents show a Georgia LLC, and both states have a domestic LLC with the same name and the same associated individual. The file goes back to the lender to confirm which entity is borrowing. A name match plus a person match cannot fix the entity. The state's own identifier can: Cobalt returns it as sosId, the registration number the state assigned, unique within that jurisdiction.[21]
Every search names one state,[22] and confidenceLevel measures how closely the returned name matches the name sent,[23] so exact-name LLCs in Ohio and Georgia can both score near 1.0. Comparing stateOfFormation with stateOfSosRegistration flags a foreign registration,[24] not which of two domestic LLCs is borrowing, and stateOfFormation is state dependent: the September 11 measurement got it from 37 of 51 jurisdictions, and the spreadsheet marks it for Georgia but not Ohio.[16] The sosId on the formation documents, confirmed with the lender and matched in the issuing state, fixes the entity.
Which Documents Actually Establish Who Can Bind the LLC?
Land Title Guarantee Company's title requirements, written for Colorado, split the work between the public record and the private documents:
The existence of a Limited Liability Company is determined by the stamped Articles of Organization filed with the Secretary of State. The authority of the members and managers to bind and convey real property is determined by the Operating Agreement.[25]
What should the operating agreement and its amendments show?
Read for four things. First, the management structure, in words the formation state's statute recognizes.[7] Second, who currently holds the manager or member positions, traced through every amendment, admission, and withdrawal. Third, what managers may do without a member vote, since acts outside the ordinary course bind the company only when authorized by the appropriate vote.[10] Fourth, any express limits on borrowing, guaranteeing, or encumbering property.
If the company has no operating agreement, the statute's defaults apply, and Land Title Guarantee Company requires all members and managers to sign the closing documents.[25]
When is a resolution, consent, or incumbency certificate needed?
A resolution or written consent is the company's own record that the people with authority approved this transaction and designated this signer. An incumbency certificate identifies who holds each position and supplies specimen signatures. Neither is a state document, and neither substitutes for reading the operating agreement, because a certificate signed by someone without authority proves nothing. Date them and tie them to the agreement section they rely on.
When does a statement of authority belong in the file?
Florida lets a company file a statement of authority that states or limits the authority of everyone in a named position, or of a specific person, to transfer real property or otherwise bind the company, and the statement lapses by operation of law five years after it or its latest amendment takes effect. Subject to the statute's management and agency sections, a grant of authority in an effective statement, other than one pertaining to transfers of real property, "is conclusive in favor of a person who gives value in reliance on the grant," except to the extent that, when value is given, the person knows otherwise, the statement has been canceled or restrictively amended, or a later-effective statement limits the grant.[26] Land Title Guarantee Company's Colorado requirements call for a statement of authority recorded in the county where the property is located when there is no operating agreement or when circumstances require departing from it.[25] Where a statement exists, it is the one public record that speaks to signing authority directly, so search the state filing system and the county real estate records. Its absence proves nothing.
How Should a Review Workflow Sequence Public Records and Governing Documents?
What is the order of operations?
Each step narrows the next; a workflow that reads the operating agreement before fixing the entity can read the wrong one.
• Fix the entity. Take the legal name, formation state, and state identifier from the formation documents, and accept a record only when its sosId matches that identifier.[21] The API reference also accepts sosId as a search input, but the spreadsheet marks its searchBySosId row for only Florida and Mississippi.[22][16] A name search also returns confidenceLevel, which Cobalt's typical guidance treats as auto-accept at 0.80 and above, review from 0.60 to 0.79, and usually reject below 0.60,[27] plus possibleAlternatives, the other close names the search found.[22] Use them to find candidates and the identifier to choose. Confirm the property-state record too when the LLC is registered there as a foreign entity.[24]
• Confirm existence and status. Record the status the state displays, the formation date, and the registered agent, and keep a capture of the state page, which a live lookup can return with a timestamp, URL, and source domain.[28]
• Collect the governing documents. Request the operating agreement, every amendment, and the consents that adopted them, dated and complete.
• Determine the management structure. Classify the company from the words of the document the formation state's statute reads, not the borrower's description: the filed articles in California and Arizona, the LLC agreement in Delaware, both in Florida.[8][9][6][7]
• Identify the signer and the basis. Name the person, the position, and the agreement section or resolution that gives that position the power to sign this instrument.
• Compare the state record to the determination. Treat agreement as corroboration and disagreement as an exception to explain, not as a veto in either direction.
• Document the exception path. Record who reviewed the conflict, what additional evidence was obtained, and what the lender required before closing.
How should a conflict between the state record and the operating agreement be handled?
Conflicts take three shapes: a manager on the state record whom the agreement no longer names, from a stale report or an unauthorized filing; a manager in the agreement whom the record lacks, because the state collects no management information or the report predates the appointment; or different management structures, because an amendment was filed without updating the agreement, or the reverse. Resolve each with evidence: the later dated document, the consent that adopted the change, and the filing that recorded it where the state exposes one. Settle a structure conflict, though, by the formation state's rule set out above, not by which document is newer.[8][9][7] The pattern that stops a file is a normalizedStatus other than active,[22] because it goes to whether the company can act at all rather than who acts for it.
What Can a Secretary of State API Contribute to a Signing-Authority Review?
By hand, the public-record steps mean opening each state's portal, searching the name, saving the page, and ordering certified copies where the state sells them. Document-retrieval firms and aggregated business databases are other routes; ask either whether a result is the state's current page or a stored copy. An API that returns the state's record as structured fields plus a page capture is a third. It does not read the operating agreement and should not be asked to.
Which fields help, and what does each one assert?
Cobalt's public Secretary of State API fields reference documents officers as an array of objects with name, title, and address, and it advises defaulting officers to an empty array so a non-disclosing state does not break a parser. Each field asserts only what the state displayed at the moment of the lookup. officers asserts that the state's record listed these people with these titles; the help center defines them as the key people in SOS filings when available, distinct from the registered agent.[29] entityType asserts the state's own label, returned only when the state provides it.[30] stateOfSosRegistration names the state whose record this is, and where that state also returns stateOfFormation, a difference likely marks a foreign registration.[24] None of these fields asserts that a listed person may sign anything.
Where does the API stop?
Cobalt is a data source. It returns officer data only where the state provides it,[17] so expect an empty officers array in the jurisdictions listed earlier, Delaware among them. There is no signing-authority field, no operating agreement, and no management-structure classification beyond the state's entityType label. Filing documents come back in only some jurisdictions,[16] and document links are valid for three days by default and can be extended up to 30 days on request, so download and store them.[31] Searching by a person's name is possible but not supported in every state.[32] The field spreadsheet answers each of these questions state by state.[15]
How should the state observation be stored next to the determination?
Cobalt's help center says every live lookup can include a screenshot with a timestamp, URL, and source domain,[28] and the spreadsheet marks screenshotUrl for all 52 jurisdictions,[16] but the API reference says screenshots are not yet available in all states.[22] Check the screenshotSucceeded flag on each result, and store the image rather than the short-lived link.[22] The record below is an illustrative, customer-owned structure, not a Cobalt response, keeping the state observation and the authority determination in separate objects with separate provenance.
{
"entity": {
"legalName": "EXAMPLE BORROWER HOLDINGS LLC",
"sosId": "FL-EXAMPLE-0000001",
"stateOfFormation": "FL",
"stateOfSosRegistration": "FL"
},
"stateObservation": {
"source": "sos_api_live",
"observedAt": "2026-09-24T14:05:00Z",
"status": "Active",
"listedPersons": [{ "name": "J DOE", "title": "MGR" }],
"screenshotStored": true,
"asserts": "what the state record displayed at observedAt"
},
"governingDocuments": {
"operatingAgreement": { "dated": "2023-04-10", "managementStructure": "manager-managed" },
"writtenConsent": { "dated": "2026-09-18" }
},
"determination": {
"authorizedSigner": "J. Doe, Manager",
"basis": ["operating agreement section 5.2", "written consent 2026-09-18"],
"reviewedBy": "closing counsel",
"stateRecordRole": "corroboration only"
}
}How Should Teams Write Rules That Use State Data Without Overreaching?
Which comparisons are safe to automate?
Automate the comparisons whose failure is informative and whose success proves little. A normalizedStatus other than active can stop a file, and a missing one should go to review. A stateOfFormation that differs from the state on the formation documents can route the file to a reviewer. A signer name absent from a populated officers array can raise a flag that a reviewer must clear against the operating agreement. A signer name present in the array is recorded as a match and nothing more. Cobalt's guide to audit-proofing loan files with automated SOS screenshots covers keeping the page capture with each result.
Which determinations must stay with a person?
The authority determination itself. Classifying the management structure under a specific statute, reading a borrowing restriction, judging whether a consent was validly adopted, and accepting an incumbency certificate are legal judgments on documents the state never sees. Nor does a federal filing fill the gap: FinCEN's final rule, issued August 11, 2026 and effective August 14, 2026, made permanent the exemption of U.S. companies from beneficial ownership information reporting.[33][34] For control-person or beneficial-owner checks, Cobalt's guide to know-your-business and beneficial owner verification covers the adjacent workflow, but it was published in January 2026, before that rule, and still describes the BOI registry as a new data source.
How should exceptions be routed?
Route by what is missing rather than by what looks wrong. A missing officers array from a jurisdiction that does not return one is expected and should not generate an exception; the workflow proceeds on documents. A populated array that disagrees with the documents is an exception with a named owner and a required resolution. A missing operating agreement is a stop until one is produced or the default path described above is followed. The top 34 questions about Secretary of State and business verification APIs cover the surrounding integration questions. To map these fields, artifacts, and exception paths into your own review workflow, schedule a demo to review the integration.
.jpg){kind=small}
.png)