Metadocumentation
open-collective
open-collective
  • Welcome
  • About
    • Introduction
    • Terminology
    • Company
    • Pricing
    • Community Guidelines
    • Values
    • Team
    • Investors
    • Contributing
  • Product
    • Features
    • Roadmap
    • Comparison
    • User Profile
    • Currencies
    • Log-in System
  • Collectives
    • FAQ
    • Creating a Collective
    • Quick Start Guide
    • Customize Collective
    • Change Core Contributors
    • Tiers & Goals
    • Add Fiscal Host
    • Change Fiscal Host
    • Transparent Budget
    • Expense Policy
    • Approving Expenses
    • Updates & Comms
    • Events
    • Funding Options
    • Data Export
    • Buttons & Banners
    • Integrations
    • Zero Collective Balance
    • Closing a Collective
  • Financial Contributors
    • FAQ
    • Payments
    • Website Badge
    • Organizations
      • FAQ
      • Bulk Transfers
      • Gift Cards
      • Sustainer Resources
    • Collectives
      • Collective to Collective donations
  • Expenses & Getting Paid
    • FAQ
    • Submitting Expenses
    • Expense Comments
    • Edit an Expense
    • Tax Information
  • Fiscal Hosts
    • FAQ
    • Becoming a Fiscal Host
    • Create a Fiscal Host
    • Fiscal Host Settings
    • Invoices
    • Payouts
    • Host Dashboard
    • Add Funds Manually
    • Refunds
    • Host Fees
    • Local Tax Support
    • Agreement Templates
    • Open Source Collective
  • Contributing
    • Design
      • Design Workflow
      • Design Contribution Guidelines
    • Development
      • Contribution Guide
      • Best Practice Guidelines
      • Bounties
      • API
        • Members
        • Users / Emails
        • Collectives
        • Events
      • README Integration
      • Architecture
      • Postgres Database
      • PayPal
      • Post-Donation Redirect
      • Custom Tweets
      • Manual Reporting
      • Github Permissions
      • Translations
      • Testing with Cypress
      • Collective's locations
    • Documentation
      • Style guide
      • Suggesting changes
    • Translation
  • Internal
    • Scope
    • Team Retreats
    • Brussels Summer Team Retreat
    • Host Admin Manual
    • Newsletter
    • Support
    • Issue Labels
    • DNS Troubleshooting
    • Developer Guidelines
    • Architecture
    • Testing
    • Queries
      • Gift Cards
      • Transactions
      • Ops
      • Collectives
      • Hosts
      • Analytics
      • Emails
    • Projects
      • Maintainerati Berlin 2019
      • Season of Docs 2019
    • The Open Collective Way
      • Values
      • Community Guidelines
      • Core Contributors Guidelines
      • Core Contributors: Communication
      • Core Contributors: Expenses
      • Core contributors: Leave
      • Core Contributors: Compensation
Powered by GitBook
On this page
  • To Submit an Expense
  • Documentation Requirements
  1. Expenses & Getting Paid

Submitting Expenses

PreviousFAQNextExpense Comments

Last updated 5 years ago

To Submit an Expense

Go to the Collective you're submitting the expense to and click "Submit Expense". You will need to upload a receipt or invoice and provide your contact details and PayPal address.

Each Collective (and its ) can specify expense policies and helpful info like the details for invoicing, at the top of the 'new expense' page ().

You can submit two kinds of expenses:

  • A receipt to be reimbursed for something you already paid for.

  • An invoice for your time or work, or if you don't have a receipt.

you can use. Fill out the blue parts, and change the payer to the correct Fiscal Host if needed (the Fiscal Host is shown under the Collective name on their page, and this info should be in their expense policies, which appear on the 'submit expense' screen for the Collective. If you are a Fiscal Host, to know what billing address you should ask your collective to use).

In order to be paid, submitted expenses must be approved by the Collective's core contributors (admins), who ensure valid use of the Collective's funds.

Documentation Requirements

A valid invoice must include:

  • What it is for (feature built, work done, etc)

  • Amount to be paid

  • Your full name

  • Your physical address

  • The name of the Collective

  • The name of the Fiscal Host organization (for most open source software projects that's "Open Source Collective")

Private information provided on invoices is not viewable publicly. The expense amount will be listed on the Collective's public page, but the invoice itself is only visible to the host and core contributors.

A valid receipt contains:

  1. Name of vendor (person or company you paid)

  2. Transaction date (when you paid)

  3. Detailed description of goods or services purchased (what you bought)

  4. Amount paid

  5. Form of payment (cash, check, or last four digits of credit card)

Fiscal Host
example
Here is an invoice template
read this