Treasury/Projects/2024/Reimbursements Systems

From Noisebridge
Revision as of 14:13, 13 March 2024 by Mcint (talk | contribs) (create page, clear processes)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Describing long-held rules the treasury is operated under.

Heuristic Rules for Reimbursements

For small reimbursements with self-evidently excellent purpose and use, the treasurer can reimburse a small amount.

For maintenance projects, working on the space, large projects need approval by a meeting, pre-approval if you don't want to risk non-reimbursement.

For installation projects, working in the space, but still for the space, with permanent presence, projects costs can sometime be split 50-50 with project creators or maintainers.

For non-installation projects, it's unlikely Noisebridge wants to split the cost for you to make a project here and walk off with it elsewhere. Exceptions may apply when these projects go to other hackerspaces in need, the hacker conference community, or other non-profits, demonstrating a clear need and Noisebridge commitment to address it, or a clear benefit for Noisebridge.

For large reimbursements, large spending, we

How

Approval, receipt, request, completion / log in finances.

Approval

  • Small purchases
    • Need: obvious excellence
    • Benefit from: consensus from discussion at meeting
  • Large purchases
    • Need: consensus from discussion at meeting
    • Benefit from: discussion in advance, risking non-reimbursement otherwise

Receipts

The treasurer needs copies of receipts, to file in books.

Request

Make requests in Slack #finance-wg or Discord #finance-forum, or seek clarifications there.

Completion

Reimbursement methods include: PayPal, Venmo. Other methods are possible, depending on situation and amount.

Log

Reimbursements are categorized and reporting in monthly financal update.