The same system, weighted differently by property.
Room-led, food-led and event-led properties use different parts of AtithiDeva heavily. Nothing is bolted on for any of them — the emphasis simply moves.
Independent hotels
One property, one team wearing several hats. The room board, the folio and the night audit are the whole job, and they sit one click apart.
- Room board with state filters
- Folio that matches the booking ledger
- Night audit with PDF and CSV output
Resorts and properties with F&B
Meal plans and restaurant charges belong on the guest's bill. Food categories and items are master data, so pricing stays consistent across outlets.
- Meal plan master
- Food category and item master
- Service charges into the invoice total
Banquet-led properties
Events run on their own sales cycle. Enquiry through quotation, booking, calendar, execution, services, payment and reporting.
- Event calendar
- Additional services per event
- Banquet payments and reports
Multi-department operations
Front office, housekeeping, restaurant, banquet and finance each have their own desk, with permissions, roles and users defined centrally.
- Permissions and roles
- Business and finance desks
- Cash box reconciliation
Four steps from an empty database to a closed business day.
Configure the masters
Rooms, floors, room types, bed types and base rates. Meal plans, food categories and food items. Travel agents, customers and OTAs. Hotel, invoice and payment settings.
Set permissions and users
Roles and permissions decide which desk each person opens into. Front office, housekeeping, restaurant, banquet and finance can be separated or combined.
Open the room board
Every room carries one state — available, occupied, cleaning or maintenance — and arrivals and departures surface on top of it for the current day and the day before.
Run a full cycle
Take one booking through check-in, charges, checkout and housekeeping, then close the date with a night audit. That single loop exercises most of the system.