Proving an EIDL Notice Defect: The Portal, the Record, and the Affidavit

Why the Record Decides This

A procedural challenge to a Treasury referral is an argument about what happened and when. Whether a required notice went out, where it went, what it said, and whether you had a fair opportunity to respond before the account moved.

Those are factual questions, and factual questions are won or lost on evidence rather than on assertion. A borrower who writes that he never got a notice has made a claim. A borrower who can show what his account displayed on a given date, what address the agency had on file, and what arrived and when, has made a record. The agency answers records. It files claims.

The practical problem is that almost none of this is stable. Portals update. Documents appear. Screens that showed one thing in March show something different in June, and the version you remember is not retrievable later. If you are reading this while the problem is live, the most valuable thing you can do today costs nothing and takes an hour.

What the Portal Does and Does Not Show

Borrowers treat the loan portal as the authoritative statement of where they stand. It is better understood as one view of the account, generated for a purpose, and not necessarily the same record the agency relies on internally.

Two gaps come up constantly. The first is that a missed payment does not always produce a visible change. The balance owed does not obviously jump, no past due figure appears, and nothing on the screen communicates that the account has moved into a different posture. A borrower checks, sees a number that looks normal, and reasonably concludes that nothing has happened.

The second is that the portal is not a correspondence archive. Documents that exist in the agency’s file may not appear there, and documents that do appear may have arrived long after the date they carry. Neither observation proves anything by itself. Both are worth documenting, because the borrower is usually the only person who saw the earlier version.

Documents That Appear Later Than They Should

A pattern worth naming, because borrowers describe it and then assume nobody will believe them.

An account shows no delinquency correspondence. The borrower raises the referral. Afterward, correspondence appears in the portal carrying dates well before the dispute was filed.

There are innocuous explanations. Systems batch-upload. Records migrate. Retention and display are not the same function, and a document can exist in a file long before it is exposed to a borrower-facing screen. None of that makes the observation meaningless. It makes it a fact that has to be established rather than asserted, and it can only be established by someone who captured the earlier state.

This is the single strongest argument for screenshotting an account the week a problem starts, with the date visible, before anyone has a reason to look. That evidence cannot be recreated afterward.

Address Mismatches

The recurring version of this is not an agency mailing to an address it had no reason to doubt. It is an agency mailing to an old address while the current one sits in the same file, often supplied by the borrower and reflected in electronic contact details.

Whether that matters turns on what the governing requirement actually demands and what the agency did, and it is fact-specific rather than categorical. What is not fact-specific is the documentation problem. Establishing it requires showing what address the agency had, when you provided it, and through what channel. Confirmation emails, portal update screens, and dated correspondence do that work. Recollection does not.

Building the Record Before You Argue

The sequence that helps most people is unintuitive, because the instinct after a bad notice is to write immediately and explain.

Capture first. Screenshot every screen of the account with the date visible, including the ones that appear to show nothing, because a screen showing nothing is the evidence. Save the full email history with the agency, including confirmations and automated messages. Collect every piece of physical mail, including envelopes, since postmarks and forwarding labels carry information the letter does not. Write down, while you remember it, the dates you updated contact information and how.

Then request the file. Asking the agency for the record of what was sent and where is a different act from disputing the referral, and doing it first means your argument is built on what the agency says it did rather than on what you think it did.

Only then write. A dispute drafted against a documented record is a different instrument from one drafted against a memory, and the first version you send is the one the agency answers.

While the Dispute Is Pending

Two expectations cause avoidable damage.

The first is assuming that filing pauses collection. It does not follow automatically, and the machinery in motion has its own timelines that are indifferent to a pending challenge. Anything you need held should be requested expressly, in writing, as its own ask.

The second is assuming that a favorable outcome resets the balance. A challenge to a referral is an argument about the referral and the servicing relationship. What has already been added to the account is a separate question governed by different authority, and it does not necessarily come off because the account moves back.

Both of those are reasons to be specific about what you are asking for. A dispute that seeks one thing and assumes three others is a dispute that gets answered narrowly.

Where This Sits

None of this is an argument that you have a defect. Plenty of borrowers received exactly what they were supposed to receive and do not remember it, and a challenge built on a defect that is not there costs time the account does not have.

It is an argument that the question is answerable, that the answer lives in documents rather than in recollection, and that the documents are easier to gather now than they will be in three months. If you are inside the window where any of this is live, the record you build this week is the record you will be arguing from.