Allow user to create Void of Coordinated Party Expenditures on Schedule F

[exalate-issue-sync]

Business Reason

As a user with a PARTY committee account, I will be able to enter a ”Void of Coordinated Party Expenditure" transaction on Schedule F of a Form 3X report so that I can accurately report on my committee's transactions.

Acceptance Criteria

Given I am a user within a

PARTY committee account

editing an in-progress Form 3X report

When I go to add a disbursement

Then I can enter a transaction with the type “Coordinated Party Expenditure" or “Void of Coordinated Party Expenditure" under the “Contributions/Expenditures to Registered Filers” accordion

Then I will be required to enter the following information (unless otherwise noted):

---

Contact

• CONTACT TYPE
  • Dropdown options: Organization, Individual
  • *Note - please default to Organization.

— if CONTACT TYPE = Organization

• ORGANIZATION NAME (Required)

— if CONTACT TYPE = Individual

• LAST NAME (Required)
• FIRST NAME (Required)
• MIDDLE NAME (Optional)
• PREFIX (Optional)
• SUFFIX (Optional)

---

Address

• STREET ADDRESS (Required)
• APARTMENT, SUITE, ETC. (Optional)
• CITY (Required)
• STATE/PROVINCE (Required)
• ZIP/POSTAL CODE (Required)

---

COMMITTEE /CANDIDATE INFORMATION

And the user will be required to select a Committee using the LOOKUP, and upon selection the following will be populated:

• COMMITTEE ID (Required)
• COMMITTEE NAME (note: not required for the specs, but do we want to display here like we do for other transactions)

And the user will be required to select a Candidate using the LOOKUP, and upon selection the following will be populated:

• CANDIDATE ID (Required)
• CANDIDATE NAME (Required)
• CANDIDATE OFFICE (Required)
• CANDIDATE STATE (Required if (CANDIDATE OFFICE is 'House' or 'Senate')
• CANDIDATE DISTRICT (Required if CANDIDATE OFFICE is 'House')

---

Expenditure Information

• DATE (Required)
• MEMO ITEM (Optional)
• AMOUNT (Required)
  • MUST be a negative amount
• GENERAL ELECTION YEAR (Required, format YYYY)
• AGGREGATE GENERAL ELECTION EXPENDITURE FOR THIS CANDIDATE (Required)
  • Aggregation is based on the PAYEE CANDIDATE and chronologically based on date of transaction (expenditure date) for the provided General Election year. If expenditure date is the same, default to the time that the transaction was created.

---

Additional information

• PURPOSE OF DISBURSEMENT (Required)
  • Note: This field is REQUIRED but editable by the user. The User must enter information here to save. If the field is not populated, red error message "This is a required field."
• ADD DESIGNATING COMMITTEE OR SUBORDINATE COMMITTEE? (Optional, dropdown, default to blank)
• If DESIGNATING COMMITTEE selected, the following fields will be available with a lookup:
  • DESIGNATING COMMITTEE ID NUMBER (required)
  • DESIGNATING COMMITTEE NAME (required)
• If SUBORDINATE COMMITTEE selected, the following fields will be available with a lookup:
  • SUBORDINATE COMMITTEE ID NUMBER (Required)
  • SUBORDINATE COMMITTEE NAME (Required)
  • STREET ADDRESS (Optional)
  • APARTMENT, SUITE, ETC. (Optional)
  • CITY (Required)
  • STATE/PROVINCE (Required)
  • ZIP/POSTAL CODE (Required)
• NOTE OR MEMO TEXT (Optional)
• CATEGORY CODE (Optional)

---

Then I will be able to:

• Cancel
• Save
• Edit

And when the user saves the transaction, then the transaction will be itemized upon saving and saved with it's own line item on the *.fec file on line SF (line 25).

QA Notes

null

DEV Notes

See schedule schema spreadsheet here: 🔒 [https://docs.google.com/spreadsheets/d/1q-vhlO08rwU094hIZPu4jpCIUfh1_eDEdlfHG7oicbM/edit?gid=1245542205#gid=1245542205|https://docs.google.com/spreadsheets/d/1q-vhlO08rwU094hIZPu4jpCIUfh1_eDEdlfHG7oicbM/edit?gid=1245542205#gid=1245542205] 🔒

PAYEE CANDIDATE and PAYEE COMMITTEE, while the names of the fields in the specifications, will not be used as terms on the front-end.

Design

DESIGNATING COMMITTEE

!Designating Coordinated Party Expenditure @2x.png|width=1200,height=2805,alt="Designating Coordinated Party Expenditure @2x.png"!

SUBORDINATE COMMITTEE

!Subordinate Coordinated Party Expenditure @2x (aecc0b4a-4606-4de4-bf28-3a8692f44f34).png|width=1200,height=3065,alt="Subordinate Coordinated Party Expenditure @2x.png"!

NEITHER

!Neither (Blank) Coordinated Party Expenditure @1x.png|width=1200,height=2757,alt="Neither (Blank) Coordinated Party Expenditure @1x.png"!

See full ticket and images here: FECFILE-2063