Every module, and what is actually in it.

The screen the hotel lives on. Rooms down, nights across, three weeks at a time, and every booking a bar you can pick up.

Asar PMS · the booking chart The chart. Rates, minimum stay and stop-sell above the rooms, so the price and the rule are on the same screen as the booking.

• The chart — rooms down, nights across, a rolling three-week window from any date. Drag a bar to another room and it is a room move; pull its edge and the stay is extended, repriced as you pull.
• Rates and rules on the same screen — the night's price, minimum stay and stop-sell sit above the rooms, so the price and the rule are read where the booking is made.
• Hover card — guest, dates, source, balance and the next action, without opening anything.
• Right-click a room — book it, or block it out of sale with who and why recorded and the block visible on the chart.
• Bookings with no room yet — a channel booking that arrived without a room is a card in its type's lane, dragged onto a room when the desk chooses. A panel lists every one still waiting.
• Occupancy heatmap — every hotel in the group a row, every day a cell, so a soft week is seen a month out.
• Colour by state — in house, due out, arrived, held, blocked, out of order. Two stays in one cell on the same day are marked, not hidden.
• Dashboard — arrivals, departures, in house, occupancy, ADR, RevPAR, revenue so far, housekeeping progress and what is still owed.

Arrival to departure. A walk-in on one screen including the ID; one click for a guest with a reservation; a check-out that ends in a GST invoice rather than in a second system.

Asar PMS · registration card The registration card, printed from the booking. Hotel, GSTIN, stay, tariff and the declaration the guest signs.

• Walk-in and check-in from reservation — guest, ID, room, rate and advance on one screen; pre-filled when the booking exists.
• Today, the first screen — after sign-in: arrivals and departures still to do, whether yesterday is closed, what was booked today and by whom, and anything flagged and left too long. The chart is one click away.
• Registration card — printed from the booking with the hotel's own declaration, numbered, and the print recorded.
• Foreign guests — nationality drives the passport fields and the Form C due list; a wrong ID number is flagged, not a wall.
• A masked Aadhaar is accepted — UIDAI tells guests to show XXXXXXXX1234, and a checksum can never pass on it. The desk records it as masked, with who saw the card and when.
• Room move — drag on the chart or use the dialog; every room listed with its verdict, an override with a reason, and the folio follows the guest.
• Swap a room — an urgent guest can take a room planned for someone who has not arrived yet; that guest moves to the room being left, or to a free room of their own type, in the same act. Nobody already in house is moved, no price changes, and nothing is oversold.
• Upgrade — when the booked type cannot house the stay (oversold, nothing free, room out of order) the guest moves up at the rate they paid. It never downgrades.
• A full room is a question, not a wall — one more person than the type sleeps is an amber warning and one confirmation, logged with who, when and from which machine.
• Check-in reuses an open folio — a guest with an advance already posted does not get a second bill.
• Prepaid OTA stays — the stay moves to the OTA's account at check-in; the card shows what is owed by the OTA and what by the guest, and the invoice always names the guest, never the OTA.
• Room free the moment the guest has left — a departure and a same-day arrival do not fight over the room.
• Check-out — balance, tender, invoice. A small remaining balance can be waived at the door as a recorded allowance with a reason and a name, under a ceiling; a bill in credit asks retain-or-refund rather than refusing.
• Change the guest on a stay — another person's name on the booking and its bills, without touching the room, dates, rate or money; administrators only, logged.
• The administrator is the super boss — a night-audited, in-house or departed booking can be corrected by an administrator, with every change carrying login, time, IP and machine. Refused only where money would be silently rewritten.
• Form C / FRRO, police register, blacklist alert — the statutory set, produced from what was captured at the desk.
• A discount on the bill — the folio's fourth tab: a percentage or an amount off the whole bill, the room, the food or one line, the GST reduced with it, a reason from the hotel's list and a name on every line; a manager above the hotel's limit.
• Early check-in and late check-out have a price — as many bands as the hotel wants per side (up to 2 hours free, up to 7 hours half, then the night); the desk posts, a manager waives with a reason, and the list of who was charged or waived is a report.
• Undo what was done today — an administrator walks back a check-in, a payment, a charge or a cancellation as a stack, until the night audit closes the day; every undo recorded.
• A cancelled booking is put back — from Find, to expected, in house or departed, missed nights billed; the desk before the audit, an administrator after.
• A settled bill is reopened by an administrator to void a wrong retention, refund it and close again — with login, IP and machine on each step.
• The GST number opens the company — type a guest's GSTIN and the company is looked up, added to the CRM if new (pay at checkout, no credit) and the bill made out to it.
• Reasons are picked, not typed — every correction, undo and status change chooses from the hotel's own lists; Other… opens a box only when chosen.

