Transaction Tags are an important way of ensuring Expense transactions are reported correctly.
How are Expenses and Transaction Tags related?
Typically, the standard data entry model in ISP is the Expense is to the Entity that was paid and the Support/Oppose Memo is associated with the Candidate (or Measure) supported. In essence this is entering what is actually going on, and we’ve built the system logic to automatically take the data entry and report it appropriately.
If you are filing with the FEC, this matches how their forms work. They have two sections for each transaction: (1) who was paid and (2) the supported FEDERAL Candidate.
However, for Non-Federal Candidates, you do not include the Candidate information; it just shows who the Expense is to. In this example from the FEC guide you’ll see the Candidate Name and Office Sought fields are blank.
What are the available Transaction Tags?
In the Specify Support/Oppose section of an Expense, there are four transaction tags listed.
- IE to Oppose
- IE to Support
- Non-IE to Oppose
- Non-IE to Support
These four tags will cover almost all of the situations in which Support/Oppose Memos are needed for reporting.
IE to Oppose
Use this tag for Independent Expenditures opposing an issue or candidate.
IE to Support
Use this tag for Independent Expenditures in support of other candidates or issues.
Non-IE to Oppose
This tag is most commonly used for member communications (e.g. The Reform Party of Orange County sends out a mailer to their supporters urging them to vote no on Prop X).
Non-IE to Support
Use this tag on either a Direct Contribution (e.g. Contribution to Committee with the Candidate as the Specify Support/Oppose) or an Expense Support/Oppose, commonly known as an Inkind Contribution (ex: Paying for fliers from ABC Printing with Maria Espinoza as the Specify Support/Oppose).