Open Collective
TUM-Dev (Campus App / tum.sexy)
Contribute
Budget
About

Receipt #235124 to TUM-Dev (Campus App / tum.sexy)

Weitere Bewirtung für die Codingnight am 15.01.2025

Paid
Reimbursement #235124
Meals & Entertainment
Submitted by Florian Schmidt•Approved by Florian Schmidt

Jan 15, 2025

Expense Details

Attached receipts
Abendessen mit dem Team
Date: January 15, 2025
€64.97 EUR
Total amount
€64.97 EUR
Accounted as (USD):
$66.96 USD
Additional Information

Collective

TUM-Dev (Campus App / tum.sexy)@tum-dev
Balance:
$13.96 USD

Paid to

Florian Schmidt@florian-schmidt

payout method

Bank account
Details  
********
By Florian Schmidt
on
Expense created
By Florian Schmidt
on
Expense approved
By Lauren Gardner
on
Expense processing
By Lauren Gardner
on
Expense paid

Amount Paid for Expense: $66.96

Payment Processor Fee (paid by TUM-Dev (Campus App / tum.sexy)): $0.63

Net Amount for TUM-Dev (Campus App / tum.sexy): $67.59

Net Amount for Florian Schmidt: €64.97

By Lauren Gardner
on
Expense updated
Collective balance
$13.96 USD

Current Fiscal Host
Open Source Collective

Expense policies
File an invoice only when you are requesting payment for services you personally performed. We can only pay the individual who completed the work -- no third parties or friends. The person who performed the work must be the owner of the account receiving payment.

We have strict requirements for what we can and cannot process. Certain information is required on all invoices, and we cannot process payment if required information is missing. 
If your expense is missing required information or documentation, you will be asked to revise it before processing can begin.  

Processing and Payment: 
  • Expenses are processed twice weekly after approval by a Collective administrator and a secondary OSC review
  • Payments are made via PayPal or Wise (bank transfer)
  • Payments are limited to countries supported by these providers
  • If you use PayPal, you may be required to complete a KYC process

An uploaded invoice is not required -- the information entered in the expense form is sufficient.
If you choose to upload an invoice, address it to:

Collective/Project Name, Open Source Collective
440 N. Barranca Avenue #3939
Covina, CA 91723, USA

First and foremost we want to support our developers by giving them all the tools they need to work efficiently. We'll also use these funds to cover any hosting costs (like registered domain names) or expenses for hackathons and other events to promote development efforts. Generally development work itself will not be able to be expensed, as we expect everyone to contribute to our open source projects in the spare time.

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.
More info →

Collective balance

$13.96 USD

Fiscal Host:

Open Source Collective