Eligibility PDFs now include submitter transaction IDs and payer trace numbers

Eligibility checks

Stedi's eligibility PDFs now include the submitter transaction ID and payer trace number when they're present in the eligibility response.

Eligibility check JSON response field

271 X12 element

Eligibility PDF label

meta.traceId

BHT03 (Submitter Transaction Identifier)

Submitter transaction ID

meta.subscriberTraceNumbers[].referenceIdentification

TRN02 (Reference Identification) of Loop 2000C (Subscriber) or Loop 2000D (Dependent)

Payer trace number[s]

Both IDs are used to trace eligibility checks across provider and payer systems.

This means you can look up a specific check in your EHR, RCM, or practice management platform, or in the payer's system, using only an eligibility PDF.

You can download eligibility PDFs using the Retrieve Eligibility PDF API endpoint or the Stedi portal.

Submitter transaction IDs

A submitter transaction ID is an identifier you – the submitter – set on an eligibility request. The payer echoes it back in the response.

EHR, RCM, and practice management platforms often use submitter transaction IDs to track eligibility checks.

When present in the response, the submitter transaction ID appears in the Request section at the bottom of the eligibility PDF.

Submitter transaction IDs in eligibility PDFs

Payer trace numbers

A payer trace number is an optional, payer-assigned ID for an eligibility check. Payers can include one or more in the response.

Providers and billers often need to cite payer trace numbers when contacting payer support about a specific eligibility check.

When present in the response, payer trace numbers appear in the Payer row of the summary at the top of the eligibility PDF.

Some payers issue separate trace numbers for the subscriber and a dependent. The PDF lists both, separated by a comma.

Payer trace numbers in eligibility PDFs

Note: Stedi also generates an internal trace number for every check. Eligibility PDFs always exclude Stedi-generated trace numbers.

Stedi's eligibility PDFs now include the submitter transaction ID and payer trace number when they're present in the eligibility response.

Eligibility check JSON response field

271 X12 element

Eligibility PDF label

meta.traceId

BHT03 (Submitter Transaction Identifier)

Submitter transaction ID

meta.subscriberTraceNumbers[].referenceIdentification

TRN02 (Reference Identification) of Loop 2000C (Subscriber) or Loop 2000D (Dependent)

Payer trace number[s]

Both IDs are used to trace eligibility checks across provider and payer systems.

This means you can look up a specific check in your EHR, RCM, or practice management platform, or in the payer's system, using only an eligibility PDF.

You can download eligibility PDFs using the Retrieve Eligibility PDF API endpoint or the Stedi portal.

Submitter transaction IDs

A submitter transaction ID is an identifier you – the submitter – set on an eligibility request. The payer echoes it back in the response.

EHR, RCM, and practice management platforms often use submitter transaction IDs to track eligibility checks.

When present in the response, the submitter transaction ID appears in the Request section at the bottom of the eligibility PDF.

Submitter transaction IDs in eligibility PDFs

Payer trace numbers

A payer trace number is an optional, payer-assigned ID for an eligibility check. Payers can include one or more in the response.

Providers and billers often need to cite payer trace numbers when contacting payer support about a specific eligibility check.

When present in the response, payer trace numbers appear in the Payer row of the summary at the top of the eligibility PDF.

Some payers issue separate trace numbers for the subscriber and a dependent. The PDF lists both, separated by a comma.

Payer trace numbers in eligibility PDFs

Note: Stedi also generates an internal trace number for every check. Eligibility PDFs always exclude Stedi-generated trace numbers.

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

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.