2026-09-11

The SAVE plan's 90-day window closes this month — how to turn pay stubs into the income documents your new plan needs

On July 1, 2026, loan servicers began mailing a notice to the roughly seven million borrowers still enrolled in the SAVE plan: leave within 90 days, or be moved automatically. The notices followed a federal court's March 10, 2026 judgment ending SAVE outright, entered as part of a settlement with Missouri and other states that had sued over the plan. Ninety days from July 1 lands right around the end of September — which means that if you're one of those borrowers, you are, right now, inside the closing days of a window that decides how your loan payment gets calculated for the next year. What the notice doesn't spell out in plain language is the paperwork fork behind that choice, or exactly what "documentation of income" has to look like if you take the path that doesn't run through the IRS. That's a job NearPDF's merge, rotate, organize, and delete tools were built for — turning a phone's worth of crooked pay-stub photos and an oversized bank statement into the one clean file a loan servicer's upload portal actually asks for, without any of it leaving your device to do it.

What happens if you don't pick a plan

studentloanborrowerassistance.org, a project of the National Consumer Law Center that tracks this kind of thing closely, describes the default in plain terms: miss your 90-day window and the Department of Education will "automatically reassign" you to the Standard Repayment Plan — a plan sized to your loan balance, not your income, with a fixed payment over up to 10 years. NerdWallet's reporting adds a caveat worth taking seriously: which plan you actually land on afterward "will depend on [your] circumstances," so treat the Standard Plan as the assumption to plan around, not a guarantee of exactly what happens. Either way, doing nothing is very unlikely to leave your payment where it is now.

Submitting an application doesn't guarantee a fast answer, either. The College Investor's tracking of the Department's own monthly status reports counted 1,386,406 income-driven repayment applications still sitting in the processing queue as of July 31, 2026 — the most recent figure the Department has published. A file that's rejected or bounced back for being incomplete, sideways, or missing a page doesn't just cost you a resubmission; it costs you another trip to the back of that line. Getting the upload right the first time isn't just tidiness — it's the difference between weeks and months.

The fork every borrower hits: consent, or documentation

With SAVE gone, the plans left on the table are PAYE, IBR, and ICR (the online application at StudentAid.gov/IDR will pick "the income-driven repayment plan with the lowest monthly payment" for you automatically if you ask it to). The application itself — Form IDR, OMB No. 1845-0102 — tells borrowers plainly that "it's faster and easier to complete this form online at StudentAid.gov" rather than mailing it, which is exactly why the file you upload matters. Before you get to picking a plan, though, the form asks a more consequential question: will you let the Department pull your income straight from the IRS every year, or will you provide it yourself?

Consenting means the Department gets your Federal Tax Information "on an annual basis" and automatically recertifies your plan each year — no upload required. Declining is explicitly allowed — "you are not required to provide your consent, approval, or agreement as a condition of eligibility for an IDR plan" — but the form is just as explicit about the tradeoff: if you don't consent, "you are required to provide alternative documentation of income." That second path is where a stack of loose files becomes a real problem, and it's also where the form gets unusually specific about what it wants:

• "The date on any supporting documentation you provide must be no older than 90 days from the date you sign this form."
• "Documentation will usually include a pay stub or letter from your employer listing your gross pay," and you should "write on [it] how often you receive the income" — "twice per month" or "every other week."
• "You must provide at least one piece of documentation for each source of taxable income" — a second job or freelance income each need their own proof, not just your main paycheck.
• Separately, the form's completion instructions say to "include your name and account number on any documentation that you are required to submit with this form" — every page, not just a cover sheet.

None of that is unusual by federal-form standards, but it does describe, almost exactly, a document-assembly job: several dated, labeled proofs, one per income source, gathered into whatever a given servicer's upload portal expects — often a single file, sometimes one file per document type.

Turning your scans into the file the form actually asks for

None of NearPDF's tools turn a photo into a PDF — a pay stub photographed on a phone still has to go through a scanning app first, exactly as described in NearPDF's post on rental application documents, which walks through the same first step for a different kind of income proof. Once you have a PDF per pay stub, employer letter, or bank statement page, NearPDF's workspace is where the actual assembly happens, entirely in the browser:

• Rotate any pay-stub photo a phone camera caught sideways or upside down, page by page, using the same per-page control described in NearPDF's rotation post — before you save, not after.
• Delete the pages of a downloaded bank statement you don't need. A servicer asking for proof of deposits doesn't need your entire 12-page statement; trim it down to the page or two that actually show income landing in the account.
• Organize the remaining pages into the order the form's own logic follows — your documentation, then your spouse's if you're filing jointly and required to document their income too.
• Merge everything into one file if that's what your servicer's upload widget expects, rather than sending five separate attachments and hoping the reviewer keeps them straight.

One mechanical limit is worth flagging before you start: NearPDF can't open a file that's already password-protected, and some banks export statements as encrypted PDFs by default — if a downloaded statement won't add to the workspace, that's very likely why, and you'll need to remove the password first using whatever tool your bank's portal provides for it.

What NearPDF genuinely can't do here

Worth being honest about the edges of this, the same way as always. NearPDF has no way to write your name and account number onto a page — the form's own instruction to label every document is something you still have to handle yourself, either by writing it on the paper before you scan it or through whatever annotation tool your scanning app offers; NearPDF's page-number tool adds a running numeric sequence, not arbitrary text, so it isn't a substitute. And because NearPDF only deletes whole pages rather than redacting parts of one, a bank-statement page that shows both the deposit you need and a list of unrelated purchases can't be trimmed down to just the deposit — your options are to include that whole page or leave it out entirely. Finally, the finished PDF isn't encrypted by NearPDF either; if a file carrying your name, account number, and income now sits on your own device before you upload it, keeping that copy secure is a job for your device's own storage, not the tool that assembled it.

The plan-by-plan cost of missing the window anyway

The same government form spells out what happens if a borrower already on one of these plans misses their annual recertification deadline — worth knowing even if your immediate task is the one-time SAVE switch, since it's the same clock you'll be on every year after:

• IBR: "failure to submit documentation by the deadline will result in the capitalization of interest and increase in payment amount to the 10-year standard payment amount" — the only one of the three surviving plans where missed paperwork also grows your principal balance.
• PAYE: the payment jumps to "the 10-year standard payment amount," but without interest capitalizing.
• ICR: the payment is "recalculated" to the same 10-year standard amount, also without capitalization.

Separately, borrowers already enrolled in one of these plans got their own extension: FSA pushed annual recertification deadlines out to "no earlier than February 2026" for most borrowers, so a due date that already looked distant may be closer than your account currently shows once servicers finish updating it. The safe assumption either way is the same one that applies to the SAVE switch itself: check your actual date at StudentAid.gov rather than guessing, and don't wait until the week it's due to start gathering documentation you don't already have as a PDF.

The honest summary

Nothing about this deadline is about page limits or file formats — it's a real legal switch, on a real clock, with a real difference between an income-based payment and one sized to your full balance. NearPDF doesn't know which plan is right for you, doesn't talk to the IRS on your behalf, and can't write the label the form asks for onto a page. What it does is the mechanical half: straightening a crooked scan, trimming an oversized statement down to the page that matters, putting everything in the order the form expects, and merging it into the one file your servicer's portal is actually built to accept — entirely on your device, with nothing uploaded until you choose to send it yourself.