Claim edit: Missing last name
Claim edits
Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a person entity with no last name.
How the edit works
In a claim, each entity, such as the billing provider or subscriber, is identified as either a person or a non-person using an entity type qualifier.
When an entity is a person, both a first name and last name are required. In X12, this is the entity’s NM1-03 element. If a person’s last name 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.
How entity type qualifiers are specified
If you use Stedi's JSON Claim Submission API endpoints, Stedi sometimes infers the entity type qualifier. For example, if you provide a firstName and lastName for the billing provider in a JSON 837P Professional Claims API request, the entity is treated as a person.
If you use X12, you set the entity type qualifier in NM1-02 (Entity Type Qualifier). 1 indicates a person and 2 indicates a non-person entity, such as a hospital or billing organization.
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 Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit.", "followupAction": "Please Correct and Resubmit" } ] }
{ "errors": [ { "code": "33", "description": "Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. 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>504>85*[DATE]*U*[AMOUNT]********Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit
STC*A6>504>85*[DATE]*U*[AMOUNT]********Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit
STC*A6>504>85*[DATE]*U*[AMOUNT]********Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit
Related claim edits
Stedi has a companion edit for missing first names. See Claim edit: Missing first name.
Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a person entity with no last name.
How the edit works
In a claim, each entity, such as the billing provider or subscriber, is identified as either a person or a non-person using an entity type qualifier.
When an entity is a person, both a first name and last name are required. In X12, this is the entity’s NM1-03 element. If a person’s last name 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.
How entity type qualifiers are specified
If you use Stedi's JSON Claim Submission API endpoints, Stedi sometimes infers the entity type qualifier. For example, if you provide a firstName and lastName for the billing provider in a JSON 837P Professional Claims API request, the entity is treated as a person.
If you use X12, you set the entity type qualifier in NM1-02 (Entity Type Qualifier). 1 indicates a person and 2 indicates a non-person entity, such as a hospital or billing organization.
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 Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. 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>504>85*[DATE]*U*[AMOUNT]********Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit
Related claim edits
Stedi has a companion edit for missing first names. See Claim edit: Missing first name.
Get started with Stedi
Get started with 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.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Product
Developers
Resources
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.
Product
Developers
Resources
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.
Product
Developers
Resources
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.
