Skip to content

CSV to 270 Generation

Need to check patient eligibility but don't have an EDI-capable billing system? EDI Paisan lets you generate valid 270 (Eligibility Inquiry) files from a simple CSV spreadsheet.

Upload your patient data → Preview the generated 270 → Download and submit to your clearinghouse.


Who Is This For?

This feature is designed for:

  • Small practices without full practice management software
  • Billers who need to check eligibility for multiple patients
  • Anyone who has patient data in a spreadsheet and needs to verify coverage

You don't need to understand X12 syntax. Just fill in the CSV template and let EDI Paisan handle the rest.


How It Works

Your CSV → EDI Paisan → Valid 270 File → Clearinghouse → Payer
  1. Prepare your CSV with patient and provider information
  2. Upload to EDI Paisan
  3. Preview the generated 270 and review any validation warnings
  4. Download the file (Pro tier required)
  5. Submit to your clearinghouse for eligibility responses

CSV Format

Your CSV must include specific columns. Here's the required format:

Required Columns

ColumnDescriptionExample
subscriber_last_nameSubscriber's last nameSmith
subscriber_first_nameSubscriber's first nameJohn
subscriber_member_idInsurance member IDMEM123456789
subscriber_dobDate of birth (MM/DD/YYYY or YYYY-MM-DD)03/15/1985
subscriber_genderGender (M/F)M
payer_idPayer/Insurance IDBCBS01
payer_namePayer nameBlue Cross Blue Shield
provider_npiYour NPI number1234567890
provider_nameYour practice nameABC Medical Group
service_dateDate of service (MM/DD/YYYY or YYYY-MM-DD)01/15/2024

Optional Columns

ColumnDescriptionExample
dependent_last_nameDependent's last name (if checking dependent)Smith
dependent_first_nameDependent's first nameJane
dependent_dobDependent's date of birth05/20/2010
dependent_genderDependent's genderF
dependent_relationshipRelationship to subscriber19 (child)
service_typeService type code (default: 30 = all)30
trace_numberYour tracking referenceINQ-2024-001

Example CSV

Basic Example (Subscribers Only)

csv
subscriber_last_name,subscriber_first_name,subscriber_member_id,subscriber_dob,subscriber_gender,payer_id,payer_name,provider_npi,provider_name,service_date
Smith,John,MEM123456,03/15/1985,M,BCBS01,Blue Cross Blue Shield,1234567890,ABC Medical Group,01/15/2024
Johnson,Mary,MEM789012,07/22/1990,F,AETNA01,Aetna,1234567890,ABC Medical Group,01/15/2024
Williams,Robert,MEM345678,11/08/1978,M,UHC01,United Healthcare,1234567890,ABC Medical Group,01/15/2024

With Dependents

csv
subscriber_last_name,subscriber_first_name,subscriber_member_id,subscriber_dob,subscriber_gender,dependent_last_name,dependent_first_name,dependent_dob,dependent_gender,dependent_relationship,payer_id,payer_name,provider_npi,provider_name,service_date
Smith,John,MEM123456,03/15/1985,M,Smith,Jane,05/20/2010,F,19,BCBS01,Blue Cross Blue Shield,1234567890,ABC Medical Group,01/15/2024

With Service Types

csv
subscriber_last_name,subscriber_first_name,subscriber_member_id,subscriber_dob,subscriber_gender,payer_id,payer_name,provider_npi,provider_name,service_date,service_type
Smith,John,MEM123456,03/15/1985,M,BCBS01,Blue Cross Blue Shield,1234567890,ABC Medical Group,01/15/2024,30
Smith,John,MEM123456,03/15/1985,M,BCBS01,Blue Cross Blue Shield,1234567890,ABC Medical Group,01/15/2024,35

TIP

To check multiple service types for the same patient, include multiple rows with different service_type values. EDI Paisan will combine them into a single inquiry.


Service Type Codes

The service_type column controls what benefit information you're requesting:

CodeDescription
30Health Benefit Plan Coverage (all benefits) — recommended default
1Medical Care
33Chiropractic
35Dental Care
47Hospital
48Hospital - Inpatient
50Hospital - Outpatient
51Hospital - Emergency Accident
52Hospital - Emergency Medical
86Emergency Services
88Pharmacy
98Professional (Physician) Visit - Office

