Skip to main content
GullySystem
Non-profit

Business solutions for Temples

Explore software for work such as “Annual brahmotsavam or the main festival”. Review each business function below, including when it fits and what to check before implementation.

Temples

How the business operates.

The temple office runs Temple Management Software, set up by GullySystem for trusts with a seva counter. Counter staff, priests and trustees use it. Seva and pooja bookings, donations by type, numbered PDF receipts, devotee details with gothra and nakshatra, festivals and priest duties sit together. The temple also gets a website with timings, sevas and a donation page.

Pooja booking

Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.

Online seva booking

Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.

Donations by type

Record every donation against a head you define, such as annadana, gau seva, building fund or hundi, with the donor’s tax ID, payment mode, reference and purpose. Each fund reads separately.

Online donations

Let devotees give from your website by bank transfer and enter the transaction reference. A numbered receipt is raised with that reference for matching against the bank statement.

Receipts and PDF

Issue one numbered series for donations and sevas as PDFs with your trust name and registration number. A wrong receipt is cancelled with a reason instead of deleted, so every number is accounted for.

Devotee register

Find devotees by phone number with gothra, nakshatra, rashi, birthday, anniversary, family members and preferred language, linked to their bookings and donations, so a returning family is greeted by name.

Festivals and events

Manage festivals, homas, bhajans, pravachanas, annadana and classes with dates, a banner and a website page. Event registration is not on screen yet and can be built at set-up.

Priests

Record each priest’s specialisation, languages, available days and hours. Assign them to bookings, and choose whether they appear on the website.

Trust members

List trustees with role, photo, term and whether their contact is shown, optionally on the website’s about page, so devotees know who to write to.

Announcements and gallery

Post festival notices, timing changes, special poojas and appeals with publish and expiry dates, and upload photos into albums for each utsava so the Brahmotsavam pictures stay together.

Temple website with your domain

Publish a site with the deity, history, darshan and aarti timings, dress code, sevas, events, gallery and a donation page on your own domain. The office changes the festival banner.

The records that hold the operation together.

  • Pooja booking. Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.
  • Online seva booking. Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.
  • Donations by type. Record every donation against a head you define, such as annadana, gau seva, building fund or hundi, with the donor’s tax ID, payment mode, reference and purpose. Each fund reads separately.
  • Online donations. Let devotees give from your website by bank transfer and enter the transaction reference. A numbered receipt is raised with that reference for matching against the bank statement.
  • Receipts and PDF. Issue one numbered series for donations and sevas as PDFs with your trust name and registration number. A wrong receipt is cancelled with a reason instead of deleted, so every number is accounted for.
  • Devotee register. Find devotees by phone number with gothra, nakshatra, rashi, birthday, anniversary, family members and preferred language, linked to their bookings and donations, so a returning family is greeted by name.
  • Festivals and events. Manage festivals, homas, bhajans, pravachanas, annadana and classes with dates, a banner and a website page. Event registration is not on screen yet and can be built at set-up.
  • Priests. Record each priest’s specialisation, languages, available days and hours. Assign them to bookings, and choose whether they appear on the website.

Operational bottlenecks to check

Receipt books run out on festival days

On festival days a queue forms before the doors open. Receipts written by hand smudge in the heat of the counter, and the evening total may not match the cash box or the hundi count.

Bookings for the next day are not visible

Bookings arrive at the counter, by phone and through trustees, and each carries a different slip. The priest learns the sankalpa count only when names are read out at the homa.

Tax-exemption receipts are requested late

A donor gave by cheque in April and asks for a tax-exemption receipt with a tax ID in January. Someone has to search the receipt book and write it out again. Errors creep in.

Cancelled receipts are not recorded

A wrong receipt is torn out of the book. When the auditor asks why number 214 is missing, there is no record of what happened, who cancelled it or why.

Devotees in other cities cannot book easily

Families who have moved to other cities want an archana, a deepam or a share in annadana. They phone the office and hope their gothra and nakshatra are noted correctly.

Donation totals are in separate books

Counter donations, cheques and hundi counts are recorded by different volunteers in different books, so trustees’ meetings begin with a discussion of whose total is right.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Sevas and slots

    Enter each pooja or seva with the name your office uses, the amount or free-will offering, the days performed, time slots and bookings per slot. Choose which ones devotees may request online, and which stay counter-only.

  2. 2. Booking

    At the counter, staff pick the seva, date and slot, note the gothra, nakshatra, rashi and sankalpa, and take payment. Online requests arrive as pending bookings with those details filled in by the devotee.

  3. 3. Receipt

    Every paid booking or donation takes the next number in the series and comes out as a PDF. Donation receipts carry the trust’s tax-exemption details and the donor’s tax ID where the trust is registered for exemption.

  4. 4. Priest assignment

    The office assigns a priest to the booking and marks it confirmed, assigned or completed. The priest opens the day’s list with every sankalpa on it, in the order of the homa.

  5. 5. Closing the day

    The dashboard shows today’s donations, the month’s total, the day’s bookings and online requests still waiting, with collections by payment mode. Exports go to the trust’s accountant for the audit file.

Roles and responsibility boundaries.

For temple office and counter staff

Book sevas, record donations, print or download receipts and add new devotees. On festival days, several counters can issue receipts from the same series without a clash of numbers.

For trustees and managing trustees

View today’s and this month’s donations, bookings and payment modes, and check cancelled receipts with their reasons before the committee meets.

For accountants

Download donations, bookings and receipts as spreadsheets for the books and the trust’s audit, with the cancelled numbers listed.

For priests

See the sevas assigned for the day with each devotee’s gothra, nakshatra and sankalpa details, in the order of the homa.

Reports your managers need.

  • Today’s and this month’s donations
  • Donations and seva bookings totals
  • Collections by payment mode: cash, cheque, bank transfer and online
  • Receipts register, downloadable as CSV
  • Seva bookings by date, with online requests still pending
  • Devotee list, downloadable as CSV

Connections to scope

  • Bank transfer references
  • WhatsApp chat button on your website
  • CSV export for your accountant

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your sevas, heads and timings

Sevas with the names your office uses, donation heads, darshan and aarti timings and receipt numbering are entered. The screens are in English.

Old records migrated

Devotee lists and past donations arrive from Excel or registers, so a returning donor’s details are already there.

Hundi and counter routine

We agree with the trustees how hundi counts are entered, under their own donation head, and who may cancel a receipt.

Website and domain

The temple website is set up on your domain with your photos, history and trust details. The donation page shows your bank details, and donors enter their transaction reference for the office to check.

Training and support

Office staff and counter volunteers are each shown only the screens that suit their work. We host the software, take backups and answer when you call.

Limitations to settle before implementation

  • A small shrine with a single priest and no receipts. A notebook is enough.
  • Temples under a government endowments department that must use the department’s own system.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Annual brahmotsavam or the main festival
  • Annadanam, the daily free meal programme
  • Wedding and naming ceremony bookings
  • Online darshan and prasadam delivery
  • Daily seva and archana bookings
  • Temple renovation and restoration appeals
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements