Resort Event & Destination Wedding Venue Software.

Numbers make the job clear, so take a wedding at a resort with 28 cottages. The family books all 28 for three nights at ₹6,500 a night, which is 84 room nights and ₹5,46,000. Three functions follow: a mehendi lunch for 150, a sangeet dinner for 250 and a wedding dinner for 300. That is 700 plates at ₹1,300, or ₹9,10,000. Lawn and ballroom hire is ₹75,000 for each function, ₹2,25,000 in all. Decor and production are ₹3,50,000. Before tax the contract is ₹20,31,000. It looks like one deal to the family, but it carries three different tax treatments, and getting them right is where the software earns its fee.

Here are the lines at an ordinary resort, one whose rooms sell below ₹7,500. Cottages at ₹6,500 fall in the 5% room slab with no input credit: ₹27,300. Food and hire sold together are a composite supply at the food rate, 5% without credit: ₹11,35,000 becomes ₹56,750 of tax. Decor is its own service at 18%: ₹63,000. Total tax is ₹1,47,050, about 7.2% of the contract, and the family pays ₹21,78,050, roughly ₹3,112 a plate all-in. At a specified-premises resort the food and hire line moves to 18% with credit. Tax becomes ₹2,04,300 on that line, total tax ₹2,94,600 and the contract ₹23,25,600. Your CA confirms which case you are in, and the software should apply it to every line.

A master contract needs a payment schedule that matches how families pay. One workable split is 30% at signing, 40% at 60 days, 20% at 15 days and the balance after the event. On the ₹21,78,050 contract that is ₹6,53,415, ₹8,71,220, ₹4,35,610 and ₹2,17,805. For services, tax generally falls due when an advance is received, so each instalment needs its own receipt voucher, and the closing invoice shows the full contract and credits every voucher. Without that discipline, a resort ends up with three advances in a spreadsheet, a final bill that ignores one of them, and a client who says she has already paid. The workbook builds this schedule from your inputs and checks that the instalments add up to the contract.

Room blocks are the quiet risk. Twenty-eight cottages held for three peak-season nights are 84 room nights of inventory. If the family only names 19 cottages, the other nine sit empty for 27 room nights unless you release them. Agree a release date, for example 30 days out, after which unnamed rooms return to inventory, and write into the contract that the family pays for any shortfall against the guaranteed minimum. Then track pickup weekly. Below 60% confirmed at four weeks out, someone should be chasing the family. At 90% or more, you can plan housekeeping. The room block sheet in the workbook shows confirmed rooms, share of block and rooms to release each week.

Seasonality decides how you staff and price, so look at the whole year. In the workbook's sample figures, a 28-cottage resort earns about ₹3.17 crore a year from rooms, and the four wedding months from November to February bring about 54% of it. Those numbers are illustrative, not benchmarks, and you should replace them with your own actuals. If your peak share is that lopsided, the monsoon months need a plan: maintenance, staff leave and corporate offsites at lower rates. A resort that only knows its yearly average will overstaff July and understaff December.

Where does a resort PMS stop and Kaliquid start? A resort PMS handles individual room sales, meal plans, housekeeping, maintenance, spa and activity bookings, and multi-outlet billing across rooms, F&B and activities. RunHotel's resort page lists exactly that kind of multi-outlet billing. Kaliquid does not do those. It handles the event side: the function calendar, the master contract, per-plate quotes, room blocks attached to the event, kitchen indents for multiple events and Tally export. Most destination resorts end up running both. Ask each vendor for a live three-day, three-venue booking before you decide. If the demo cannot hold that, the wedding season will find the gap for you.