Skip to main content
Access
Global KYB v2 runs on the standard GLB-Organization-* workflow suite on the V2 platform. It’s enabled per customer through two Portal Features toggles and a country-by-country configuration grid — see Enabling international coverage below, or contact your FrankieOne representative.

​
Overview

Onboarding a business outside Australia has traditionally meant a different integration, a different data shape, and a different tool per country. Global KYB v2 replaces that with one API, one organization object, and one set of workflows that route to the right registry provider automatically based on the business’s country — the same way domestic Australian KYB already works on V2. Coverage spans 160+ jurisdictions through Kyckr. Enhanced profiles (full ownership data, officeholders, share capital) are available in major markets; Lite profiles (basic company data) cover the rest. The United States is verified separately through Middesk and is out of scope for this guide — see US Business Verification. This is the final major capability gap between FrankieOne’s V1 and V2 platforms: with international coverage on V2, V1 customers using international KYB can now port over to V2.

​
How it works

International KYB uses the exact same organization entity, the same five GLB-Organization-* workflows, and the same reports as domestic KYB. The only difference is where the data comes from, which the platform resolves automatically from the business’s country:

​
Via the Portal

From an organization search, select the country you want to search in from a configurable country dropdown (your account only sees the jurisdictions it’s been enabled for), then search by name or registration number. Select a result to view its full registry details before creating the entity. Once created, the entity’s Overview tab shows a registry-sourced profile panel with the same field set as domestic (legal name, country, company type, registration number, status, jurisdiction, registration authority, incorporation date, registered address), and the Relationships tab shows ownership the same way domestic entities do — including an explicit “Unknown” row treatment for parties the registry couldn’t classify as an individual or organization. When manually associating a party with an organization, the officer now searches the relevant business registry the same way as when creating an entity — free-text manual entry for organizations has been removed, so every associated organization is registry-verified. (This doesn’t affect individuals, who still take manual details, since a person can’t be looked up in a business registry.)
Create new entity profile screen with the Organization tab open and the country dropdown expanded

Selecting a country from the organization search dropdown.

Organization search results for a United Kingdom company, expanded to show registry details and a Create this entity button

Reviewing a result's full registry details before creating the entity.

Entity Overview tab showing the Organisation Profile panel and a completed GLB-Organization-Ownership workflow

The Overview tab with the registry-sourced Organisation Profile.

Entity Profile tab showing Organisation info and the registered office address

The Profile tab for an international organization.

Relationships tab showing a Credit limit has been reached banner with a Continue report generation button, above the Ultimate beneficial owners table

The Relationships tab after an ownership run reaches its credit limit.

​
Via the API

1

Look up the business

Search by country plus name or registration number. Returns candidate registry records and an organizationToken.
2

Create the organization

Create the entity from the organizationToken.
3

Execute a workflow

GLB-Organization-Profile for registry details, or GLB-Organization-Ownership for the full beneficial-ownership tree. Force-refresh variants of both always re-fetch instead of reusing recently cached data.
4

Poll for the result

Workflows run asynchronously.
5

Retrieve the enriched organization

The same organization object used for domestic entities, now populated with international registry data.
Ready to integrate? See the Global KYB Implementation Guide for the full walkthrough with request and response examples.

​
Enabling international coverage

International KYB is switched on per customer through two settings in Configuration → KYB:
  • KYB in Portal — enables KYB V2 in the Portal at all.
  • International KYB — the master switch for international organization search. With this off, the Portal only offers Australia, regardless of anything configured on the Countries tab.
Coverage is then configured per country on the Countries tab, with four independent settings: whether the country appears in the Portal’s dropdown, whether registry lookup is allowed, and whether the profile and ownership checks are allowed. All four need to be turned on for a country to work end to end — a country visible in the Portal but not enabled for Profile will let an officer search and select a company, then watch the workflow fail. Contact your FrankieOne representative to review or change your account’s configured countries. Configuration changes can take up to 10 minutes to take effect.

​
Key capabilities

  • Organization lookup — search by country plus name or registration number. Whether search-by-number is available depends on the jurisdiction.
  • Organization profile — registry-sourced company details, single-level ownership where the registry publishes it.
  • Organization ownership — full recursive UBO tree, using the same 25% blocking threshold and ownership-insights policy as domestic.
  • UNKNOWN entities — where a registry discloses that a shareholder or officer exists but not whether it’s a person or a company, that party is stored as a distinct UNKNOWN entity type rather than guessed at. UNKNOWNs are de-duplicated against each other but never against individuals or organizations.
  • NAME_IN_ENGLISH alternate names — a romanised or English name returned alongside a local-script name (for example, a Japanese company) is stored as an alternate name. Display and storage only — it is not used in compliance checks or entity matching.
  • AML screening and monitoring — the same ComplyAdvantage screening as domestic, including ongoing monitoring, verified against non-English names.
  • Risk — the same risk-factor engine as domestic, extended with country-aware gating (a factor can be scoped to specific countries) and a distinct “cross-border” factor separate from focus-organization-relative foreign ownership.
  • PDF reports — an International Profile Report and a generic Ownership Report, structurally identical to the domestic reports with AU-specific sections (ABR/ASIC extracts, GST, ANZSIC codes) suppressed. Report template selection is automatic, based on the organization’s jurisdiction — there’s no customer setting or API parameter for it.
  • Country restriction — per-customer allow-lists, configured separately for profile and ownership, so an account only runs KYB in jurisdictions it has been vetted and priced for.

​
Supported jurisdictions

Coverage is config-driven and reviewed periodically. As currently deployed: Profile and ownership country coverage are configured independently: an account can be enabled to pull a company profile in a country while UBO discovery there stays closed. Your FrankieOne representative can confirm your account’s specific allowed countries. Non-Latin company and officer names render correctly in PDF reports for seven scripts: Japanese, Chinese (Simplified and Traditional), Korean, Arabic/Persian, Thai, and Hebrew. A script outside that list is not yet supported and will render as corrupted, unrelated Latin characters in the PDF with no error raised. If you’re onboarding a market that uses a different script, talk to your FrankieOne representative before go-live.

​
Frequently asked questions

No. The same GLB-Organization-Profile, GLB-Organization-Ownership, and their Force-Refresh variants used for Australian entities work for international ones. The platform routes the request to the right registry provider based on the business’s country automatically.
No. Major markets get Enhanced profiles with full ownership data; other markets get Lite profiles with basic company data only. Registry publishing practices also vary — a sparse profile for a given country is expected behavior, not an error.
That party is stored as an UNKNOWN entity type rather than guessed at. It shows up in ownership results and the Portal’s Relationships tab with an explicit Unknown treatment. Note that an UNKNOWN holding below the 25% ownership threshold is classified as an “other owner,” not a blocking entity — this surprises people reviewing a tree for the first time.
Not currently. Kyckr only provides a normalized legal status once you purchase a full profile, not at lookup time, so international lookup results may not include status.normalized the way a domestic AU lookup does.
Registry document ordering is a V1-only capability today and is not part of the V2 standard workflow suite.
Not supported today — an ownership workflow run against a US (or Canadian) focus entity is refused at the workflow’s jurisdiction gate before any provider is called, because Middesk (the US provider) has no shareholder/UBO product. Portal support for this is under consideration as a potential addition later in the year, though it isn’t confirmed for any specific release yet. See US Business Verification for what is supported for US entities today.
Yes. Portal visibility, lookup, profile, and ownership each have their own setting, per country, per customer. A blocked country fails the check before any provider is called, so it costs nothing and produces no billing event. Contact your FrankieOne representative to review or change your account’s configured countries.

​
References