Claim edit: Invalid date format

Claims

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"
    }
  ]
}
{
  "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"
    }
  ]
}
{
  "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
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
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

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

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.