UPI Donation Reconciliation for NGOs: A Practical Workflow
UPI donation reconciliation for NGOs means matching every UPI donation received with the correct donor, campaign, bank entry, receipt, and accounting record. A reliable workflow combines bank statement checks, payment-provider reports, donor data, receipt controls, and clear exception handling rather than relying on screenshots or manual memory.
UPI has made it easier for people in India to donate through QR codes, UPI IDs, payment links and fundraising pages. It has also created a new accounting problem: money may reach the NGO’s bank account quickly, while donor details, payment references, charges and receipts remain spread across different systems.
For a small NGO, this can lead to unanswered donor queries, duplicate receipts, incorrect 80G records, delayed utilisation reports and difficulty explaining balances to trustees or auditors. The solution is not necessarily an expensive enterprise system. It is a consistent process supported by the right data fields and sensible automation.
Why UPI Donation Reconciliation Matters
A UPI transaction appearing in the bank statement confirms that money was received. It does not always confirm who donated, which campaign the donation belongs to, whether a receipt was issued, or whether the amount recorded in the accounting system is correct.
For example, an NGO may receive a bank credit with a UTR or transaction reference but no complete donor name. The donor may have entered a name differently on the payment page, used a family member’s UPI account, or omitted an email address. If the NGO later receives a request for an 80G receipt, staff must connect the request with the correct payment.
Donation reconciliation helps answer five operational questions:
- Did the donor’s payment actually reach the NGO’s account?
- Is the amount recorded correctly before or after any payment charges?
- Can the payment be linked to a donor and campaign?
- Has the correct receipt been issued?
- Has the transaction been recorded in NGO accounting records?
It also creates a defensible trail for internal review, statutory compliance and donor communication.
UPI payments are not always the same
An NGO may receive UPI donations through different arrangements:
- A static QR code linked directly to a bank account
- A dynamic QR code generated for a particular donation amount
- A UPI ID displayed on the NGO’s website
- A payment gateway supporting UPI, cards and net banking
- A fundraising platform that collects money before settlement
- A payment link shared through WhatsApp or social media
- A bank account used for a specific campaign or project
Each arrangement produces different information. A direct bank transfer may show a UTR and payer name but no campaign field. A payment gateway may provide donor information, campaign details and status reports, but the settlement amount may be net of fees and GST.
Before designing the workflow, identify every channel through which UPI donations enter the organisation.
The Basic Reconciliation Model
A useful reconciliation model has four records:
- Donation request or donor form — what the donor intended to pay and the information they submitted.
- Payment or gateway record — what the UPI provider reports as successful, failed, refunded or settled.
- Bank statement — what actually reached the NGO’s bank account.
- Accounting and receipt record — what the NGO recognised, receipted and reported.
These records may not match immediately. A successful payment on a gateway can settle into the bank later. A bank credit can appear without a matching donor form. A refund may be processed after the original receipt was issued.
Reconciliation is the process of comparing these records and resolving differences.
The key identifiers
The following fields are particularly useful for bank matching and donation reconciliation:
| Field | Why it matters |
|---|---|
| Donation ID | Internal reference used across the NGO’s systems |
| Gateway order or payment ID | Connects the payment page to the provider report |
| UTR or bank reference | Helps match the transaction with the bank statement |
| Donor name | Supports receipt preparation and donor communication |
| Donor email and mobile number | Helps send receipts and resolve queries |
| Amount paid | The gross amount attempted or received |
| Fees and GST | Needed where a gateway deducts charges |
| Net settlement | Amount deposited into the NGO’s bank account |
| Payment date and settlement date | Distinguishes donor payment from bank credit |
| Campaign or project | Supports restricted-fund tracking |
| Payment status | Prevents receipts for failed or pending transactions |
| Receipt number | Connects the financial entry with the donor document |
A small NGO may not need every field on a visible screen, but it should preserve the important data in its internal records.
Gross amount and net amount
Suppose a donor pays ₹5,000 through a payment gateway. The gateway may charge a processing fee and GST, then deposit a lower amount into the NGO’s account. The donation record should normally retain the gross donation amount, while the accounts should separately record the gateway charges according to the NGO’s accounting treatment.
Do not treat the net bank credit as the donor’s donation merely because it is the amount visible in the statement. Ask the gateway provider for its settlement report and fee structure. The exact treatment should be confirmed with the NGO’s accountant or auditor.
For direct UPI transfers into the bank, there may be no gateway fee. However, the bank statement can still contain unclear payer information or multiple transactions with similar amounts.
Step 1: Map Every UPI Donation Channel
Start by preparing a simple channel register. List each QR code, UPI ID, payment link, gateway account and fundraising platform used by the NGO.
For each channel, document:
- The bank account receiving or ultimately receiving the money
- The legal name displayed to the donor
- Whether the channel is static or dynamic
- Whether donor details are collected
- Whether a campaign or project can be selected
- Where transaction reports are downloaded
- How often settlement occurs
- Whether fees and GST are deducted
- Who has access to the dashboard
- Whether refunds can be initiated
- Whether the QR code is still active
This exercise often reveals a practical issue: old QR codes remain printed on posters, school circulars, event banners or social media posts. If the linked account or purpose has changed, those codes can create reconciliation problems.
Use controlled naming for channels, such as:
General Fund - Bank A - QR 01Flood Relief - Gateway - Campaign 2025Education Sponsorship - UPI LinkAnnual Event - Bank B - QR 02
Do not create a new bank account or payment channel for every small campaign without considering the accounting burden. Separate accounts can help with restricted funds, but they also require additional review and controls.
Review the donor-facing experience
A donor should see clear instructions before paying. The payment page or QR information should explain:
- The NGO’s registered name
- The purpose of the donation
- Whether the donor must enter a name and email
- How to share payment confirmation if required
- Whether an 80G receipt may be available, subject to applicable conditions
- Which details are needed for the receipt
- A contact method for payment problems
Avoid asking donors to send only a screenshot as proof. A screenshot can support an investigation, but it is not the primary accounting record. The bank and payment-provider records should determine whether the payment succeeded.
Step 2: Capture Donor and Payment Data Properly
Direct UPI payments are convenient but can produce limited donor information. A static QR may not collect the donor’s email, address, PAN or campaign selection. If the NGO needs reliable receipts and donor reporting, it should consider placing a short donor form before or after payment.
The form should collect only information that the NGO genuinely needs. Depending on the receipt and reporting process, this may include:
- Full name
- Mobile number
- Email address
- Address, where needed for the receipt
- PAN, where required for the NGO’s process
- Donation amount
- Donation purpose or campaign
- Payment date
- UTR or transaction reference
- Consent for communication, if the NGO sends updates or appeals
If the form is completed before payment, create an internal donation ID and display it in the payment instructions where possible. If it is completed after payment, allow the donor to submit the UTR and amount so staff can match it later.
For payment gateways, capture the provider’s payment ID and order ID in addition to the UTR. These identifiers may be different and are useful at different stages.
Do not rely on the payer name alone
The name in a bank statement may be:
- A short form of the donor’s name
- A family member’s name
- A business or company name
- A UPI handle rather than a legal name
- A bank-generated description
- Missing or inconsistent across transactions
Use a combination of amount, date, UTR, payment ID, donor-submitted information and campaign context. If there is still uncertainty, mark the entry as unmatched instead of guessing.
Step 3: Reconcile Daily or on a Defined Schedule
The right frequency depends on donation volume, staff capacity and reporting requirements. A small NGO with occasional donations may reconcile on a fixed weekly schedule. An NGO receiving donations for an active relief campaign may need daily review.
A basic daily process is:
- Export or download the previous period’s bank transactions.
- Download the payment gateway or platform report.
- Import new donor-form submissions.
- Match successful payment records to bank credits.
- Mark failed, pending, refunded and disputed transactions.
- Issue receipts only for verified donations.
- Record unmatched items in an exception list.
- Review the reconciliation summary before closing the period.
For bank statements, use a consistent date range and preserve the original downloaded file. If the bank provides CSV, Excel or PDF formats, retain the original file in a restricted folder. Do not overwrite it after editing.
For payment gateways, download both transaction-level reports and settlement reports where available. The transaction report may show what donors paid, while the settlement report explains what reached the bank.
A practical matching sequence
Use the strongest identifier first:
First match: UTR or bank reference
Second match: Gateway payment ID or order ID
Third match: Exact amount and date
Fourth match: Donor name, mobile number, email and campaign
Final step: Manual review with supporting evidence
Avoid matching two similar amounts solely because they occurred on the same day. If the NGO received three donations of ₹1,000, the amount alone cannot identify the correct donor.
Statuses to use
A reconciliation sheet or software system should use clear statuses instead of vague notes such as “checked” or “done”.
Useful statuses include:
- Payment initiated
- Payment successful, awaiting settlement
- Bank received, donor details missing
- Matched and receipted
- Matched, receipt pending
- Failed
- Refunded
- Duplicate
- Under review
- Unidentified credit
- Donor claim pending verification
These statuses make handovers easier. A new staff member can understand what requires action without reading long message threads.
Step 4: Handle Exceptions Without Guessing
Most reconciliation effort goes into exceptions, not straightforward matches. Build an exception process before the NGO starts receiving higher volumes of UPI donations.
Successful payment but no bank credit
A gateway may show a successful payment while the settlement has not yet reached the bank. Check the settlement cycle, bank holidays, account details and any provider hold. Do not issue a final receipt based only on an unverified gateway status if the NGO’s internal policy requires bank confirmation.
Some providers distinguish between “success”, “captured”, “settled” and “failed”. Define which status is sufficient for receipt issuance and apply it consistently.
Bank credit but no donor record
Create an unmatched-credit entry with:
- Bank date
- Amount
- UTR or reference
- Bank narration
- Receiving account
- Initial review date
- Follow-up owner
- Final classification
Search email, website forms, WhatsApp messages and campaign records using the amount and date, but do not make unverified assumptions. If the donor can be identified later, update the record with the evidence used.
If the donor cannot be identified, ask the accountant or auditor how it should be classified and disclosed. Do not assign the money to a restricted project without a reliable basis.
Donor says money was debited but NGO did not receive it
Ask for the UTR, date, amount and payer bank details. Check the gateway or bank statement. A debit from the donor’s account does not always mean the NGO received the money; the payment may be pending, reversed or credited to a different account.
Give the donor a clear status rather than promising an immediate resolution. If the payment failed or was reversed, the donor may need to contact their bank or payment provider.
Duplicate payments
A donor may pay twice because the first confirmation was delayed. Match both UTRs separately. Do not combine them into one receipt unless the NGO’s accounting policy supports that treatment and the donor has requested it.
If one transaction is refunded, record the original donation, refund reference, refund date and final status. Keep the communication trail.
Incorrect or incomplete donor details
A donor may request a change to the name or address after payment. Maintain the original payment evidence and record the correction as an approved update. Do not silently overwrite important receipt data without an audit trail.
For 80G-related documentation, the NGO should follow its tax professional’s advice on the details required and the applicable rules for the relevant period.
The Role of Receipts and NGO Accounting
Donation reconciliation is not complete when the bank entry is marked as matched. The receipt and accounting entry must also be linked to the transaction.
A practical record should connect:
Donation ID → Payment ID or UTR → Bank entry → Receipt number → Ledger entry → Campaign or fund
This can be maintained in accounting software, a donor management system, or a controlled spreadsheet for a smaller organisation.
Receipt controls
Use sequential receipt numbers or another controlled numbering method. Record:
- Receipt number
- Receipt date
- Donor name
- Donation amount
- Payment mode
- UTR or payment reference
- Purpose, where applicable
- Relevant registration and tax details
- Authorised signatory or approval record, if used
- Email or delivery status
Do not issue multiple receipts for the same verified donation. If a receipt is cancelled or replaced, retain the old number and record the reason.
The exact content of a donation receipt depends on the NGO’s legal status, tax registrations and professional advice. An NGO may have 12A or 12AB registration, 80G approval, CSR eligibility, FCRA registration or none of these. These are different matters and should not be treated as interchangeable.
Domestic donations and FCRA funds
An NGO receiving foreign contributions must follow the Foreign Contribution (Regulation) Act requirements applicable to it, including rules around designated accounts, reporting and utilisation. A UPI payment from an Indian account is not automatically a foreign contribution merely because the donor has a foreign connection, but the source and applicable rules must be assessed carefully.
Do not route different categories of funds through accounts or ledgers without checking the requirements. Separate fund tracking, approval controls and professional review are especially important where FCRA funds or restricted grants are involved.
Restricted donations
If a donor gives money for a specific purpose, record the restriction at the time of donation. Examples may include scholarships, medical support, a relief project or a school programme.
Do not assume that the campaign name alone is enough. Preserve the donor’s stated purpose, the appeal wording and any relevant communication. Reconciliation should show not only that the money reached the bank, but also which fund or project should receive the accounting entry.
Choosing Between a Spreadsheet and Software
The right tool depends on transaction volume, number of channels, staff capacity and reporting needs. A spreadsheet can be appropriate when the process is disciplined and access is controlled. It becomes risky when multiple people edit copies, formulas are overwritten or donor records are kept across WhatsApp chats.
| Approach | Suitable for | Strengths | Common limitations |
|---|---|---|---|
| Controlled spreadsheet | Low-volume NGOs with one or two channels | Low setup effort, flexible fields, easy review | Manual imports, duplicate edits, weak automation |
| Accounting software with donation ledger | NGOs needing formal books and reports | Better ledger control, bank reconciliation, audit support | Donor communication and campaign tracking may be limited |
| Donor management system | NGOs with recurring donors and multiple campaigns | Donor history, receipts, campaigns, communication | Requires clean setup and ongoing data discipline |
| Payment gateway dashboard plus accounting system | NGOs receiving online payments at regular volume | Payment status, settlement reports, broader payment support | Gateway and accounting data still need reconciliation |
| Custom workflow or integration | NGOs with several channels or specific reporting needs | Automated matching, dashboards, tailored approvals | Needs planning, maintenance and access controls |
The tool should reduce duplicate entry, not simply display more information. Before buying or building a system, document the current workflow and exceptions.
What a useful system should do
A practical solution should support:
- Multiple donation channels
- Import of bank and gateway reports
- UTR and payment-ID fields
- Gross, fee, GST and net-settlement fields
- Campaign or fund tagging
- Receipt numbering
- Duplicate detection
- Exception queues
- Role-based access
- Export for the accountant
- Basic audit history
- Donor data correction with change tracking
- Backup and recovery
Automatic bank matching can save time, but it should not automatically classify every transaction. Low-confidence matches should be sent for human review.
Data Protection and Access Controls
Donation records contain personal information. Names, mobile numbers, email addresses, addresses, PAN details and payment references should not be accessible to every volunteer or vendor.
Use role-based access where possible:
- Donation-entry staff can add and view relevant records.
- Finance staff can reconcile and post ledger entries.
- Programme staff can see campaign totals without unnecessary donor details.
- Trustees can receive summary reports.
- Technology vendors receive only the access needed for the service.
Avoid storing complete bank credentials, UPI PINs or sensitive payment authentication information. The NGO should never ask donors to share their UPI PIN or OTP.
Use individual logins rather than one shared password. Enable two-factor authentication for bank, gateway, email, cloud storage and accounting accounts. Review access when a staff member, intern or vendor leaves.
For forms and databases, define a retention policy. Keep records required for accounting, tax, audit and donor-service purposes, but do not retain unnecessary personal information indefinitely. The NGO should review applicable Indian privacy and data-protection requirements with its adviser, particularly if it uses overseas software or shares donor data with external vendors.
Monthly Review and Management Reporting
Daily matching handles transactions. Monthly review checks whether the overall process is reliable.
A monthly reconciliation pack can include:
- Opening unreconciled items
- Total UPI donations by bank account
- Total by channel and campaign
- Gateway fees and GST
- Gross donations and net settlements
- Matched transactions
- Unidentified credits
- Pending settlement items
- Refunds and chargebacks
- Receipts issued and pending
- Restricted-fund totals
- Closing exceptions
- Person responsible for each unresolved item
Compare the bank total with the accounting total and gateway settlement total. Explain every difference. A short written note is better than leaving a balance with no context.
Review recurring patterns. For example, repeated missing donor emails may indicate a poorly designed form. Many unidentified credits may indicate that the QR code does not provide enough information. Frequent duplicate payments may indicate slow confirmation messages or unclear donor instructions.
The objective is not merely to close the month. It is to improve the workflow so fewer exceptions are created next month.
Common Mistakes to Avoid
Treating screenshots as the accounting record
Screenshots can be edited, lack complete information and are difficult to search. Use them as supporting evidence when investigating a payment, not as the primary source for reconciliation.
Issuing receipts before verifying payment
A donor may show a pending or failed transaction. Establish a receipt rule based on the provider status and bank confirmation process.
Recording net settlement as the donation
Where charges are deducted, separate the gross donation from gateway fees and GST according to the accounting advice received.
Using one QR code without campaign controls
A single general QR code may be convenient, but it can make campaign-level reporting difficult. Use campaign fields, donor forms or separate controlled links when project tracking matters.
Keeping donor data only in WhatsApp
WhatsApp messages are easy to miss, delete or leave with one staff member. Move required details into the organisation’s controlled record and restrict access appropriately.
Editing bank exports
Keep the original bank or gateway file unchanged. Work on a copy or import it into a system that preserves the source record.
Allowing unrestricted spreadsheet editing
Use protected columns, dropdown statuses, named owners, version history and regular backups. Do not allow several people to maintain separate “final” files.
Ignoring old payment channels
Deactivate or clearly label unused QR codes, links and UPI IDs. Review printed material during each campaign change.
Frequently Asked Questions
What is UPI donation reconciliation for NGOs?
It is the process of matching UPI donation records with payment-provider reports, bank credits, donor information, receipts and accounting entries. It confirms both that money was received and that it was recorded under the correct donor, campaign and fund.
Can an NGO reconcile UPI donations in Excel?
Yes, a controlled spreadsheet can work for low-volume donations and a small number of payment channels. It should include unique IDs, UTRs, payment statuses, receipt numbers, campaign fields, exception owners and protected formulas. As volume or staff involvement grows, accounting or donor-management software may reduce risk.
Should an NGO issue an 80G receipt for every UPI payment?
The NGO should issue receipts according to its eligibility, applicable rules and internal verification process. A UPI payment alone does not resolve questions about donor details, receipt content or tax treatment. Confirm the process with the NGO’s accountant or tax adviser.
What should an NGO do when the bank shows a UPI credit but the donor is unknown?
Create an unmatched-credit record with the date, amount, bank narration and UTR. Check gateway reports, donor forms and campaign communications, then contact possible donors only where there is a reasonable basis. If the donor cannot be identified, obtain accounting advice before assigning the money to a specific restricted fund.
Is a UPI QR code enough for donation reconciliation?
A QR code can receive money, but a static QR may not capture enough donor or campaign information. For better reconciliation, pair it with a donor form, dynamic payment link, gateway workflow or clear instructions for submitting the UTR and required receipt details.
How often should an NGO reconcile UPI donations?
Set a defined schedule based on volume and risk. Weekly review may be adequate for occasional donations, while active fundraising campaigns may require daily checks. Perform a complete monthly reconciliation before closing the accounts for the period.
Where to Start
Begin with a channel register listing every QR code, UPI ID, payment link, gateway and receiving bank account. Then create one standard donation record with a donation ID, amount, date, UTR, donor details, campaign, payment status, receipt number and reconciliation status.
For the next reconciliation cycle, download the bank and payment-provider reports, match clear transactions first and maintain a separate exception list. After one month, review which fields were missing and which manual steps caused delays.
If you need help designing a donation database, reconciliation dashboard or integration with your existing accounting workflow, talk to the Govindani Infotech team on WhatsApp; project pricing is confirmed by the team there.