BLOG
Before adding a U.S. customer or supplier to your CRM, check who the legal counterparty is and which evidence your decision actually needs. A state business search can help confirm a registered entity’s name, number, jurisdiction, and status; it does not approve credit, prove a salesperson can sign, or establish that a service provider holds every license. This U.S. adaptation replaces a Brazilian CNPJ lookup with a layered vendor and customer review. The California Secretary of State’s records guide illustrates useful fields and why one registry is only a starting point.
Define the purpose of the check
A form submitted to ask for a quote needs different evidence from a vendor onboarding process that will send payments or receive sensitive data. Write down the decision first: Are you checking the exact legal name for a contract, a mailing address for an order, a professional license, or payment risk? Collect only what supports that decision. A generic “verified business” flag with no source or scope can mislead staff later. If a customer does not need formal vetting to receive information, do not block a useful conversation because a field is missing.
Start with the entity’s own information
Ask the contact for the legal entity name, state of formation, business address, and the name of the person signing or receiving invoices. Keep the submitted trading name separately. A brand may be used by an LLC with a different legal name; several businesses can have similar names. Match the information on the proposal or purchase order against the details supplied in the onboarding form. When they differ, request clarification rather than editing the CRM record to whichever name seems most familiar.
Use the correct official state search
Search the Secretary of State or corresponding agency for the relevant state. The company may be formed in one state and registered to operate in another. California’s business search FAQ warns that a foreign entity’s California status describes its California registration, not its status in the formation jurisdiction. A sole proprietorship may not appear in an entity database at all. Keep the state, search date, query, result number, and matched fields with your review, because registry information can change.
| Question | Appropriate evidence |
|---|---|
| Is this the same entity? | Name, number, state, address, and contract |
| Is its filing active? | Current official state status |
| Can it perform regulated work? | Relevant licensing authority |
| Will it pay on time? | Separate commercial review, not a registry status |
Distinguish identifiers
An Employer Identification Number, state entity number, license number, sales-tax permit, and internal vendor ID have different purposes. There is no single public U.S. number that works exactly like the CNPJ in the Brazilian source article. Do not design a form that asks for “the business number” without saying which one and why. Avoid treating an EIN as a general public lookup key. If a tax form is required for payment, obtain it through the appropriate controlled process rather than displaying sensitive details in a shared CRM note.
Check licenses and authority when relevant
Some services require state or local professional licensing. Search the authority that regulates the actual work, not only the entity registry. Verify the person or company named on the license and the relevant expiration date. For a contract, confirm that the signatory has authority under the organization’s own process. An “active” entity can still have an unrelated license issue, and a licensed professional may be operating under a different legal structure. Keep these findings separate so staff do not mistake one check for the other.
Do not turn filing status into credit approval
A company may be registered and still dispute invoices, pay late, or lack the funds for a project. Conversely, a new legitimate business may have little public history. Decide payment terms, deposits, credit limits, and references using your own commercial process and applicable law. Do not label a lead fraudulent because an automated name match failed. The registry is evidence of a filing, not a promise about future behavior. Escalate high-value or unusual cases to the person authorized to assess them.
Store the result in the CRM without overwriting the source
Keep the name entered by the customer, the legal name found, the source URL, date, reviewer, and decision in distinct fields. If the match is uncertain, set a review state and ask for a document or clarification. Do not automatically merge two contacts because their names resemble one another. An automation that overwrites the original answer can erase the reason a human asked a question. Give staff a way to record why a mismatch was accepted or rejected.
Automate the stable part only
A workflow may normalize names, prompt for a missing state, attach a query link, or alert a reviewer. Official registries differ in access methods and terms; do not claim an API exists for every state. If you use a data provider, check update frequency and licensing. Keep a manual path for ambiguous results, foreign entities, sole proprietors, and entities with recently changed names. Test the workflow against known examples before letting it change live customer status.
Define what the automation may write back. A useful first version can record the search term and a review task without declaring a match. If a human later approves a legal name, save the approver and evidence. Re-run tests when a state portal changes its search layout or when a vendor changes its dataset. A successful HTTP response is not confirmation that the returned company is the one in your contract.
Recheck when the relationship changes
A one-time registration check may be enough for a low-risk quote, but a long-term vendor relationship can call for periodic review. Set a date based on the decision’s risk and the expiration of licenses or contract documents. Record changes in the same audit trail instead of deleting the old result. When a status changes, notify the responsible owner before the system blocks payments or customer communications. A registry update may require interpretation and a direct conversation.
Maintain a review queue rather than sending every status change straight to sales or accounts payable. The reviewer can confirm that the search still points to the same entity and that the state has not changed the meaning of a field. Note whether the company remains a customer, vendor, or both; a decision for one relationship does not automatically cover the other. Store only the evidence necessary for the agreed retention period.
Common questions
Does an active state filing approve a customer for credit? No. Can I reject every company missing from a state search? No; some structures are not represented there, and a query can fail to match. Should my CRM accept only digits for a business identifier? No universal format covers all state numbers. Define each field by the authority that issued it. What if the name differs? Preserve both values and ask the contact or responsible reviewer to resolve the mismatch.
Finish with a decision that states what was checked and what remains open. “Legal name matched to a California filing on this date” is meaningful. “Company verified” is too broad unless the team knows exactly what it includes. The goal is a traceable onboarding process that helps staff work with the right customer or supplier without implying that a public record can answer every commercial, legal, or payment question.
For a multistate relationship, keep each jurisdictional finding separate. A company can have a formation record in one state and a foreign registration in another, with different status dates. Label the source and jurisdiction clearly so an employee does not read one state result as a nationwide clearance.
