Tax season document collection: beating the January crunch

For years, tax season at Scale CPA opened the way it does at most firms: a document request per client, sent the first full week of January, listing everything needed to prepare the return. Bank statements were always on that list. They were also, reliably, the items that came back last. A client would reply the same day with a payroll summary and the new loan agreement, and the twelve bank PDFs would trickle in over the following weeks, two or three at a time, with a couple of accounts still open when the preparer wanted to start.

None of that chase is unusual. What took us longer to see is that the January version of the problem behaves differently from the October version, and treating it with the same tools, a reminder email and then another one, is exactly how it swallows the season.

A year of collection debt, due at once

In a normal month, a late statement is an annoyance. One client, one or two documents, a short delay. Firms quietly tolerate this. If the tracker shows most accounts covered by mid-month, nobody escalates, and the two or three stragglers roll forward.

Tax season is where those stragglers stop rolling. Every gap you tolerated between February and November is still a gap, and now the file cannot ship without it. Multiply a few missing months per client across a full book and the PBC list stops being a request and becomes an excavation.

The list itself works against you. A PBC list is long, and clients answer long lists the way everyone does: they knock out the easy items and stall on the rest. Payroll reports come from one login and one export. Bank statements mean logging into each bank, finding the documents tab, selecting the right account, and downloading twelve separate periods per account. That is the item that gets deferred, which is the same dynamic we wrote about in how to stop chasing clients for bank statements, amplified by the fact that in January your email competes with every other advisor, lender, and processor asking that same client for year-end paperwork.

The difference between collecting as you go and collecting in one January pass looks like this:

Why December cannot arrive on January 2

Even a perfectly responsive client cannot complete your PBC list in the first week of January, because the documents do not exist yet.

A bank publishes a statement a few days after the cycle closes. Retrieval channels like Plaid’s statements API can only hand over a PDF once the bank has generated it, and the same is true of the client clicking around their own online banking. So a calendar-month December statement typically appears somewhere in the first week of January, later if the bank is slow.

Accounts on mid-month cycles are worse. A credit card that cycles on the 14th puts the back half of December into a statement running December 15 through January 14, which posts around January 17. Your year-end file is structurally incomplete until then, no matter who you email. We covered the mechanics in when statements don’t follow calendar months; at year end the straddle stops being a bookkeeping nuisance and starts gating tax work.

Here is the part that quietly poisons the season: if your PBC list goes out January 6 and your first reminder fires January 13, you have already nagged the client once for a document that did not exist. Do that every year and clients learn that your reminders can be ignored, including the ones that matter.

Problems that only surface in January

Three failure modes hide all year and reveal themselves during the crunch.

Closed accounts. A client shuts down an account in June, and most banks revoke online access at or shortly after closure. In January you discover the tracker has six months of history behind a login that no longer works. Recovering it means a phone tree, a branch visit, or a per-statement research fee, on the bank’s timeline rather than yours.

Broken connections and security holds. If you rely on bank feeds or stored logins, some fraction of them break every month through password changes, reissued cards, and bank security reviews. The big consumer banks, Wells Fargo, Chase, Bank of America, and Citi among them, all have security-hold flows that can freeze a previously working connection until the client acts. Discovering that in January, when you need twelve months of history through that connection, is the worst possible timing. The failure modes are cataloged in why bank statement connections break.

Processor statements. Ecommerce and SaaS clients get 1099-Ks from Stripe, PayPal, Square, Shopify, and the rest, and those forms need to tie to something. The monthly settlement statements from each processor are the support, and they are collected even less consistently than bank PDFs because nobody’s checklist mentions them until the 1099-K shows up.

What to do about it

The fixes stack. Each one shrinks how much the next has to carry.

Collect monthly, all year

This is the real answer, and there is no shortcut around it. If statements land in a consistent folder structure every month, the January PBC list drops its heaviest items and the season starts from verification instead of collection. The IRS expects supporting records to exist regardless of when you gather them; gathering them twelve times in small doses beats once in a landslide. The monthly cadence, filing convention, and ownership questions are laid out in our complete guide to collecting client bank statements.

Run a November inventory

Whatever your monthly discipline looked like this year, audit it before the season starts. Build the account list from the books rather than memory, then walk a simple grid of account by month and mark what is actually on file. Flag three things specifically: accounts closed during the year, cards on mid-month cycles whose December support will not exist until mid-January, and any connection that has not produced a document recently. Send one specific chase per client in November, naming exact accounts and months, and escalate by phone before the holidays. Clients still answer email in November. Our statement collection checklist is a reasonable starting grid.

December on autopilot

The structural fix is to stop asking for statements at all. With connection-based retrieval, each client authorizes a read-only link to their bank once, through Plaid or Mastercard Open Banking, and the official PDFs are fetched directly as each bank publishes them. This is the model we built StatementFlow around, on our own client book first: it learns each account’s real posting cycle, retries within the right window, verifies every download, and files it into the firm’s own Google Drive by client, year, and month. A coverage board shows the account-by-month grid with gaps, needed reconnects, and bank security holds flagged, so the November inventory is a screen rather than a project. It also pulls settlement statements from Stripe, PayPal, Square, Shopify, and similar platforms, which handles the 1099-K support problem in the same pass. To be clear about scope: it retrieves and files documents. It does no OCR or data extraction, it covers US banks only, and it is currently in early access.

Under that setup, December statements arrive in the first half of January without anyone asking, straddle-cycle cards show up when their cycles actually close, and the PBC list shrinks to the things only the client can provide.

The January crunch is optional. If you want your December statements to show up on their own next season, request early access and we will start with your account list.