Version 1.0


A primary responsibility of leaders is to ensure that the organisation is transparent to the Joomla community, and accountable for its programs and finances to its contributors, members, the public and government regulators.

Accountability requires that the organisation comply with all applicable laws and ethical standards; adhere to the organisation’s mission; create and adhere to conflict of interest, ethics, personnel and accounting policies; protect the rights of members; prepare and file its annual financial report with the Internal Revenue Service and appropriate state regulatory authorities and make the report available to all members of the board and any member of the public who requests it.

The development of proper internal controls helps organisations ensure accountability. This purpose of this document is to specify these internal controls for the financial aspects of the Joomla project such as spending, reimbursements, event funding and budgeting.

Financial Policies

The following policies will govern the financial aspects of the Joomla Project.

1. Finance Team Membership

Membership in the Finance Team will follow any and all project-wide policies for adding/voting in members. In addition:

  1. Membership on the Finance Team will be preceded by a 3-month provisional status. After the provisional period, the Treasurer will consult with the Finance Team lead and then decide whether to invite the provisional member to the team.
  2. All Members of the Finance team, including provisional members, will undergo a background check.
  3. All Members of the Finance team, including provisional members, will sign a confidentiality agreement prior to accessing any financial documents, tools, online banking or financial records.

2. Travel

The following policies will govern booking and reimbursing travel on behalf of the Joomla project:

  1. Transportation Class. In all cases, economy/coach class transportation will be used by travellers. Any and all upgrades must be paid by the traveller and will not be reimbursed
  2. Airfare purchase lead time. To ensure reasonable prices, all airfare will be booked no sooner than 6 months nor later than 30 days prior to departure.
  3. Airfare Cost. Costs for transportation must be within 20% of the lowest available fare within the purchase lead time.
  4. Port of Entry. Transportation to and from the event must be to the closest reasonable Port of Entry. Advance permission must be obtained from the budget line item owner and the Treasurer when the location of the venue does not match the arrival and/or departure city for the event.
  5. Eligible Expenses. Travel-related expenses for the following items are eligible for reimbursement:
    1. Transport to and from place of departure (eg. airport, bus station, train station) will be reimbursed. Use of private/personal vehicles will be reimbursed at the IRS mileage rate[1].
    2. Parking at place of departure (eg. airport, bus station, train station). Please note maximum days below.
    3. Transport to event city (eg. airline, train, bus).
    4. Transport to and from event venue using taxi or public transportation will be reimbursed. Modern car services like Uber or Lyft are acceptable with the exclusion of their premium-tier services (i.e. Uber Black/Select).
    5. Event registration fees will be reimbursed.
    6. WiFi expenses incurred while travelling to and from the event, and while attending the event, will be reimbursed up to $10.00[2] per day.
  6. Eligible time. Reimbursements for daily expenses will be provided for the number of days of the event plus:
    1. 1. one (1) day for events requiring up to 8 hours of travel.
    2. 2. two (2) days for events requiring between 8 and 24 hours of travel.
    3. 3. three (3) days for events requiring greater than 24 hours of travel.
  7. Ineligible Expenses. The following expenses will not be reimbursed under any circumstances:
    1. Alcoholic beverages.
    2. Tips.
    3. Private cars and limousine services.
    4. Expenses that promote any 3rd-party organisations or businesses, including those owned (in full or in part) by the traveller.
  8. Documentation required. Receipts for all expenses — including, meals, taxis and incidental expenses — are required for all reimbursements.
  9. Conflict of Interest.. When travel costs are paid by the project, it is important that travellers properly manage any real or perceived conflict of interest (see also: OSM Conflict of Interest policy document[3]). To manage Conflict of Interest, attendees will disclose any 3rd-party organisations they own (in full or in part) as follows:
    1. By completing an annual COI disclosure form.
    2. By disclosing any 3rd-party organisations they own (in full or in part) at the beginning of any talk.
    3. By not wearing any branded clothes related to any 3rd-party organisations they own (in full or in part).
  10. Exceptional circumstances. On rare occasions, it may be necessary to book travel or incur expenses in a way that contradicts the above travel policy (i.e. illness preventing travel resulting in substitute speaker; cheap, last-minute flights). These rare exceptions will be approved or denied on a case-by-case basis by the Finance Team.
  11. Optional per diem limits. Reimbursements for accommodations, meals, and incidental expenses may be limited to the calculated per diem lodging rates based on the event location[4], at the discretion of the Treasurer.

