KYB Compliance for US Territories: Puerto Rico and USVI Explained

When compliance teams talk about KYB compliance in US territories, the conversation often stalls. Puerto Rico and the U.S. Virgin Islands occupy a legally unique space — they are part of the United States, yet their business registries and regulatory frameworks differ meaningfully from the fifty states. For financial institutions, fintechs, lenders, and any business required to verify the entities they work with, ignoring these distinctions is not just a gap in due diligence. It is a regulatory exposure.

This guide explains how KYB compliance applies to Puerto Rico and the USVI, what federal rules govern business verification there, and how tools like the OpenSOSData API can close the data gap in minutes rather than days.

Why US Territories Create a KYB Blind Spot

Most automated KYB workflows are built around Secretary of State lookups across the 50 states. That makes sense — the bulk of US business entities are registered in states like Delaware, Wyoming, or Florida. But Puerto Rico and the USVI are not states. They have their own corporate registries, their own local statutes, and their own filing cadences. A compliance platform that silently fails to query these registries will return no match for a legitimately registered business, triggering false negatives and manual review backlogs.

The stakes are real. According to the Puerto Rico Department of State, over one million business entities have been registered on the island over the years. The USVI's Division of Corporations and Trademarks maintains its own active registry. Businesses incorporated in these territories open US bank accounts, apply for federal contracts, participate in SBA programs, and engage in interstate commerce — all of which trigger KYB obligations under federal law.

Federal Regulatory Framework That Applies to the Territories

Bank Secrecy Act (BSA)

The Bank Secrecy Act applies in full to Puerto Rico and the USVI. Financial institutions operating in or with businesses from these territories must maintain anti-money laundering (AML) programs, file Suspicious Activity Reports (SARs), and conduct Customer Due Diligence (CDD). There is no territorial carve-out. FinCEN has made clear that BSA obligations follow US persons and US-regulated institutions regardless of whether a counterpart is in Miami or San Juan.

FinCEN Beneficial Ownership / BOI Rules

The Corporate Transparency Act (CTA) and its implementing regulations, which took effect in 2024, require most US business entities — including those formed in Puerto Rico and the USVI — to report beneficial ownership information (BOI) to FinCEN. A company formed under Puerto Rico's General Corporations Act is a "domestic reporting company" under the CTA unless it qualifies for an exemption. The same logic applies to USVI entities. This means compliance teams verifying business partners must now layer BOI checks on top of traditional Secretary of State record verification.

OFAC Sanctions Screening

OFAC sanctions apply universally across all US territories. Any entity or individual on the SDN list operating through a Puerto Rico or USVI shell company remains a sanctions risk. Robust KYB compliance in US territories must therefore include both registry verification and OFAC screening in the same workflow.

What a Territorial Business Registry Record Contains

Puerto Rico and the USVI registries contain fields that align closely with state-level Secretary of State records, though the data quality and update cadence can vary. A well-structured API lookup should return:

• Entity name — the legal name as registered
• Entity type — corporation, LLC, partnership, etc.
• Entity ID — the registry's unique identifier
• Status — active, inactive, dissolved, revoked
• Formation date — when the entity was registered
• Registered agent name and address — the statutory point of contact

These fields are exactly what the OpenSOSData API returns for all 50 states plus Puerto Rico and the USVI, covering more than 23 million US business entities in a single normalized data model.

Comparison: Puerto Rico vs. USVI vs. State-Level KYB

Practical API Integration: Verifying a Puerto Rico or USVI Entity

The OpenSOSData API uses a single POST endpoint for all jurisdictions. You pass the state or territory code and the entity name or ID, and the API returns normalized registry data. Full API documentation is available at opensosdata.com/openapi.yaml.

Below is a Python example that queries for a Puerto Rico entity and then a USVI entity in sequence — exactly the pattern you would embed in a KYB onboarding pipeline:

import requests

# Your API key from https://app.opensosdata.com
API_KEY = "your_api_key_here"
ENDPOINT = "https://api.opensosdata.com/v1/lookup"

HEADERS = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json"
}

