Mandirji

Written for a mandir trust and the people who run its counter. A temple’s day is receipts — daan against a dozen different income heads, rent from the aavas rooms, hall bookings — and every one of them has to be numbered, printed, acknowledged, and eventually explained to a trustee.

Mandirji does that in one program, on one set of masters, with the accounting sitting underneath it so the trust’s books come out of the same entries the counter typed.

Built for Shri Aadinath Bahubali Digambar Jain Mandir Trust, Borivali, Mumbai, and installed at both their Borivali West and Podanpur offices.

Receipts — the whole point of it

It is one receipt screen, not five. You pick the type, and the screen asks the questions that type needs — the boli reference for a boli, the room for an aavas stay, the form for a hall booking. Each type then runs on its own automatic sequential series, so the donation book and the rent book never share a number:

• General — daan against any income head from the account master, and boli collected against an event
• Rent — yatri aavas and permanent aavas, against the room
• Hall — hall bookings, against the booking form

More than one account head on a single receipt, with a running total, for the day the money arrives against three heads at once. Cash, cheque or NEFT, with bank name, cheque number, cheque date and branch captured where they apply, and the donor picked from the master — or created on the spot without leaving the screen.

Narration comes from the master, from the previous entry, or from the previous entry of that same account on a right-click. Nobody retypes the standard line.

The SMS goes out with the receipt

This is what the counter actually feels. The moment a receipt is booked, the donor gets a message on the mobile number held against them —

Recd from <name> Rs. <amount> Vide Receipt No. <no> by cheque no. <no> for Daan

— signed off in the trust’s own name, and the receipt itself is printed or produced as a PDF in the same click, or mailed. The wording changes with the receipt type: Daan for a donation, Rent for aavas, Booking for a hall.

Receipts can also be ticked in bulk from the register and messaged together, for the day a hundred donations were taken at an event and nobody had time to press send. SMS runs on an approved DLT template, registered as part of the installation.

Receipt printing runs over a date range with bulk print in one go, so a morning’s book is printed as a batch rather than a receipt at a time.

Masters

• Account master — head, group, Tally alias, mobile number, PAN and Aadhaar, and the flags that decide what a head is for: Daata, Member, Boli Daata, Tenant, Yatri Aavas Booking and Hall Booking. That is how a donor list, a member list, a tenant list and a boli list are each a real list rather than a search
• Account master details and a master details edit grid, so a hundred mobile numbers are corrected in one screen rather than one form at a time
• User master and a separate web user master
• Date range and narration masters
• Accounts merged where the same donor was created twice, multiple delete for heads that were never used, and master and balance transfer between mandirs

Reports

• Member receipt register and member register
• Cash book and bank book
• Balance analysis and monthly analysis
• Statistics — user-wise work done — and an entry list carrying created-by, modified-by and deleted-by with the date and time of each
• Any report generated as Excel or PDF, or mailed straight out
• Every grid filters, sorts, groups, hides, wraps and re-orders columns like Excel, with subtotals on the grouped column and a sort that can be saved or cleared, and exports exactly as you left it
• Reports print through the software’s own grid printer, so what is on screen is what comes out

Export to Tally

The trust’s auditor keeps the books in Tally, and nobody wants the receipts typed twice. Mandirji writes a Tally XML file for a date range which imports in one shot — provided the same account heads exist on the Tally side, which is what the Tally alias on each account master is for.

Trustees and control

• User-wise login with rights on every menu, so a counter volunteer books receipts and sees nothing else
• Web and mobile users created separately, as Manager or Admin, for office bearers who want to see collections without being handed the accounting program
• Created-by, modified-by and deleted-by with date and time on every entry — for a body that answers to a committee, this is the part that matters
• Selective period lock, so a closed year cannot move
• Reminders on startup and at the times you set — this is where pending boli is chased: the pledge made in front of everyone and quietly never paid is the one thing a trust cannot track from memory
• Document scan and attach, so the counterfoil sits against its entry, plus a message log and mail settings with the trust’s own SMTP and signature
• More than one mandir in the same installation, switched between without leaving the program, each on its own database
• New year rollover carrying masters and balances forward, and database backup and attach from inside the program

Built to the trust’s own requirement

Mandirji is not a shrink-wrapped package. It was written to a specification agreed with the trust’s office bearers, and it is extended the same way. If your mandir runs its counter differently, that difference is the specification.

Technical details

• Front end: Microsoft .NET (VB.NET) on Windows
• Back end: Microsoft SQL Server, a separate database per mandir
• Output: native Excel and PDF, SMTP mail, DLT-approved SMS, Tally XML
• Installed on site, supported remotely, with training after installation