3. Reimbursement Processing

To simplify reimbursements and the accounting of personally incurred expenses, the reimbursement workflow will adhere to these guidelines:

  1. All reimbursements will be processed through the official, project-wide reimbursement form[5].
  2. Reimbursement requests must be submitted within sixty (60) days of the event or sixty within (60) days incurring the last expense in the request. Requests received after 60 days may be rejected at the discretion of the Treasurer.
  3. For each person, one reimbursement will be processed per event/meeting.
  4. Reimbursements will be only processed following the meeting.
  5. Reimbursement by wire transfer will have a $100.00 minimum payout threshold. Reimbursement requests below this threshold will be combined and processed when the threshold is exceeded. This threshold does not apply for PayPal reimbursement requests.
  6. PayPal reimbursements will be in US dollars only using currency conversion rates[6] on the date of reimbursement submission.
  7. Reimbursements will be approved by the appropriate line item owner. In the case of conflict of interest (i.e. self-approving reimbursements), the department head, Treasurer, or President/Vice-President will be called on for approval.
  8. Reimbursements will be processed within 14 days of receipt of an approved request.

4. Payment Requests

Requests for payment for products and services will be similar to the reimbursement request workflow and include similar approval steps.

5. Financial Transparency

Every open source project needs to build a culture of transparency and accountability[7], and maintain an expectation of auditing by federal and state agencies. items below will be implemented to facilitate this:

  1. Financial decision making and responsibility will be decentralized by assigning a line item owner to each line item in the budget.
  2. Line item owners will have the following responsibilities:
    1. To be the primary decision maker on all expenditures from their line item.
    2. Maintain appropriate records and decision making documentation (if appropriate) for all expenditures.
    3. Serve as the main point of contact for all finance-related enquiries by the Finance Team.
    4. Upon request, provide complete project information to the Finance Team for line item-related projects.
  3. If a line item owner leaves the project, the budget for the line item is frozen until a new owner is assigned.
  4. Banking transactions and reconciliation of said transactions will be decoupled and should not be performed by the same individual.
  5. Bank reconciliation will be performed monthly. Budget vs. Actual reports will be sent to line item owners each month following reconciliation.
  6. Accounting of the project's finances and organisation of the budget will use the Unified Chart of Accounts from the National Center for Charitable Statistics.

6. Funding for Joomla Events

As a condition of funding/sponsorship for Joomla Days and related events, the events team will facilitate the signing of an agreement between event organizers (and/or organizing corporations) and OSM with the following terms:

  1. The organizer(s) agree to protect and hold harmless Open Source Matters, its members, volunteers, and representatives from any cost, injury, and damage incurred by, or to any person, or property whatsoever, during the event. In the event of an action, court costs, expenses of litigation and reasonable attorneys' fees will be carried out by the event organizer.
  2. The organizer(s) agree to abide by the terms of the Joomla Events Charter[9].
  3. The organizer(s) agree that funds/sponsorship will be returned if not used (i.e. if there is a budget surplus).
  4. The organizer(s) agree that funds/sponsorship will be returned if the event is cancelled.
  5. The organizers agree that no payments will be made to personal bank accounts or PayPal accounts. All receiving accounts must be associated with legally incorporated entities.

7. Requests for Proposals

All new expenditures for permanent or semi-permanent assets and/or services with annual expenses projected to be in excess of $10,000.00 will go through an RFP process to select the best vendor.

8. Legal and Financial Services

Expenses for legal, financial and similar professional services will be paid for by the project and overseen by the governing body of the project.

9. Budgeting.

