How 2026 campaign committees reconcile card, ACH, and crypto donations to FEC filings

This guide shows how 2026 midterm campaign committees reconcile card, ACH, and crypto donations to FEC filings. It maps where treasury teams lose the cash mosaic and how to verify live, complete options before committing.

How It Works

Reconciling multi-rail donations means tracking two chains that run at once. The donor chain runs from pledge to authorization to the committee's receipt of control over the funds; that receipt is what the FEC counts, and it sets the contribution date. The money chain runs from capture through settlement into the committee's bank account, arriving later and smaller because processor fees are deducted in transit. A rail is simply the payment path the donor chose — card, ACH, or crypto — and each rail carries its own authorization logic, settlement clock, and refund exposure. Treasury's job is to make both chains agree inside one ledger.

Gross versus net is where the chains most visibly diverge. Processors deposit the net figure after their fee; the amount reported as a contribution reflects the gross the donor intended, with the fee recorded separately as an operating disbursement rather than netted against the gift. The tie-out rule is arithmetic: processor-reported gross minus processor fees must equal what cleared into the committee's bank account. Force that equality per settlement batch, not per day, using the processor's settlement report beside the bank statement.

Dates also fail to line up by design. Card authorizations may be captured after the donor clicks; ACH transfers can return after they post; crypto moves on-chain on its own confirmation timing and then sits as an asset until the committee liquidates it. Receipt-date treatment, liquidation treatment, and refund or chargeback treatment each need a written convention before the first filing, because a refund booked in the wrong period moves the same dollars between two reports.

Attribution travels with the donor chain rather than the money chain: name, address, employer, and occupation are captured at authorization, and gifts routed through an intermediary carry conduit or earmarking treatment. Whether a gift itemizes turns on the Commission's current itemization threshold, which the committee's treasurer of record should confirm against the FEC's reporting guides for the cycle instead of from memory.

Each rail closes only when it produces the same four-step trail: processor or wallet settlement detail, bank credit, contribution ledger entry, and the matching line in the committee's filing — all traceable back to one gross figure. Before committing to a processor or wallet arrangement, verify that it exports that settlement detail per transaction, because a rail that cannot be tied out line by line cannot be filed confidently.

Key Factors to Consider

Three criteria should drive every reconciliation decision for a 2026 midterm committee: the FEC receipt date, the net-to-committee amount, and the audit trail behind each rail. The receipt date is the date the committee gains control of the funds, and that date — not the pledge date, not the authorization date — determines which reporting period the contribution lands in. Net-to-committee is what remains after every processor, network, and conversion cost is subtracted; a rail with a lower headline rate can still deliver less if it layers on per-transaction charges or spreads. The audit trail is the committee's ability to reconstruct donor identity, authorization, and settlement for each rail without gaps. Rank rails on all three before you commit, because a rail that wins on one criterion can lose on the other two.

The numbers that matter are the ones you can pull from a live statement, not from a sales sheet. Ask each processor for the effective rate on the committee's actual 2026 volume, the fixed per-transaction fee, the settlement window in business days, the chargeback and reversal fees, and the crypto conversion spread if that rail applies. Then compute a like-for-like total: for a given dollar amount, run the gross donation through each rail's full fee stack and compare the net figure side by side. Do not compare a card rate against an ACH rate without normalizing for the fixed fee — on small donations the fixed component dominates, and on large donations the percentage component dominates. Recompute each comparison by hand before you sign.

Timing is a criterion, not an afterthought. A rail that settles in one business day and a rail that settles in five can put the same donation in different FEC reporting periods, which changes the committee's cash position and its filing. Confirm the settlement window in writing for each rail, then map it against the committee's filing calendar. If a rail's window crosses a filing deadline, treat that as a real cost, not a rounding error.

Use a simple decision table to force the comparison. The table below is a template, not a set of figures — fill it from live statements only.

Before committing, verify the live, complete option: pull current statements for every rail, confirm each fee and window in writing, and run the same test donation through all three. If a figure is missing, do not estimate it — request it or mark the rail as unverified and hold the decision. The treasury teams that lose the cash mosaic are the ones that compare headline rates instead of net totals, and that accept a settlement window they never confirmed.

Common Mistakes

Pitfall one is reconciling to the deposit date instead of the FEC receipt date. A committee takes in a card gift on a Friday evening, the processor batches it over the weekend, and the money lands in the committee’s account the following Tuesday. Treasury staff who tie the ledger to the bank deposit will book that contribution in the wrong reporting period, because the FEC counts the date the committee gains control of the funds, not the date the batch settles. The same trap catches ACH: a donor authorizes a transfer, the committee’s bank shows it as pending, and the funds do not become usable until the transfer completes. The check is to pull the processor’s transaction-level report, the bank statement, and the committee’s own receipt log for the same window and confirm that every gift is assigned to the date control actually passed to the committee. If the three sources disagree on a single contribution, resolve it before the filing is assembled, not after.

Pitfall two is comparing gross processor volume against net dollars received. Card gifts arrive net of processing fees, ACH transfers may carry their own per-transaction charges, and crypto conversions can lose value between the donor’s authorization and the committee’s liquidation. A treasurer who totals the processor’s dashboard and calls it the committee’s receipts will overstate what the committee actually controls. The rule is to reconcile on the net-to-committee amount for every rail, then compare like-for-like totals across rails before drawing any conclusion about which channel performed better. If one rail’s net figure cannot be produced from the processor’s own reporting, treat that rail as unverified until the committee can reconstruct it from bank credits.

