Claim edit: COB service lines must be balanced
Claims
Stedi now rejects 837P professional, 837D dental, and 837I institutional claims sent to a non-primary payer when a service line's coordination of benefits (COB) amounts don't balance.
How the edit works
When a patient has multiple insurance plans, the provider submits a claim to each payer in order. The first is the primary payer. Any that follow are secondary, tertiary, and so on. This process is called coordination of benefits (COB).
A service line is a line item for a specific service on a claim, like an office visit or X-ray.
When you submit a claim to a non-primary payer, you must include each previous payer's adjudications – their payments and adjustments. Include both claim-level and service line-level adjudications from each prior payer. Don't include the same amounts at both levels.
Balancing service lines
When you include prior payer adjudications at the service line level, the amounts must add up as follows:
Billed line charge
Claim type | JSON API field | X12 element |
|
| |
|
| |
|
|
Prior payer line paid amount
Claim type | JSON API field | X12 element |
|
| |
|
| |
|
|
Line adjustment amounts
Claim type | JSON API field | X12 element |
| ||
| ||
|
If the amounts don't balance for any service line adjudication, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which are slower and delay payment for the provider.
We previously added a separate edit for claim-level COB balancing.
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 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:
Stedi now rejects 837P professional, 837D dental, and 837I institutional claims sent to a non-primary payer when a service line's coordination of benefits (COB) amounts don't balance.
How the edit works
When a patient has multiple insurance plans, the provider submits a claim to each payer in order. The first is the primary payer. Any that follow are secondary, tertiary, and so on. This process is called coordination of benefits (COB).
A service line is a line item for a specific service on a claim, like an office visit or X-ray.
When you submit a claim to a non-primary payer, you must include each previous payer's adjudications – their payments and adjustments. Include both claim-level and service line-level adjudications from each prior payer. Don't include the same amounts at both levels.
Balancing service lines
When you include prior payer adjudications at the service line level, the amounts must add up as follows:
Billed line charge
Claim type | JSON API field | X12 element |
|
| |
|
| |
|
|
Prior payer line paid amount
Claim type | JSON API field | X12 element |
|
| |
|
| |
|
|
Line adjustment amounts
Claim type | JSON API field | X12 element |
| ||
| ||
|
If the amounts don't balance for any service line adjudication, the payer may reject the claim.
This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which are slower and delay payment for the provider.
We previously added a separate edit for claim-level COB balancing.
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 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:
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
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.
