Itemized Contributions: How Employer/Occupation Fields Are Collected and Displayed

What itemized contributions are and why employer and occupation fields matter

Definition of itemized contributions

Itemized contributions are individual receipts that meet federal reporting thresholds and that must be reported with certain contributor details, including name and mailing address; for many itemized receipts committees must also report the contributor’s employer and occupation, as required by federal regulation and guidance 11 CFR §104.3 – eCFR.

Reporting employer and occupation helps provide transparency about who gives to campaigns and supports basic analysis of potential sources of influence, attribution, and filing accuracy, according to FEC reporting guidance FEC reporting guidance and for more context see the about page.

Not every small gift is itemized; committees report only receipts that meet itemization thresholds and some itemized records may still omit employer or occupation when donors did not supply that information or when committees receive incomplete data FEC reporting guidance.

How federal rules and FEC guidance require itemized contributions to be reported

Key citations and filing thresholds

The recordkeeping and reporting rule at 11 CFR §104.3 explains what committees must keep and when a contribution must be itemized for public disclosure; the regulation frames the legal requirement to collect contributor name, address, and, for many itemized receipts, employer and occupation 11 CFR §104.3 – eCFR.

FEC guidance and filing pages to consult

The FEC guidance pages explain filing thresholds and the practical steps committees follow when preparing reports, including which fields to include on itemized receipts and where to find instructions for common forms FEC reporting guidance. Additional technical notes on the agency’s data and methodology are available from the FEC methodology.

The FEC also publishes technical documentation for its open data services and the receipts endpoints that show the contributor_employer and contributor_occupation fields exposed to researchers and the public FEC API documentation for receipts.

Committees gather employer and occupation information from a variety of intake points, including paper donor forms, online contribution processors, and vendor intake systems, and those channels may validate or map fields differently before the committee files reports FEC reporting guidance.

Many values start as short free-text inputs from donors or staff and the way a processor maps an intake field to the FEC schema can change what appears in the filing; committees may or may not run additional validation before submission OpenSecrets methodology on standardization.

The FEC publishes employer and occupation values essentially as they appear on committee filings and exposes them through the API fields contributor_employer and contributor_occupation, so the public dataset reflects what committees or processors submitted rather than a normalized name list FEC API documentation for receipts and the openFEC project on GitHub.

The FEC does not perform comprehensive normalization or canonicalization of employer and occupation strings before public release, so variations in spelling, abbreviations, and mapping choices appear in the published records FEC reporting guidance.

Researchers using bulk FEC data should expect to see the raw input from committees and third-party processors, and plan to apply their own cleaning if consistent names are required for analysis FEC API documentation for receipts.

Several common data-entry patterns produce noisy fields, including abbreviations, misspellings, donors writing “self” or “retired”, entries in multiple languages, and omitted fields, all of which complicate automated matching and display OpenSecrets methodology on standardization.

Short free-text inputs and local abbreviations make it hard for string-matching tools to group variants reliably, and online processors or vendor systems can add mapping differences on top of donor-entered noise Sunlight Foundation overview of employer and occupation issues.

When you see short or unclear entries in an aggregator, a few simple checks often clarify whether the value reflects the donor’s report or later processing. See related posts on the news page.

Transparency organizations and researchers commonly use authority lists, fuzzy string matching, and manual review to group variant spellings and corporate subsidiaries under consistent canonical names for analysis OpenSecrets methodology on standardization.

Automated matching reduces noise but has limits; manual review is time consuming and heuristics can misclassify ambiguous or small donors, so organizations publish methodology notes that document tradeoffs and known gaps Data Foundation report on data quality.

Backfilled or standardized names shown by aggregators represent additional processing after FEC release and should be understood as an interpretation rather than a primary record FEC API documentation for receipts.

Fixing the official public record generally requires the reporting committee to file an amended report or for donors to supply corrected information for future filings; practical barriers such as filing deadlines and staff resources limit how often committees can retroactively fix entries FEC reporting guidance.

Data aggregators can sometimes backfill standardized names when they have corroborating records, but those updates reflect post-release processing rather than changes to the original FEC filing FEC API documentation for receipts.

When a canonicalized employer appears in an aggregator, readers should seek supporting documents such as the raw filing or other primary records before relying on the standardized label for reporting or analysis FEC reporting guidance.

Next, compare the raw value to any aggregator canonicalization and read the aggregator’s methodology note to understand how they matched or backfilled names OpenSecrets methodology on standardization.

If an aggregator provides documentation showing corroborating sources for a standardized name, the label is more likely to be reliable; if methodology notes are absent or the donor value is ambiguous, flag the entry and seek secondary documentation Data Foundation report on data quality.

Common tricky entries to watch for include entries like “self”, single-word company names, short abbreviations, or foreign-language forms; these cases often need extra verification before you treat the employer string as authoritative OpenSecrets methodology on standardization.

Checklist for verification:

1. Find the raw FEC filing or API receipt.
2. Check aggregator notes for backfill explanations.
3. Search for corroborating primary records if the name affects a report.
4. When in doubt, label the entry as unverified in any published account.