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

Host Dashboard section for Tax Forms (US) #7136

Closed
Tracked by #7346
Betree opened this issue Dec 1, 2023 · 1 comment · Fixed by opencollective/opencollective-frontend#10302
Closed
Tracked by #7346

Host Dashboard section for Tax Forms (US) #7136

Betree opened this issue Dec 1, 2023 · 1 comment · Fixed by opencollective/opencollective-frontend#10302
Assignees
Labels
api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) complexity → complex feature frontend
Projects

Comments

@Betree
Copy link
Member

Betree commented Dec 1, 2023

Part of #7346

Needs

Solution

  1. Add a new dashboard section for US hosts called Legal Documents (if we want to be generic) or Tax Forms (if we want to keep it specific).
  2. Show some filters: search by text, year (default=current)
  3. Show a table that queries the list of all expenses that require a tax form (we do have such queries in Metabase) and returns a summary grouped by the payee, along with the submitted document link (if the host is connected to Dropbox Forms). We have a query like that in Metabase.
  4. For each entry, add an action dropdown that will let us implement the aforementioned actions.
  5. Add a button to export the results as CSV (accounting firms usually require a document like that)
  6. Bonus: add a button to export a .zip with all the tax forms

image

@Betree Betree added feature complexity → complex api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) frontend labels Dec 1, 2023
@Betree Betree added this to To do in Tax forms via automation Dec 1, 2023
@iamronen
Copy link
Contributor

Some comments

  1. I suggest discerning between two kinds of entities (at least from the user experience perspective).
    • required tax forms
    • tax forms
  2. Perhaps the pipeline pattern can be used here for: Required, On Record, Expired/Invalid.
  3. Is there going to be a drawer where a single tax form can be viewed and downloaded?
  4. If there is going to be a drawer, it may be useful to show in it through which collectives a payee is getting paid.
  5. It can be useful to add to the context menu a link to "Expenses" for a given payee -> redirect to a filtered list of expenses (both paid and waiting to be paid).
  6. It can be useful to add an indicator if a payee has expenses waiting to be paid that are blocked because of the missing tax form.
  7. Clarify what country is being shown here? Country of residence of the Payee?
  8. My understanding is that the downloads (both the CSV and the forms) is needed per fiscal year. If that is the case lets make sure that it is clear in the UX,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) complexity → complex feature frontend
Projects
Development

Successfully merging a pull request may close this issue.

2 participants