Differences between revisions 2 and 3
Revision 2 as of 2019-10-08 16:47:56
Size: 1427
Editor: DLange
Comment: proper Wiki CamelCase
Revision 3 as of 2019-10-17 12:42:55
Size: 1479
Editor: DLange
Comment: move to Fundraising name space
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from DebConf/InvoicingSponsors

Invoicing a Sponsor

Via SPI

Since the bulk of our sponsors are invoiced via SPI, we issue invoices ourselves. Here is the workflow that needs to be followed:

  1. Open an RT ticket at debconf-invoices@rt.spi-inc.org saying who you are invoicing and for what amount.

  2. Fill out the SPI invoice model in the sponsors git repository (/sponsors/dcYY/invoices/SPI/00_invoice_model.ott)
  3. Save the invoice as yyyymmdd-rtticketnumber_name in PDF and ODT format in git (ex. 20181129-2475_bfh.pdf)
  4. Add the PDF invoice to the SPI RT ticket
  5. Send the invoice to the sponsor
  6. Update the sponsor file accordingly (modify status, add entry, etc.)
  7. Once the money arrived on SPI's bank account, SPI treasurer will close the RT ticket.

If you need help with this process, please write on the mailing list or ping people who have done this before on the IRC channel.

Via Debian France

  1. Send an email to tresorier@france.debian.net with all the relevant details.

  2. Save the invoice they send you in the git repository
  3. Update the sponsor file accordingly (modify status, add entry, etc.)

Via Debian CH

  1. Send an email to treasurer@debian.ch with all the relevant details.

  2. Save the invoice they send you in the git repository
  3. Update the sponsor file accordingly (modify status, add entry, etc.)