Changelog

Claim edit: Duplicate contract amount on a service line

Stedi now rejects 837P professional and 837D dental claims that report the same contract amount on a service line and at the claim level.

Important: Most claims don't include a contract amount. Submitters send one only when the provider’s contract with the payer requires it. Confirm with the payer before including it.

What is a contract amount?

A contract amount is the dollar amount a payer agreed to pay for a service in their contract with the provider. This amount often differs from the provider’s billed charge amount.

When you submit a claim, you can specify the contract amount at two levels: the claim level and the service line level.

The claim-level contract amount covers the whole claim.

Claim-level contract amount

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.claimContractInformation.contractAmountCN1-02 (Contract Amount) of Loop 2300 (Claim Information)
837D dentalclaimInformation.claimContractInformation.contractAmountCN1-02 (Contract Amount) of Loop 2300 (Claim Information)

The service-line contract amount specifies the contracted dollar amount for a specific service on the claim. A claim can have multiple service-line contract amounts – one for each service.

Service-line contract amount

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.serviceLines[].contractInformation.contractAmountCN1-02 (Contract Amount) of Loop 2400 (Service Line Number)
837D dentalclaimInformation.serviceLines[].contractInformation.contractAmountCN1-02 (Contract Amount) of Loop 2400 (Service Line Number)

How the edit works

A service-line contract amount should not duplicate the claim-level contract amount.

Some payer systems treat service-line contract amounts as an override of the claim-level value. These systems may read a duplicate contract amount at the claim and service line level as a conflicting or erroneous override.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Service Line Contract Amount. The submitted service-line contract amount on line 1 must not equal the claim-level contract amount, 500. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>545*[DATE]*U*[AMOUNT]******A8>710**Invalid Service Line Contract Amount. The submitted service-line contract amount on line 1 must not equal the claim-level contract amount, 500. Correct and resubmit.~

Resolution tip

If a service line has the same contracted amount as the claim, remove the service line’s contract amount. The claim-level amount already applies to every line on the claim.

Claim edit: Invalid EPSDT certification and condition indicator combination

Stedi now rejects 837P professional and 837I institutional claims where the Early and Periodic Screening, Diagnostic, and Treatment (EPSDT) certification indicator and the first EPSDT condition indicator contradict each other.

What are EPSDT certification and condition indicators?

Early and Periodic Screening, Diagnostic, and Treatment (EPSDT) is a mandatory federal Medicaid benefit for children and other beneficiaries under the age of 21. It covers routine checkups and screenings, plus any follow-up care those screenings show the patient needs.

837P professional and 837I institutional claims include dedicated fields for EPSDT services. A payer uses these fields to decide how coverage rules apply and whether to approve the services on the claim:

  • EPSDT Certification Condition Code Applies Indicator, also called the EPSDT certification indicator – A yes/no flag for whether the patient needs follow-up care based on the screening. A value of N indicates the patient does not need follow-up care.

  • EPSDT condition indicators – Two-character codes that describe whether the patient was referred for follow-up care and the outcome of that referral. For example: AV (Referral Available – Not Used), S2 (Under Treatment), or ST (New Services Requested). A value of NU (Not Used) indicates the screening didn’t result in a referral for follow-up care. A claim can contain one or more EPSDT condition indicators.

EPSDT certification indicator

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.epsdtReferral.certificationConditionCodeAppliesIndicatorCRC-02 (Certification Condition Code Applies Indicator) of Loop 2300 (Claim Information)
837I institutionalclaimInformation.epsdtReferral.certificationConditionCodeAppliesIndicatorCRC-02 (Certification Condition Code Applies Indicator) of Loop 2300 (Claim Information)

EPSDT condition indicators

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.epsdtReferral.conditionCodes[]CRC-03 (Condition Indicator) of Loop 2300 (Claim Information)
837I institutionalclaimInformation.epsdtReferral.conditionCodes[]CRC-03 (Condition Indicator) of Loop 2300 (Claim Information)

How the edit works

