Skip to main content

Party Countries

The prm_party_countries view associates parties with the countries they operate in or are connected to. This is separate from the physical address stored in locations — a party's country associations represent a broader geographic relationship, such as the jurisdictions where a company is registered or the markets it serves.

Why country associations are separate from locations​

A party's physical locations tell you where offices and warehouses are. Country associations tell you something different — where the party has legal presence, regulatory obligations, or commercial interests. A company headquartered in New Zealand may also be registered in Australia and serve customers in Singapore, giving it three country associations but perhaps only one physical location.

Separating country associations from locations keeps each concept clean and avoids overloading address records with jurisdictional meaning.

What a party country record contains​

  • party_id — the party this association belongs to
  • country_code — an ISO 3166-1 alpha-2 country code (e.g. NZ, AU, SG)
  • Primary country flag — indicates which country is the party's primary jurisdiction
  • Standard columns — active flag, start/end dates, audit fields

The primary country​

Each party can have one country marked as primary. This is typically the country of incorporation or the main operating jurisdiction. The primary flag allows the system to quickly determine a party's "home" country without scanning all associations.

Multiple country associations​

A party can be linked to any number of countries. Common patterns include:

  • A multinational corporation associated with every country where it holds a subsidiary
  • A compliance-focused entity associated with every jurisdiction where it has regulatory obligations
  • An individual associated with their country of citizenship and their country of residence

Use in compliance and reporting​

Country associations play an important role in compliance workflows. Knowing which jurisdictions a party is connected to helps determine:

  • Which regulatory frameworks apply (e.g. AML/CFT requirements differ by country)
  • Which data protection rules govern the party's data (e.g. GDPR for EU-associated parties)
  • Which sanctions lists need to be checked

The country association model gives compliance teams a structured, queryable view of geographic exposure without relying on free-text address parsing.