Expenses
Newest First
All expenses
All methods
All
All
from GITHUB, INC. to Open Collective Engineering •
$10.00 USD
Paid
Charge #142641
$120.00 USD
Approved
Invoice #142616
security
bounty
from Vercel to Open Collective Engineering •
$80.00 USD
Paid
Charge #142602
$6,088.00 USD
Approved
Invoice #142531
engineering
core team
from FS *crowdin to Open Collective Engineering •
$150.00 USD
Paid
Charge #142440
$3,115.10 USD
Approved
Invoice #142321
engineering
core team
from Amazon web services to Open Collective Engineering •
$97.73 USD
Paid
Charge #142299
€8,090.00 EUR
~ $8,640.86 USD
Approved
Invoice #142180
engineering
core team
from nullptr to Open Collective Engineering •
$7,612.00 USD
Approved
Invoice #142169
engineering
core team
from apilayer (Fixer.io) to Open Collective Engineering •
$99.99 USD
Paid
Charge #142117
Collective balance
Tags
Expense policies
Expense policies
All expenses must have a valid invoice or receipt. Payments are made weekly on Thursdays, once they have been approved by a core contributor.
Make invoices out to: Open Collective Inc, 440 N. Barranca Avenue #3717, Covina, CA 91723, USA
FAQ
How do I get paid from a Collective?
Submit an expense and provide your payment information.
How are expenses approved?
Collective admins are notified when an expense is submitted, and they can approve or reject it.
Is my private data made public?
No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.
When will I get paid?
Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.
Why do you need my legal name?
The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.