If your organization is a financial institution or creditor that offers or maintains covered accounts, identity theft risk can show up fast. A fake ID at account opening, a sudden address change, a customer who stops receiving statements, or unusual activity on a new account can all point to the same problem: someone may be using another person’s information without permission.
That’s the focus of the Red Flags Rule under the Fair and Accurate Credit Transactions Act (FACTA). The rule requires certain financial institutions and creditors with covered accounts to maintain a written Identity Theft Prevention Program designed to identify, detect, respond to, and stay current with identity theft risks.
This guide covers the questions most readers actually have: what the red flags are, who the rule may apply to, what those warning signs look like in practice, and where secure document destruction fits into a broader FACTA compliance program.
What the Red Flags Rule Covers

FACTA amended the Fair Credit Reporting Act. The FTC’s Red Flags Rule overview explains that the rule is part of the federal identity theft framework. For organizations that fall within it, a written policy alone is not enough. The program must be designed to detect, prevent, and mitigate identity theft in connection with new and existing covered accounts.
The rule and FTC guidance break that program into four practical duties: identify relevant red flags, detect them in day-to-day operations, respond appropriately when they appear, and update the program as risks change.
Administration matters, too. The written program should be approved by the board of directors, an appropriate committee of the board, or a designated senior management employee when no board exists.
Who Needs a Program
The rule does not apply to every business that sends invoices or accepts credit cards. The FTC’s how-to guide says the analysis starts with whether the organization is a financial institution or creditor, and then whether it has covered accounts.
For consumer accounts, the test is fairly direct. If an account is for personal, family, or household purposes and involves multiple payments or transactions, it is covered. Other accounts also may be covered if there is a reasonably foreseeable risk of identity theft, including financial, operational, compliance, reputation, or litigation risk.
That is why the rule can be important outside of traditional banking. Some organizations in utilities, telecommunications, education, and health care may qualify depending on how they extend credit or maintain accounts. The key question is functional: does the organization offer or maintain accounts where identity theft risk is reasonably foreseeable?
The 26 Illustrative Red Flags
Appendix A to 16 CFR Part 681 includes 26 illustrative red flags grouped into five categories. These are examples, not a universal checklist. Your program should use the red flags that fit your account types, customer access points, and actual risk patterns.
Credit Report Alerts
1. A fraud alert or active duty alert appears in a consumer report.
2. A consumer reporting agency sends a notice of credit freeze in response to a request for a report.
3. A consumer reporting agency sends a notice of address discrepancy.
4. A consumer report shows activity that does not fit the applicant’s or customer’s usual history, such as a recent spike in inquiries, an unusual number of new credit relationships, a major change in credit use, or an account previously closed for cause or abuse.
These are often early warning signs because they come from outside your organization. Staff who review reports should know when those notices require a second look.
Suspicious Documents
5. Identification documents appear altered or forged.
6. The photo or physical description on the identification does not match the person presenting it.
7. Information on the identification does not match information the applicant or customer provides.
8. Information on the identification does not match information already on file, such as a signature card or recent check.
9. An application appears altered, forged, or pieced back together.
This category is straightforward, but it still gets missed when employees are rushed. Your procedures should tell staff exactly how to pause and escalate the review.

Suspicious Personal Information
10. Personal identifying information conflicts with external sources. For example, the address does not match the consumer report, or the Social Security number was never issued or appears on the Social Security Administration Death Master File.
11. Personal identifying information conflicts with other information supplied by the same person, such as a date of birth that does not align with the Social Security number range.
12. The personal information is linked to known fraud through internal or third-party sources, such as an address or phone number already used on a fraudulent application.
13. The personal information fits patterns associated with fraud, such as a fake address, a mail drop, a prison address, an invalid phone number, or a phone number tied to a pager or answering service.
14. The Social Security number is the same one used by other applicants or customers.
15. The address or phone number matches, or is very similar to, one used by an unusually large number of other applicants or customers.
16. The person opening the account fails to provide all required identifying information after being told the application is incomplete.
17. The personal identifying information does not match information already on file.
18. The person cannot answer challenge questions with information that would not already be available from a wallet or consumer report.
A large share of identity theft prevention lives in data consistency checks. Strong programs compare information across applications, internal files, consumer reports, authentication tools, and follow-up verification.
Suspicious Account Activity
19. Soon after a change-of-address notice, the organization receives a request for a new, additional, or replacement card, a cell phone, or added authorized users.
20. A new revolving credit account is used in a pattern associated with fraud, such as using most available credit for cash advances or easy-to-resell goods, or failing to make payments after the first bill.
21. An existing covered account is used in a way that breaks normal patterns, such as unexplained nonpayment, a major jump in available credit use, a major change in spending, unusual electronic fund transfer behavior, or changed call patterns on a cellular account.
22. An account that has been inactive for a long time suddenly becomes active again.
23. Mail to the customer is repeatedly returned as undeliverable even though transactions continue on the account.
24. The organization learns that the customer is not receiving paper account statements.
25. The organization is notified of unauthorized charges or transactions.
These account-use red flags matter because identity theft is not only an account-opening problem. Ongoing monitoring is important, too.