Every charge, every payment, every correction on one bill the cashier can read aloud to a guest — and never quietly rewritten. A void is a new line reversing the old one; the original stays.

Asar PMS · a guest folio One folio, three departments. The dinner at Darbar is a posting on the room bill with its own GST line — not a second bill somebody carries over.

• Folio windows — one stay, several bills: guest, company, travel agent — settled separately without duplicating the booking.
• Charges and payments — cash, card, UPI, bank transfer, wallet, cheque, OTA-collected or company account, each labelled and each in the cashier's report. Split tender is one all-or-nothing action.
• Refunds that go back the way they came — a refund names the payment it returns, cannot exceed what came in, carries a reason and an approver, and sits behind a capability the desk deliberately does not hold.
• Charge routing — the company pays room and tax, the guest pays extras; set once, applied to every posting.
• Transfer to a company account is a settlement — the bill is settled and the company owes it; it is not negative revenue.
• The full document set — proforma at any moment, tax invoice, credit and debit notes, each numbered in its own series and printable on the hotel's own letterhead, inherited account → brand → property.
• Tax invoice with a QR anyone can verify — against the system that issued it.
• Invoice numbers begin where the hotel says — a hotel moving from another system continues its series.
• An invoice freezes when its GST month is filed — after the month following check-out nobody, administrator included, changes the booking or its bill. A correction after that is a new entry in the current month.
• CGST and SGST are exact halves — tax is worked to the paisa and the two halves are always equal, enforced by the database. The hotel's own state is the place of supply.
• Void, write-off and override each behind a capability — authority is granted, not assumed by whoever is at the terminal.
• Cashier shift — opened and closed with a denomination count; the variance is stated rather than absorbed.
• GST panel — this hotel's registered payers only, searchable, so a B2B invoice picks the right GSTIN first time.
• Give a discount — beside Post a charge, Take a payment and Send money back: the reduction is an allowance per tax slab, shown on the invoice and filed in GSTR-1 as printed.
• The day book — a month of days: cash opening to closing carried forward, the bank register with a confirmed tick per line, the till's expenses written into the ledger the same instant.

Corporate business in India is rarely one company at one address. A group sits over branches, because the branch is what has its own GSTIN — and the GSTIN is what decides the invoice. Since September the city ledger is a proper receivables ledger inside the books.

Asar PMS · invoices Every bill for the business date, with its CGST/SGST split and whether the customer's GSTIN is on it yet.

• Group over branches — legal name, PAN and credit pool at the group; city, GSTIN, billing address and contact at the branch. Both bookable, both billable.
• Contracted rates that inherit — attached at group level, overridden per branch, scoped to the properties they cover. A chain deal and a single-hotel deal are the same object.
• Credit limit as a pool with sub-limits — the block says which one tripped.
• Bill-to-company routing and billing instruction per branch — consolidated to HQ or separate, which drives the GSTIN that prints.
• A company says when it pays — settle at check-out, on invoice, or on statement, held on the account.
• Receivables — AR invoices, receipts allocated oldest-first or by hand, TDS the customer withheld recorded as receivable, reminders per hotel (off until switched on), write-off and provision with an approver.
• Statements and ageing — per branch and rolled up per group, so a group view shows which branch is dragging the overdue.
• Travel agent commission — calculated on the stay and carried into the agent's bill; merchant channels, which keep their commission, get none.
• Loaded at scale — 6,930 corporate accounts for one customer, imported from their spreadsheet in an afternoon.

Built in nine stages against a 970-line requirement list, all nine live. Not a status board with a mobile skin: the attendant's phone, the supervisor's inspections, the store, the rules, the people, the dashboard and the forecast, on the same rows the front desk reads.

