Skip to main content

Overview

BenefitFlow delivers six CSV datasets via SFTP, refreshed weekly every Saturday. Together they provide a complete picture of US employer-sponsored benefits: which employers offer what coverage, through which carriers, brokered by whom, at which offices, and the people at those brokerages and employers.
BenefitFlow aggregates data from multiple public and proprietary sources. For a complete overview, see Where does BenefitFlow’s data come from?

Entity Relationships

The six datasets connect through shared identifiers. Use these keys to join across files.

Join Keys

Key Relationships

  • Employer → Policy is one-to-many. A single employer can have multiple policies (e.g., one for Health, one for Dental, one for Life). The Policy file is the most granular view of coverage.
  • Employer → Broker is surfaced two ways: the Employer file carries denormalized “Primary Broker” fields (the broker with the most business), while the Policy file shows the specific broker on each individual policy. These can differ — an employer may use Broker A for health and Broker B for dental.
  • Broker → Office → Contact is hierarchical. A broker firm (e.g., “Lockton Companies”) has many offices, and each contact is associated with one office.
  • Employer → Employer Contact is one-to-many. Employer contacts are the people at the employer (HR, benefits, executives) rather than at the brokerage. They share the same contact data model as broker contacts but are linked to an employer instead of a broker.

Employer

One row per employer. Includes firmographics, benefits program details, primary broker relationship, and P&C insurance information.
Sources: Form 5500, state-level filings, employee review platforms, Proprietary · Refresh: Weekly (Saturday)

Policy

One row per policy per employer. An employer with Health, Dental, and Life coverage will have at least three rows. This is the most granular view of benefits coverage.
Sources: Form 5500 · Refresh: Weekly (Saturday)

Broker

One row per brokerage firm. Aggregated metrics across all of the broker’s clients, offices, and contacts.
Sources: Form 5500, Proprietary · Refresh: Weekly (Saturday)

Broker Office

One row per broker office location. Each office belongs to one broker firm and includes aggregated metrics for the clients and contacts associated with that office.
Sources: Form 5500, Proprietary · Refresh: Weekly (Saturday)

Broker Contact

One row per individual contact at a brokerage. Includes professional details, licensing information, the office they are associated with, and aggregated firm-level metrics for the parent brokerage.
Sources: Public profiles, third-party data partners, State Departments of Insurance · Refresh: Weekly (Saturday)
Updated May 14, 2026. Firm-level fields (Headquarters, Total Office Locations, Total Clients, Total Contacts, Total Commissions, Total Carrier Premiums, BenefitFlow Broker URL) were added so that contact records carry the associated brokerage account fields. Five office fields were renamed with the Closest Broker Office prefix to disambiguate them from the new firm-level fields. See SFTP Schema Changes — May 14, 2026 for the full changelog.

Employer Contact

One row per individual contact at an employer. Includes professional details, employer association, and aggregated employer-level firmographic and benefits fields for the associated company.
Sources: Public profiles, third-party data partners · Refresh: Weekly (Saturday)
Updated May 14, 2026. Employer-level fields (NAICS, EIN, location, employee counts, funding, lines of business, carriers, renewal dates, primary broker, P&C broker/carrier, PEO, accounting firm, benefits rating, BenefitFlow Employer URL) were added so that contact records carry the associated employer account fields. License Types and NPN Number were removed (not applicable to employer contacts). Five office fields were renamed with the Primary Broker Reported Office prefix to disambiguate them from the new closest-office fields. See SFTP Schema Changes — May 14, 2026 for the full changelog.

Data Delivery Details

For connection setup and SFTP client configuration, see the Bulk Data Access Setup Guide.

Implementation Notes

Many fields contain commas within values (e.g., Lines of Business, addresses). Always use a proper CSV parser — do not split on commas.
Fields like EIN, NAICS Code, ZIP Code, and NPN Number are prefixed with a single quote (') to prevent spreadsheet tools from stripping leading zeros. Strip the leading quote during ingestion and treat as strings, not numbers.
All BenefitFlow IDs — Employer ID, Broker ID, Broker Office ID, Closest Office ID, Primary Broker ID, and Primary Broker Closest Office ID — are UUIDs (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
One-time ID change (June 2026). Broker, Office, and Contact-Office IDs were previously 32-character hex hashes and were re-keyed to UUIDs. The new values are stable going forward, but they do not match the old hash values. If you cached IDs from a snapshot dated before June 6, 2026, re-pull the current files and re-join — old hash-based joins will return no matches.
The Policy and Employer files include denormalized broker and office fields for convenience. The Broker and Broker Office files are the canonical source for broker-level data.
When no broker is identified for a record, the broker name may show NO Broker and the broker ID field is left blank. Filter these out when analyzing broker relationships. (In snapshots before the June 2026 ID change, the Broker ID was instead populated with the sentinel ffffffffffffffffffffffffffffffff — treat that legacy value the same as blank.)
Record Type, Lead Source, and BenefitFlow User contain the same value for every row in a given file. They exist for system compatibility and can be safely ignored during analysis.
Two broker office locations appear on Employer and Policy records. Closest Office is the BenefitFlow-determined office nearest to the employer. Reported Office is the office listed on the original Form 5500 filing. These often differ — the filing may reference a headquarters while the closest office reflects the local servicing branch.
Last modified on June 8, 2026