This edit compares the EPSDT certification indicator against the first EPSDT condition indicator:

  • If the first condition indicator is NU (Not Used), the EPSDT certification indicator must be N.

  • If the EPSDT certification indicator is N, the first condition indicator must be NU.

If the EPSDT certification indicator and first EPSDT condition indicator contradict each other, Stedi rejects the claim. This prevents later payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

If the first condition indicator is NU but the EPSDT certification indicator is not N:

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid EPSDT Condition Indicator. When the EPSDT condition indicator is 'NU' (not used), the EPSDT certification code applies indicator must be 'N' (no). Submitted indicator is 'Y'. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If the EPSDT certification indicator is N but the first EPSDT condition indicator is not NU:

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid EPSDT Certification Condition Code Applies Indicator. When the EPSDT certification applies indicator is 'N' (no), the EPSDT condition indicator must be 'NU' (not used). Submitted indicator is 'AV'. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

If the first condition indicator is NU but the EPSDT certification indicator is not N:

STC*A7>527*[DATE]*U*[AMOUNT]******A8>564**Invalid EPSDT Condition Indicator. When the EPSDT condition indicator is 'NU' (not used), the EPSDT certification code applies indicator must be 'N' (no). Submitted indicator is 'Y'. Correct and resubmit.~

If the EPSDT certification indicator is N but the first EPSDT condition indicator is not NU:

STC*A7>564*[DATE]*U*[AMOUNT]******A8>527**Invalid EPSDT Certification Condition Code Applies Indicator. When the EPSDT certification applies indicator is 'N' (no), the EPSDT condition indicator must be 'NU' (not used). Submitted indicator is 'AV'. Correct and resubmit.~

Resolution tips

To avoid triggering this edit, match the claim’s EPSDT certification indicator and its first EPSDT condition indicator:

  • Use EPSDT certification indicator N with an EPSDT condition indicator of NU (Not Used).

  • Use EPSDT certification indicator Y with an EPSDT condition indicator of AV (Referral Available – Not Used), S2 (Under Treatment), or ST (New Services Requested).

Stedi is now CAQH CORE certified for claims, claim status checks, and ERAs

CAQH CORE has officially certified Stedi for claims, real-time claim status checks, and payment and remittance (ERAs).

Stedi was already CORE certified for eligibility checks. With this certification, we’re now CORE certified for all major HIPAA transaction types.

What is CAQH CORE?

The Council for Affordable Quality Healthcare (CAQH), now DataSpring, is a non-profit backed by major health insurers and provider groups. The U.S. Department of Health and Human Services (HHS) designated CAQH as the official authoring entity for the operating rules that govern HIPAA administrative transactions.

HIPAA requires payers, providers, and clearinghouses to exchange transactions using the X12 EDI format. X12 defines the structure of each transaction, but leaves room for interpretation on response content, error handling, connectivity, and system availability. That gap creates inconsistencies that make systems harder to integrate.

CAQH created the Committee on Operating Rules for Information Exchange (CORE) to close that gap. The CORE Operating Rules build on X12 with stricter requirements for data content, standardized error messages, connectivity, and uptime and performance benchmarks. Certification confirms, through independent testing, that a system meets those rules.

What Stedi’s certification covers

Stedi is now CORE certified for:

Why CORE certification matters

CORE certification is one of the few public signals that a clearinghouse's systems behave as expected. It confirms, through independent testing, that we meet defined benchmarks for each transaction type: standardized error codes, connectivity requirements, and uptime and response-time floors. Some payers also require CORE certification before opening a direct EDI connection.

Try Stedi

Start free with a sandbox account. Upgrade to production when you're ready. There are no monthly minimums or setup fees. You only pay for the transactions you use. See our pricing.

Blue Cross NC is now one-click enrollment

Healthcare payer Blue Cross NC (Payer ID: BCSNC) now supports one-click transaction enrollment for Electronic Remittance Advice (ERAs).

About one-click enrollment

Transaction enrollment is the process of registering a provider to exchange specific healthcare transactions with a payer. Payers always require transaction enrollment for ERAs. For other transactions, it depends on the payer.

