Funding policy proposal

Invoice Expenses Policy

When paid work can be invoiced, what approval is needed and how invoices are reviewed.

Organisation: Comutability
Version: 0.1
Status: Proposal pending human approval
Drafted: 15 November 2026
Applies to: Comutability's Open Collective finances, once a fiscal host and authorised reviewers are confirmed

Not yet adopted. This policy is a proposal, subordinate to the approved Founding Charter v1.1 and to applicable law, Open Collective terms and fiscal-host requirements.

Built together. Open to everyone.

Purpose and eligibility

Invoices pay individuals or organisations for authorised work or services that advance Comutability's open-source mission. Examples include development, infrastructure services, design, documentation, accessibility reviews, security audits, translations, education and agreed technical support.

All charges must be necessary, reasonable, adequately documented and linked to an approved Comutability project or activity. An invoice is not a retrospective request to convert volunteered work into paid work.

Approval before work starts

Seek authorisation from an appropriate human maintainer or financial administrator before committing costs or beginning paid work. Obtain written agreement on scope, deliverables, rate or fixed fee, maximum cost, project and any milestone dates. If prior approval was not obtained, payment is not guaranteed.

AI may help prepare or check an invoice, but must not approve expenses, commit funds or instruct payments. No person should approve their own invoice; conflicts must be disclosed and handled by another authorised human reviewer.

Submitting an invoice

Use the Invoice expense type on Comutability's Open Collective page. Include the payee's name or business identity, project, a clearly titled service, service dates, amount and currency, applicable tax information, an itemised invoice where required, and a link or reference to authorisation and deliverables where safe to publish. Use the platform's protected payment process for banking details. Do not put private bank, identity or security information in a public title or description.

Ineligible costs

Unapproved or unrelated work, duplicate claims, misleading invoices, personal purchases, unlawful transactions, excessive charges, conflicts of interest that have not been managed, and expenses inconsistent with the Charter or the agreed open-source licence are not eligible.

Review, payment and transparency

The human reviewer verifies authorisation, evidence, budget and any applicable work product. The fiscal host then applies its own checks and schedules payment. Submission or Comutability approval does not guarantee a payment date. Public transaction records may show the payee, project, purpose and amount, subject to platform settings and privacy protections.

For clarification or a disputed decision, contact the project maintainers through the applicable project discussion or the Open Collective expense conversation. Review and exceptions must be documented by an independent human decision-maker and remain subject to host rules.

This policy becomes effective only after recorded human approval.