Asar PMS · housekeeping dashboard The dashboard. Every tile is a number the module already keeps — nothing here is a second count. Refreshes every minute. Asar PMS · the floor map The floor as it is. Colours are the live board’s; a badge is an open request or a fault. Arrange lets the hotel drag each room where it really is. Asar PMS · the board on the phone The board. An attendant picks their name and PIN; every step at the door is written with it. Asar PMS · housekeeping people People. Absent or on leave frees the rooms at once; credits weight the work so a suite is not a standard room.

• The room's story — an append-only timeline per room: who set what, when, from which phone. Room status is a consequence of visits, not a field someone edits.
• The board on the phone — an attendant picks their name, enters a PIN, and every step is written with it. At the door: checklist, DND, refused, make-up, guest asks, voice note, photo, fault, found something, damage. Works over the property Wi-Fi with an offline queue of events.
• Which clean, decided by rule — fifteen service kinds; one rule engine with twenty-one conditions decides each room's service for the morning once; the guest's own opt-out (eco, no service) beats every rule.
• Inspections — a fifty-one-line built-in checklist the hotel versions, scored 0–5 per line with critical lines; a fail sends the room back to dirty and a re-clean to the same attendant. Audit draws by percentage.
• The store — chemicals, consumables, linen, minibar, each with par levels; issues and returns; soiled linen as a transfer; minibar posts straight to the folio; guest laundry dockets priced from a list.
• People — shifts, zones, skills, trainings, weekly off, attendance. Absent or on leave frees the rooms at once. Credits weight the work (a suite is not a standard); auto-assign goes own floor first, then lightest load; a room being cleaned does not move.
• The queue — rush from the front office, a guest waiting in the lobby, expected-ready times recalculated on every read.
• Guest requests and preferences — fourteen request kinds with their effects (clean now rushes; clean later flags make-up until the hour); sixteen preference keys applied at check-in by trigger.
• SLAs, escalation and handover — one chain supervisor → executive → manager, each thing escalated once; the shift handover snapshot signed by another supervisor.
• Dashboard, floor map, analytics — fifty-four live tiles, a floor map the hotel arranges, sixty-three daily KPIs rolled up idempotently, cost per room at ₹ per credit, budget against actual, and the group compared hotel by hotel with anomalies against the median of the others.
• Forecast — manpower from the bookings already on the chart, and demand ahead.
• Reports by email on a schedule, and sixteen webhook events with HMAC signatures for anything the hotel wants to listen.

The engineering department the housekeeping build brought with it. A fault raised from the room on the phone reaches an engineer with a clock on it.

Asar PMS · housekeeping desk The desk. Raise a fault from here or from the room on the phone; the clock is the hotel’s SLA per severity.

• Faults — category, severity, SLA hours per severity; open → assigned → in progress → fixed → housekeeping re-check → closed. A re-check by a supervisor is what lifts the hold on the room.
• Room hold — a fault can take the room out of sale, and the chart shows it as such.
• Preventive maintenance — recurring rounds generated when the day opens, spread across the period.
• Public areas — areas with QR tokens on the wall; a sweep marks what was missed.
• Lost and found — chain of custody; disposal needs a manager and waits the hold period for valuables.
• Damage — reported with a photo, verified, approved, and charged to the folio.
• Turnaround — hours to fix, hours to close, late, re-check failed and cost, per category, over the last thirty days.

Built in, not bolted on. The restaurant, the bar and room service run on the same database as the rooms — and a restaurant with no rooms at all is a valid account.

Asar POS · billing Tables, the menu and the open order on one screen. Settle at the counter, or send it to the room. Asar POS · restaurant setup The outlet, its GST groups and HSN codes, and which kitchen station each dish’s KOT prints at.

