How to Track Who Actually Paid for a College Event

The Treasurer's Dilemma in University Societies

In student politics and club leadership, the role of Treasurer is often the most stressful. When a college fest collects ₹50,000 across 300 workshop attendees, the student treasurer is personally accountable to: - The Faculty Advisor who must sign off on society accounts. - The College Accounts Section which demands formal receipts and reconciliations. - The Student Council which audits society expenditures. - Attendees who demand immediate confirmation of their ticket passes.

When payments are tracked haphazardly on spreadsheets, reconciling records is nearly impossible. Attempting to track college event payments without a dedicated system leads to lost revenue, delayed approvals, and contentious financial audits.

---

Why Traditional Tracking Methods Fail

┌────────────────────────────────────────────────────────────────────────┐
│                   THE 4 BREAKING POINTS OF SPREADSHEET FINANCE         │
├──────────────────────────────────┬─────────────────────────────────────┤
│ 1. The "Parent Account" Problem  │ Paid from father's UPI; student's   │
│                                  │ name nowhere on the bank record     │
│ 2. Asynchronous Bank Delays      │ Funds credited hours after submit   │
│ 3. Lack of Access Controls       │ 5 coordinators editing one sheet    │
│ 4. No Status Audit Trail         │ Inability to trace who approved what│
└──────────────────────────────────┴─────────────────────────────────────┘

1. The "Parent Account" Problem Over 40% of college students in India pay registration fees using their parents' bank accounts. When an attendee named Rohan Sharma registers, the incoming payment appears on the bank statement as Rajesh Sharma. Treasurers searching their bank feed for Rohan find nothing, leading to wrongly rejected registrations and angry attendee disputes.

2. Asynchronous Bank Settlement Delays During peak festival registration days, inter-bank UPI servers experience occasional traffic lags. An attendee completes their transaction, but the credit notification arrives in the club's account two hours later. Without structured transaction IDs, coordinators cannot match delayed credits to pending registrations.

3. Multiple Editors Corrupting Spreadsheets When four different committee members share edit access to a single Google Sheet, cells are accidentally overwritten, rows are deleted, and payment statuses get corrupted.

4. Lack of Approval Accountability If a student enters an event without paying, who approved their pass? In a shared spreadsheet, there is no audit log showing which coordinator approved the transaction or when the approval occurred.

---

How Spark Delivers Flawless Financial Reconciliation

Spark structures the entire payment lifecycle into an immutable, verifiable ledger:

[Attendee Submits 12-Digit UTR] ──> [Spark Checks Uniqueness] ──> [Treasurer Reconciles] ──> [Pass Minted]

1. UTR-Centric Matching (Bypasses Name Confusion) Spark does not depend on account holder names. It requires the attendee to submit their 12-digit bank Reference / UTR number. When the treasurer searches the bank statement for that specific 12-digit code, it matches exactly—regardless of whether the payment originated from the student, their parent, or a roommate.

2. Database Deduplication Enforcement If two attendees attempt to register using the exact same 12-digit transaction number, Spark immediately blocks the second submission with a clear error: "This transaction reference has already been submitted." This stops receipt sharing across hostel rooms instantly.

3. Role-Based Approval Permissions Only verified club executives with treasurer permissions can approve or reject payment records. Every approval action is stamped with the reviewer's identity and exact timestamp, maintaining total organizational accountability.

4. Real-Time Revenue Dashboards Organizers view live totals of collected revenue, approved passes, pending reviews, and rejected transactions directly inside the dashboard, eliminating manual calculation errors.

---

Step-by-Step Daily Reconciliation Workflow for Treasurers

3 Common Payment Reconciliation Edge Cases & Solutions

1. Partial Amount Payment Errors Occasionally, an attendee accidentally transfers ₹100 instead of the required ₹250 registration fee. In Spark, the treasurer can flag the registration as Underpaid, sending an automated notification to the attendee to complete the remaining balance with a supplemental UTR before their pass is issued.

2. Multi-Ticket Group Payments When one student pays for their entire three-person hackathon team with a single ₹600 UPI transfer, the primary registrant inputs the 12-digit UTR and lists their teammates' registered email addresses. The treasurer verifies the single lump-sum credit once, approving passes for all three teammates simultaneously.

3. Inter-Bank UPI Settlement Lags When a student's private bank experiences NPCI server delays, the money leaves the student's account but takes up to an hour to appear in the club's passbook. Spark keeps these transactions in a visible Pending Review status rather than rejecting them, allowing the treasurer to approve the pass as soon as the bank credit clears.

---

Audit-Ready Documentation for College Administration

When the festival wraps up, the treasurer must present final accounts to faculty coordinators and college deans. Spark's exportable ledger includes: - Attendee Full Name, Roll Number, and College - Ticket Tier and Registration Fee - 12-Digit Bank UTR Code - Payment Approval Timestamp & Reviewer ID - Physical Gate Check-In Timestamp

With this complete audit trail, passing faculty financial reviews is seamless and transparent.

Take the anxiety out of society finances. Start tracking on Spark and manage your event accounts with complete clarity.