On May 29, 2026, the Department of Education published Electronic Announcement GENERAL-26-31, a set of best practices for preventing FAFSA fraud and protecting Title IV funds. The guidance is direct about what it wants institutions to do: place immediate holds on accounts when risk indicators appear, hold the release of credit balance refunds while a case is under review, and require layered identity documentation that can run from a government-issued photo ID all the way to a birth certificate and a signed Social Security card.
For most financial aid directors, the next question arrives within about thirty seconds: under what authority? The FSA Handbook is unambiguous that a school cannot require extra information from a student to package Title IV aid. So how does an institution square an aggressive hold-and-document posture with a rule that appears to forbid exactly that?
The EA Tells You What to Do, Not How to Do It
GENERAL-26-31 is sub-regulatory guidance. It says so plainly: the practices it describes “are not exhaustive and do not replace existing statutory or regulatory requirements.” The Department is pointing institutions toward an outcome — earlier fraud detection, fewer improper disbursements — and citing real campus policies as illustrations, but it is not handing schools a new, self-contained legal mechanism for holding aid or demanding documents.
That is the gap most institutions are feeling right now. The EA describes the destination without naming the road that gets you there lawfully.
The road already exists. It runs through 34 CFR 668.16(f) — the conflicting information requirement that has governed Title IV administration for decades. The reframe institutions need is simple: suspected FAFSA fraud is conflicting information. Once you treat it that way, the authority to require documentation and to hold aid is not improvised. It is the same authority your office already exercises every time an ISIR comes in with a discrepancy.
Why You Can Require Documentation: Suspected Fraud as Conflicting Information
Start with the rule institutions worry about. The Application and Verification Guide states that the FAFSA form is the only application a student must complete to apply for Title IV aid, and that “a school cannot require extra information from students to package Title IV aid, except for verification, resolution of conflicting information, or professional judgment determinations.”
Read the exception, not just the prohibition. Resolution of conflicting information is one of the three carve-outs that permit a school to require more from a student. So the question is whether a credible fraud concern qualifies as conflicting information. It does.
Under 34 CFR 668.16(f), an institution must develop and apply an adequate system to identify and resolve discrepancies in the information it receives from different sources about a student’s Title IV application. The Handbook is explicit that a school must resolve conflicting information before disbursing aid, that this duty applies to every student rather than only those selected for verification, and that the obligation to resolve conflicting information supersedes the verification rules entirely. When a school has reason to believe an applicant’s information is incorrect, it must resolve that discrepancy first.
A suspected-fraud signal is, by definition, a reason to believe the information may be incorrect. The new real-time fraud detection framework described in Electronic Announcement APP-26-03 (April 15, 2026, updated May 29, 2026) reinforces this. An ISIR carrying Reject Code 74 with Comment Code 354 or 355, or Reject Code 75 with Comment Code 357, is the Department telling you it could not confirm the applicant’s identity and considers the application high-risk or higher-risk for fraud. That is conflicting information arriving on the transaction itself. Treating it as anything less is hard to defend.
The practical consequence: when you have a documented, good-faith fraud concern, requiring identity documentation is not “requiring extra information to package aid.” It is resolving conflicting information — squarely within the exception — and you may withhold disbursement until the discrepancy is resolved.
Playbook A: Update Your Conflicting Information Policy to Cover Fraud
If suspected fraud is conflicting information, then your conflicting information policy is the document that has to carry the weight. Most policies written before 2025 do not mention fraud indicators at all. Three steps close that gap.
First, name fraud indicators as conflicting information triggers, in writing. Your policy should state that specified red flags constitute conflicting information requiring resolution before disbursement. Tie the list to two sources: the indicators GENERAL-26-31 describes — suspicious identity documents, inconsistent demographic data, unusual address changes, conflicting FAFSA submissions, suspicious refund requests — and the APP-26-03 comment and reject codes. When the trigger is mapped to a regulatory basis, a hold stops looking arbitrary and starts looking like administrative capability.
Second, build the escalation channel the EA assumes you already have. GENERAL-26-31 stresses that conflicting information can originate in admissions, the registrar, academic affairs, and other offices, and that fraud prevention is a campuswide responsibility rather than a financial aid function. The Handbook agrees: any office that holds information affecting a student’s Title IV eligibility must route it to the school’s designated coordinating official, who forwards it to financial aid for resolution and documentation before the student receives further aid. Put that channel in writing — a single intake path from admissions, the registrar, the bursar or student accounts, IT, conduct, and campus security into the FA coordinating official — and the policy becomes operational instead of aspirational.
Third, specify documentation tiers, hold authority, and the resolution standard. Define what a lower-risk case requires versus a higher-risk case, consistent with the layered approach the EA endorses. State who has authority to place and release a hold. And specify the resolution standard the Handbook already requires: you have resolved conflicting information when you have determined which data are correct, and you must document that finding with an explanation that justifies the decision. Resolution is not “we collected a document.” It is “we determined the truth and wrote down why.”
Playbook B: Holding and Documenting a Title IV Credit Balance
The credit balance question is where institutions feel the most exposure, because the timing rule looks absolute. Under 34 CFR 668.164, a school generally has 14 calendar days to pay a Title IV credit balance to the student or parent unless it has written authorization to hold. Delaying a refund past that window is a common audit finding.
But the 14-day clock rests on a premise: that a bona fide Title IV credit balance exists. A credit balance arises only after Title IV funds have been properly disbursed to an eligible student and exceed allowable charges. When a credible fraud concern is unresolved, the student’s underlying eligibility has not been confirmed — which means a genuine, payable credit balance has not yet been established. On that reading, the 14-day obligation has not been triggered, because there is not yet a credit balance the institution is required to release. This is McClintock & Associates’ reasoned interpretation of how the conflicting information requirement and the cash management rules interact; it is not a verbatim Department position. So document accordingly.
The Department’s own guidance supports holding in this posture. In Electronic Announcement GENERAL-24-71 (updated August 1, 2024), ED reminded schools that they may not return already-disbursed Title IV funds while waiting to receive requested documentation under the interim disbursement rules, and that the school should not make subsequent disbursements until the documentation is received and reviewed. The Handbook likewise provides that when conflicting information is discovered after disbursement, the school may remove the disbursements from the student’s account and require resolution before disbursing any further aid.
What you document matters more than the hold itself. For each held credit balance, your file should capture the specific conflicting information that triggered the hold, the date it was identified, the regulatory basis (668.16(f) and the relevant comment or reject code), the documentation requested, the resolution steps taken, and the outcome. If the student resolves the discrepancy, release the funds and note the resolution. If they do not, follow your overpayment and referral procedures.
One guardrail keeps this defensible. Under 34 CFR 668.16(s), a school must disburse funds in a timely manner and may not avoid a Return of Title IV Funds calculation or to manage its 90/10 ratio. A blanket delay applied to manage cash flow, dodge an R2T4, or shape a 90/10 result is not — and it will be read as exactly that in an audit. The line between the two is your documentation.
McClintock’s Perspective
The EA is, in effect, an invitation to use authority institutions already have more aggressively. The risk is not that schools will lack the authority to act — it is that they will act without the policy architecture that makes the action defensible.
Two environments concentrate the exposure. Online and short-term programs, where a fraudulent actor’s entire objective is to secure a credit balance refund before being identified, are where holds matter most and where speed pressure is highest. And institutions operating at scale, processing fraud flags across many programs and campuses, are where an inconsistent or undocumented conflicting information practice turns into a systemic finding rather than a one-off.
In our experience analyzing Title IV compliance for postsecondary institutions, the schools that weather fraud scrutiny are not the ones with the most aggressive holds. They are the ones whose conflicting information policy already named fraud as a trigger, whose escalation channel already existed on paper, and whose files already showed a determination of which data were correct and why. The authority is settled. The discipline is what gets audited.
If your conflicting information policy still reads the way it did before the Department stood up real-time fraud detection, it is worth a focused review before the next disbursement cycle. We can help you align your policy, escalation channel, and credit balance documentation with the conflicting information framework — so that when you hold aid, the file defends the decision.
Frequently Asked Questions
Yes, when the request is tied to a documented conflicting information concern. The FSA Handbook permits a school to require additional information for verification, resolution of conflicting information, or professional judgment determinations. A credible fraud indicator is conflicting information under 34 CFR 668.16(f), so layered identity documentation — up to and including a birth certificate and signed Social Security card, as ED’s May 29, 2026 guidance illustrates — falls within that exception.
Yes. Under 34 CFR 668.16(f), an institution must resolve discrepancies in the information it receives about a student’s Title IV application before disbursing aid. A credible fraud signal — including a FAFSA flagged with Reject Code 74 or 75 and the associated fraud comment codes under Electronic Announcement APP-26-03 — is a reason to believe the application information may be incorrect, which is the definition of conflicting information.
A school generally must pay a Title IV credit balance within 14 calendar days under 34 CFR 668.164 unless it has written authorization to hold it. However, a bona fide credit balance only exists once funds are properly disbursed to an eligible student. When suspected fraud is unresolved conflicting information, eligibility is not yet confirmed, so a payable credit balance has not been established and the 14-day clock is not triggered. This is a reasoned interpretation rather than an explicit ED rule, so institutions should document the conflicting information basis carefully and avoid any hold that functions as a delay to manage R2T4 or 90/10.
Possibly. Resolving a discrepancy for packaging purposes is separate from the referral duty. Under 34 CFR 668.16(g), an institution must refer credible information indicating fraud or other criminal misconduct in connection with a Title IV application to the Department’s Office of Inspector General. You do not need to prove the case before referring it.
Yes. The Handbook is explicit that the duty to resolve conflicting information applies to all students, not only those selected for verification, and that it supersedes the verification rules. A school must resolve a fraud-related discrepancy before disbursing aid regardless of the student’s verification status.
