Invoice #260541 to Testcontainers

Maintenance of Testcontainers for Node.js

Paid
Invoice #260541
Maintenance and Development

Submitted by Cristian GrecoApproved by Kevin Wittek

Aug 6, 2025

Expense Details

Invoice items
Maintenance of Testcontainers for Node.js
Date: August 6, 2025
£1,503.41 GBP
$2,000.00 USD

Total amount £1,503.41 GBP

Accounted as (USD):
$2,021.56 USD
Additional Information

Collective

Testcontainers@testcontainers
Balance:
$47,544.24 USD

payout method

Bank account
Details  
********

on
Expense created
on
Expense approved
on
Expense marked as incomplete
on
Re-approval requested
on
Expense approved
on
Expense processing
on
Expense paid
Amount Paid for Expense: $2,021.56
Payment Processor Fee (paid by Testcontainers): $5.25
Net Amount for Testcontainers: $2,026.81
Collective balance
$47,544.24 USD

Current Fiscal Host
Open Source Collective

Expense policies

We process expenses twice a week after an admin of the Collective has approved them. We make payments via PayPal and Bank Transfer (using Wise) and can only make payouts to countries served by these payment processors. You are not required to upload an invoice document (the data you submit in the expense form is sufficient), but if you would like to include an uploaded invoice, please make it out to:
Collective Name, Open Source Collective, 440 N. Barranca Avenue #3939, Covina, CA 91723, USA

INFORMATION REQUIRED ON EXPENSES:
Please refer to the documentation here for payment processing requirements on reimbursements and invoices.

REFUNDS:
If you would like a refund, please email [email protected] with the transaction #, the collective you donated to, the date, and the amount of the transaction.


Anyone can file an expense, but should agree this with the Testcontainers core team before incurring any costs. If the expense makes sense for the development of the community, it will be “merged” in the ledger of our open collective by the Testcontainers core team and the person who filed the expense will be reimbursed.

Money will first be used to cover direct project costs:

  • Bug bounties
  • Website hosting
  • Tooling, such as CI infrastructure
  • Legal protection

Then, money will be used to:

  • Pay for project expenses (e.g. ‘swag’, stickers, T-shirts, etc).
  • Pay expenses for core maintainers’ travel to present at conferences and meetups, if not reimbursable by the conference/meetup or employers.
  • Pay expenses for developer gatherings: travel expenses for core maintainer meetings
  • Pay core maintainers for time expended on key project engineering activities, e.g. release engineering, project housekeeping, expedited PR review for bug-bountied tickets.

Who can approve expenses (the ‘Testcontainers core team’)?

This list is likely to change over time, but is currently Richard North, Sergei Egorov and Kevin Wittek.

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.

Collective balance

$47,544.24 USD