Recipt V — Simple Fee. Instant Receipt.

⚡ A minimal system to manage school fees and generate receipts instantly

Fast • Clean • Practical

---

🎯 Purpose

Recipt V exists to solve one real problem:

Schools still rely on manual fee tracking and handwritten receipts.

This project replaces that with a simple, digital, and reliable system.

No complexity.
No bloated ERP.
Just what’s needed.

---

🧠 Philosophy

• Keep it simple
• Keep it fast
• Keep it useful

Build small → Scale later.

---

✨ What It Does

• Track student fees
• Show paid vs remaining
• Generate instant receipts
• Provide a clean admin view
• Allow parents to check & pay

---

⚙️ Tech Direction

Layer	Stack
Frontend	HTML, CSS, JavaScript
Backend	Firebase Firestore
Hosting	Firebase
Payments	Razorpay (planned)

---

🧩 Experience

• Clean light UI
• No learning curve
• Works in seconds
• Designed for real school usage

---

🚀 Vision

Recipt V is not the end.

It is the starting point for:

• Full school digital systems
• Smarter financial tracking
• Simple tools that actually get used

---

📋 Business Logic Decisions

1. Strict Overpayment Prevention Policy

Overpayments are strictly disallowed. Before a payment is accepted (whether online checkout via Razorpay or manual Cash/UPI recorded by an admin), the backend verifies that the payment amount does not exceed the remaining unpaid balance for that specific fee component.

• Validation: Checks existingPaid + requestedAmount <= totalOwed for the target componentId in the student's active feeStructure.
• Behavior: Violations are rejected on the server side with a failed-precondition error, preventing any transaction capture.

2. Notification Failure Graceful Resilience

If the WhatsApp or SMS receipt notification fails to deliver (due to network faults, API provider timeouts, or invalid phone numbers), the payment status remains fully completed.

• Reasoning: A notification delivery issue must never block, void, or roll back the actual school fee collection record.
• Behavior: The background triggers catch notification delivery exceptions, flag the payment document's notification.status to failed, and record the error message without affecting the payment capture.

---

🛠️ Status

Currently in active development.

Core system being built step-by-step.

---

🤝 Contributing

If you want to improve this, feel free to fork and build.

---

💌 Support / Donate

If you believe in simple tools solving real problems,
you can support the project.

📧 Contact for support/donations:
vinayakkghai@gmail.com

Even small support helps keep this alive ❤️

---

Built with focus, not noise.