If omitted, EDI Paisan defaults to 30 (all benefits).


Relationship Codes

For dependent inquiries, use these dependent_relationship codes:

CodeRelationship
01Spouse
19Child
20Employee
21Unknown
39Organ Donor
40Cadaver Donor
53Life Partner
G8Other Relationship

Validation & Preview

After uploading your CSV, EDI Paisan:

  1. Validates your data for required fields and formatting
  2. Previews the generated 270 in the file viewer
  3. Shows warnings for any issues that might cause rejections

Common Validation Warnings

WarningMeaningFix
Missing NPIProvider NPI is requiredAdd valid 10-digit NPI
Invalid date formatDate couldn't be parsedUse MM/DD/YYYY or YYYY-MM-DD
Missing member IDSubscriber member ID requiredAdd insurance member ID
Unknown payerPayer ID not recognizedVerify payer ID with clearinghouse

:::note Warnings don't prevent generation, but the resulting 270 may be rejected by payers. :::


Free vs Pro

FeatureFreePro
Upload CSV
Preview generated 270
View validation results
Download 270 file
Batch processing (multiple files)

Free tier lets you see exactly what your 270 will look like before committing to Pro. You can verify your CSV format and data are correct.

Pro tier unlocks the download — the file you can actually submit to your clearinghouse.


Step-by-Step Guide

1. Prepare Your CSV

  • Use the column headers exactly as shown above
  • Ensure dates are formatted consistently (MM/DD/YYYY recommended)
  • Double-check member IDs against insurance cards
  • Use your valid NPI number

2. Upload to EDI Paisan

  1. Navigate to Tools → CSV to 270 (or equivalent)
  2. Click Upload CSV or drag and drop your file
  3. Wait for processing

3. Review the Preview

  • Check that patient names and IDs are correct
  • Verify the payer information
  • Review any validation warnings
  • Use the 270 viewer to inspect the generated structure

4. Download (Pro)

If everything looks correct:

  1. Click Download 270
  2. Save the .edi or .270 file
  3. Submit to your clearinghouse

5. Wait for 271 Responses

Your clearinghouse will return 271 (Eligibility Response) files — one response per inquiry. Upload those to EDI Paisan to view the coverage details.


Troubleshooting

"Invalid CSV format"

Cause: Missing required columns or incorrect headers.

Fix: Ensure your CSV includes all required columns with exact header names (case-sensitive).

"Date parsing failed"

Cause: Dates aren't in a recognized format.

Fix: Use MM/DD/YYYY (e.g., 01/15/2024) or YYYY-MM-DD (e.g., 2024-01-15).

"NPI validation failed"

Cause: NPI is not 10 digits or fails checksum validation.

Fix: Verify your NPI at NPPES NPI Registry.

"Member ID not found" (from payer)

Cause: The member ID doesn't match the payer's records.

Fix: Verify the member ID from the patient's insurance card. Check for typos or missing digits.

"Payer not recognized" (from clearinghouse)

Cause: The payer ID isn't valid for your clearinghouse.

Fix: Contact your clearinghouse for the correct payer ID. Different clearinghouses may use different payer identifiers.

Blank or empty responses

Cause: Payer couldn't process the inquiry.

Fix: Check for AAA rejection segments in the 271. Common reasons:

  • Invalid date of birth
  • Member not found
  • Service date outside coverage period

Best Practices

Before Uploading

  • ✅ Verify member IDs against insurance cards
  • ✅ Confirm your NPI is active and valid
  • ✅ Use consistent date formats
  • ✅ Include trace numbers for easy tracking

After Downloading

  • ✅ Submit promptly — eligibility can change
  • ✅ Keep copies of your 270s for records
  • ✅ Match 271 responses using trace numbers

General Tips

  • Batch similar requests — Group patients by payer for easier tracking
  • Check before appointments — Run eligibility 1-2 days before scheduled visits
  • Re-verify for procedures — Coverage can change; always verify before high-cost procedures

Your Friend in EDI