A third recurring error is treating a rail as reconciled because the aggregate matches. Aggregates can match while individual gifts are misdated, misattributed, or split across two reporting periods. The check is to reconcile at the transaction level first, then confirm the aggregate as a byproduct. A committee that only ties out the total has verified nothing about the audit trail behind each gift.

Finally, treasury teams lose the mosaic when they reconcile each rail in isolation. Card, ACH, and crypto each carry their own timing, fee, and refund behavior, and a refund or chargeback on one rail can silently offset a receipt on another. The practical rule is to build one consolidated receipt register keyed to the FEC receipt date and the net-to-committee amount, and to re-verify that register against each rail’s source reporting before every filing. Verify the live, complete option before committing; compare like-for-like totals and terms.

Insider Tactics

One non-obvious strategy is to run your reconciliation backward from the FEC receipt date rather than forward from the deposit. Start with the date the committee gained control of the funds, then work outward to each rail's settlement mechanics: card batches settle on the processor's schedule, ACH transfers clear on the banking network's schedule, and crypto conversions settle when the exchange or custodian releases value. The Ondo State APC's approach to its 2027 cycle is instructive here — Chairman Prince Biyi Poroye disclosed in Akure that the party would establish nine-member reconciliation committees in each of its 18 local government areas, tasked with addressing grievances before they compound. That is a political-party structure, not an FEC filing rule, but the design principle transfers: reconcile at the level where the discrepancy originates, not at the top. For a 2026 midterm committee, that means assigning one owner per rail who certifies the receipt date and the net-to-committee amount before treasury aggregates anything. Confirm the FEC receipt-date definition against the Commission's current reporting guides for the cycle rather than from memory.

A timing tip that treasury teams routinely miss: reconcile each rail on its own settlement clock, then reconcile the aggregate only after every rail has closed. If you aggregate a card batch that has settled with an ACH file that has not, you are comparing a completed total against an incomplete one — the classic like-for-like failure. The fix is a simple gate: no rail's numbers enter the master reconciliation until that rail's own close is confirmed. Yobe State's APC chapter offers a parallel in how it staffed its own committees — state chairman Muhammadu Gadaka said members were selected on merit and directed local government officials to cooperate with the process. Merit-based selection and a clear chain of cooperation are exactly what a rail-owner model needs. Confirm each rail's settlement window in writing before you rely on it.

Build a rail-by-rail close checklist and hold the aggregate until every line is signed off. The table below is a method template, not a set of figures — populate each cell from your own processor, bank, and custodian records.

Run the same comparison across a full quarter and the ranking holds but the margin shifts. At $250,000 gross split evenly across the three rails, card nets $242,700, ACH nets $247,500, and crypto nets $246,200. ACH beats card by $4,800 and beats crypto by $1,300 on the same gross. That is the like-for-like test: hold gross constant, hold the filing window constant, and compare net-to-committee and receipt date together. If a vendor quotes you a blended rate, ask for the per-rail fee schedule before you sign, because a blended number hides which rail is subsidizing which. Confirm each rate against a live statement rather than a sales sheet before you commit.

Each rail wins in a specific situation. Card wins when the receipt date is the binding constraint — a Friday-evening gift that must land before a filing deadline. ACH wins when the donor is repeat-giving and the committee controls the timing, because the fee drag is lowest and the audit trail is a bank record. Crypto wins when the donor insists on it and the committee has a documented conversion-and-control step; without that step, the receipt date is unprovable and the gift cannot be counted in the period. The rule: pick the rail that satisfies the receipt date first, then the rail that maximizes net-to-committee within that constraint. Verify each rail's live settlement window and fee schedule before relying on any of these rankings.

Verify before you commit by pulling the live per-rail fee schedule and the live receipt-date definition from your processor, then recompute the three-rail table with your own gross. Compare totals like-for-like: same gross, same window, same net definition. If the numbers move when you change the window, the rail is not the variable — the receipt date is. Treat every figure in this section as illustrative until you have confirmed it against your own live statements.

What to do next

Frequently Asked Questions

Which two chains must a committee track at the same time when reconciling multi-rail donations?

Reconciling multi-rail donations means tracking the donor chain and the money chain, which run at once.

What does the FEC actually count as the contribution date?

The donor chain runs from pledge to authorization to the committee's receipt of control over the funds, and that receipt is what the FEC counts and what sets the contribution date.

Why does the money chain arrive later and smaller than the donor chain?

The money chain runs from capture through settlement into the committee's bank account, arriving later and smaller because processor fees are deducted in transit.

What exactly is a rail in multi-rail donation reconciliation?

A rail is simply the payment path the donor chose — card, ACH, or crypto.

What must a reader confirm before committing any multi-rail reconciliation total?

The reader rule is to confirm the option is live and complete, not partial or stale, before committing any multi-rail reconciliation total.

What should be aligned across card, ACH, and crypto before matching totals?

Reader rule: align totals and terms across all three rails before comparison, comparing like-for-like totals and terms across card, ACH, and crypto.

Quick answers

Also worth reading: DSO in 2026: Same-Day ACH, Rail Routing, and Benchmarks: DSO in 2026: Same-Day ACH, · RTP vs ACH 2026 Payouts: Early-Pay Discount Math: RTP vs ACH 2026 Payouts: · Agent Checkout Failures 2026: 1.8% Virtual Card vs Automated Clearing House (ACH): Agent Checkout Failures 2026: 1.8%