Send us the file before you send the bureaus the file. Your pre-transmission Metro 2 file is matched against the enrollment network, and what comes back is the data and the corrections: every account that needs the DS code, every DS code already on the file without verification behind it, and the evidence record for each line. You make the changes. You transmit the file.
Your monthly Metro 2 file moves over the secured channels — portal upload or SFTP with your own key. Identifiers are converted to one-way hashes on arrival; raw SSNs are never stored.
The file is checked account by account, across the whole institution — CDIA’s rule is that DS reports on all applicable accounts at the same financial institution, so the review is institution-wide, not account-by-account sampling.
A corrections package keyed to your file: adds, removals, and status changes, each with the enrollment status, the settlement company, an evidence grade, and an as-of date. Apply what you accept; your file stays yours.
Illustrative lines. Every line in a real package carries the full evidence record, and the whole review is written to an audit log.
Two models exist for a service like this. We chose the one that keeps your reporting defensible.
Your duties under FCRA §623 and Regulation V attach to the information you furnish. Regulation V defines the integrity of furnished information as information substantiated by the furnisher’s records at the time it is furnished. Our corrections package and evidence records become part of your records — the substantiation lives exactly where the rule expects it.
Your file generation does not move, your bureau agreements do not change, and no vendor gets the pen on your tradelines. It starts with one file, reviewed, with the corrections argued line by line before anything reports differently.
Reviews run inside your cycle: send the file when you generate it, and the corrections return in time to apply before transmission. Turnaround is fixed in your agreement — and the same review doubles as the pre-file check your written accuracy procedures can point to. Start with one file.
The Metro 2 file you are about to transmit — the same full file your systems already generate each cycle. It arrives over encrypted SFTP or the portal; identifiers are hashed on arrival and matching happens on the hashes.
A corrections package keyed to your file: accounts to add DS to, accounts whose DS code lacks current verification, lifecycle status changes, and a no-change confirmation for the rest — plus the evidence record behind every line and an analysis summary for the cycle.
Then it does not go in your file. Every correction shows its evidence grade and basis precisely so your team can accept, question, or reject it. The decision — and the record of it — stays with the furnisher.
File review checks the file in front of you, once per cycle. Monitoring watches your whole inventory continuously and tells you when an account enters settlement, so most DS decisions are already made before the file is generated. Most furnishers end up running both.
Start with a mutual NDA and one file. We review the file you are about to transmit, hand back the corrections with the evidence behind each one, and you decide what reports.
Get Started