Very interesting project. Non-profit really needs an affordable and efficient all-on-one solution. They can have open source specialized tools for managing members or funding but many NGOs have generic management needs.
I will gladly participate to the wiki, as a freelancer who work regularly with local NGO for several years.
PS : I may contribute to the code too, as soon as I confirm my move from Odoo to ERPNext…
There has to be something about funders and a provision for them to see the status of on-going projects and programmes that they are subscribed to (controlled by staff). Usually NGOs get bogged down with the reporting to their funders regarding project/programme results.
For data collection alot of NGOs in developing regions will use surveys in rural areas or generally areas of unrealible if any connectivity. Offline data capture is essential. See tools like dhis2.org or commcarehq.com. SMS can also be a useful tool for data capture and community engagement, see RapidPro [community.rapidpro.io], a great open source SMS utility.
Fundraising and donations can be done pretty much they way ERPNext sells products on the site with minor adjustments.
I think this is an awesome feature. One thought about the initial setup workflow:
Currently on provisioning a new instance, the setup wizard asks a load of questions, e.g. customer, suppliers, products etc. which are clearly all geared up for “For Profit” organisations. It would be great to be asked whether you are setting up a for or not-for profit organisation.
Only relevant modules will be added to the dashboard (e.g. Memberships, Chapters, Volunteer Management, Donor Management, Event and Grant)
Initial questions will query for donors rather than customers etc.
I’d like to mention a few issues that came up after I discussed the Non-Profit Module with some of my higher-ups:
The way the system is setup is very redundant, There are contacts, customers (I’ll get to where those come in - in a sec), and donors, three places where the same information is stored and three places for confusion. The same goes with donations and payment entries. There’s no reason to have an extra doctype that only shows a little bit of information, it’s only a waste of time for those that need to use it.
In QuickBooks (we use this currently, so this is what I can compare too), Donors are customers (both give you money), a donation is a purchase/transaction, and a pledge is an invoice. Even currently (in ERPNext), you can’t use a donor as a party in a Payment Entry, and for the sake of data duplication, it’s definitely better not to make that possible. The same goes with donations and pledges, and furthermore, there’s no need to make two doctypes that show the exact same information in only a slightly different form.
I think that the best resolution to this would be to simply replace the donor with a checkbox that says “Donor”, and now you can filter out donors from plain customers and also add membership types and other things. Also, do the same with donations and payment entries. I think you get where I’m going with this.
I agree with @chabad360 about reusing doctypes. As a monolith system, this should be one of the main concern in developing ERPNext. Otherwise, it is a megalith platform that has many modules that may not inter-working between modules and may create more confusion.
This is almost the case with some existing domains: services, retail, wholesaler.
Activating those domains doesn’t make any different with the available doctypes. They are just there.