Metadocumentation
master
master
  • Welcome
  • About
    • About
    • Company
    • Pricing
    • Community Guidelines
    • Values
    • Team
    • Investors
    • Contributing
    • Terminology
  • Product
    • Product
    • Roadmap
    • Comparison
    • User Profile
    • Currencies
    • Log-in System
  • Collectives
    • Collectives
    • 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
    • Backers & Sponsors
    • Sponsor FAQ
    • Payments
    • Collective to Collective donations
    • Organizations
    • Gift Cards
    • Bulk Transfers
    • Website Badge
    • Sustainer Resources
  • Fiscal Hosts
    • Fiscal Hosts
    • 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
  • Expenses & Getting Paid
    • Expenses & Getting Paid
    • Submitting Expenses
    • Expense Comments
    • Edit an Expense
    • Tax Information
  • 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
    • Internal
      • 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
      • Style Guide
    • Projects
      • Maintainerati Berlin 2019
      • Season of Docs 2019
    • The Open Collective Way
      • Core Contributors Guidelines
      • Core Contributors: Communication
      • Core Contributors: Expenses
      • Core contributors: Leave
      • Core Contributors: Compensation
Powered by GitBook
On this page
  • Where should expense submitters address invoices?
  • Collectives as projects of the Fiscal Host
  • Collectives as independent unincorporated partnerships
  • Communicating the invoicing address
  1. Fiscal Hosts

Invoices

Where should the invoices for a collective be addressed to?

Where should expense submitters address invoices?

For invoices directly submitted by a vendor or contributor for payment from a Collective's balance, what should the billing address be? It depends on the Fiscal Host.

We've seen two main ways that Fiscal Hosts define their relationship with Collectives: as a project of the Fiscal Host or as an independent unincorporated partnership. The details depend on the legal situation of the country where the Fiscal Host is located and the specifics of how their legal entity is set up.

Collectives as projects of the Fiscal Host

In this case, the Fiscal Host is liable for the activities of the Collective, just as companies are responsible for projects or departments within them. Invoices should be addressed to the Collective with the address of the Fiscal Host.

E.g.:

Babel Open Source Collective 501(c)(6) 340 S. Lemon Ave. #3717 Walnut, CA 91789 USA

This is the most common setup. It offers all the benefits of having a shared legal entity. However, it's best used by hosts that have a limited scope (either by topic or by region) and that have strong trust and policy agreements with their Collectives.

Collectives as independent unincorporated partnerships

In this case, liability is held by the Core Contributors of the Collective and the Fiscal Host is just holding money on their behalf. Invoices should be addressed to one of the Core Contributors of the Collective and be under the name of the Collective.

E.g.:

XR Belgium Xavier Damman Personal address 1000 Brussels

Host should check with local authorities to see if this is something you can do within the bounds of “Fiscal Sponsorship” regulations in your country. It's a good setup for when Hosts don't want to or can't assume legal liability for the actions of Collectives. In Europe, the Collective may need to register for their own VAT number if they have regular commercial activities.

Communicating the invoicing address

The Fiscal Host Expense Policy is shown on the Submit Expense page of each Collective you host. To define it, go to the settings of your Fiscal Host profile and edit the 'Expense Policy' section. It can also be useful to link to an invoice template.

PreviousFiscal Host SettingsNextPayouts

Last updated 4 years ago

A custom Fiscal Host expense policy
Edit expense policy