Invoicing: Approver <--> Approvee governance

[May-Lee]

We at Tahoe enjoy a high level of project trust namely due to having a culture of communication about the work we are doing and the times when we can't. Only once have we had a contractor who was dishonest about the work they were doing and their contract was terminated. The proposed approver<-->approvee process is similar to the BASICS process, in which contractors file Activity Reports which the Community Manager reviews before payment.

Aspiration (and other stakeholders) want there to be more transparency into Tahoe's finances. Hopefully, we can come up with processes that allow us to keep our flattish hierarchy and continue with our organizational culture of autonomy, constant learning/mentoring and project efficacy. Without adding too much bureacracy.

The current approver<-->approvee process looks like this:

1. Send your invoice to J------ at Aspiration and your "approver"
   • everyone must have an approver
2. Your approver will respond to J----- with "approved" after they've looked at your invoice
   J----- keeps a list of all approver<-->approvee relationships
   • Your approver and you should have a close enough working relationship that they will have insight into your workflow
   • Your approver cannot be someone you supervise or have power over