Changes

Some Sugar Labs projects have a budget (e.g., Google Summer of Code). Typically there is a project leader who has put together a budget that has been vetted by the Conservancy (See [[#Project proposal approval]]). If you have incurred a project-related expense, please submit a copy of your receipt to conservancy AT sfconservancy DOT org along with a brief explanation of the expense. Please be sure to include reference to the specific project for which the expense applies.

Some Sugar Labs projects have a budget (e.g., Google Summer of Code). Typically there is a project leader who has put together a budget that has been vetted by the Conservancy (See [[#Project proposal approval]]). If you have incurred a project-related expense, please submit a copy of your receipt to conservancy AT sfconservancy DOT org along with a brief explanation of the expense. Please be sure to include reference to the specific project for which the expense applies.

Similarly, if you need to invoice Sugar Labs, please submit your invoice along with a reference to a project to accounting AT sfconservancy DOT org.

Similarly, if you need to invoice Sugar Labs, please submit your invoice along with a reference to a project to accounts-payable AT tix DOT sfconservancy DOT org.

'''Please note''' that [[https://wiki.sugarlabs.org/go/Finance finances]] are routinely processed around the ides (15th) of each month. (Hence the latency in payments after approval can be up to 30 days.)

'''Please note''' that [[https://wiki.sugarlabs.org/go/Finance finances]] are routinely processed around the ides (15th) of each month. (Hence the latency in payments after approval can be up to 30 days.)