A small NGO can run on a spreadsheet for donors, accounting software its auditor accepts, a payment link that records the donor's PAN and address, and a shared folder for programme proofs. Add a donor CRM when you pass a few hundred donors, and consider custom software only when your process, such as campaigns, sponsorships or beneficiary tracking, no longer fits a tool you can buy.
The hard part is not the interface. It is the data: who gave what, which receipt number, which purpose, and who was helped. Get that right and any tool works. We have not compared or priced specific products, and compliance rules for receipts and reporting change, so check incometax.gov.in and ask your auditor before you design a format.
The records an NGO has to get right
| Record | What to capture | Why it matters |
|---|---|---|
| Donor ledger | Name, PAN or ID where required, address, amount, date, mode, purpose, receipt number | Basis for receipts, donor statements and the filings that 80G registration brings; the exact filings are for your CA to confirm |
| Receipt series | Serial number, date, NGO registration details, a copy kept | A gap or duplicate in the sequence is an audit question |
| Restricted and unrestricted funds | Which donation is for which project or cause | Spending a restricted gift elsewhere can breach a donor's terms |
| CSR and grant tracker | Agreement, budget lines, tranches, utilisation certificates, reporting dates | Missed reports delay the next instalment |
| Beneficiary register | Name, age, location, service received, consent, dates | Source of impact data; handle as sensitive personal data |
| Volunteer and staff register | ID, role, hours, safeguarding checks, signed policies | Needed for safety and for CSR volunteer reports |
| Asset and stock register | What was bought, from whom, where it is, condition | Funders and auditors ask for it |
Spreadsheets: good for the first year
Google Sheets or Excel is a fair start if you are disciplined. Use one sheet per record, drop-down lists for purpose and mode, locked columns for receipt numbers and one person responsible for edits. Keep a version history on, and export a monthly copy to a separate folder.
- Donor sheet and receipt series with a formula that blocks duplicate receipt numbers.
- A form for volunteers and beneficiaries that feeds a sheet, with a consent tick box in the local language.
- Mail merge to send thank-you emails and, where applicable, receipts as PDFs, which your auditor must approve first.
- Programme tracker with one row per session or camp: date, place, attendance, spend, photos link.
- Where it breaks: shared edit access, accidental deletion, typing PAN wrongly, receipts issued twice, no history of who changed what, and a founder's personal laptop holding the only copy.
A free tool is not free if a former volunteer owns the account. Create the NGO's own Google or Microsoft account and put at least two trustees as owners.
Accounting and receipts: off the shelf
Your auditor will usually dictate the accounting tool. Many Indian CAs work in Tally or similar packages and some prefer cloud accounting; pick what your CA is comfortable reviewing so you do not pay for conversions every year. Ask whether the software can handle fund-wise or project-wise accounts and the format your type of entity files accounts in.
| Need | Tool category | What to check before choosing |
|---|---|---|
| Books, vouchers, bank reconciliation | Desktop or cloud accounting (Tally, Zoho Books and similar) | Does your auditor use it? Can it split funds by project and export audit-ready reports? |
| Online donations with receipts | Payment gateway or donation page from a payment provider | Does it accept non-profit use? Does it capture PAN and address? Who generates the receipt, and in what format? |
| Donor database and email | CRM, or a mailing tool connected to a sheet | Can you export all data? Is data stored in India or abroad, and who is the processor? |
| Recurring gifts | UPI AutoPay mandates, e-NACH or card standing instruction, through a gateway | Cancel flow, failure retries, donor consent record |
| Staff and volunteer attendance | Simple attendance app or sheet with a QR check-in | Works offline in the field? Data stays with you? |
| Documents and approvals | Shared drive with folder structure and access levels | Two trustees as owners; backup outside the founder's laptop |
The GST billing software guide is written for businesses, but the same questions about invoice numbering and audit trail apply to your receipt series.
A donor CRM: when the sheet starts to hurt
Move to a CRM when you are losing track of who gave last year, when the same donor appears under three spellings, or when more than two people send messages to donors. A basic CRM keeps one record per donor with every gift and conversation, tags by cause, reminders for renewal and a log of what was sent.
- Dedupe and import. The first job is cleaning the sheet, matching on phone and PAN, and not on names alone.
- Segments. Monthly givers, first-time donors, CSR contacts, volunteers who also gave, lapsed donors.
- Permission fields. Whether you may call, WhatsApp or email, and when they last agreed.
- Tasks. Thank-you calls, renewal reminders, report due dates for large grants.
- Access. Fundraisers should not see beneficiary health data; check that the tool can restrict that.
A general-purpose business inbox and CRM setup can cover this, as can sector-specific donor tools. Run a one-month trial with real data before paying for a year.
Impact reporting without inflated claims
Donors and CSR teams want numbers and stories. Decide in advance the five or six things you will count every month, such as sessions held, children attending, camps run, people screened and referrals made, and collect them in the same way each time. Count activities and outputs honestly. Outcomes, such as improved learning or health, need baselines and follow-up, and should not be claimed until you have the data.
| Report | Typical contents | Source in your system |
|---|---|---|
| Monthly donor note | Money in, money spent, what happened, one story with consent, what next | Donor ledger, expense sheet, programme tracker |
| Quarterly funder report | Activities against plan, budget against actual, challenges, photos | Grant tracker, vouchers, attendance |
| CSR utilisation report | Milestones, expenses against sanctioned heads, proof folders, beneficiary counts | Asset register, bills, delivery proofs |
| Annual report | Governance, audited accounts, programmes, numbers, learning | All of the above plus audited statements |
Never publish a beneficiary's photo, name, diagnosis or address without informed consent. For children, take a guardian's consent and avoid identifying details.
When custom software starts to pay
Custom is rarely worth it for an NGO with fewer than a few thousand donors and a single programme. It starts to pay when you run several of these at the same time: public campaign pages with progress and updates, many small recurring donors, sponsorship of individual beneficiaries, multiple centres feeding one dashboard, or a volunteer and field-data app that must work offline.
| A custom build might cover | Why a sheet or CRM struggles | What stays manual |
|---|---|---|
| Campaign pages, UPI giving, automatic receipts and a public fund-use record | Tools charge per transaction or limit custom fields; reporting is thin | Verification of each campaign, thank-you calls, filings with the authorities |
| Sponsorship matching and annual renewals | Stateful logic and reminders per sponsor | Updates from the field |
| Field data capture, offline-first | Forms need signal; sync conflicts | Training workers and checking data quality |
| Role-based access for staff, partners and donors | Sheets cannot enforce who sees what | Safeguarding decisions |
Read app development cost in India and how to choose an app development company before asking for quotes, and keep a plain-language data export clause in any contract.
The concept build and The Saral
Pitchin is our concept build for a trust-first giving platform: two-tap UPI donations, campaign pages, automatic 80G-style receipts and a public record of fund use. It is a concept to look at, not a finished product you can sign up for, and it does not cover your accounting, filings with the authorities, beneficiary case management or donor CRM.
The Saral is a small studio that builds custom web and mobile products. If a campaign platform or field app is where your NGO is heading, read the crowdfunding platform solution, then brief us. Until then, a sheet, an accounting tool your CA likes and a clean receipt series will do the job. Back to the NGO playbook.
More on starting a NGO
- Start hereThe full playbook →Models, licences, startup costs and the steps to your first customer.
- Go deeperWhat to buy →Office kit, cash controls, field supplies and what to postpone, costed for a small NGO.
- Go deeperWho to hire →Programme staff, accountant and volunteers in hiring order, with pay, vetting and contracts.
- Go deeperGetting customers →Donors, CSR partners, beneficiaries and volunteers: channels, first 20 donors and retention.
- Go deeperFinding suppliers →Vendors, partner NGOs and clinics: quotes, MoUs, payment terms, backups and red flags.
Questions people ask
What software does a small NGO in India need?
A spreadsheet for donors and programme records, accounting software your auditor can work in, a payment link that captures donor details and a shared drive owned by the NGO. Add a CRM when donor numbers or staff grow. Pick tools your auditor accepts and check the current receipt requirements before designing formats.
Can software generate 80G receipts automatically?
Yes, many payment and donor tools can, but you are responsible for the content and number series. Make sure the receipt carries your registration details as your registration requires, and have your auditor approve the format. Rules on what must appear and what must be reported change, so confirm on incometax.gov.in.
Do I need a donor CRM from day one?
No. A clean spreadsheet is fine for the first few hundred donors. Move to a CRM when duplicates, missed thank-yous and several people messaging donors become a problem. Test a tool with your real data for a month and check you can export everything before committing for a year.
How should an NGO store beneficiary data safely?
Collect only what you need, with informed consent in the local language, on devices and accounts owned by the NGO. Restrict access by role, back up regularly, and avoid sharing lists on open WhatsApp groups. Health and children's data need extra care. Read the DPDP checklist and ask a lawyer about your obligations.
When is custom NGO software worth the cost?
When you run several of these together: public campaign pages, many recurring donors, sponsorships, multiple centres and offline field data, and no tool fits without painful workarounds. For a single-programme NGO with a few hundred donors, a sheet plus an off-the-shelf tool is cheaper and safer. Get a fixed scope and data ownership in writing.