What reconciliation actually means for a campaign
The math behind a reconciled campaign account — matching deposits to contributions, checking donor fields, rolling up aggregate totals — is straightforward arithmetic. What actually takes work is getting to the point where you can trust that every bank deposit has been accounted for and every contribution record ties back to something real, when no single document hands you that confirmation automatically.
This guide walks through that process step by step, from the raw bank statement to a documented, source-backed reconciliation — whether you do it by hand or with a tool that reads the statements for you.
Nothing here assumes a specific compliance software, a specific donation platform, or a specific committee type — the eight steps that follow work the same way whether you're reconciling a first-time candidate committee's single bank account or a PAC managing contributions across several committees at once.
Why this matters more than the report itself
Two treasurers can file reports that look equally polished and still be sitting on very different risk — one has verified that every reported dollar traces to an actual deposit, the other is trusting that the compliance system's numbers are correct because nothing has obviously gone wrong yet. The report itself is never the risk. The reconciliation behind it is what determines whether the report actually holds up.
That's the reason this guide is organized as eight sequential steps rather than a single instruction to "check the numbers" — each step exists specifically to catch one of the failure modes that turn a straightforward reconciliation into a wrong one, and skipping a step tends to reintroduce exactly the error that step was there to prevent in the first place.
Pull the bank statement for the full reporting period
Gather the bank statement covering exactly the FEC reporting period you're reconciling — not approximately, since the reporting period's start and end dates rarely line up cleanly with a bank statement's own monthly cycle. If the campaign uses more than one account, all of them need to be gathered, not just the primary operating account.
Where the reporting period splits across two bank statement cycles, pull both statements rather than approximating from just one — a deposit that lands in the last few days of a bank cycle can easily fall on either side of the actual reporting-period boundary.
Pull every platform payout report for the same period
Gather the payout or disbursement reports from every donation platform used during the period — ActBlue, WinRed, or any other processor — covering the same date range as the bank statement. These reports are what break a lump-sum bank deposit down into the individual contributions behind it.
Match each bank deposit to its source
Every credit on the bank statement gets tied to a specific source — a batch payout from a platform, a direct check, a wire transfer. This is the step that turns a flat list of bank transactions into a list of transactions each with a known origin.
A deposit that can't be matched to any obvious source at this stage isn't a failure — it's exactly what step 7 exists to catch. Note it and move on rather than guessing at its origin to force a match.
Break down batch payouts into individual contributions
For every deposit matched to a platform payout, confirm the sum of the individual contributions listed in that payout report, less any disclosed processing fee, equals the deposit amount on the bank statement. This is the check that catches a fee miscalculation or a contribution that was refunded after the payout report was generated.
A batch that doesn't tie out exactly is worth a second look before assuming it's a rounding difference — a genuine mismatch here is precisely the kind of gap that's cheap to catch now and expensive to explain during a report review later.
Check occupation and employer on every itemized gift
For every contribution that pushes a donor's aggregate above the itemization threshold, confirm the occupation and employer fields are present and specific enough to be usable — not blank, and not something too vague, like "self-employed" with no further detail, to satisfy the best-effort requirement.
This step is worth doing deliberately rather than skipping, even under deadline pressure — a missing or insufficient occupation/employer field is one of the single most common reasons the FEC sends a Request for Additional Information after a report is already filed.
Roll up aggregate totals per donor
Sum every contribution from the same donor, split by which election it's designated for, into a running total across the full election cycle — not just the current reporting period. This is what surfaces a donor who's approaching or has crossed the federal limit through a series of individually modest contributions.
Set aside what doesn't reconcile
Once every matched deposit and contribution is accounted for, what's left — unmatched deposits, payout totals that don't tie out, donor records with missing fields — gets set aside as its own follow-up list, rather than forced into the reconciliation to make the totals appear to close cleanly.
A short follow-up list is a normal, healthy outcome of a careful reconciliation. A reconciliation with no follow-up items at all, on a campaign with any real transaction volume, is worth a second look — it more often means something was missed than that everything was genuinely perfect.
Document the reconciliation before you file
Record the reconciled totals — matched deposits, aggregate donor totals, the follow-up list — with a reference back to the specific bank statement and payout report each figure came from. In the event of an FEC inquiry, being able to show precisely how a reported number was built is worth far more than the number alone.
Include the date the reconciliation itself was prepared, and the reporting period it covers, directly on the document — a reconciliation with no as-of date attached ages quietly and can end up being relied on months after it stopped reflecting reality, with nobody noticing until it's pointed out.
Signs a reconciliation is off
A batch payout total that's off by an oddly specific amount
A discrepancy of a few dollars and cents usually points to a fee miscalculation, not a rounding difference — worth tracing to its exact cause rather than writing off.
A donor's aggregate that jumps sharply between periods with no obvious explanation
A sudden jump is worth double-checking — it can be a genuine large gift, or it can be two different donors accidentally merged into one record.
The follow-up list has a recognizable pattern
Several unmatched deposits from the same platform, or the same missing field appearing repeatedly, usually means step 3 or step 5 needs another pass before the reconciliation can be trusted.
A committee total that doesn't roughly match what the treasurer remembers raising
Not proof of an error on its own, but worth reconciling — a large gap between the documented total and the treasurer's own recollection deserves a conversation before the reconciliation is finalized.
When the committee uses more than one bank account
Some committees split funds across two accounts — a primary operating account and a separate account for a specific purpose, such as a recount fund or a segregated reserve. When that's the case, run the full eight-step process on each account independently first, rather than trying to merge the raw transaction lists together before matching.
Merging first tends to introduce false pattern matches — a deposit in one account and an unrelated one in the other can coincidentally share an amount and date, and if you've already combined the transaction lists you lose the account-level context that would otherwise make the mismatch obvious. Reconciling each account separately, then comparing the two finished reconciliations at the end, keeps that context intact.
What columns the working spreadsheet actually needs
| Column | Why it's there |
|---|---|
| Bank deposit date and amount | Feeds the matching in step 3 |
| Matched source (batch/check/wire) | Your working assignment, revised as matching firms up |
| Donor name, occupation, employer | Feeds the field check in step 5 |
| Election designation | Feeds the aggregate rollup in step 6 |
| Statement source and page | The reference that makes step 8's documentation possible |
Keeping the matched-source label as its own editable column, rather than immediately sorting transactions into separate tabs per source, makes it much easier to revise an early matching guess as steps 4 and 5 surface new evidence — moving a row between tabs is more friction than editing a label, and that friction quietly discourages the corrections that keep the reconciliation accurate.
Double-checking the finished reconciliation
Before treating a reconciliation as final, add every matched deposit back together and compare the total against the bank account's actual total credit activity for the period, net of any non-contribution deposits like transfers between committee accounts. A reconciliation that accounts for an implausibly small share of total deposits usually means a source was missed in step 3; one that accounts for an implausibly large share usually means a non-contribution deposit got counted as a contribution by mistake.
It's also worth re-running step 7's follow-up check one final time after the reconciliation feels complete — a fresh look with the confirmed matches already in mind sometimes catches a small, low-frequency deposit that a first pass reasonably treated as resolved.
A reporting period, reconciled start to finish
A House candidate committee reconciles a quarterly reporting period covering direct checks and ActBlue online contributions.
| Step | Result |
|---|---|
| Bank deposits matched to source | 38 of 39 |
| Batch payouts verified against deposits | 18 of 18 tied out |
| Occupation/employer gaps found | 5, flagged |
| Donors near the aggregate limit | 2, surfaced for review |
The one unmatched deposit turns out to be a refund reversal from a platform, correctly excluded from the contribution total but initially confusing on the bank statement alone — resolved in a few minutes once the platform's own transaction detail was checked, rather than left as an unexplained gap going into the filing.
A printable checklist
Full reporting-period bank statement gathered, all accounts included
Every platform payout report gathered for the same period
Every bank deposit matched to a specific source
Every batch payout verified against its bank deposit
Occupation/employer confirmed on every itemized contribution
Donor aggregate totals rolled up across the full election cycle
Unreconciled items set aside as a follow-up list, not forced to close
Reconciliation documented with source references before filing
How long each step takes
For someone with a steady routine, most steps move quickly once the documents are in hand — steps 3 and 4, matching deposits and breaking down batch payouts, typically take the most time. Reading the statements into a structured form once shifts most of that time to a few minutes of upload instead of an afternoon of manual cross-checking.
Steps 1, 2, 5 and 8 are comparatively fast once a routine is established — gathering documents, checking a specific field, and recording the result are mechanical once the harder matching decisions in steps 3, 4, 6 and 7 have already been made.
Common mistakes worth avoiding
Accepting a batch payout total at face value
The sum of individual contributions isn't checked against the deposit, letting a fee error or a reversed contribution slip through unnoticed.
Treating a vague occupation field as sufficient
"Self-employed" or "retired" with no further detail often doesn't meet the best-effort standard, and surfaces as a gap at the worst possible time.
Resetting the donor aggregate every reporting period
A donor's running total needs to persist across the full election cycle, not restart each time a new report is filed.
Forcing an unmatched deposit into the reconciliation
Guessing at a deposit's source to make the totals close cleanly hides a genuine gap rather than resolving it.
How often this actually needs doing
Ideally at the close of every reporting period, so a discrepancy or a missing field is caught quickly — not only when a filing deadline makes it urgent. The later a gap is caught, the harder it is to reconstruct exactly what happened.
A regular cadence also keeps each individual reconciliation small. Letting several reporting periods accumulate before the next check means more transactions to sort through at once, and a longer stretch of time during which an error could have compounded unnoticed.
A monthly rhythm, even for a committee that only files quarterly, tends to work well in practice.
With tooling vs. by hand
By hand, this process is fully workable — many treasurers do exactly this for their campaigns. What a document-reading tool changes is the matching step itself: instead of manually cross-checking every deposit against every payout report, the matches are identified automatically, with anything genuinely ambiguous flagged for a human decision.
The eight steps themselves don't change either way — what changes is how much of each step is mechanical versus manual. Steps 1 and 2 stay essentially the same regardless; steps 3 through 6 are where automation does the most work, since matching deposits and rolling up aggregates across many transactions is exactly the kind of repetitive cross-referencing a document-reading tool handles quickly.
Neither approach removes the judgment steps entirely — step 5's occupation/employer check and step 7's follow-up decisions still benefit from a person who understands the campaign's specific donor relationships, regardless of how much of the mechanical matching is automated.
If this is your first reporting period
Start with the most recent reporting period, where the transactions are freshest and easiest to confirm, rather than attempting to reconstruct a full election cycle's history at once. One completed reconciliation gives you a working process to extend backward if earlier periods still need it.
It's also worth accepting, on a first attempt, that a few items may end up on the follow-up list simply because the process is new — treat the first pass as a working draft that gets cleaner each time it's repeated, rather than expecting a perfect close on the very first try.
A first-time treasurer benefits from working alongside someone who's done this before, whether that's a compliance consultant or a more experienced colleague, precisely for the judgment calls that steps 3 and 5 require — recognizing what counts as a reasonable match, and what genuinely needs to be flagged, is a skill that develops with repetition.
Who this guide is for
Campaign treasurers preparing for a filing, compliance consultants managing multiple campaign clients, and bookkeepers supporting political clients will all recognize this process — the steps are the same regardless of who performs them.
It's also written to work for someone doing this for the very first time, not just for someone with existing campaign finance experience — the eight steps assume no prior familiarity with the account beyond the documents themselves, which is deliberate, since a first-time treasurer facing their first filing deadline is exactly the audience most likely to need a structured process rather than intuition built from repetition.
Doing this across many reporting periods
Each period goes through the same eight steps, and the confirmed donor totals from earlier periods make later periods faster to check — once a donor's aggregate is established, later contributions mostly extend the existing total rather than requiring fresh discovery.
Treat each period's pass as a confirmation exercise rather than starting from zero — check that previously matched deposits still line up, then apply step 7's follow-up check to that period specifically, watching for anything new that doesn't match an already-confirmed pattern.
Over a full election cycle, this compounding familiarity is where the real time savings show up — a treasurer who has reconciled six consecutive reporting periods the same way recognizes the campaign's typical donor patterns, its usual batch payout size, and its normal fee structure well enough to spot a genuine anomaly almost immediately, rather than having to work it out from scratch every single time.
A short glossary
| Term | Meaning |
|---|---|
| RFAI | Request for Additional Information — the FEC's follow-up when a report has an apparent error or gap |
| Itemization threshold | The cumulative contribution amount from a donor above which their details must be individually reported |
| Aggregate limit | The maximum a donor may contribute to a single election, tracked across the full cycle |
| Batch payout | A single bank deposit representing many individual contributions processed by a platform |
These four terms cover most of what comes up while working through the eight steps — RFAI and itemization threshold describe the compliance stakes, while aggregate limit and batch payout explain the two specific things the reconciliation is actually checking. Knowing the difference between a batch payout and an individual bank deposit, in particular, is what makes step 4's verification make sense rather than feel arbitrary.
Handing this off to a compliance consultant
A reconciliation that lives only in one person's spreadsheet, without the underlying matching documented, is hard for anyone else to trust or extend. Handing a compliance consultant or a new treasurer the reconciliation alongside the source bank statements and payout reports means they can verify it themselves instead of taking your word for it. See the full overview for how this fits into the rest of the compliance process.
A good handoff also anticipates the question that comes next, not just the reconciliation itself — a consultant receiving a campaign's reconciled account will almost always ask why a specific deposit was matched where it was, and having that reasoning already documented turns the handoff into a genuinely useful starting point instead of just a set of numbers to re-verify.