The letter that arrives after a report is already filed
A Request for Additional Information from the FEC almost never shows up because of a dramatic, obvious violation. It shows up because something small and routine — a blank field, a total that doesn't quite add up, a contribution that quietly crossed a limit over several reporting periods — slipped through a report that otherwise looked complete.
This article looks closely at what actually triggers an RFAI in practice, why these gaps are so easy to miss under filing deadline pressure, and how a reconciled bank record catches most of them before a report is ever filed.
Why RFAIs are a recurring problem, not a rare one
Campaigns run on volunteer and short-staffed operations far more often than well-resourced ones — the person collecting donor information at a fundraiser is rarely the same person compiling the FEC report weeks later, and information can get lost or simplified somewhere between the two. A filing deadline compounds this: reports are frequently compiled in a rush at the end of a reporting period, exactly the condition under which a careful field-by-field check is most likely to get skipped.
It's also rarely a single reckless decision. More often it's a series of individually reasonable shortcuts — an occupation field left as "N/A" because the donor didn't answer, a batch payout total copied straight from the platform without independently verifying it against the bank deposit. Each shortcut makes sense in isolation; it's only the accumulated gaps, reviewed together by the FEC, that produce a Request for Additional Information in the end.
The single most common trigger
Federal law requires a committee to make a best effort to obtain and report a donor's occupation and employer for contributions above the itemization threshold. In practice, this single requirement generates more RFAIs than almost any other category — a field left blank, or filled with something too vague to satisfy the best-effort standard, on an otherwise well-documented contribution.
What makes this trigger so persistent is that it rarely comes from carelessness — it comes from a donor genuinely not answering the question at the moment of giving, especially for an online contribution made quickly through a mobile donation form. The best-effort standard doesn't require a committee to have the information at the moment of collection, but it does require following up to try to get it before the report is filed, which is the step that most often gets skipped under deadline pressure.
When the totals simply don't add up
A report where the sum of itemized and unitemized contributions doesn't match the reported total raised is one of the most mechanically obvious things the FEC's own review software catches. This usually traces back to a batch payout total that was never independently verified against its bank deposit — a processing fee miscalculated, or a contribution refunded after the payout report was generated but before the total was finalized.
Because this kind of error is purely arithmetic, it's also one of the easiest to prevent — the check is simple to run, it just has to actually be run on every batch, not assumed to be fine because the platform's own report looks authoritative.
A subtler version of the same problem shows up when a committee's own compliance system total and its bank-derived total are compiled by different people, from different source documents, without ever being cross-checked against each other before the report is assembled — two internally consistent numbers that simply disagree with one another, neither one obviously wrong until someone actually compares them.
Contributions that quietly cross the limit
A donor's third or fourth contribution across several reporting periods can push their aggregate total past the federal limit even though each individual gift looked unremarkable on its own. Without a persistent, cross-period aggregate tracked per donor, this pattern is invisible until the FEC's own review flags it after the fact.
This trigger is particularly common for donors who give consistently but modestly — a $500 contribution four times a cycle looks, on any single occasion, like a perfectly ordinary mid-size gift. It's only when someone deliberately adds all four together, checked against the correct election designation, that the pattern becomes visible.
A contribution that should have been itemized, and wasn't
A donor whose contributions individually stayed under the itemization threshold but whose cumulative total for the cycle crossed it should have their full contribution history itemized retroactively — not just the specific gift that pushed them over. Missing this retroactive itemization is a common, easy-to-overlook gap, since it requires looking backward at prior contributions from the same donor, not just forward from the current one.
This is exactly why a persistent, cross-period aggregate matters for more than just the contribution limit itself — the same running total that flags a donor approaching the federal limit is what also flags the moment a donor's cumulative giving first crosses the itemization threshold, triggering the retroactive itemization requirement before it becomes a gap discovered later.
The one check that catches most of these before filing
Nearly every trigger described above shares a common root: a reported figure that was never independently verified against the underlying bank record. Reconciling every deposit against its source contributions, checking every itemized donor field for completeness, and rolling up aggregate totals across the full cycle — done together, before a report is filed rather than after an RFAI arrives — catches the overwhelming majority of these issues at the point where they're cheapest to fix.
The documentation a real reconciliation actually needs
| Document | Used to confirm |
|---|---|
| Bank statement for the full reporting period | Every deposit that actually hit the account |
| Platform payout reports (ActBlue, WinRed, etc.) | The individual contributions behind each batch deposit |
| Prior period contribution records | Cross-period aggregate totals per donor |
The most common findings
A donor field left as generic filler text
"N/A" or "unknown" entered on a required occupation or employer field to move past it quickly during data entry.
A batch payout total accepted without verification
The platform's reported total copied directly into the report without checking it against the actual bank deposit.
A donor's aggregate never rolled up across periods
Each reporting period treated in isolation, missing that the donor's cumulative total had already crossed the limit.
A contribution recorded on the wrong date
The compliance system's entry date used instead of the bank's actual transaction date, shifting which reporting period a contribution belongs to.
An example of what a finding looks like
A congressional campaign believed its quarterly report was clean, based on a compliance system export that matched its own internal donor list. A closer reconciliation against the bank statement revealed a batch payout from an online platform where the disclosed processing fee had been miscalculated, leaving the reported total roughly $400 short of what the bank actually deposited.
| Item | Detail |
|---|---|
| Reported total from payout report | $18,600 |
| Actual bank deposit | $19,020 |
| Root cause | Processing fee miscalculated in the platform's own summary, never independently verified |
What happens when an RFAI arrives
An RFAI itself is a request to clarify or correct, not an accusation — but it does start a clock. A committee that responds promptly and clearly, typically by filing an amended report that fixes the identified issue, generally resolves the matter without further escalation. A committee that misses the response window, or responds incompletely, risks the matter escalating toward a more serious review.
There's also a reputational dimension worth naming, even though it's harder to quantify than a compliance penalty. RFAIs and any amended filings that result from them are part of the public record, viewable by opposition researchers, journalists and watchdog groups alike. A committee that resolves an RFAI quickly and cleanly rarely draws further attention; one that accumulates several over a cycle, or responds slowly, can become a small but recurring line in coverage of the campaign's operations.
How much time you actually have to respond
The FEC's letter specifies its own response deadline, commonly around two weeks from the date of the request. That window is often tighter than it looks once the actual work of pulling supporting documentation, confirming what happened, and drafting an amendment is accounted for — especially if the campaign is also mid-cycle and juggling an active fundraising and reporting schedule alongside the response.
A campaign with an already-reconciled bank account has a significant advantage here: the supporting documentation for whatever the RFAI is asking about is already organized and traceable, turning what could be days of reconstruction into a much shorter task of pulling an existing record.
Preparing before the FEC asks
The most effective preparation isn't waiting for an RFAI to force the question — it's having a fully reconciled bank account and a documented aggregate donor history ready before a report is even filed. A committee that can answer "does this tie to the bank record" for every figure in a report is far less likely to receive an RFAI in the first place.
This kind of preparation also pays off in a context beyond the RFAI itself — a campaign approaching a bank for a line of credit, a lender conducting due diligence, or a national party committee evaluating whether to invest further resources in a race all benefit from a campaign that can produce clean, reconciled financials on short notice, rather than scrambling to assemble them under a new deadline.
The value of a periodic internal check
A reconciliation done at the close of every reporting period — even a modest one — is the simplest way to catch a gap early, before it compounds into a larger surprise. It doesn't need to be exhaustive; confirming that deposits match their sources and donor fields are complete for that specific period is often enough.
The habit is worth more than the individual check. A campaign that reconciles every period builds a running, current picture over time, where each check only has to confirm what changed since the last one. A campaign that never checks until an RFAI forces the question has to reconstruct an entire reporting history from scratch under a response deadline — a materially harder and more error-prone task than the routine version ever was.
There's also a quieter cost to the alternative worth naming directly: a committee that never reconciles until forced to carries a low-grade, ongoing uncertainty about its own numbers that never fully goes away. That uncertainty shows up as hesitation whenever a hard question is asked — by a journalist, an opponent's campaign, or the FEC itself — even when the underlying finances turn out to be perfectly fine once actually checked.
Myths worth retiring
"If a field were missing, our compliance software would have caught it"
Compliance software validates the data it's given — it can't catch a field that was never populated correctly in the first place, or a bank deposit that was never independently checked against it.
"An RFAI means something serious went wrong"
Most RFAIs address a single, correctable gap — a field, a total, an aggregate — not a broad pattern of wrongdoing.
"Only large, well-funded campaigns get RFAIs"
Smaller campaigns with less formal financial oversight are, if anything, statistically more exposed, simply because there's less redundancy checking the work.
"Once the report is filed, there's nothing more to do"
A filed report isn't final until the reporting period closes without a follow-up request — treating filing as the finish line, rather than reconciliation as the ongoing habit, is what leaves gaps unaddressed.
When an RFAI becomes something more serious
Most RFAIs resolve cleanly with a prompt, complete response or an amended filing. The matter tends to escalate when a response is missed entirely, when the same category of gap recurs across multiple reporting periods without correction, or when a response raises further questions rather than resolving the original one — patterns that suggest a systemic reconciliation gap rather than a one-off oversight.
A committee facing a recurring pattern of RFAIs is generally better served by fixing the underlying reconciliation process than by treating each individual letter as an isolated event to respond to and move past.
It's worth being clear about what "more serious" actually means in practice: a referral for further review, a formal audit, or in genuinely severe cases, an enforcement matter. These outcomes are uncommon and generally reserved for patterns of neglect or apparent intentional misreporting, not for a single missed field or an isolated timing gap — the vast majority of RFAIs never escalate beyond a straightforward amended filing.
A small race vs. a well-funded campaign
A local race with a handful of donors and one bank account rarely needs a formal reconciliation process at all — the volume is low enough to check by memory. A well-funded federal campaign running multiple fundraising channels, hundreds of donors, and a compressed filing calendar faces a fundamentally different volume problem, and the risk of a gap surfacing rises sharply with each additional channel and each additional reporting period.
How long records should be kept
Federal law generally requires campaign finance records to be retained for a set period after a report is filed, and keeping bank statements, payout reports and reconciliation documentation organized well beyond the minimum gives a much stronger position if an RFAI or audit ever reaches back to a prior cycle.
In practice, digital storage makes this retention nearly costless — the marginal reason to delete old reconciliation records before the retention window even closes is thin, and the downside of not having them if a question resurfaces years later is real. Most committees are better served by keeping records longer than the minimum rather than treating the requirement as a ceiling.
A checklist before every filing
Every bank deposit matched to a specific source
Every batch payout verified against its bank deposit
Occupation and employer confirmed on every itemized contribution
Donor aggregate totals rolled up across the full election cycle
Unreconciled items resolved or documented as a known follow-up
Any recent refunds or redesignations reflected in the totals
How a review typically unfolds
A typical pre-filing review starts with matching every bank deposit to its source, followed by verifying batch payout totals against those deposits, then checking donor fields and rolling up aggregate totals. If anything doesn't tie out cleanly, that step is revisited until nothing unexplained remains before the report is submitted.
Does committee type change the risk
Candidate committees, PACs and party committees all face the same underlying triggers — the specific form filed differs, but the requirement that every reported dollar trace to a bank record doesn't. A PAC contributing to many candidates simultaneously simply has more surface area for a gap to occur, given its higher transaction volume, not a different kind of risk.
Presidential committees add their own layer of complexity — larger fundraising volume, more donation platforms in play at once, and often a compressed timeline for the earliest reporting periods of a campaign — but the same fundamental principle applies: every dollar reported has to trace to an actual bank deposit, regardless of how many zeros are involved.
Life after an RFAI
After resolving an RFAI, the natural next step is examining why the underlying gap wasn't caught before filing — whether that means adding a reconciliation step to the existing workflow, or simply building the habit of checking every batch payout against its bank deposit going forward. Many campaigns use the experience as the moment to establish the periodic review habit they didn't have before.
What might change going forward
FEC reporting and review processes continue to evolve, and some of the most common triggers — particularly automated math-error checks — are increasingly caught by the FEC's own filing software before a report is even accepted. That doesn't remove the value of independently confirming what's actually in the bank account before filing — a documentation habit built around reconciliation remains useful regardless of how the FEC's own review tools evolve.
What's less likely to change is the underlying reason these gaps occur in the first place — campaigns will keep running on compressed timelines and thin staffing, and the fields most dependent on manual follow-up, like occupation and employer, will likely remain the harder category to fully automate away. A reconciliation habit built around catching these gaps early stays relevant regardless of how the FEC's own tooling evolves around the edges.
The specific mechanics of compliance software will keep changing; the underlying discipline of checking every reported number against the bank record it came from is likely to remain the constant worth building a routine around.
In short
An FEC Request for Additional Information is easy to miss coming because it hides inside ordinary, routine gaps — a blank field, an unverified total, a slowly accumulating donor aggregate — not because anyone is trying to conceal anything. Reconciling every bank deposit against its underlying contributions, checked carefully before a report is filed, is what separates a committee that never hears from the FEC beyond a routine acknowledgment from one that's fielding a follow-up letter every other cycle.
None of the individual checks described here is exotic — a date, an amount, a name are the same three things any bank statement and payout report already print. What separates a clean filing history from a recurring RFAI pattern is simply whether those checks get run carefully and consistently, rather than skipped under the pressure of the next deadline.