What Does Status Code DA Mean on a Credit Report?

What does status code DA mean?

You already filed an identity-theft report when a card you never opened finally falls off one bureau. The cleanup trail references DA - delete entire account due to confirmed fraud - and you still need the other two bureaus clean.

Status code DA is commonly used as a delete entire account due to confirmed fraud instruction. The consumer-facing work is the fraud packet and multi-bureau verification. You may never see DA printed on a retail portal. You should see the fake account gone, or still fighting to stay.

Industry files use Metro 2 style status language for these operations. Treat the code as a fraud-cleanup signal, then prove the result on free weekly reports from AnnualCreditReport.com.

If the account was never fraud, stop. A legitimate debt you dislike is a different problem from identity theft. Using the wrong packet wastes time and can stall real disputes under the FCRA.

The identity-theft workflow that makes DA meaningful

Confirmed-fraud deletes rest on documentation quality. Here is the sequence I would run:

• Create or update a report at IdentityTheft.gov and save the recovery plan PDF.
• File a police report when your local process and the recovery plan call for it.
• List every fraudulent account with creditor name, account number or last four, and approximate open date.
• Place fraud alerts or credit freezes as your plan recommends.
• Dispute each fake line with the bureaus and send proof to furnishers when you have it.
• Pull free reports again and confirm which fakes are gone.

The statute path for accuracy fights still runs through reinvestigation rights under 15 U.S.C. § 1681i. The identity-theft packet is what makes a fraud claim specific instead of theatrical.

How DA differs from 98 and DF

Code 98 is a non-fraud delete entire account path. DA is confirmed-fraud delete of the entire account. DF is a related confirmed-fraud delete path used in neighboring fraud-suppression workflows.

For you as a consumer, the practical split is evidence type. Non-fraud cleanups follow ordinary dispute or furnisher correction proof. Fraud paths need identity-theft materials. Related fraud path DF still lives in the fraud family; it is not a casual synonym for a normal paid-delete myth.

If a company blurs all three codes into one miracle product, ask which path matches your facts. If they cannot answer, walk away.

Multi-bureau cleanup and what success looks like

Success is not a feeling after one portal refresh. Success looks like this:

• The fraudulent account number is gone on all three free reports.
• No new clone account opened with a similar name or address mix-up.
• Alerts or freezes you placed are still active if you wanted them.
• You have dated PDFs proving the before-and-after state.

Partial cleanup is common. Experian may drop a fake card while TransUnion still shows it. Treat each bureau as its own track until the fake identifiers are gone everywhere you can check for free.

Also check for mixed-file damage: someone else's accounts riding along because of a similar name. Fraud cleanup and mixed-file cleanup can overlap, but the exhibits differ.

When a DA fraud delete goes wrong

A fraud delete is incomplete when any of these are true:

• The fraudulent account remains after a complete identity-theft packet.
• Only one bureau deleted while others still show the fake line.
• A legitimate account you own was removed as fraud by mistake.
• The wrong account number was targeted.
• The fake line reappears after a prior fraud delete result.

Dispute with exhibits under 15 U.S.C. § 1681i. Silence alone never auto-deletes a reinserted fraud line. For the full prepare and escalate calendar, use how to dispute credit report errors.

Monitor after a confirmed-fraud delete

Identity theft is a season, not a single afternoon. For at least ninety days after a DA-path cleanup:

• Pull free reports on a fixed schedule and search for the old fake account numbers.
• Watch for new inquiries and new accounts you did not open.
• Keep freezes or alerts in place until your recovery plan says otherwise.
• Store every new PDF with bureau and date in the file name.

If a fake line returns, you already have the first delete proof and the identity-theft report number. That combination is stronger than starting from zero.

Reject anyone who promises permanent immunity from fraud or demands payment before services are fully performed (CROA, 15 U.S.C. § 1679b).

Practical checklist for status code DA work

• Start or update an IdentityTheft.gov recovery plan and save the PDF.
• List every fake account with identifiers before you dispute.
• Pull all three free reports and save before PDFs.
• Dispute fake lines with ID, recovery plan materials, and account tables.
• Confirm multi-bureau deletion; do not stop after one portal looks clean.
• Monitor for reinsertion and new fraudulent openings for ninety days.
• Keep freezes or alerts active while risk remains high.

That is the real DA workflow. The code is operational. Your packet and monitoring are the consumer controls.

Frequently asked questions