• Tables, menu and the open order on one screen — punch, fire a KOT, settle at the counter, or charge to a room with the guest's name checked against it.
• KOTs the kitchen can hold — sized for a print rail, routed per station (kitchen, bar, bakery), modify and cancel with a reason and a reprint.
• Menu the restaurant keeps itself — categories, dishes, variations and add-ons, per-channel prices, GST groups and HSN codes, which station each dish prints at. Changing a price is not a support ticket.
• Settlement — cash, card, UPI, room, company account, staff and non-chargeable with a reason.
• Cashier shifts and the outlet day-end — each outlet closes its own business date; it refuses while an order is unsettled or a till is open, and refuses to close a day that has not happened.
• Bill print with its own numbering series and tax split — restaurant GST is a different rule from room GST and is handled as one.
• The kitchen's stock — ingredients, recipes and movements valued as they are written (landed cost on receipt; moving average, standard or FIFO on issue), counts as a document approved by a second login, theoretical against actual food cost, wastage with a reason.
• Goods received against vendor bills — three-way matched in Payables (below).
• Stands alone — a POS-only account never sees a booking chart and is priced as a restaurant.

The day has to move, and it has to move by itself. One transaction: post every room and its tax, price every no-show, roll the date, lock the day. Each hotel chooses whether the day closes by itself and at what hour — midnight, or 3 am for a hotel with early arrivals — in its own timezone. If the day is overdue, the desk is stopped at check-in and offered to close it there and then.

Asar PMS · night audit The night audit. Everything that will happen when the day closes, priced, before it closes.

• Everything priced before it commits — the arrivals nobody checked in, the departures still in, the open folios, each with what the audit will do to it.
• It refuses rather than guesses — where the audit would decide something a person should, the hotel is held and reported, not audited. It refuses a day that has not ended yet.
• Idempotent — running it twice cannot post the night twice. Tested, not assumed.
• Reversible — the last audit can be undone by an administrator and re-run, with the postings reversed rather than deleted.
• Automatic per hotel, or manual — a switch per property; off means the timer leaves that hotel alone and says so after two days.
• The GST slab follows the tariff, night by night — a mid-stay rate change produces the right tax for each night without anyone intervening.
• A watchdog that keeps speaking — nine hotel-shaped checks every five minutes: the business date moved, the rate sheet still reaches thirty days out, the mail queue is draining, a backup landed. A failure re-alerts daily instead of firing once and going quiet.
• Three reports by mail — the audit report, the day's no-shows and the day book go to the hotel's address when the timer closes the day.
• Finance audits the day before it is believed — the books equal the folios, no room went uncharged, no comp unapproved, no bill left open; the controller signs the day off.

One desk that can see what every hotel in the group can sell — including the ones it cannot, and why. Full on the 14th? The sister property four kilometres away has four rooms at eight hundred less.

Asar CRS · reservations One desk over every hotel: search by guest, company, agent or reference, and book into any of them.

• Group availability, priced, in one search — every hotel, every room type, every rate plan, through the same quote the booking engine and the front office use. If one of them refuses a date, they all refuse it, for the same stated reason.
• Book into any hotel from one screen — the booking lands on that hotel's chart, in its own numbering, under its own business date.
• The board — the group forward, hotel by hotel, day by day, summed not averaged.
• Every booking in the group on one list — search by guest, company, agent or reference; filter by status, source or hotel. The call takes no property argument and is not privileged: row-level security decides the scope, so the same screen is right for a chain owner and for a duty manager at one hotel.
• Each hotel's own business date on the strip — a stopped day at one property is visible from the group screen.
• One party, several room types — a line per room type and plan with its own dates and occupancy; one group, one booking per room; a room type is one stock however it is sold.
• Who took it and who sold it — the login that typed a booking is frozen on it; the credit goes to the company's salesperson or whoever typed it; incentive plans and payouts on what was realised.
• Where the business came from — every booking in a window in one row under its person, OTA, agent, company or source, with a subtotal per group.
• A payment is trusted first, verified after — money recorded on a booking is paid at once; the accountant confirms or rejects it on the Approvals screen, and a rejection voids only the payment.

Everybody the group has ever taken a booking for, with what they have actually spent beside the name — before the phone is picked up. It holds no second copy of a person: a guest, a company branch or an agent in the CRM is the same row the folio is billed to.

Asar CRM · people Everybody the group has ever taken a booking for, with what they have actually spent beside the name.

