Reference·SBR Segment·SBR01
X12 837D Reference

X12 837D SBR01 (Payer Responsibility Sequence Number Code): Format, Values, and Testing Notes

Jul 28, 2026 · 4 min read
SBR02 →

Dual dental coverage is common enough — through two working spouses, for instance — that SBR01 sequencing errors in 837D claims show up constantly, and because the segment still validates with two loops both marked primary, nothing catches it before the payer does.

Quick answer

SBR01 is the Payer Responsibility Sequence Number Code in an X12 837D claim — a single-character code stating whether the payer named in this SBR loop is responsible as the primary, secondary, or tertiary payer for the dental services billed.

Valid code values

P
Primary — this dental payer is billed first and pays before any other dental coverage applies
S
Secondary — this dental payer pays after the primary dental payer has adjudicated
T
Tertiary — this dental payer pays after both primary and secondary dental coverage have adjudicated

Example

Synthetic example Generated by Synthibase
SBR*P*19*GRP-DNT7731*BRIGHTSMILE DENTAL PLAN*****CI*

The P immediately after SBR is SBR01, marking this loop as the primary dental payer for the claim. Synthetic claim data.

Where this trips people up

Dual-coverage dental scenarios — a child covered under both parents' separate dental plans, for example — require careful, deliberate sequencing rather than the birthday-rule shortcuts some test generators borrow from medical COB logic. Building a secondary dental SBR loop by copying the primary loop and forgetting to flip SBR01 from P to S produces a claim that looks complete but leaves the payer unable to tell which plan pays first.

X12 837D SBR Segment Guide: Fields, Format, and Testing Gotchas
What is X12 837P? Complete Format and Field Guide
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Test primary, secondary, and tertiary dental sequencing correctly
Synthibase generates synthetic 837D claims with SBR01 sequenced correctly across every dental payer loop, so dual-coverage coordination-of-benefits logic gets exercised the way it will in production.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.