XBFCRA / FDCPA Dispute States
Compliance Condition Code XB: Account Information Disputed by Consumer (FCRA / FDCPA)
Compliance Condition Code XB means "Account Information Disputed by Consumer (FCRA / FDCPA)". The consumer disputed the account directly with you under the FCRA or FDCPA and your investigation is not finished. The tradeline carries a dispute flag while this code is in place. It is reported in Compliance Condition Code (Field 32) of the Base Segment, 2 characters at position 215.
Specification
| Code | XB |
|---|---|
| Meaning | Account Information Disputed by Consumer (FCRA / FDCPA) |
| Field | Compliance Condition Code (Field 32) |
| Record | Base Segment |
| Length / position | 2 chars · 215–216 |
| Category | FCRA / FDCPA Dispute States |
| CRRG reference | CRRG Exhibit 8 (Compliance Condition Codes) |
What Compliance Condition Code XB means
- Applies to a direct dispute -- the consumer contacted you, the furnisher, rather than filing through a credit bureau.
- Report it while the investigation is open. It is a statement about the state of your investigation, not a statement that the consumer is right.
- A tradeline flagged XB is generally excluded from scoring by the bureaus, which is exactly why leaving it on after the investigation closes causes harm.
- This is the compliance condition code the product runtime maps an open FCRA dispute to.
When to report XB
- 1A consumer writes to say the balance you reported is wrong and you have opened an investigation.
- 2A borrower disputes the delinquency history on an installment loan directly with your servicing team.
- 3A debt collector receives a written dispute under FDCPA section 809 and reporting continues while it is investigated.
- 4A consumer disputes the ownership of an account you furnish and verification is in progress.
Reporting rules
- Report XB from the cycle you receive the dispute until the cycle your investigation concludes.
- When the investigation concludes and the consumer accepts the outcome, move to XH -- do not simply blank the field, because blank retains XB.
- When the investigation concludes and the consumer still disagrees, move to XC.
- Correct the underlying data if the dispute is valid. The flag is not a substitute for fixing the record.
Codes and fields that must agree
A file can be structurally valid and still be wrong. These are the cross-field conditions Compliance Condition Code XB has to satisfy.
- Blank in the next cycle does NOT clear XB. Clearing requires XC, XH, or XR.
- Do not report XB together with XF -- an FCRA dispute and an FCBA billing-error dispute are different codes, and only one CCC may be sent per record.
- If the account is also closed at the consumer's request, report XD instead of XA and XB separately.
Common errors involving XB
Vocabulary
Keep browsing
- All 10 compliance condition codes — the full set with categories and cross-field rules.
- Metro 2 codes cheat sheet — every CRRG code set on one page.
- Compliance Condition Code field reference — position, length, and validation rules.
- Metro 2 format reference
See Compliance Condition Code XB in your own file
Drop a .dat file into the free in-browser viewer and inspect every record carrying XB. No signup, and nothing is uploaded — your file stays on your device.