• People — stays, room nights, ADR, value and what is still owed, backfilled from every booking already there. Nobody imports anything.
• Companies and agents — the corporate the sales desk is chasing is the corporate the GST invoice is raised against. Opening one does not create a second.
• Enquiries on a board — pipelines with stages and stage tasks, weighted by stage, with follow-up dates.
• One timeline — stays, complaints, messages, calls, notes.
• Segments and outreach — with do-not-email absolute: the refusal is the feature.
• Switched on per account — a hotel that does not want a CRM does not see one.

We connect to a channel manager rather than becoming one. Rates, inventory and restrictions go out to AxisRooms, bookings come back in, and AxisRooms carries MakeMyTrip, Booking.com, Agoda, Goibibo and the rest. Sixteen of their nineteen endpoints are built; the connection is live for our own hotels.

Asar PMS · channel manager What is mapped, what is queued, and every call the channel has made — taken or refused. Partner IP addresses are masked here.

• Rates, inventory and restrictions pushed — a price change at the desk reaches the channels; pushes are folded to one per kind per window so the queue never storms.
• Bookings applied in the same request — a pushed booking is on the chart before the channel gets its 200, with a room assigned where one is free and a no-room card where none is.
• Modifications and cancellations pulled; a no-show is told back to the channel.
• Stated tax of zero means the price is inclusive — the card adds nothing on top of an OTA's inclusive price.
• Every knock at the door recorded whole — inbound calls stored complete before they are interpreted, with request and response bodies on the sync log, so a payload that fails to parse can still be read later.
• Channel mapping as a master — room type and rate plan against the channel's ids; adding a channel is their mapping, not our project.
• Credentials in an encrypted vault — the database holds ciphertext and never the key; every read is logged with an actor and a reason.
• A queue that says when it is not moving — what is mapped, what is queued, what failed and why, on one screen; a sync report per hotel.
• The CM Log in four tabs — reservations, inventory, rates and cancellations, both directions: a stay cancelled at the desk and still live at the OTA is shown as not yet told.

Said plainly: live. Bookings from Booking.com, MakeMyTrip, Goibibo, Agoda, Expedia and Cleartrip have arrived through it since 8 September — 371 of them by 1 October, each on the chart in the same request. Hotels we moved from eZee are linked one at a time, after go-live. If you already run AxisRooms, that stays exactly as it is and we plug into it. If you run something else, tell us at the demo — it is built against one channel manager first and we would rather say so.

The hotel's own booking page, on the hotel's own domain, on the hotel's own rates, with no commission on it — and a payment link a guest can settle from before they arrive.

The hotel’s own booking page The hotel’s own page, on the hotel’s own rates, with no commission on it.

• Search, offers and booking against live availability, through the same quote the desk uses.
• Razorpay and PhonePe — the hotel's own gateway account, credentials encrypted, callback signatures verified. A new provider is an insert, not a release.
• The guest payment page — a held booking sends a link showing the stay and the amount; it takes the deposit or the full balance, receipts it to the folio, and confirms the hold. A dead link says so rather than showing a login screen.
• Confirmation reaches the guest without anyone remembering to send it.
• Google free booking links and Hotel Ads pointing at the hotel's own engine roadmap

118 in the catalogue, every one computed against the same figures the folio uses, so a report and an invoice cannot disagree. The ones that cannot be produced from live data say so instead of returning an empty page.

Asar PMS · reports 118 reports in the catalogue. The manager flash, run.

• Front office — manager flash, arrivals and departures, in-house, police report, Form C register, night audit report, room discrepancy, no-show and cancellation, expected occupancy.
• Revenue — daily and monthly production, by segment, source, rate plan and room type; ADR and RevPAR trend; OTA production and commission; corporate production branch-wise with the group rollup.
• Finance — sales register, tax summary, receipt register, city ledger ageing, agent commission, void and discount audit, cashier summary — and the accounting programme's own reports on its pages.
• POS — item and category sales, KOT versus bill, NC report, outlet day summary, shift variance.
• Housekeeping — productivity, room status history, cost per room, sixty-three daily KPIs, the group compared.
• Each behind its own capability — a report is not a back door into data a role cannot otherwise see.
• By email, on a schedule — any report in the catalogue to anyone, daily, on weekdays or monthly, at an hour in the hotel's own time, for yesterday, the week, the month to date or last month; CSV attached.
• Custom report builder — pick columns, filter, save, schedule roadmap