Batch eligibility CSVs now support MBI lookups
Feb 4, 2026
Eligibility checks
You can now run Medicare Beneficiary Identifier (MBI) lookups – with or without a Social Security Number (SSN) – using a CSV batch eligibility check.
Previously, batch eligibility CSVs didn't support some address or SSN fields required for MBI lookups. We've now added several new supported fields to batch eligibility CSVs.
New fields for batch eligibility CSVs
With this update, batch CSVs now support the following fields.
Provider:
providerReferenceIdentification
Subscriber:
subscriberSsnsubscriberGendersubscriberSuffixsubscriberAddress1subscriberAddress2subscriberCitysubscriberAddressStatesubscriberPostalCode
Dependent:
dependentMiddleNamedependentSsndependentGenderdependentSuffixdependentAddress1dependentAddress2dependentCitydependentAddressStatedependentPostalCode
For more information, see our batch eligibility docs.
Required fields for MBI lookups
With Stedi, you run MBI lookups as eligibility checks with the respective MBILU (MBI Lookup with SSN) or MBILUNOSSN (MBI Lookup without SSN) payer IDs. You can now run these checks using batch eligibility CSVs.
Note: MBI lookups require setup through transaction enrollment. See our related documentation.
MBI lookup with an SSN
To run an MBI lookup with an SSN, you must provide:
The patient’s first name –
subscriberFirstNameordependentFirstNameThe patient’s last name –
subscriberLastNameordependentLastNameThe patient’s date of birth –
subscriberDateOfBirthordependentDateOfBirthThe patient’s Social Security Number (SSN) –
subscriberSsnordependentSsn
MBI lookup without an SSN
To run an MBI lookup without an SSN, you must provide:
The patient’s first name –
subscriberFirstNameordependentFirstNameThe patient’s last name –
subscriberLastNameordependentLastNameThe patient’s date of birth –
subscriberDateOfBirthordependentDateOfBirthThe patient’s U.S. state –
subscriberAddressStateordependentAddressState
What to include in MBI lookups
In an eligibility check, the patient may be the subscriber or a dependent. Generally, if the dependent has their own member ID, we recommend providing their information as a subscriber.
We don't recommend including more patient demographic information, such as additional address data, than what's required. Doing so can lower MBI lookup success rates.
For more information, see our MBI lookup docs.
You can now run Medicare Beneficiary Identifier (MBI) lookups – with or without a Social Security Number (SSN) – using a CSV batch eligibility check.
Previously, batch eligibility CSVs didn't support some address or SSN fields required for MBI lookups. We've now added several new supported fields to batch eligibility CSVs.
New fields for batch eligibility CSVs
With this update, batch CSVs now support the following fields.
Provider:
providerReferenceIdentification
Subscriber:
subscriberSsnsubscriberGendersubscriberSuffixsubscriberAddress1subscriberAddress2subscriberCitysubscriberAddressStatesubscriberPostalCode
Dependent:
dependentMiddleNamedependentSsndependentGenderdependentSuffixdependentAddress1dependentAddress2dependentCitydependentAddressStatedependentPostalCode
For more information, see our batch eligibility docs.
Required fields for MBI lookups
With Stedi, you run MBI lookups as eligibility checks with the respective MBILU (MBI Lookup with SSN) or MBILUNOSSN (MBI Lookup without SSN) payer IDs. You can now run these checks using batch eligibility CSVs.
Note: MBI lookups require setup through transaction enrollment. See our related documentation.
MBI lookup with an SSN
To run an MBI lookup with an SSN, you must provide:
The patient’s first name –
subscriberFirstNameordependentFirstNameThe patient’s last name –
subscriberLastNameordependentLastNameThe patient’s date of birth –
subscriberDateOfBirthordependentDateOfBirthThe patient’s Social Security Number (SSN) –
subscriberSsnordependentSsn
MBI lookup without an SSN
To run an MBI lookup without an SSN, you must provide:
The patient’s first name –
subscriberFirstNameordependentFirstNameThe patient’s last name –
subscriberLastNameordependentLastNameThe patient’s date of birth –
subscriberDateOfBirthordependentDateOfBirthThe patient’s U.S. state –
subscriberAddressStateordependentAddressState
What to include in MBI lookups
In an eligibility check, the patient may be the subscriber or a dependent. Generally, if the dependent has their own member ID, we recommend providing their information as a subscriber.
We don't recommend including more patient demographic information, such as additional address data, than what's required. Doing so can lower MBI lookup success rates.
For more information, see our MBI lookup docs.
Get started with Stedi
Get started with Stedi
Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Developers
Resources
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Developers
Resources
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
