> ## Documentation Index > Fetch the complete documentation index at: https://docs.getsolum.com/llms.txt > Use this file to discover all available pages before exploring further. # Insurance Monitoring > Submit multiple eligibility checks at once using a CSV file # Batch Eligibility Checks Run eligibility checks for multiple patients in a single upload. Prepare a CSV file with patient and provider details, upload it on the [batch eligibility page](https://app.getsolum.com/eligibility/batches/new), and Solum processes every row as an individual 270/271 transaction. ## Quick Start 1. **Download the CSV template** from the batch creation page. 2. **Fill in your data** — one row per eligibility check. 3. **Upload the CSV** on the batch page. 4. **Review validation** — fix any errors shown instantly. 5. **Submit** — Solum sends the checks and you can track progress from the batches list. *** ## CSV Format Your CSV must include a header row with column names in **camelCase** exactly as shown below. Column order does not matter. ### Required Fields | Column Name | Description | Format | Example | | -------------------------------------------- | ------------------------------- | -------------------- | ----------------- | | `subscriberFirstName` | Patient first name | Text | `John` | | `subscriberLastName` | Patient last name | Text | `Doe` | | `subscriberDateOfBirth` | Patient date of birth | `YYYY-MM-DD` | `1990-01-15` | | `subscriberMemberId` | Insurance member / policy ID | Text | `ABC123456789` | | `tradingPartnerServiceId` | Payer ID (trading partner) | Text | `BCBSMA` | | `providerOrganizationName` | Rendering provider name | Text | `Acme Healthcare` | | `providerNpi` **or** `serviceProviderNumber` | Provider identifier (see below) | 10-digit NPI or text | `1234567890` | | `serviceTypeCodes` | Service type code(s) | Comma-separated | `30` or `30,33` | | `encounterDateOfService` | Date of service | `YYYY-MM-DD` | `2026-01-23` | ### Optional Fields | Column Name | Description | Format | Example | | -------------------------------- | --------------------------- | ------------ | ------------ | | `submitterTransactionIdentifier` | Your unique ID for this row | Text | `CHECK-001` | | `dependentFirstName` | Dependent first name | Text | `Jane` | | `dependentLastName` | Dependent last name | Text | `Doe` | | `dependentDateOfBirth` | Dependent date of birth | `YYYY-MM-DD` | `2015-06-20` | | `dependentMemberId` | Dependent member ID | Text | `DEP987654` | | `dependentRelationshipCode` | Relationship to subscriber | Code | `19` | Any columns not listed above are ignored (you will see a warning). *** ## Provider Identification Every row requires **exactly one** of these two columns: * **`providerNpi`** — The provider's 10-digit National Provider Identifier. * **`serviceProviderNumber`** — An alternative provider number assigned by the payer. Including both on the same row is an error. Omitting both is also an error. *** ## Service Type Codes The `serviceTypeCodes` column accepts a single code or multiple comma-separated codes. | Value | Meaning | | ------- | ---------------------------- | | `30` | Health Benefit Plan Coverage | | `33` | Chiropractic | | `47` | Hospital | | `88` | Pharmacy | | `30,47` | Multiple codes in one check | For a full list of X12 service type codes, see the [ASC X12 270/271 reference](https://x12.org). *** ## Date Formats All date fields must use **YYYY-MM-DD** format (e.g., `2026-01-15`). If your CSV contains dates in `YYYYMMDD` format (e.g., `20260115`), they are automatically converted during parsing. However, the recommended format is `YYYY-MM-DD`. *** ## Duplicate Detection Solum prevents accidental duplicate rows in two ways: ### With `submitterTransactionIdentifier` If you provide this column, each value must be unique within the file. Two rows with the same identifier are flagged as duplicates. ### Without `submitterTransactionIdentifier` A composite key is built from these fields: * `subscriberMemberId` * `subscriberFirstName` * `subscriberLastName` * `subscriberDateOfBirth` * `tradingPartnerServiceId` * `encounterDateOfService` * `serviceTypeCodes` If two rows have identical values across all these fields, the second row is flagged as a duplicate. *** ## Validation Validation runs instantly in your browser when you upload a file. No data is sent to the server until you click Submit. ### What is checked * All required fields are present and non-empty * Dates are in a valid format * NPI is exactly 10 digits (if used) * Exactly one provider identifier per row * No duplicate rows * At least one data row exists ### Error report If validation fails, you can **download an error report** — a CSV listing every error with its row number, column, and message. Fix the issues in your source file and re-upload. *** ## Troubleshooting | Problem | Fix | | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | "Required field is empty" | Check that the column exists in your header row and the cell has a value. | | "Must have exactly one of provider\_npi or service\_provider\_number" | Each row needs either `providerNpi` or `serviceProviderNumber`, but not both. | | "Invalid date format" | Use `YYYY-MM-DD` (e.g., `1990-01-15`). | | "NPI must be exactly 10 digits" | Verify the NPI — it must be 10 numeric digits with no spaces or dashes. | | "Duplicate row data" | Two rows have identical key fields. Add a `submitterTransactionIdentifier` column or remove the duplicate. | | "Unknown columns will be ignored" | A column header doesn't match any known field. Check for typos in the header name. | | "No data rows found" | The file has a header but no data rows, or is empty. |