Splitting by Payer

Split a multi-payer EDI file into separate files — one per payer. Works with both 837 claims and 835 remittance files.

---

What Is Payer Splitting?

When a batch EDI file contains claims or payments for multiple payers, the By Payer split mode groups everything by payer and produces one output file per unique payer. Each output file contains all the subscribers and claims associated with that payer, wrapped in valid ISA/GS/ST/SE/GE/IEA envelopes.

How It Works

For 837 Files (Claims)

The payer is identified from the NM1*PR segment in each subscriber's 2010BB loop:

HL*2*1*22*0~              ← Subscriber HL
SBR*P*18*GRP100200...~
NM1*IL*1*MARTINEZ*CARLOS...~   ← Subscriber
NM1*PR*2*BCBS OF FLORIDA...~   ← Payer (used for grouping)
CLM*001*250...~            ← This claim goes to the BCBS file

All subscriber HL loops that share the same payer are combined into one output file. If two different subscribers have the same payer (e.g., both have BCBS), they appear together in the same output file.

For 835 Files (Payments)

The payer is identified from the N1*PR segment at the transaction header level. All transactions from the same payer are grouped into one output file.

---

When to Use Payer Splitting

Scenario	Description
Payer-specific clearinghouse routing	Different payers require submission through different clearinghouses
Payer analysis	Isolate claims for a specific payer to review billing patterns or rejection rates
Targeted resubmission	Pull out all claims for one payer after a batch rejection
Payer-level reconciliation	Match payer-specific claim batches against remittance files
Compliance reporting	Separate files by payer for audit or regulatory reporting

---

Step-by-Step Guide

1. Upload Your File

Load your multi-payer 837 or 835 file into EDI Paisan. The file will parse and display in the viewer.

2. Open the Split Panel

Click the Split button in the toolbar to open the splitting panel.

3. Select "By Payer"

Choose By Payer from the split mode dropdown. This mode appears for both 837 and 835 file types.

4. Preview the Results

EDI Paisan shows how many payer groups were found:

Split Results: 4 files
Mode: By Payer

Chunk 1: payer_BCBS_OF_FLORIDA — 3 claims, $910.00
Chunk 2: payer_AETNA_HEALTH_PLANS — 1 claim, $520.00
Chunk 3: payer_UNITED_HEALTHCARE — 1 claim, $310.00
Chunk 4: payer_CIGNA_HEALTHCARE — 1 claim, $350.00

5. Inspect and Download

Click on any chunk to preview its contents. When satisfied, download individual files or use Download All for a batch download.

File naming

Output files are named {original}_payer_{payer_name}.edi for easy identification.

---

How Grouping Works

Grouping Key

Payer identity is determined by:

1. Payer ID (NM109 in NM1*PR) — preferred, since payer names can have minor variations
2. Payer Name (NM103 in NM1*PR) — fallback when payer ID is not present
3. "unknown_payer" — fallback when neither is available

This means "BCBS OF FLORIDA" with ID BCBSFL01 and "BLUE CROSS BLUE SHIELD OF FL" with the same ID BCBSFL01 will correctly group together.

Multiple Subscribers, Same Payer

When the same payer covers multiple subscribers in one file, all their claims are combined:

Original file:
  Subscriber 1 (Carlos Martinez) → Payer: BCBS Florida → 1 claim
  Subscriber 2 (Sarah Johnson)   → Payer: Aetna        → 1 claim
  Subscriber 3 (James Thompson)  → Payer: BCBS Florida → 2 claims

Split by Payer produces:
  File 1: BCBS Florida — 2 subscribers, 3 claims
  File 2: Aetna — 1 subscriber, 1 claim

HL Renumbering

When subscriber HL loops from different positions in the original file are combined, EDI Paisan automatically renumbers the HL segments to maintain sequential numbering. This ensures the output file is valid X12 and ready for submission.

---

Output File Structure

Each output file contains:

1. ISA/GS/ST envelope — With fresh control numbers
2. Header segments — BHT, submitter (NM141), receiver (NM140), billing provider (HL level 20)
3. All subscriber HL loops for this payer — Including subscriber info, patient info (if dependent), and all claims with service lines
4. SE/GE/IEA trailer — With accurate segment and transaction counts

---

Limitations

Single Billing Provider per Output

If the same payer has subscribers under different billing providers (e.g., in a multi-provider batch), the output file uses the billing provider from the first subscriber found for that payer. A warning is displayed when this occurs.

Payer ID Availability

Some 837 files may not include payer IDs (NM109) in the NM1*PR segment. In these cases, grouping falls back to payer name, which may not merge payers with slightly different name spellings.

---

Best Practices

1. Check payer IDs — Files with consistent payer IDs produce the most accurate grouping
2. Preview before download — Verify the expected number of payer groups before downloading
3. Verify claim counts — The sum of claims across all payer files should equal the original file's claim count
4. Use Pro for production — Free tier generates preview control numbers; use Pro for clearinghouse-ready output

---

Related Documentation

• Claim Splitting Overview — All split modes
• How to Split Files — Step-by-step guide
• 837P Reference — Understanding claim structure
• 835 Reference — Understanding payment structure