def verify_entity(jurisdiction: str, entity_name: str) -> dict:
    """
    Look up a business entity by name in a given US jurisdiction.
    jurisdiction: two-letter state code or territory code (e.g., 'PR', 'VI')
    entity_name: the legal business name to search
    """
    payload = {
        "jurisdiction": jurisdiction,
        "name": entity_name
    }
    response = requests.post(ENDPOINT, json=payload, headers=HEADERS)
    response.raise_for_status()
    return response.json()

# --- Puerto Rico lookup ---
pr_result = verify_entity("PR", "Caribe Solutions LLC")
print("Puerto Rico Result:")
print(f"  Entity Name   : {pr_result.get('name')}")
print(f"  Status        : {pr_result.get('status')}")
print(f"  Formation Date: {pr_result.get('formation_date')}")
print(f"  Reg. Agent    : {pr_result.get('registered_agent')}")

# --- US Virgin Islands lookup ---
vi_result = verify_entity("VI", "Island Trade Corp")
print("\nUSVI Result:")
print(f"  Entity Name   : {vi_result.get('name')}")
print(f"  Status        : {vi_result.get('status')}")
print(f"  Formation Date: {vi_result.get('formation_date')}")
print(f"  Reg. Agent    : {vi_result.get('registered_agent')}")

Live lookups are priced at $0.10 per query standard, scaling down to as low as $0.0314 with volume. If your workflow can tolerate slightly older data, cached lookups start at just $0.01 and go as low as $0.00314 at volume. There are no subscriptions or seat fees — pure pay-as-you-go pricing. Sign up at app.opensosdata.com to get your API key.

Building a Complete KYB Workflow for Territorial Entities

Step 1: Identify the Jurisdiction at Onboarding

Ask applicants to specify the territory of incorporation explicitly. Many onboarding forms default to a 50-state dropdown, leaving Puerto Rico and USVI out entirely. Fix this at the UI layer before it becomes a compliance gap at the data layer.

Step 2: Query the Registry via API

Use the OpenSOSData API to retrieve the entity's status, formation date, and registered agent. An active status confirms the entity is in good standing with the territorial registry. A dissolved or revoked status is an immediate red flag that warrants escalation.

Step 3: Cross-Reference with BOI Data

Since CTA reporting applies to territorial entities, your KYB workflow should prompt the applicant to provide beneficial ownership information and validate it against any available FinCEN BOI data. Document this step in your audit trail.

Step 4: Run OFAC Screening

Screen the entity name, registered agent, and any disclosed beneficial owners against the OFAC SDN and consolidated sanctions lists. This step is non-negotiable regardless of the jurisdiction.

Step 5: Document and Retain

BSA recordkeeping rules require you to retain CDD documentation for a minimum of five years. Store the API response payload, the OFAC screening results, and the BOI data together in your compliance record for each entity.

Common Pitfalls to Avoid

• Treating territories as foreign jurisdictions: Puerto Rico and USVI entities are domestic US companies for BSA and CTA purposes. Do not route them through your foreign correspondent or cross-border AML workflow.
• Accepting self-certification without registry verification: An applicant saying "we're a Puerto Rico LLC" is not sufficient. Always verify against the official registry record.
• Ignoring language in filings: Puerto Rico filings may contain Spanish-language entity names or officer names. Your matching logic must handle Unicode and accent characters to avoid false non-matches.
• Assuming inactive means dissolved: Some territorial registries use "inactive" to mean a filing deadline was missed, not that the entity is legally dissolved. Understand the status taxonomy for each jurisdiction.

Frequently Asked Questions

Conclusion

KYB compliance in US territories is not a niche edge case. It is a real regulatory obligation that many compliance programs have quietly left unaddressed by treating Puerto Rico and the USVI as afterthoughts in their onboarding tools. The BSA applies. The CTA applies. OFAC applies. And the businesses registered in these territories are actively engaging in US commerce every day.

Closing this gap is straightforward with the right data infrastructure. The OpenSOSData API covers all 50 states plus Puerto Rico, the USVI, and Washington D.C. — more than 23 million entities in a single, normalized API. Whether you are building a new KYB pipeline or auditing an existing one, adding territorial coverage is a single configuration change that carries significant compliance weight. Start your integration at app.opensosdata.com today.