Enrollment data is the record of who is in a debt settlement program: each consumer’s status, the company running the program, and the dates that show how current the record is. It is the raw material behind every scrub and every monitoring report.
Strip away the workflow and an enrollment record is a small, precise statement: this consumer is in a for-profit debt settlement program, with this company — or was, until this date. Nothing about balances owed, nothing about where the consumer lives, nothing borrowed from a credit file. The record exists to answer the enrollment question and to keep answering it correctly as the answer changes, because enrollment is not a permanent state: consumers sign up, and consumers drop out, every month.
That narrowness is deliberate. Data built for one question can be kept exact about that question — current, dated, and unambiguous — instead of approximating five questions at once. The market numbers behind the demand are on the data page; this page is about the records themselves.
Illustrative examples — not real records. A complete SSN is never displayed in any result.
Currently enrolled, or dropped out. The single most important field — it decides whether an account is represented by a program or workable again.
Every hit names the debt settlement company holding the enrollment — the party actually receiving the consumer’s program payments.
An “as of” date on every record states how current it is; for drop-outs, the date the consumer left the program is carried with it. History is kept, with dates, rather than overwritten.
Enrollment data decays. A list that was accurate in January misroutes accounts by spring, because the underlying facts moved: new consumers enrolled, others left. The network is therefore kept current — refreshed as often as daily — and every record and every result carries its as-of date, so the age of an answer is always known rather than guessed. A dated answer can be relied on, audited, and defended; an undated one is a rumor with a workflow built on it.
Single accounts checked in the moment — at intake, inside a workflow, before a decision. The answer returns with its status, company, and as-of date attached.
Full portfolios move as files over the encrypted channel: an entire inventory out, the matched records back — and, under monitoring, a change report every month.
Two services consume the same data in two different ways: the scrub reads it as a point-in-time check of a submitted inventory, while monitoring reads it as a monthly comparison against a standing one. The difference between the two is laid out in monitoring vs. one-time scrub.
Contact us to set up secured access, or start with how the scrub works.
The record of who is enrolled in a debt settlement program: for each consumer, the enrollment status, the company holding the enrollment, and the dates — including an as-of date on every record and the dropped date when a consumer leaves a program.
A status (currently enrolled or dropped out), the debt settlement company named on the hit, an as-of date, and for drop-outs the date the consumer left. A complete SSN is never displayed in any result.
The network is refreshed as often as daily, and every result is stamped with its as-of date — the currency of the answer is part of the answer.
Two ways: real-time API calls for single-account checks, and SFTP file transfers for portfolios and monthly change reports. Both channels are encrypted end to end, and identifiers are hashed on arrival.
No. The records cover for-profit debt settlement programs only — debt management plans are a different product and are not in the network.
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