US Business Verification (FrankieOne KYB v2)

Overview

FrankieOne KYB v2 supports business verification in the United States through an integrated Middesk connector. When you verify US-based organizations, you get business registration status, tax identification verification, address validation, and officer identification — through the API and, as of this release, the Portal.

Who needs this?

If you’re onboarding US businesses and need to:

Verify business registration with Secretary of State
Validate Tax Identification Numbers (TIN/EIN) against IRS records
Confirm physical addresses and detect mail drop locations
Discover officers from state filings

Then US business verification provides automated verification across all these categories.

Why use US business verification?

Compliance requirements: US anti-money laundering (AML) and know your business (KYB) regulations require verification of business identity, officer structures, and registration status. Risk detection: Address verification flags high-risk indicators like Commercial Mail Receiving Agencies (CMRA), undeliverable addresses, and registered agent addresses that may indicate shell companies. Automated officer discovery: Middesk identifies officers and directors from state filings and proprietary data sources, reducing manual research.

Prerequisites

US business verification requires your account to be configured with a US-enabled KYB workflow. Contact your Customer Success Manager to confirm your setup includes US jurisdiction support.

How it works

FrankieOne uses jurisdiction-based routing to determine which data provider to use when verifying an organization. Jurisdiction is determined from the address you submit when creating the organization:

Australia (AUS) — Routes to ABR and CreditorWatch for registry data
United States (USA) — Routes to Middesk for business registration, officer, name, address, and tax verification

Routing is automatic. You use the same workflow execution endpoints regardless of jurisdiction — provider selection is handled based on the organization’s country.

What data is returned?

When the GLB-Organization-Profile workflow executes against a US organization, Middesk performs verification across four categories. Each produces a distinct result:

Category	What it checks	Result values
Business name verification	Validates the business name against Secretary of State registrations	`MATCH`, `NOMATCH`
Address verification	Confirms the physical address is legitimate. Flags CMRA (Commercial Mail Receiving Agency) addresses, undeliverable addresses, and registered agent addresses as high risk, independent of the match result	`MATCH`, `PARTIALMATCH`, `NOMATCH`
Tax identification (TIN) verification	Validates the TIN against IRS records, if one was submitted	`MATCH`, `NOMATCH`, `UNCHECKED`
Registration verification	Confirms business registration status with the Secretary of State	`MATCH`, `NOMATCH`, `UNCHECKED`

Officer discovery runs alongside these: officers and directors are identified from state filings and Middesk’s data sources and added to the organization’s officials. Each verification result also carries a risk level (LOW, MEDIUM, HIGH, UNACCEPTABLE) from FrankieOne’s risk engine — a separate dimension from the result value above. A business with a verified registration in good standing will typically score LOW; a business with no matching Secretary of State record (UNCHECKED) doesn’t score on that factor, leaving the outcome driven by name and address results. Tax ID is optional. If you don’t submit a TIN, tax verification simply returns UNCHECKED rather than failing the request — the other three categories still run normally. UNCHECKED registration is normal, not an error. It means Middesk searched but found no matching Secretary of State record — common for sole proprietorships and general partnerships, which have sparser state filings in most states, or for states where Middesk’s registry feed is incomplete.

US-specific features

PDF reports

KYB v2 generates PDF reports for US organizations that include US-specific business details alongside the standard profile and officer information. Reports include:

Business registration status from Secretary of State records
TIN verification results
Address verification results and any flags (CMRA, undeliverable)
Officers as discovered by Middesk

Each verification badge on the report is driven by Middesk’s own status, not the risk level: Verified (green), Not verified (red), Warning (amber), or Unknown (grey). PDF reports can be generated through workflow execution or via the Portal UI.

US organisations in the Portal

Portal support for US organisations shipped 2026-10-21. There is no registry search for US businesses — officers create a US organisation by entering its details directly, and it’s verified against US state registries afterwards.

Create — From New entity or Add entity (when manually associating a party), select United States and enter the business name, address, and optionally a TIN. There’s no state picker and no search step.
Overview — Shows the details you entered until the organisation is verified, then the registry-sourced profile. Only workflows tagged for US organisations are offered, so officers aren’t shown options that don’t apply (e.g. ownership).
Workflow Events — Shows what Middesk verified (name, address, TIN) and the state filings at a glance, for the Organisation profile workflow run.
Profile — Shows where each address and name came from (you, or Middesk), and every state the organisation is registered in.
Relationships — Shows the business’s officials as discovered by Middesk, with a banner explaining that ownership information isn’t available for US organisations (see Limitations below). The heading reads “Officials” rather than “Officeholders & other roles,” since US entities have no separate roles distinction.

Limitations

Limitation	Detail
No ownership / UBO data	US registries don’t publish shareholder or beneficial-ownership information. Running the `GLB-Organization-Ownership` workflow against a US organization fails with an explicit unsupported error rather than returning an empty or partial result.
Sole proprietorships and partnerships	Secretary of State filings are sparser for these entity types in most states — expect `UNCHECKED` rather than a definitive match on registration more often than for corporations or LLCs.
No lookup / autocomplete	Unlike Australian and international organizations, US organizations can’t be searched by name before creation — in the API, you create the entity directly; in the Portal, there’s no search step.
Foreign-registered companies	Not supported — Middesk covers US-registered entities only (LLC, Corporation, Partnership, Sole Proprietorship, Non-Profit, Trust).
Deduplication	US registry data is sparser than Australia’s, so officers discovered from state filings are currently linked as individuals rather than deduplicated against existing records with the same precision as AU KYB.

AML, PEP, and sanctions screening already work for US entities. This isn’t new or specific to this release — FrankieOne’s existing screening capability (via ComplyAdvantage) runs for US organizations the same way it does for any entity, as part of the standard workflow.

Differences from Australian KYB

If you’re already integrated with FrankieOne for Australian KYB, here are the key differences when extending to US verification:

Aspect	Australia	United States
Country code	`AUS`	`USA`
Jurisdiction	Not required (single national registry)	Derived automatically from the submitted address (e.g., DE, CA, NY)
Data provider	CreditorWatch / ABR	Middesk
Registration types	ABN, ACN	State filing number, EIN
Tax verification	Not applicable	TIN verified against IRS records (optional field)
Address verification	Basic address normalization	Full verification with CMRA, deliverability, and registered agent detection
Lookup / search	Supported via `/v2/organizations/lookup`	Not supported — create the organization directly
Ownership	Full recursive UBO discovery	Not supported — no shareholder/UBO data exists in US registries

Use cases

Fintech onboarding: Verify US businesses opening commercial bank accounts or applying for business credit cards. Marketplace compliance: Screen US sellers or service providers before allowing them to transact on your platform. B2B vendor onboarding: Validate US suppliers and partners as part of third-party risk management. Regulatory compliance: Meet Customer Due Diligence (CDD) requirements for US-based business customers under Bank Secrecy Act (BSA) regulations.

Next steps

Ready to implement? See the US Business Verification Implementation Guide for API endpoints, request/response examples, Portal walkthrough, and error handling. Related guides:

Executing a workflow — Learn the full workflow execution and polling pattern
Interpreting workflow results — Understand the workflow result object and how to parse verification outcomes
Organization profile — Learn how organization profiles work, including officer data for US businesses

​Overview

​Who needs this?

​Why use US business verification?

​Prerequisites

​How it works

​What data is returned?

​US-specific features

​PDF reports

​US organisations in the Portal

​Limitations

​Differences from Australian KYB

​Use cases

​Next steps