Transaction enrollment requirements vary by payer. Some payers may require the submitter to sign PDFs or complete tasks in the payer's portal.

With one-click transaction enrollment, you only need to submit an enrollment request. There are no follow-up steps. Stedi handles everything else.

You can check whether a payer supports one-click enrollment using the Stedi Payer Network or the Payer APIs.

Introducing single sign-on (SSO) and SCIM

Your team can now sign in to Stedi using single sign-on (SSO) and sync accounts automatically with directory sync (SCIM).

What is SSO?

SSO lets Stedi account members sign in to the Stedi portal through an identity provider, such as Okta or OneLogin, instead of using a separate Stedi username and password.

Stedi’s SSO supports SAML and OIDC, the protocols used by all major enterprise identity providers.

What is SCIM?

Directory sync (SCIM) automatically creates and removes Stedi accounts as you add or remove users in your provider. For example, when you deactivate an employee in Okta, SCIM automatically removes their access to Stedi.

Availability

SSO and SCIM are available by request on our custom pricing plan. To enable SSO/SCIM or to learn more about custom pricing, contact us.

To learn more about Stedi SSO and SCIM, see our documentation.

Claim edit: Invalid provider UPIN format

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a Unique Physician Identification Number (UPIN) in an invalid format.

What is a UPIN?

A Unique Physician Identification Number (UPIN) is a legacy identifier previously assigned to providers by the Centers for Medicare & Medicaid Services (CMS).

UPINs were replaced by National Provider Identifiers (NPIs) in 2007. Some payers, including certain state Medicaid payers, still accept a UPIN as an alternate provider identifier. Payers may also populate the UPIN in secondary or tertiary claims they generate for coordination of benefits (COB).

How the edit works

When you submit a claim, you can specify a UPIN for any provider listed on the claim, such as the rendering provider or supervising provider.

All valid UPINs are exactly six characters in one of two layouts:

  • One letter followed by five digits, like A12345 (X99999)

  • Three letters followed by three digits, like ABC123 (XXX999)

If a claim includes a UPIN with an invalid format, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Provider UPIN Number. UPINs must follow one of these formats: X99999 (one letter followed by five digits) or XXX999 (three letters followed by three digits). The submitted value '123456789' does not match either format. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>133>DN*[DATE]*U*[AMOUNT]********Invalid Provider UPIN Number. UPINs must follow one of these formats: X99999 (one letter followed by five digits) or XXX999 (three letters followed by three digits). The submitted value '123456789' does not match either format. Correct and resubmit.~

Claim edit: Missing total claim charge amount

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that are missing the total claim charge amount.

What is the total claim charge amount?

The total claim charge amount is the full dollar amount billed by the provider for a claim, before adjustments or payments.

The total claim charge amount should equal the sum of the individual service line charges. Payers use it to balance a claim by checking its math.

Total claim charge amount

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.claimChargeAmountCLM-02 (Total Claim Charge Amount) of Loop 2300 (Claim Information)
837D dentalclaimInformation.claimChargeAmountCLM-02 (Total Claim Charge Amount) of Loop 2300 (Claim Information)
837I institutionalclaimInformation.claimChargeAmountCLM-02 (Total Claim Charge Amount) of Loop 2300 (Claim Information)

How the edit works

When the total claim charge amount is missing, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Claim Charge Amount. The total claim charge is required on all claims. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A6>178*[DATE]*U*[AMOUNT]********Missing Claim Charge Amount. The total claim charge is required on all claims. Correct and resubmit.~

Related claim edits

Stedi has another edit that validates the total claim charge amount. See Total claim charges must equal line-level charges.

Introducing a read-only CMS-1500 view for professional claims in the Stedi portal

When you open a professional claim from the Stedi portal’s claims view, details are now shown in a read-only layout that mirrors the CMS-1500 form, also called the HCFA, the standard paper form for professional claims.

CMS-1500 claim view in the Stedi portal

