FEC Compliance Bookkeeping for Political Campaigns and PACs: A Treasurer's Guide

A campaign treasurer in a mid-size House race gets a letter from the Federal Election Commission 45 days after filing a quarterly report. It's a Request for Additional Information — an RFAI — flagging a $2,600 contribution that didn't match the itemization on Schedule A, a vendor payment coded to the wrong purpose, and a cash balance that didn't reconcile to the bank statement by $340. The campaign has 35 days to fix it, or the discrepancy gets escalated toward an audit referral. None of this happened because anyone tried to hide anything. It happened because nobody was doing double-entry bookkeeping, and a spreadsheet full of manual entries drifted quietly out of sync with reality.

This is the single most common way small campaigns and political action committees get into trouble with the FEC: not fraud, but sloppy recordkeeping that data-driven review catches almost automatically. The Federal Election Commission's Reports Analysis Division (RAD) reviews every disclosure report filed by every federal candidate committee, party committee, and PAC, and increasingly does so with automated matching against bank records, prior filings, and donor databases. If your books don't reconcile, the system finds it — and finding it starts a clock you don't want ticking.

Who Needs to Care About This​

If you're a treasurer for a candidate committee, a political action committee (PAC), a separate segregated fund (SSF) tied to a corporation or union, or a state/local party committee that touches federal elections, FEC compliance isn't optional bookkeeping hygiene — it's a legal duty with personal liability attached. The treasurer, specifically, is the person the Federal Election Campaign Act holds responsible for the accuracy of every report filed, even if a bookkeeper or compliance vendor does the day-to-day entry work.

That personal liability is worth sitting with for a second. Unlike a business owner who can point to an LLC's liability shield, a campaign treasurer signs disclosure reports under penalty of law and can face civil penalties, and in serious cases referral to the Department of Justice, for reports that are knowingly false or grossly negligent. Good books aren't just about avoiding an audit — they're about protecting the person whose name is on the filing.

The Core Recordkeeping Requirements​

Every dollar that comes into a federal committee needs to be tracked with more detail than a typical small business would ever bother with, because the source of money in politics is the whole point of disclosure law.

For every contribution, regardless of amount, the committee must record:

• The name and address of the contributor
• The date received and the amount
• The date it was deposited (contributions must be forwarded to the treasurer within 10 days of receipt, and deposited or refunded within a further set window)

Once a contributor's cumulative giving to the committee exceeds $200 in a cycle, the recordkeeping bar rises sharply. The committee now must also capture:

• The contributor's occupation and employer
• Itemized reporting on Schedule A of the relevant disclosure report

This $200 aggregation threshold is where most bookkeeping systems fall apart, because it's not a per-transaction rule — it's a running total. A donor who gives $75 in January, $60 in March, and $90 in June crosses $200 on that third gift, which means all three contributions now need occupation and employer data attached, not just the one that pushed the total over. If your tracking system isn't built to aggregate by contributor across the full reporting period, you'll miss this every time, and it's one of the most frequently cited errors in FEC audit reports.

Cash contributions have their own hard ceiling: no more than $100 in cash from any one source, and anonymous cash contributions are capped at $50 — anything above that must be disposed of for a purpose unrelated to any federal campaign.

Records must be kept for three years from the filing date of the report the records support, not three years from when the contribution was received. For a committee that operates across a full election cycle, that means retaining detailed contributor records well past the election itself.

2025–2026 Contribution Limits, and Why They're a Bookkeeping Problem​

The dollar figures matter for compliance, but the bookkeeping challenge is less about knowing the limit and more about tracking against it in real time, across every contributor, across every account the campaign might have.

For the 2025–2026 cycle:

• Individual to a candidate committee: $3,500 per election (primary and general count separately, so an individual can effectively give $7,000 across a full cycle if the candidate runs in both)
• Multicandidate PAC to a candidate: $5,000 per election
• Individual to a national party committee: $44,300 per year (up from $41,300 in the prior cycle)
• Individual to a national party's separate accounts (for things like conventions, headquarters, and legal proceedings): triple the regular limit, or $132,900 per account per year

The reason this becomes a bookkeeping headache rather than a simple lookup table is that limits apply per election, not per calendar year, and a single donor can touch a candidate committee, a joint fundraising committee, and a PAC in ways that all need to be tracked against the same underlying cap. A joint fundraising committee in particular has to allocate each check across participating committees according to each one's remaining capacity under the donor's limit — get the allocation math wrong and you've created an excessive contribution for one of the recipients, which then has to be refunded within 60 days of discovery or it becomes a reportable violation in its own right.

