There are four ways to find out — three of them are slow, partial, or unverifiable. The reliable way is to check the account against an enrollment database: a debt settlement scrub.
Most operations discover an enrollment by accident — after weeks of calls, letters, and skip tracing against a consumer whose payments are already committed to a settlement program. These are the options, in the order most teams try them.
A rumor of enrollment is not verification. Trade-press survey work on the DS code rollout found the industry’s top adoption hurdle is defining what evidence is sufficient to confirm enrollment. Evidence-grade means four things on every result: the status, the company, the currency (an as-of date), and an audit trail showing when the check ran and what it returned. Anything less is a guess with a workflow built on it.
Contact us to set up secured access — or read what the DS code requires if reporting is your driver.
Both. The API answers single-account checks in real time; portfolios go over SFTP in batches. Most customers scrub the full inventory once, then check new placements as they arrive.
The enrollment status — currently enrolled or dropped out — the debt settlement company holding the enrollment, an as-of date, and for drop-outs the date the consumer left the program.
The network is refreshed as often as daily. Monitoring re-checks your entire inventory monthly and reports exactly those changes: new enrollments and drop-outs.
The DS code requires verified enrollment in a for-profit debt settlement program before it is reported. A network match returns the dated evidence — status, company, as-of date, audit trail — that the verification standard calls for. See the DS code page.
Send your first file this week. We set up your secured access, run your full-inventory scrub, and turn monitoring on the same day — plans priced by volume, quoted for your portfolio.
Get Started