If you use the Stedi portal’s CMS-1500 form to submit professional claims, you can now view a claim in the same form you used to submit it. Previously, the Stedi portal rendered professional claims in a Stedi-specific layout that didn't resemble the submission form.

You can also correct and resubmit a claim from the CMS-1500 claim view. Click Edit and resubmit and select CMS-1500 resubmission. This opens the claim in the editable CMS-1500 form, where you can update and resubmit it.

This change applies to professional claims only. Dental and institutional claims viewed in the Stedi portal still use their existing layouts.

Unmapped X12 paths

Stedi transmits all claims to payers as HIPAA-compliant X12. If you submit professional claims using our JSON APIs or the CMS-1500 form, we handle the translation to X12 for you.

Certain X12 paths don’t map cleanly to the CMS-1500 form and aren’t rendered in the new view. Instead, you can view unmapped X12 paths from the bottom of the CMS-1500 claim view, alongside a link to the EDI tab for the raw 837.

Unmapped X12 paths in the CMS-1500 claim view

Submit raw X12 claims in the Stedi portal's claims view

You can now submit claims as raw 837 X12 EDI files in the Stedi portal’s claims view.

Previously, you could only submit raw X12 claims in the Stedi portal using the transactions view. We're retiring the transactions view’s raw X12 claim submission flow with this change.

How to submit a raw X12 claim in the Stedi portal

To upload a raw X12 claim from the claims view, click Submit claim, select Upload raw X12 file, and add your .edi file.

You can also select an X12 implementation guide, such as 837P Professional Claim (X222A1) or 837D Dental Claim (X224A2), and paste in your X12.

Click Submit claim when you’re ready to submit.

The editor validates the file against the implementation guide’s spec and flags structural errors. You can fix these errors before submitting.

Error in the Stedi portal's EDI editor

Submit multiple claims in one file

A single 837 X12 file can contain multiple claims, as long as they’re the same claim type – 837P professional claim, 837I institutional claim, or 837D dental claim – and use the same X12 implementation guide.

For guidance, see:

Claim edits

The Stedi portal’s EDI editor only checks a claim’s X12 structure. Stedi also runs claim edits after you submit a claim to catch other errors that could lead to a payer rejection.

If you submit a claim as raw X12 in the Stedi portal’s claims view, these edits run asynchronously. If the claim fails an edit, Stedi will reject the claim with a 277CA claim acknowledgment after submission.

Availability

All Stedi production accounts can submit claims as raw X12 in the Stedi portal’s claims view.

Introducing pay-as-you-go pricing

We're introducing a new pay-as-you-go pricing plan. With the new pay-as-you-go plan, you get a full production account (including API and SFTP access) and only pay for the transactions you use, with automatic volume discounts and no monthly minimums, setup fees, or per-provider/location fees.

Previously, API and SFTP access was only available with a $500 monthly minimum plan. That minimum priced out startups, practices, and solo developers who wanted to move from prototype to production without a commitment.

Existing Stedi accounts stay on their current pricing plans by default and can switch to a pay-as-you-go or custom plan at any time by contacting Stedi support.

How pay-as-you-go pricing works

The pay-as-you-go plan uses tiered pricing. For most transactions, the per-transaction rate drops as your monthly volume grows.

When you sign up for the pay-as-you-go plan, you add a credit card and fund an initial Stedi account balance, starting at $25.

Each transaction draws down the balance at the rate for its pricing tier. See our pricing page for an estimator and full breakdown of each tier.

Stedi automatically adds funds to your balance when it drops below a trigger you set. For example, you can add $25 to your balance whenever it falls below $10, the minimum trigger.

Auto recharge

Your balance rolls forward month to month. At the end of each month, Stedi sends an invoice that covers your monthly usage. If you send zero transactions in a month, you pay nothing.

For more details, see our announcement blog.

Test ERAs now support professional claims without an NPI

Stedi's test claims workflow now returns a test Electronic Remittance Advice (ERA) for professional claims without the billing provider’s National Provider Identifier (NPI).

The test claims workflow lets you submit a test claim to the Stedi Test Payer and get a test ERA in response. You can use the workflow to do end-to-end validation and build integration tests.

