Open Collective
Open Collective

Invoice Summary to MODX

Core Development

Invoice #115437

Submitted by Joshua Lückers on December 24, 2022

Invoice items
2 hours of Core Development and Integration (reviewing submissions and submitted bug fixes)
Date: December 24, 2022

$80.00 USD

Total amount $80.00

payout method

Bank account

Paid from Fiscal Host

Open Source Collective

440 N Barranca Ave #3717 Covina, CA 91723

By Joshua Lückerson

Expense created

By Mark Hamstraon

Expense approved

By Ember Buckon

Expense processing

By Ember Buckon

Expense paid

Collective balance
$2,376.39 USD

Fiscal Host
Open Source Collective

Expense policies

We process payouts twice a week after they have been approved by the admin of the Collective. 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 #3717, Covina, CA 91723, USA
Here are examples of what a Reimbursement or Invoice needs to contain in order for us to process it for payment. 
If you would like a refund, email [email protected] with the # of the transaction, the collective you made the donation to, the date and the amount of the transaction.


Policy for expenditure on the MODX Security Team:
  • Must be an active volunteer on the MODX Security Team
  • Must keep a statement of time spent on specific reported issues - initially not intended to cover pentesting/auditing until budget grows
  • Expense must be approved by Security Team Lead (Jason)
  • Hourly rate capped at $50/hr
  • Capped at 60 hours per year ($3000) per volunteer, may be removed if overall budget allows
Policy for expenditure on Core Development:
  • Must be an active volunteer core developer on the Integrators Team (i.e. have merge access), or someone assigned by the Integrators Team before the work is performed
  • Covers time spent on project work for the MODX core: generic maintenance, reviewing submissions, merging submissions, project management (prioritisation/triage)
  • Also covers time spent on development of features, improvements, or bug fixes that have been approved by a majority of the Integrators Team. The exact process of such approvals is to be determined.
  • Expense must be approved by Code Owners (Jason, Mark) once work is done.
  • Hourly rate capped at $40/hr
  • Capped at 200 hours per year ($8000) per volunteer and 40 hours per month ($1600), may be removed if overall budget allows
Policy for one-off projects:
  • Detailed pitch including estimated budget must be provided on the Core Development forum
  • Hourly rate capped at $40/hr for development, design, or project management on larger projects
  • Total cap for a one-off projects is one month of the OpenCollective budget if at least three times the total project budget is currently in the balance
  • The pitch must be approved by a supermajority (2/3rds) of the Integrators Team prior to performing the work


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