This is exactly the kind of problem that benefits from a system with real double-entry logic and an audit trail, rather than a shared spreadsheet where the running-total formula gets overwritten by a well-meaning volunteer three weeks before the pre-general filing deadline.

The 2026 Filing Calendar​

2026 is a midterm election year, which changes the filing rhythm for a lot of committees:

• Year-end report: due January 31, 2026, covering all activity through December 31, 2025
• PACs that filed semi-annually in 2025 move to quarterly filing in 2026 — this is an easy one to miss if you're running on last cycle's calendar
• National party committees file monthly, no exceptions
• Candidate committees file quarterly, plus pre-primary and pre-general reports timed to actual election dates in their state, plus a post-general report if the candidate makes it to the general election
• 48-Hour Notices (FEC Form 6) are required any time the committee receives $1,000 or more from a single source in the final 20 days before an election — these are filed on top of, not instead of, the regular periodic report
• Special elections layer their own pre- and post-election reports on top of whatever regular schedule a committee is already on

Electronic reports must be received and validated by the FEC by 11:59 p.m. Eastern on the filing date — not just submitted, validated. A file that bounces for a formatting error at 11:58 p.m. is a late filing, and late filings are one of the FEC's most consistently assessed civil penalties, usually calculated on a sliding scale tied to how late the report was and how much financial activity it covered.

What Actually Triggers an Audit​

The FEC doesn't publish its exact internal thresholds for referring a committee from routine review to a full audit — those procedures are deliberately kept partially confidential so committees can't reverse-engineer exactly how much to skate under. But the publicly known pattern is consistent across audit reports the Commission does release:

1. Reports that don't reconcile. If the cash-on-hand figure in one report doesn't mathematically connect to the prior report plus that period's receipts minus disbursements, RAD flags it immediately. This is the single most common trigger, and it's almost always a bookkeeping failure, not a disclosure failure.
2. Repeated RFAIs on the same issue. A committee gets a Request for Additional Information and has 35 days to amend or explain. Fix it once, no problem. Get the same category of RFAI two or three reporting periods in a row, and it reads as a pattern of non-compliance rather than a one-off error — which pushes a committee toward the Office of General Counsel or the Audit Division rather than a simple administrative fine.
3. Contributions that exceed limits or come from prohibited sources (corporate treasury funds, foreign nationals, contributions in someone else's name) that aren't refunded within the required window.
4. Random and for-cause selection. The FEC does select some committees for audit essentially at random as part of routine oversight, but a documented complaint, a whistleblower tip, or a pattern spotted by RAD analysts can also trigger a for-cause audit outside the random pool.

The through-line across all four is that clean, reconciled, well-documented books are the actual audit-prevention strategy — not clever interpretation of the rules. A committee that can produce a bank reconciliation matching its FEC filing to the penny, with every contributor's aggregate total tracked and every disbursement purpose-coded, essentially audits itself before the FEC ever needs to ask.

Building a Bookkeeping System That Actually Holds Up​

A few practices separate campaigns that sail through reporting periods from ones that live in a permanent state of RFAI response mode:

• Reconcile the bank account before you build the report, not after. Every disbursement and every deposit should match a bank transaction before it goes on a disclosure form. Building the report from bank truth rather than from memory or an unreconciled ledger eliminates the single most common audit trigger outright.
• Track contributor aggregates continuously, not at filing time. Waiting until the report deadline to sum up each donor's cycle-to-date total is how the $200 occupation/employer threshold gets missed. A ledger structured so every contribution posts against a running per-donor total catches the threshold the moment it's crossed.
• Separate accounts by purpose from day one. A candidate committee, an affiliated joint fundraising committee, and a leadership PAC are legally distinct entities even when the same people run all three. Commingling their transactions in one set of books — even informally, even temporarily — is exactly the kind of error that turns into an excessive-contribution problem during an audit.
• Code every disbursement to a purpose the moment it's paid, not in a batch before the filing deadline. FEC reports require a stated purpose for every operating expenditure, and reconstructing "what was this $4,200 wire for" three months later from memory is a recipe for the misclassified-expenditure errors that show up in nearly every FEC audit report as a finding.
• Keep an audit trail, literally. Plain-text, version-controlled records — where every entry is a diffable line in a file rather than a cell that silently changed in a shared spreadsheet — mean that when an RFAI arrives asking "what changed between the draft and the filed version," the answer is a git log, not a guess.

That last point is where the accounting method itself starts to matter as much as the policy knowledge. Beancount.io provides plain-text, double-entry accounting with a complete, tamper-evident history of every transaction — exactly the kind of audit-ready record that makes reconciling a report against a bank account, and defending that report six months later, straightforward instead of stressful. Get started for free and see how plain-text accounting brings the same rigor campaign compliance already demands to the books behind it.