Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System to provide guidance on who should join FECFile #2500

Open
exalate-issue-sync bot opened this issue Jan 21, 2025 · 2 comments
Open

System to provide guidance on who should join FECFile #2500

exalate-issue-sync bot opened this issue Jan 21, 2025 · 2 comments
Assignees

Comments

@exalate-issue-sync
Copy link

No description provided.

@exalate-issue-sync exalate-issue-sync bot changed the title Design updated pages w/added text recommending who should join, decide on placement System to provide guidance on who should join FECFile Jan 23, 2025
Copy link
Author

akhorsand commented: [~accountid:712020:6466b08c-50a2-42ee-ad81-cfe79921d3e8] [~accountid:5b93ddba73130a2b8c662e23] FYI when drafting the language:

Committees we CAN support through FECFile: Form 3X filers without allocation needs that are new filers or have no financial activity reported

Committees we CANNOT yet support through FECFile:

Form 3X filers

New Form 3X filers who allocate

Long established Form 3X filers (ex. Honeywell)

Long established Form 3X filers who allocate

Non-Form 3X filers 

Form 3/3P

Form 5, 7, 9

No import functionality; it will be very user-unfriendly for committees who have large amounts of pre-existing data.

No ability for FECFile to amend/detect when reports that have been filed through another system or “catch up” to the current state of the committee’s reports

Copy link
Author

akhorsand commented: Notes from 1/28/25 requirements session: we should try to avoid the words “established” and “filers”. Also new official name is FECfile+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants