Business Graph: Understanding Corporate Structures for KYB

How graph-based data models reveal business relationships, ownership structures, and risk patterns that traditional databases miss.

10 min read

A business graph is a data model that represents companies as interconnected nodes—brands, legal entities, locations, and people—linked by ownership, operational, and affiliation relationships. Unlike traditional databases that store business records as isolated rows, graphs make relationships first-class data, revealing structures that matter for KYB verification.

This guide explains how business graphs work, what they reveal, and why they’re essential for advanced KYB verification and risk detection.

Why Graphs?

The Limits of Tables

Traditional databases store business information in tables:

Business Name	Address	EIN	State	Owner
GTL Services LLC	1209 Orange St	12-3456789	DE	Smith Holdings LLC

This works for simple lookups: “Find GTL Services LLC.” But it fails when relationships matter:

Who ultimately owns GTL Services LLC? (Smith Holdings is another company)
What other businesses share this address?
Is this the same entity operating as “Green Thumb Landscaping” elsewhere?
Are there concerning patterns in the ownership network?

To answer these questions with tables, you need complex joins, recursive queries, and significant engineering. With graphs, you just traverse relationships.

Graphs Make Relationships Explicit

In a graph, both entities and their connections are stored:

[Person: Jane Smith]
       │
       │ owns (60%)
       ↓
[Entity: Smith Holdings LLC]
       │
       │ owns (100%)
       ↓
[Entity: GTL Services LLC]
       │
       ├── operates_as → [Brand: Green Thumb Landscaping]
       │
       ├── registered_at → [Location: 1209 Orange St, Wilmington DE]
       │
       └── located_at → [Location: 456 Main St, Columbus OH]

Query: “Who ultimately owns GTL Services LLC?” Graph traversal: Start at GTL Services LLC → follow ‘owns’ edges upward → reach Jane Smith.

Graph Structure

Node Types

Business graphs typically include these node types:

Person nodes: Natural persons who own, control, or represent businesses

Beneficial owners
Directors and officers
Registered agents (individuals)
Authorized signers

Entity nodes: Legal structures recognized by jurisdictions

Corporations
LLCs
Partnerships
Trusts
Foreign entities

Brand nodes: Customer-facing business identities

Trade names (DBAs)
Franchise brands
Product/service brands

Location nodes: Physical and registered addresses

Headquarters
Operating locations
Registered agent addresses
Mailing addresses

Edge Types (Relationships)

Edges connect nodes with typed, often attributed relationships:

Ownership edges:

owns: Person → Entity, Entity → Entity
Attributes: ownership percentage, effective date, type (direct/indirect)

Operational edges:

operates_as: Entity → Brand
located_at: Brand → Location, Entity → Location
registered_at: Entity → Location

Role edges:

officer_of: Person → Entity (with role: CEO, CFO, etc.)
director_of: Person → Entity
agent_for: Person → Entity, Entity → Entity

Temporal attributes:

Start/end dates for relationships
Historical versions
Change events

What Graphs Reveal

Ownership Chains

The primary use case: tracing beneficial ownership through corporate layers.

Simple ownership:

Jane Smith (Person)
    │ owns 100%
    ↓
ABC Company (Entity)

UBO: Jane Smith owns 100%

Layered ownership:

Jane Smith (Person)
    │ owns 60%
    ↓
Smith Holdings LLC (Entity)
    │ owns 80%
    ↓
GTL Services LLC (Entity)

Effective ownership: Jane Smith owns 60% × 80% = 48% of GTL Services LLC

Complex ownership:

Jane Smith ──owns 40%──→ Holding A ──owns 50%──→ Target Co
          ──owns 60%──→ Holding B ──owns 30%──→ Target Co

Total effective ownership: (40% × 50%) + (60% × 30%) = 20% + 18% = 38%

Graphs handle these calculations through path traversal and aggregation.

Hidden Connections

Graphs reveal relationships that aren’t obvious from individual records:

Shared registered agents:

[Agent: ABC Registered Agents Inc.]
    │
    ├── agent_for → [Entity: Company 1]
    ├── agent_for → [Entity: Company 2]
    ├── agent_for → [Entity: Company 3]
    └── agent_for → [872 more entities...]

A formation agent servicing hundreds of entities isn’t suspicious alone. But if those entities were all formed on the same day, share the same beneficial owner, and are now applying for merchant accounts…

Address overlap:

[Location: 1209 Orange St, Wilmington DE]
    │
    ├── registered_at ← [Entity: Company A]
    ├── registered_at ← [Entity: Company B]
    └── registered_at ← [15,000 more entities...]

This is a well-known registered agent address (Corporation Trust Center). Expected for Delaware entities. But if a company claims this as their operating location, that’s a red flag.

Officer networks:

[Person: John Doe]
    │
    ├── officer_of → [Entity: Recently formed LLC 1]
    ├── officer_of → [Entity: Recently formed LLC 2]
    ├── officer_of → [Entity: Recently formed LLC 3]
    └── [all filed same day, same agent, similar names...]

Patterns emerge that record-by-record review misses.

Network Patterns

Graph analysis reveals structural patterns:

Star pattern: One node connected to many others

