Branches
The branches entity contains branch location reference data.
Overview
Branch data enables:
- Geographic analysis of customer activity
- Branch-level risk assessment
- Regulatory reporting with branch details
Entity Relationships
Branches connect to customers (primary_branch) and accounts (branch_number).
Key Fields
| Field | Description | Example |
|---|---|---|
number | Branch identifier | 001, 0025 |
name | Branch name | Downtown Main |
routing_transit_number | ABA routing number | 123456789 |
city | City | Nashville |
state_code | State abbreviation | TN |
Required Fields
At minimum, include:
number- Branch identifier (matches references in other entities)name- Human-readable branch name
Recommended:
routing_transit_number- For wire/ACH routingcity,state_code,postal_code- Location details
Best Practices
- Consistent branch numbers - Match the format used in account and customer data
- Include all branches - Even if some have minimal activity
- Update as needed - Submit when branches open, close, or move
Field Reference
See Branches Field Reference for the complete field list with types and descriptions.