The job of this console
Generate, transmit, reconcile rejects by fixing enrollment, regenerate.
People · Benefits
Benefits Carrier Files
Exchange files with carriers — generated from enrollments, not a manual census spreadsheet as source.
Scroll to Flowcharts. Scenario: Generate a carrier file from enrollments.
Carrier exchange
Files from elections, not a parallel census
Carrier files generate from live enrollments. Patching only the extract leaves Employee wrong.
Payroll → Benefits carrier files
Route
/benefits/carrier-files
Org flag benefitsEnabled
Payroll Manager · HR Admin · Admin
Seat at the table
HR and payroll admins. Carriers receive files; they do not edit Tracopus.
The working rhythm
After elections, generate, send, fix rejects, repeat.
Moments that bring you here
Monthly feed. Open enrollment dump. A reject file. New carrier.
ⓘ
Enrollment is source
Handle PHI carefully. Integrations may move the file; this console owns the extract.
Flowcharts
1 — Generate from elections
Build the carrier file from enrollments, then transmit.
flowchart TD
A[Open Carrier files] --> B[Select carrier]
B --> C[Generate from enrollments]
C --> D[Transmit]
D --> E{Rejects?}
E -->|Yes| F[Fix enrollment]
E -->|No| G[Done]
- 1OpenPayroll → Benefits carrier files.
- 2GenerateFrom elections.
- 3SendCarrier.
- 4Fix sourceEnrollment, not only the file.
Overview
Carrier files are exchanges. Source of truth for who is on a plan is enrollment on Employee. Integrations may transport.
How to use
1. PHI
Treat files as sensitive.
2. Don’t census in Excel as master
Fix elections.
3. Timing
After enrollment window.