The budget process should focus on balancing expenses against revenue, providing funding for measurable goals, and personal accountability.

  1. Budget Process/workflow
    1. Prior to beginning the budget process, the Finance Team will provide the following to all Budget Liaisons and/or Department heads:
      1. Estimate of total available funds (including annual revenue and transfers from reserves/savings) for the forthcoming year.
      2. An up-to-date report of the current year spending.
    2. Set project-wide goals between teams and/or departments.
    3. Collect budget requests for each goal containing the following information:
      1. Detailed expenses and/or revenue estimates including account numbers.
      2. Line item owner (i.e. decision maker for expenditures)
      3. “Why should this request be funded?”
      4. “When will the funds be required?”
      5. “How will success will be measured?”
      6. Does the request include operational expenses such as those for Google Apps, registration fees for existing domain names, hosting costs, GitHub, and prior contracted products/services?
    4. Combine budget requests into a draft budget.
    5. Send draft budget for review to all proposed line item owners and department heads.
    6. Send finalized budget for board approval.
    7. Publicly share approved budget and project-wide goals on
  2. Prioritization policy.
    1. A prioritization policy is needed when the total requested budget exceeds the expected total available funds (including annual revenue and transfers from reserves/savings) for the forthcoming year. In this case the following method will be used to decide which budget request get priority:
      1. Operational expenses — such as those for Google Apps, registration fees for existing domain names, hosting costs, GitHub, and prior contracted products/services — will be automatically approved.
      2. All other budget requests will be ranked[10] either (i) by an equal number of representatives from each leadership team or (ii) by each department head and the board of directors.
      3. Based on rankings an average priority will be assigned to each budget request.
      4. Requests will be approved in order of priority until the total amount of all approved requests matches the expected total available funds (including annual revenue and transfers from reserves/savings) for the forthcoming year less any operating expenses.
  3. Re-budgeting/reallocation. During the current fiscal year it might become clear that an allocated budget item(s) will not be used in it’s entirety. A request for reallocating this budget may be submitted to the Board for approval and will consider the following points:
    1. The current budget status.
    2. How well the new request meets one of the goals that were in the approved budget.
  4. Transferring line item ownership. When a line item owner (see Budgeting, above) leaves a team or can no longer serve as the decision maker for approving expenditures, the associated team or department will specify a new line item owner.
  5. Short-term budget resolution. When the budget for the forthcoming year has not been approved on or before the start of the fiscal year, operational expenses — such as those for Google Apps, registration fees for existing domain names, hosting costs, GitHub, and prior contracted products/services — will be automatically approved as a short-term budget resolution. Amounts and payment schedules for operational expenses from the last approved budget will be used until a new budget has been passed.

10. Foreign Assets Control

The Office of Foreign Assets Control (OFAC) of the US Department of the Treasury administers and enforces economic and trade sanctions against targeted foreign countries and regimes, terrorists, international narcotics traffickers, etc.. As an incorporated entity in the United States, Open Source Matters, Inc. will not knowingly send funds to nor receive funds from any country, corporation or individual listed in the OFAC database.[11]

11. Policy Changes

This Financial Policy document should be reviewed annually by the Finance Team in consultation with any and all existing leadership teams and/or department heads. Any proposed changes must be approved using the accepted voting practices of the Joomla Project at the time of the proposed change(s).

Appendix A - Unified Chart of Accounts

The Unified Chart of Accounts is included in the PDF version of this document.

Appendix B - Contributors

The primary authors of this document are Martijn Boomsma, Mike Demopoulos, and Victor Drover.

In addition, the following people provided feedback: Michael Babker, Peter Bui, Ruth Cheesley, Ronni Christiansen, Jessica Dunbar, Jorge Lopez-Bachiller, Peter Martin, Rod Martin, Tessa Mero, Ryan Ozimek, and Sander Potjer.

Appendix C - Changelog

  • Nov. 2014: Initial draft presented at joint leadership summit at Joomla World Conference 2014 (Cancun, Mexico).
  • Nov. 2014 - Aug. 2015: Comments collected from leadership members.
  • Sept. 2015: Comments reconciled and final points added at the 2015 Finance Summit (Milwaukee, WI).
  • Oct. 5, 2015: Policy sent to OSM board for review and approval.
  • Oct. 8, 2015: Policy approved by OSM board. 



[2] All financial references in this document will be in US Dollars (USD) unless otherwise noted.


[4] Worldwide per diem rates will be calculated here:

[5] Currently located at the following website

[6] Historical currency conversion rates will be calculated here:


[9] The charter is found here:

[10] Cheap/simple tools like SurveyMonkey allow for easy ranking forms. eg.

[11] OFAC countries can be found online: The complete, searchable database is also available here:

 Official Policy Version

The official version of the Financial Policy that was ratified on Oct. 8, 2015 by the board of Open Souce Matters.

pdfDownload the Official Financial Policy as PDF (version 1.0)316.11 KB