iamronen

attn @Memo-Es copy for the backwards compatibility option: - Delete the first part: Separate transactions compatibility - Leave only: Export taxes and payment processor fees as columns. - Add tooltip:...

thank you @Memo-Es attn @kewitz

This project was pitched for this cycle but was not prioritized. However we have engaged in a series of workshops to research and advanced this effort so that we can...

Jan 4, 2024 Workshop: - Engineering presented some thoughts about how to structure the API to create better infrastructure (flexibility and performance) for reporting. - We reviewed the shortcomings of...

Jan 11, 2024 Workshop: 1. The work we are doing in this cycle is exploratory and aimed at producing a pitch for implementation next cycle. 2. Whatever we build in...

Thank you for the update @Memo-Es this feels very promising and I am keen to see it implemented. A few small comments: 1. The names in the dropdown create confusion....

Week 4 sync summary: 1. We are almost at a working and promising MVP. 2. We have run into the need for originatingTransaction,kind in order to discern between payment processor...

Summary of last sync call: 1. We have a good outcome that we are confident making available to all fiscal hosts. 2. Missing pieces: - Exports: - An export affordance...

@kewitz please coordinate with @gustavlrsn the integration here (in the new report) of the new export modal.

As an expense submitter: 1. If I have already filled out a tax form for one fiscal host and I get asked to fill out another one for another fiscal...