Cycle Four Reflection 

• We introduced a new unreplied “tab” in the expenses tool where we list expenses that have been commented on and need attention. This makes it much easier for Fiscal Hosts to keep track of and followup expenses directly on the platform without having to depend on external support tools.
  

  

  
  
  
• Fiscal Hosts can now indicate on accounting categories whether they apply to Fiscal Host (operational) funds and Collective (managed) funds.

• A new expense report is now available for Fiscal Hosts providing periodic summaries of expenses by accounting categories.
  

  

  
  
  
• We built an MVP for a tool to import off-platform transactions and represent them as expenses, contributions and added funds (and their underlying transactions) on the platform. This tool is already in testing and available as a preview feature. We will integrate the feedback we get together with additional use cases we wish to explore as work to take on in future cycles. 

• We conducted a workshop on inconsistencies in the expense batch functionality and have flagged potential work for us to consider in future cycles.

1. We built two new public profiles, one dedicated to fundraising and the other dedicated to Collective story-telling. 
2. We built a new “accounts” tool in Collective dashboards.

We did a major UX iteration on the new expense submission flow and introduced many improvements (large and small) that are packed and ready to go as an engineering project we can take on in future cycles.

Cycle Five Overview 

1. Adding comment threads (that we currently have on expenses) to Collective applications (to join Fiscal Hosts). This will enable Fiscal Hosts to interact with new Collectives directly on the platform (instead of having to rely on other mediums such as email and support tickets). The comment thread will then become a record (that both the Host and Collective can access) of the application dialogue and any terms, conditions and agreements that are established in the process. 
2. Enabling Fiscal Hosts to pause recurring contributions for frozen Collectives. In our response to the OCF dissolution we developed a capability to pause and reactivate recurring contributions. We now want to make it available to Fiscal Hosts who need to be able to halt (and resume) contributions to specific Collectives.
3. Added funds are manually added to the ledger by Fiscal Host admins. Fiscal Hosts have expressed a need to be able to make corrections to these transactions. This has not been possible due to the immutability of the ledger. In this project we are going to be introducing some kind of “reverse transaction” capability that will create transactions that negate existing transactions. This will then make it possible for us to create an “edit” user experience that, behind the scenes, will create reverse transactions and then create new ones to replace them. We anticipate that the ability to “reverse transactions” will be of service in additional contexts.
4. Typically, when contributions are refunded, payment processors (such as Stripe and PayPal) do not refund fees and the ledger was built around this assumption. However there are (rare) cases where partial fees are refunded and we are currently unable to correctly represent this on the platform. This results in rare accounting discrepancies that we wish to avoid. This project will address this edge case.

1. It is something we believe in and is aligned with the core platform values of transparency and freedom. 
2. It improves our GDPR compliance.
3. The export operation opens the door to an import operation which we will open the door for us take on the challenge of “migrating to another instance of the platform.”