Person connected to many entities → possible nominee, formation agent, or serial entrepreneur
Address connected to many entities → registered agent office or possible address fraud

Chain pattern: Sequential ownership layers

Depth of ownership chain correlates with complexity/opacity
Very deep chains may indicate intentional obscuration

Circular pattern: Ownership loops

A owns B owns C owns A
May be legitimate (cross-holdings) or concerning (ownership obscuration)

Cluster pattern: Densely connected groups

Group of entities sharing addresses, officers, formation dates
May indicate related-party network, shell company factory, or fraud ring

Temporal Patterns

Graphs with temporal data reveal evolution:

Burst formation: Many entities created in short period
Ownership churning: Frequent ownership changes
Status changes: Active → Dissolved → Reinstated patterns
Officer turnover: Frequent officer/director changes

Graphs in KYB Workflows

Verification

Enrich verification with graph context:

Application received: “Green Thumb Landscaping” at “456 Main St, Columbus OH”

Graph lookup:

Resolve “Green Thumb Landscaping” to known brands
Find connected entities (GTL Services LLC)
Verify entity exists and is active
Retrieve ownership graph
Identify beneficial owners

Result: Complete picture of business identity and ownership for verification decision.

Risk Scoring

Graph features improve risk models:

Feature	Calculation	Risk Signal
Ownership depth	Layers to reach natural person	Complexity/opacity
Address concentration	Other entities at same address	Shell company risk
Agent entity count	Other entities sharing agent	Formation agent pattern
Formation timing	Days since registration	Established vs. new
Network density	Connections among related entities	Related-party risk
Officer overlap	Shared officers with other applicants	Potential fraud ring

These features are impossible to calculate without graph structure.

Ongoing Monitoring

Graphs enable event-driven monitoring:

Change detection:

New ownership edge added → ownership change alert
New entity added to owner’s network → related entity alert
Officer resignation → control change alert
Entity status change → operational status alert

Periodic review:

Re-traverse ownership for UBO refresh
Check for new concerning patterns
Validate continued accuracy

Building a Business Graph

Data Sources

Graphs are constructed from multiple sources:

Authoritative sources:

Secretary of State filings (entities, agents, officers)
Business registries (ownership, status)
UBO registries (where available)

Commercial sources:

Business information aggregators
Corporate data providers
Commercial registry compilations

Web/public sources:

Business websites (brands, locations)
Google Business Profiles
Social media presence

Transaction/operational sources:

Payment processing records
Customer applications
Internal CRM data

Entity Resolution

Entity resolution is prerequisite to graph construction. Before connecting nodes with edges, you must know which records represent the same entity.

The graph actually helps with resolution—shared relationships provide evidence for matching:

Two records share an officer → more likely same entity
Two records share address AND phone → strong match signal

This creates a virtuous cycle: better resolution enables richer graphs; richer graphs improve resolution.

Graph Technology

Graph databases: Purpose-built for graph storage and traversal

Neo4j, Amazon Neptune, TigerGraph
Native graph query languages (Cypher, Gremlin)
Optimized for relationship traversal

Relational with graph queries: Graph features on traditional databases

PostgreSQL with recursive CTEs
SQL Server with graph tables
Slower for deep traversal but familiar

Knowledge graph platforms: Semantic graph infrastructure

Schema and ontology management
Reasoning and inference capabilities
Often used for enterprise knowledge management

Maintenance

Graphs require ongoing maintenance:

Regular updates:

Pull fresh data from sources
Apply changes to graph
Version historical state

Quality monitoring:

Detect orphan nodes (unconnected entities)
Identify data gaps
Validate relationship accuracy

Performance tuning:

Index frequently traversed paths
Partition large graphs
Cache common queries

Practical Considerations

Starting Simple

You don’t need a full knowledge graph to benefit from graph thinking:

Phase 1: Ownership chains

Store ownership relationships in any database
Query with recursive joins or simple traversal
Calculate effective ownership percentages

Phase 2: Address and agent networks

Link entities sharing addresses
Identify registered agent patterns
Add basic network analysis

Phase 3: Full business graph

Multiple node types (persons, entities, brands, locations)
Multiple edge types with attributes
Graph database for performance
Advanced analytics

Buy vs. Build

Build if:

Core competitive advantage
Unique data sources
Specific requirements not met by vendors
Graph expertise in-house

Buy/partner if:

Speed to market critical
Standard KYB use cases
Limited graph expertise
Prefer operational simplicity

Many organizations use commercial business graphs for baseline coverage and enrich with proprietary data.

Key Takeaways

Graphs model relationships as first-class data—not an afterthought
Ownership chains become traversable with simple queries
Hidden patterns emerge—shell companies, fraud rings, suspicious networks
Risk scoring improves with graph features that tables can’t provide
Entity resolution and graphs reinforce each other—better resolution enables richer graphs
Start simple—ownership chains add value before full graph infrastructure
Maintenance matters—graphs require ongoing updates and quality monitoring

What is KYB? — Foundational overview
Entity Resolution — The foundation for graph construction
UBO Verification — Beneficial ownership verification
Business Graph (glossary) — Quick reference
Formation Agent — Understanding shell company patterns