Notice From Others
26. The organization is told by a customer, an identity theft victim, law enforcement, or another person that it opened a fraudulent account for someone engaged in identity theft.
This category is easy to overlook because the report may come through customer service, collections, compliance, or another channel outside a formal fraud queue.
How Red Flags Show Up
A red flag is not always proof of identity theft. It is a signal that your organization needs a repeatable review process. Teams run into trouble when they either treat every discrepancy as routine noise or treat every discrepancy as confirmed fraud without investigation.
A finance company might pause account opening until information is verified through a second channel. A college bursar’s office may need tighter controls around address changes and payment-plan access. A hospital or medical group may need closer review when a billing or financing-related file shows conflicting personal information. The details vary, but the operating principle does not: staff should know what’s most important, how to escalate it, and what responses are allowed.
How to Build Red Flags Rule Compliance
A workable identity theft prevention program starts with a risk assessment and turns that assessment into procedures people can actually follow.
- Start by identifying where covered accounts exist in your business. Then look at how accounts are opened, what information you collect, how customers authenticate, and how they access those accounts.
- Next, build detection steps into the workflow. That can mean verifying government-issued ID for in-person openings, reviewing discrepancies in consumer reports, requiring follow-up on suspicious address changes, or using challenge questions and transaction monitoring for existing accounts.
- Then define responses in advance. FTC guidance points to options such as monitoring the account more closely, contacting the customer, changing passwords or other access credentials, reopening an account with a new number, declining to open a new account, closing an account, not collecting on a fraudulent account, or notifying law enforcement.
- Assign ownership, too. Someone needs authority to review exceptions, decide on account action, update scripts and forms, and coordinate training. A written policy without operational ownership usually breaks down.
- Finally, update and administer the program over time. Risks change, account access changes, and service-provider arrangements change. If outside vendors handle account-related work, your organization still needs reasonable assurance that those activities account for identity theft risk.
Common Compliance Gaps
Many Red Flags Rule programs weaken in familiar ways. One common problem is using a generic template without tailoring it to the accounts the organization actually offers. Another is naming red flags without building a detection method or response path for them.
Training is another weak spot. Employees do not need theory. They need practical direction on what to look for, where to check, when to stop a transaction, and how to escalate the issue.
At the same time, it’s important not to lose sight of the flow of paper, too. Even organizations with strong electronic controls can leave printed applications, consumer reports, billing documents, and account statements in desk drawers, open recycle bins, or unsecured storage rooms.
How Destruction Supports Compliance
The Red Flags Rule focuses on detecting, preventing, and mitigating identity theft tied to covered accounts. It is not the same as the FACTA Disposal Rule. Secure destruction can support identity theft prevention and information governance, but it is not a substitute for covered-account analysis, written procedures, training, and program oversight.
Still, the connection is practical. If old applications, denied applications, printed reports, or account documents are left in standard trash or open office areas, your organization makes identity theft easier. Many businesses treat secure destruction as one layer of a broader prevention program.
That is where a clear retention and destruction process helps. A written document retention and destruction policy helps you decide what to keep, how long to keep it, and when to dispose of it. A documented certificate of destruction can support audits and internal controls. If your organization has higher security requirements, the right shredder security levels and clear chain-of-custody expectations become critical — which is why it helps to understand whether professional shredding services are safe and when witnessed destruction is the right call before you commit to a provider.

A Simple Action Plan
If you are cleaning up an older Red Flags Rule program, start with these five questions:
- Which accounts are actually covered today?
- Where do red flags appear in your workflow: application, authentication, billing, address change, or account servicing?
- Does each red flag in your written program have a detection step and a response step?
- Do your service providers and disposal practices support the same control environment?
- Can you prove what happened after documents were destroyed or a suspicious account event was escalated?
Those questions usually expose gaps quickly. They also help you decide whether you need policy updates, staff training, secure bins, a recurring destruction schedule, or a larger one-time purge.
How Shred Nations Can Help
If you are updating an identity theft prevention program, reviewing account-opening controls, or planning secure disposal for old account files, we can help you find the right next step without calling vendors one by one. We connect businesses with local providers based on project size, proof requirements, and service type.
For low-volume cleanup, a nearby drop-off shredding location may be enough. For larger purges, archived account files, or compliance-sensitive cleanouts, a one-time purge shredding or scheduled destruction may make more sense.
If your team wants destruction at your location, mobile shredding can support immediate chain-of-custody needs. If the priority is efficiency for larger volumes, off-site service can be a strong fit when handled through secure transport and documented custody controls.
Across our network, providers may offer features such as witnessed destruction, sealed transport, barcode-based tracking, electronic signatures, GPS-tracked transport, and monitored facilities. Our national network serves organizations in sectors like legal services and education, with coverage in cities such as Philadelphia and Oakland.
If you have a small volume of documents, we can help you locate a nearby drop-off option. If you have a larger or compliance-sensitive project, calling is often the best starting point so we can scope documentation needs, timing, and service type before connecting you with qualified providers. To get started, fill out our form or call (800) 747-3365.