Atypical providers – providers without an NPI – sometimes submit professional claims using a commercial number or location number.

Previously, the test claims workflow required the billing provider’s NPI in the submitted claim to generate and return a test ERA. Now, the test ERA uses the billing provider's tax ID instead.

Submitting the test claim

To generate a test ERA without the billing provider’s NPI, include the billing provider’s tax ID and a state license number when submitting the test professional claim to the Stedi Test Payer.

Field837P Claims Submission JSON API fieldX12 element
Tax IDbilling.employerIdREF02 of Loop 2010AA (Billing Provider Name), where REF01 = ”EI” (Employer's Identification Number)
State license numberbilling.stateLicenseNumberREF02 of Loop 2010AA (Billing Provider Name), where REF01 = ”0B” (State License Number)

Receiving the test ERA

The test ERA identifies the payee by tax ID and returns the state license number from the original claim.

Field835 ERA Report API fieldX12 element
Tax IDpayee.federalTaxPayersIdentificationNumberN104 of Loop 1000B (Payee Identification), where N103 = ”FI” (Federal Tax ID)
State license numbertransactions[].payee.stateLicenseNumberREF02 of Loop 1000B (Payee Identification), where REF01 = ”0B” (State License Number)

For example, an ERA retrieved using the 835 ERA Report endpoint:

{
  "transactions": [
    {
      "payee": {
        "name": "Test Provider",
        "taxId": "123456789", // Billing provider's tax ID
        "stateLicenseNumber": "LIC987654", // Billing provider's state license, if submitted
        ...
      },
      ...
    }
  ]
}

For more information, see our Test claims workflow docs.

Claim edit: Invalid diagnosis-related group code format

Stedi now rejects 837I institutional claims with a diagnosis-related group (DRG) code that isn't three or four numeric digits.

Diagnosis-related group codes

In institutional claims, a diagnosis-related group (DRG) code groups inpatient hospital stays into categories expected to consume similar resources. DRG 470 covers inpatient hip or knee replacements without complications.

Payers use DRG codes to determine fixed reimbursement rates under DRG-based contracts with providers. Medicare inpatient hospital reimbursement is the most common use case, though Medicaid and some commercial plans use different DRG systems. DRG codes are only required if the provider's payer contract uses DRG reimbursement.

Diagnosis-related group code (DRG)

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.diagnosisRelatedGroupInformation.drugRelatedGroupCodeHI01-02 (Industry Code) of Loop 2300 (Claim Information) where HI01-01 = DR (Diagnosis-related group)

How the edit works

X12 standards require all valid DRG codes to be three or four numeric digits. If a claim’s DRG code is a different length or contains a non-numeric character, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>256*[DATE]*U*[AMOUNT]********Invalid Diagnosis Related Group (DRG) code. When entered, the DRG code must be three or four numerics and a valid code. The submitted code, 47A, is invalid. Correct and resubmit.~

Claim edit: Missing address line 1 when line 2 is present

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include an address with line 2 populated but line 1 missing or blank.

How the edit works

Every address in a healthcare claim can contain two lines:

  • Line 1 is the primary street address (e.g. 123 Main St).

  • Line 2 is a secondary line such as a suite, apartment, or floor (e.g. Suite 100).

X12 standards require that addresses with a populated line 2 also have a populated line 1. If any address on the claim has line 2 populated but a missing or blank line 1, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

The error description names the specific entity whose address failed the check. For example, Billing Provider, Subscriber, or Service Facility.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Address line. When submitting address lines, line 1 is required when line 2 is present. Submitted Billing Provider address includes a line 2 but missing the line 1 address. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A6>503>85*[DATE]*U*[AMOUNT]******A8>732**Missing Address line. When submitting address lines, line 1 is required when line 2 is present. Submitted Billing Provider address includes a line 2 but missing the line 1 address. Correct and resubmit.~

Claim edit: State and province codes must be two characters

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a state or province code that is not exactly two characters.

How the edit works

X12 standards require claims to use a 2-character state or province code for any address in the U.S. or Canada:

If a state or province code is not exactly two characters, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Important: X12 standards only require state and province codes for addresses in the U.S. and Canada. Claims that omit a state or province code are unaffected by this edit.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid State/Province code. The state or province code is required when the city is in the U.S. or Canada. All codes must be abbreviated and exactly two (2) characters. The submitted code for Subscriber is invalid. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>501>HK*[DATE]*U*[AMOUNT]******A7>569**Invalid State/Province code. The state or province code is required when the city is in the U.S. or Canada. All codes must be abbreviated and exactly two (2) characters. The submitted code for Subscriber is invalid. Correct and resubmit.~

Introducing CMS-1500 Claim Form PDF downloads in the Stedi portal's claims view

You can now download CMS-1500 Claim Form PDFs for professional claims from the Stedi portal’s claims view.

Previously, manual downloads were only available from a claim's transaction details page.

You can use the PDFs to export submitted claims for record keeping, physically mail a claim to a payer, or review claim information in a familiar format.

When you download the PDF, you can choose whether to include the CMS-1500 form background or omit it to print claim data onto pre-printed forms.

For API access, you can continue to use the CMS-1500 PDF: Business Identifier or CMS-1500 PDF: Transaction ID endpoints. For more information, see our CMS-1500 Claim Form PDF docs.

Introducing semantic filenames for SFTP files received from Stedi

You can now configure Stedi's SFTP server to deliver files with semantic filenames that include the X12 transaction set.

Previously, files in the from-stedi directory used UUIDs, such as f9591145-8343-4bd8-a338-5bcca8ac3baf.x12, as filenames. You had to open or parse each file to know whether it contained a 277CA claim acknowledgment, 835 Electronic Remittance Advice (ERA), and so on. Semantic filenames include a transaction set identifier so you can route, filter, or sort files without parsing their contents.

How semantic filenames work

You can configure filenames on the SFTP setup page of your account settings. Set File naming to one of:

  • Semantic – {TIMESTAMP}_{UUID}_{SEMANTIC_IDENTIFIER}.x12

Example: 20260416124500_f9591145-8343-4bd8-a338-5bcca8ac3baf_277CA.x12

  • UUID only – {UUID}.x12 Example: f9591145-8343-4bd8-a338-5bcca8ac3baf.x12

Semantic identifiers cover the X12 transaction sets that Stedi delivers:

The filename configuration only affects files that you receive from Stedi. Stedi delivers these files to your from-stedi directory. Files you upload to Stedi keep their original names, and files Stedi sends to payers are unaffected.

Existing Stedi accounts will continue using UUID-based filenames by default. New Stedi accounts will default to semantic filenames.

For more information, see our SFTP file naming docs.

Claim edit: An external cause code can't be the principal ICD-10-CM diagnosis code

Stedi now rejects 837P professional and 837I institutional claims that list an external cause code as the principal ICD-10-CM diagnosis code.

ICD-10-CM diagnosis codes

In healthcare claims, diagnosis codes describe what’s wrong with the patient. HIPAA requires that professional and institutional claims only use valid, billable ICD-10-CM codes as diagnosis codes. For example, M54.50 is the billable ICD-10-CM code for “Low back pain, unspecified.”

A claim can include multiple diagnosis codes. The first one listed – called the principal (or primary) diagnosis – is the condition primarily responsible for the visit. The rest are additional diagnoses.

Principal diagnosis code

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.healthCareCodeInformation[0].diagnosisCodeHI01-02 (Diagnosis Code) of Loop 2300 (Claim Information), where HI01-01 is ABK (ICD-10-CM)
837I institutionalclaimInformation.principalDiagnosis.principalDiagnosisCodeHI01-02 (Principal Diagnosis Code) of Loop 2300 (Claim Information), where HI01-01 is ABK (ICD-10-CM)

External cause codes

An external cause code is an ICD-10-CM diagnosis code used to describe how an injury or condition occurred. For example, V03.10XA (pedestrian struck by car) is an external cause code. External cause codes always start with V, W, X, or Y.

How the edit works

External cause codes are valid ICD-10-CM diagnosis codes, but ICD-10-CM guidelines only allow them as additional diagnoses to supplement the principal diagnosis. External cause codes are not allowed as the principal diagnosis. Payers may reject claims that break this rule.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Principal Diagnosis. External cause codes, which describe how the condition occurred, cannot be used as the principal diagnosis. The submitted diagnosis code, W1830XA, is an external cause code (codes beginning with V, W, X, or Y). Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>254*[DATE]*U*[AMOUNT]******A7>509**Invalid Principal Diagnosis. External cause codes, which describe how the condition occurred, cannot be used as the principal diagnosis. The submitted diagnosis code, W1830XA, is an external cause code (codes beginning with V, W, X, or Y). Correct and resubmit.~

Resolution tip

In most cases, you can pass this edit by setting the principal diagnosis to the resulting injury or condition and listing the external cause code as an additional diagnosis.

For example, on a claim for a pedestrian struck by a car, list the injury, like S72.001A (fracture of the right femur), as the principal diagnosis and an external cause code, such as V03.10XA (pedestrian struck by car), as an additional diagnosis.

Related claim edits

Stedi has other edits that enforce principal diagnosis rules. See:

Claim edit: Duplicate value codes in institutional claims

Stedi now rejects 837I institutional claims that include the same value code more than once.

Value codes

In institutional claims, value codes are two-character alphanumeric codes used to report financial or clinical information that affects reimbursement to the payer. For example, 01 is the value code for "Most Common Semi-Private Room Rate." Value codes are paired with monetary amounts.

Value code

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.valueInformationList[][].valueCodeHI-02 (Value Code) of Loop 2300 (Claim Information), where HI-01 is BE (Value)

How the edit works

X12 standards allow up to 12 value codes per claim. Each value code within a claim must be unique. With duplicate codes, the payer can't determine which monetary amount to apply for the value code and may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Duplicate Value Code(s). Each value code must be unique. Submitted value code(s), D4, appear more than once on the claim. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>725*[DATE]*U*[AMOUNT]******A7>732**Duplicate Value Code(s). Each value code must be unique. Submitted value code(s), D4, appear more than once on the claim. Correct and resubmit.~

Claim edit: Invalid date format

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a date in an invalid format.

Date formats

X12 standards require that every date on a claim, such as the service date or admission date, use one of two formats:

  • Single date – Eight digits in CCYYMMDD format. Example: 20260515.

  • Date range – Two dates in CCYYMMDD-CCYYMMDD format. Example: 20260515-20260516.

In raw X12, each date has a related qualifier indicating the format: D8 for single dates and RD8 for date ranges.

Date formats in the JSON API

In Stedi’s JSON Claim Submission API endpoints, most dates that support both formats use paired fields. For example, in the JSON Professional Claim Submission endpoint, you can provide a service date either as:

Some dates support both formats in a single field. For example, in the JSON Dental Claim Submission endpoint, the claim-level serviceDate field accepts either a single date or a date range.

How the edit works

When a date in a claim doesn't match one of these formats, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Date Range Format. The Service date range (20250708-abc) must be submitted in format 'CCYYMMDD-CCYYMMDD' when reported with the date range qualifier (RD8). Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>569*[DATE]*U*[AMOUNT]********Invalid Date Range Format. The Service date range (20250708-abc) must be submitted in format 'CCYYMMDD-CCYYMMDD' when reported with the date range qualifier (RD8). Correct and resubmit.~

Introducing ERA views in the Stedi portal

You can now view Electronic Remittance Advice (ERAs) in the Stedi portal's claims view.

Features include:

  • A filterable list of all ERAs received through Stedi.

  • A detail page for each ERA showing payer and payee info, payment date and method, total paid, and claim-level adjustments.

  • A click-through from a claim's timeline to any ERAs that match its Patient Control Number (PCN).

  • Download options for the full ERA PDF, a single claim's PDF, or all claim PDFs at once.

For more details, see our announcement blog.