Help

The manual, in full, without signing in.

Every screen, every field, and every sentence Asar PMS can refuse with — 262 pages, written for the person at the desk rather than for a reviewer. If the system has just told you it cannot do something, paste that sentence in here.

Signed in? Press ? on any screen for the help for that screen.

Getting started

Signing in, finding your way around, and the one date everything hangs off

Bookings and the calendar

Making a booking, changing it, holding a room, cancelling

Reading the calendarRooms down the side, dates across the top, and four things worth knowing about the colours. Blocking a room from the chartRight-click a room, say why, from which night to which, and who is blocking it. The channel is told; the chart draws it; a booking into it is refused. Making a bookingNew booking, or click an empty square on the chart. What each field is for. A booking the desk may hold and a manager confirmsAn OTA booking, or one billed to a company or an agent, is held by the desk for 30 minutes — or confirmed there and then with a manager's own login. Bookings that have no room yetEvery live booking with no room number, from any source, is drawn on the chart and listed beside it — and dragged onto a room. Taking a group at your own deskA party needing rooms of more than one kind — a wedding, an offsite, a tour — is taken from the calendar as ONE group: a line per room type, one contact, one code over all of it. Who is paying for a bookingOn a booking typed by hand, the payer — guest, company, travel agent or OTA — can be corrected. The bill moves with it. Where the price comes fromThe rate plan sets the price. Who may change it is a separate question with a deliberate answer. Changing the rate on a bookingAnybody at the desk may name the rate until the guest checks out; after that only an administrator, and it is a tax note. An OTA rate is never changed here. Changing a bookingDates, room, guest and rate can all be amended. Some changes are refused, and some can be overridden. Cancelling, and no-showsBoth need a reason from the list, and both leave the record standing. Holding a room, and the guest pay linkA time-boxed hold with a link the guest can pay on. It releases itself if they do not. Putting a stay in another guest's nameOnly an administrator. Any status, before or after check-out. The booking and its bills carry the new guest; the invoice number, the charges and the tax do not move. A room with more people than it sleepsMoving a party of four into a room that sleeps three is allowed: the picker warns, asks once, does it, and records who said yes. Day use: a room sold for the day, not the nightA guest who arrives in the morning and leaves in the evening and never sleeps in the room. It reserves nothing, holds no room until the desk hands over a key, and the same room can serve two day guests and still take its overnight guest. Booking the same stay againBook again copies a stay for a returning guest, and tells you what the price would be now. Group bookingsMany rooms under one name, created together and cancellable together. Moving a guest to another roomDrag the bar on the chart, or use Move room. It asks for a reason and refuses for good ones. UpgradesMove a guest up a grade, priced or complimentary, with the reason recorded. Messaging a guestTemplates render the message; a person sends it. Nothing goes out on its own.

The front desk

Check-in, the folio, taking money, check-out

Arrivals, in house, departuresThe day lists under Reports → Front office operations, and what the Rate and Payment mode columns mean. Checking a guest inRoom, identity, and the folio opens. What stops a check-in and what to do about it. Aadhaar, PAN, passport and Form CWhat identity the law wants, what the system checks, and where Form C is filed. Form C for foreign guestsRecording a passport and visa, raising the form, reading out what the portal asks for, and the register. The folioOne guest, one stay, every charge and payment on it — and what its balance means. Settling the bill at check-outA balance at the door opens one window: collect, discount and waive, adding up to what is owed — then Settle and check out. Sending money backHow a refund is recorded, who may authorise one, and the four things that will stop you. Posting a chargePost a charge on the folio, choose what it is for, and it lands with your name on it. No-shows: marked by the desk, decided by the managerMarking a no-show charges nothing and tells no OTA. Every one goes on a queue where a manager, the revenue manager or an administrator decides twice — retention, and whether the channel is told — with their name on it. Early check-in and late check-out chargesWhat the hotel charges for a guest who arrives before check-in time or leaves after check-out time, who decides, and who can waive it. The guest who paid the OTABalance from the OTA is the stay; balance from the guest is zero. Collect nothing at the desk, and the invoice is still in the guest's name. A payment is trusted first, and verified afterA deposit recorded against a booking is paid from that moment. It also goes to the accountant, who confirms the money arrived or rejects it with a reason — and only then does it come off the bill. A date change inside the cancellation window is a question, and the policy's charge goes on the bill. A booking cancelled by mistake is put backA cancelled or no-show booking is found with Find and put back with one press and a reason. Before the night audit anybody at the desk can; once the audit has closed a night of the stay, the administrator can. The nights the audit passed over go on the bill. Taking a paymentTake a payment on the folio: method, amount, reference. It is the reference that saves you later. Splitting a payment across methodsOne settlement, several methods, checked against the folio as one movement. The registration card (GRC)Print it from the booking card. It carries the guest details, the stay, and the declaration they sign. Reprinting a registration cardReprints are allowed and counted. The second onwards is stamped COPY. Advances and depositsMoney taken before the charges exist, held against the stay and applied when they do. Correcting an invoice that has already been issuedDo not reopen the bill. Issue a credit note if the value falls, a debit note if it rises. The deadline for reclaiming tax on a credit noteTax may be adjusted until 30 November after the invoice financial year. After that, the money is credited and the tax is not. Voiding a posting, writing off a balanceNothing is deleted. A mistake is reversed with a reason, and both lines stay visible. Giving a discount on the billThe folio's fourth tab: a percentage or an amount off the whole bill, the room, the food, or one line — with the GST reduced to match, a reason, and a name on it. The GST number says who the company isType a guest's GSTIN on the card: the company is looked up, added to the CRM if it is new (pay at checkout, no credit), and the bill is made out to it. Checking out, and the tax invoiceSettle the folio, print the invoice, and the room goes dirty for housekeeping. Dummy rooms, and a guest walked to another hotelA dummy room parks a booking the hotel cannot house. Only an administrator puts one there, it is never stock, and a walk records where the guest went and what it cost. A guest who arrives in the night: here for last night?Arriving after midnight but before the hotel's day starts, on a booking for today — the desk is asked whether the guest is here for last night. Checking a company's GST registration before the invoiceThe panel on the Invoices tab lists the companies on your bills and bookings, and says when each GSTIN was last checked. Search for one that is not there yet. Corrections: putting a booking rightOne screen that finds a booking and lists every correction there is — including the ones that do not apply to it, and why. Each needs a reason and is logged. Splitting a stay across several invoicesRoom, food and spa on one bill or three — the guest decides, and you tick the lines. Waiving a small balance at check-outA guest owes ₹150 and has their bags in hand. The desk may forgive it up to the hotel's limit, with a reason and their name on it — the money is not taken out of the till. A guest who paid for more nights than they stayedAt check-out the bill may hold more than it owes. You are asked: keep it, or send it back — and the guest leaves either way. Proforma invoice — a bill before the stayWhat a company needs to raise a purchase order. Not a tax invoice, and it says so. The day book: opening, closing, expenses and the bankOne row per day of the month, cash opening to closing carried day to day, the bank receipts ticked when the bank shows them, and the till's expenses written where they happened. The OTA refunded a night to the guestA prepaid OTA guest left early and the OTA gave the unused night back. Take it off what the OTA owes — nothing goes back from the desk. Undo a mistake the desk made todayThe administrator takes back the last thing done to a booking — check-out, check-in, cancellation, a charge — as long as the night audit has not closed the day. The administrator corrects any booking — and the log is the priceAn account administrator may correct a booking that is audited, in house, departed or billed: its dates, room, guests, rate or status. Every correction is recorded with login, time, machine and reason. Reopening a settled billA bill closed at zero or in credit is reopened only by an account administrator; then a charge can be voided, money refunded, and the bill closed again — every step with a name on it. Billing a company: the city ledgerA folio routed to a company instead of collected, and the ageing that follows it. Money owed and open balancesThe list that stops a hotel losing money quietly, and the red dot that counts it.

The day and the night audit

What closing a day does, and what stops it closing

Housekeeping and guest service

Room status, the board, and requests

Room statuses, and who changes themVacant-clean, vacant-dirty, occupied, out of order — and what moves a room between them. The housekeeping boardToday, by room: what needs cleaning, who is doing it, and what disagrees with the desk. Guest requests and complaintsRaise it, assign it, resolve it — so a request is a record rather than a memory. Taking a room out of orderOut of order removes a room from availability for a period, with a reason. When housekeeping and the front desk disagreeThe discrepancy report lists rooms where the two views differ. Check those rooms first. Rooms out of order, and for how longGive an out-of-order room a date range. A room with no end date is out for ever. Analytics, the kept numbers, and the budgetSixty columns per hotel per day, kept by the night audit; trends; cost per room; budget against actual. A room's storyEverything that ever happened in a room, in order, with who and when; it cannot be edited. Damage and missing itemsReported with a photograph and a value, verified by a supervisor, approved by a manager, charged to the folio. Equipment and its service historyEvery AC, geyser, sofa and pump, in its room, with when it was last serviced and when it is next owed. Faults, and the recheckOne tap from the room raises the ticket; engineering fixes it; housekeeping rechecks before it closes. Guest requests, and Do Not DisturbTowels, water, a cot, "clean my room now" — each with a clock, an assignee and the guest told; DND with attempts and a threshold. Handover, help, and the day on paperThe going shift writes what is open and the coming one signs; help is asked for from the room; the sheet prints and the reports email themselves. Leakage, fraud, and the investigation queueSix questions asked of the hotel's own history every night; each opens an investigation a manager closes with a finding. Linen and laundryFresh to the room, soiled to the batch, the batch to the laundry and back with the count checked; and a guest's laundry as a docket that charges the folio. Lost and foundWhat was found, where it is kept, every attempt to reach the guest, and how it went back. Not done, and whyEvery round missed, room visit left undone and scheduled job past its date — whose it was, and the reason. People, shifts and the rosterWho is on the floor today, what each can do, and how the rooms are shared out. Photographs on the storyA before, an after, a failure, a damage or a maintenance photograph, taken on the phone, kept on the room's story with who and when. Preventive workAC servicing, filter cleaning, drain cleaning, mattress rotation, pest control — on a schedule the night audit runs, over rooms or machines. Public areasThe lobby, lifts and washrooms cleaned at set times or on a frequency, by a named owner, started and finished by scanning the code on the wall. Rules that act, the clocks, and the trayIF this moment THEN do that — with approval where the hotel wants it; every open thing has an SLA and a chain; notifications in one tray. SOPs and who has read themThe written standard, versioned, and the staff acknowledgement that goes with it. The checklistWhat a clean consists of, ticked on the phone; the room and bathroom lines, mandatory ones, versions, and when it blocks Done. The dashboard and the floor mapEvery number of the day on one screen, and the floor drawn as it is, coloured by state. The floor's screenOne card per room, one tap per step; the room attendant's whole day on a phone. The group, and the brand standardEvery hotel a row, ranked; a brand checklist pushed to hotels with lines they cannot remove. The guest remembered, and the eco stayPreferences on the guest come back next stay; an eco stay skips the clean or keeps the linen, and the savings are counted. The housekeeping storeConsumables, linen, chemicals and minibar stock on one ledger: receive, move to a pantry, issue to a room, count, and see the variance. The inspectionA supervisor scores the cleaned room line by line; a pass makes it ready, a fail makes the re-clean by itself. The minibarFilled from the store, sold to the guest on the folio by the person who saw the empty bottle, counted at check-out. The morning paragraph, the ETA, and the demandWhat the queue predicts for today, which arrivals are at risk, the move that helps — and what the store will need this week. The phone: offline, alerts, languages, voiceTaps are kept without a signal and sent when it returns; rush rooms reach the phone; the floor reads Hindi, Bengali or Nepali; a voice note becomes a ticket. Webhooks and messagesSixteen events posted to any URL with a signature and retry; five WhatsApp messages in the hotel's own words. What a clean costsConsumables, chemicals and linen washes added up per visit, per room, per type, per floor, per attendant. Which clean a room getsCheckout, stay-over full or light, turndown, deep clean — the kinds of visit, their targets, and the rules that decide. Which room comes firstA guest waiting, a VIP, an arrival, a rush from the desk — one number puts the room at the top. Who cleans wellRooms, minutes against target, inspection scores, fail rate, re-cleans, complaints — per attendant, for any period — and the lines each one keeps failing.

Halls and functions

Taking an enquiry, holding a hall, and the sheet the kitchen works from.

The restaurant

Shifts, orders, KOTs, bills and day end

Setting the restaurant up

Outlets, the menu, prices, GST and tables

Creating an outletAn outlet is one restaurant, bar or room service. It has its own menu, tables, tax and day. The menu: categories, dishes, sizes and pricesBuild the menu yourself. Changing a price is a price change, not a deployment. GST groups, and the restaurant rateTax comes from the group on the dish — and which group is right depends on the rooms. Tables and kitchen stationsTables are where an order sits. Stations are where a KOT prints. Taking a dish off tonight (86-ing)Mark an item unavailable and it disappears from ordering until you put it back. Different prices for dine-in, room service and deliveryOne dish can carry a price per channel, and a price that applies only at certain hours. The kitchen store: what is on the shelfEvery ingredient with what is on hand, what it is worth and what is running low; a movement or a count is one form; every item has its story. Units, places and ingredientsThe store measures in units that convert to a base; every ingredient is bought in one unit, kept in one place, and has a reorder level. Recipes: what a portion is made of and what it costsA recipe is per size of a dish, in grams, millilitres or pieces per portion, with wastage; it draws stock when the KOT fires and prices the dish against its menu price. Buying: suppliers, purchase orders and deliveriesA purchase order is a promise; the GRN is what moves stock. Short delivery leaves the order open; payables are by supplier. Food cost, variance, and what to orderWhat sold and what it cost in ingredients; the menu card at today's prices; what the recipes say should have left the store against what did; what is below reorder.

Human resources

Your people: who works where, their records and documents, and the copy from the old HR dashboard.

Setting a hotel up

The wizard, rooms, rates, your own lists, and going live

Opening a hotel: the whole thing in orderSix phases from the GST certificate to the first night audit, and what each one needs. Getting the hotel group signed upWhat Asar does, what the hotel does, and why nobody here chooses your password. After the wizard: making the hotel actually readyThe wizard makes a hotel that exists. This is what makes it one that can trade. Setting the restaurant up, in the order it has to be doneGST groups and stations before dishes, dishes before tables. Backwards means rebuilding the menu. The first real dayOne booking end to end before you rely on it, then the three daily habits. The month after openingFour things to read on a schedule, and the one that changes on its own. Adding a hotel: the five stepsOne wizard, five steps, and the hotel exists. Everything after it is adjustable. Room types and real room numbersThe type sets the price. The numbers are the rooms a guest is actually given. Room categories and room numbersAdding a category, putting rooms in it, moving a room, and taking one out of the inventory. Rates, plans and the cancellation policyA rate per type and date, and the rules that go with selling it. Adding and changing rate plansCreating a plan, what the meal codes mean, pricing one plan off another, and what stops you retiring one. Closing a date, minimum stay and stop sellThe five rules that decide whether a night may be sold, how to set them, and how to lift one. Rates run out — the check that is not about configurationA hotel that was ready in August stops being sellable in February. Load rates further ahead. Changing a room's numberA room keeps its bookings, bills and history when its number changes. A guest in the room does not stop it. Seasons — a date range that prices differentlySetting a peak or a lean period once instead of typing a hundred nights. Moving a room to another category, and what is waiting on youA room can change category even with bookings ahead of it. Each of those bookings waits for a manager: upgrade it free, upgrade and charge, or release the room. Going live: the readiness checksEleven or so checks per hotel, and what each one means it cannot do yet. The rate sheetEvery room type, every plan, every night, with the rooms still free above them. It opens on All plans. Counting a room as another category for a few daysWhen something about a room changes for a while — a balcony shut, a lift out, a view gone — the room can be counted as a different category for stated nights and go back to its own on the night after. The onboarding boardEvery hotel in the group at once, and what each is still missing. One number and the gaps — the derived rate sheetPrice the cheapest room once; every other room type and plan is a gap on top. Type what you want in hand and be shown the rate to push. Invoice numbers: where they start and how they countHotel details has a box for the next invoice number — type it the way your accountant writes it, 27ACP01, and every bill after counts up. The system's own bill number stays beside it as the internal record. Only an administrator; never rewound over a bill already issued. Lists and reasonsEighteen short lists your staff pick from, and why free text was worse. GST registrations — one per state, and every rule with a dateThe registration is the unit of filing: one GSTIN per state per legal entity, its kind, its dates, its e-invoice threshold; which hotel invoices under it; the HSN/SAC master with dated rates and the condition in words.

Running a group

Adding hotels, who works where, and what a group can see across all of them

Selling online

The channel manager, mapping your rooms to it, and bookings arriving from the OTAs

Guests, companies and enquiries

Every guest and every company the hotel has ever billed, the enquiries that are not bookings yet, and the follow-ups.

Team and access

Logins, roles, and who can see which hotel

Reports and compliance

Running a report, the ones an auditor asks for, and the books: receivables, payables, bank, tax, budget, payroll, the group, approvals and the close

Running a reportPick it, set the hotel and the dates, Run. Export CSV for anything that leaves the building. Which report answers which questionForty reports, grouped by the question somebody actually asked. The occupancy heatmapEvery hotel you may see, the month day by day: rooms, occupancy and ARR in each cell, coloured by occupancy, last year beneath, the month summed on the right. The log: everything that happened, on one pageOperations → Log is every kind of event for this hotel in one list — bookings, rooms, messages, mail, channel traffic, support access — newest first, seven days by default. GST, GSTR-1 and the tax invoiceWhat the system produces, and the two things it does not do. What an auditor will ask forThe six reports that get asked for every time, and what each proves. Approvals: what needs a second signatureOne machine for everything one person must not do alone: a rule says what needs approving, at how many levels, by whom, above what amount; the queue is where it is signed. How many rooms are leftThe night-by-night availability sheet: rooms, out of order, sold, on hold and what is left to sell, per room type and in total. Closing the month by a listA month is locked only when its checklist is done — every day audited, the sub-ledgers agreeing, the bank reconciled — and at the lock the trial balance is snapshotted and hashed. Reopening needs two signatures. The budget: the year planned by account, the month measured against itAn amount per account per month. The rooms lines are derived from occupancy and rate, the outlet from covers and check, the rest typed; then every month the ledger is measured against it and a rolling forecast says where the year is heading. The payroll: the month received, posted and paidThere is no HR module. The payroll engine's result — by department: gross, PF, ESI, PT, TDS, advances, net — is imported once a month and posted as one journal; then the net and each authority is paid, with a challan. The group adds up: consolidated statements and the owner's pageOne statement for a hotel, for a legal entity's hotels, or for the whole group — profit and loss, balance sheet, consolidated trial balance — and the owner's page: equity, the result, distributions, the FF&E reserve. What to run daily, weekly and monthlyA short habit that catches most problems while they are still small. A report sent by mail, on a scheduleAny report in the catalogue, to anyone, daily, on weekdays, or monthly on a day — at an hour in the hotel's own time, for yesterday, the last seven days, the month to date or last month. What the books noticed: anomaly alertsRules, not models, read the live books every day and raise an alert with its evidence — a near-duplicate bill, an odd manual journal, a cashier's voids, a vendor's price drift, a bad GSTIN, an uncharged room, an unmatched bank line. Nothing posts by itself. A rupee is not the only money: foreign invoices and revaluationAn overseas agent invoiced in dollars, an OTA that remits in dollars: the invoice keeps its rupee value, carries a foreign face at the rate it was quoted, and at month end the open balance is revalued — the gain or loss named in the books. One ledger, many dimensions: department, cost centre, geographyOne Electricity account for the whole group, with the hotel, the department, the cost centre and the city carried on every line — instead of one account per location. The books then read by any of them. The compliance calendar: what is due, and whenEvery statutory obligation the hotel actually has — from its own PAN, TAN, GST registrations, headcount and turnover — raised before it is due, prepared, approved, filed and evidenced. What the books already know is filled in from the books. A government notice, and what was done about itA notice from any authority — its number, section, amounts, the date the answer is due — with every response, hearing, extension and order dated under it, and a deadline that escalates like any other. A shared cost spread by a rule, and what one company owes anotherHead office pays the electricity for four hotels: a rule spreads it by occupied rooms, revenue, headcount or a fixed share, reads the driver from the books, and posts. What one company of the group owes another is then settled and eliminated. PF, ESIC, professional tax and the payroll returnsThe staff master the authorities need — UAN, ESIC IP, PAN, state, joining and leaving — and from a posted payroll month: the PF ECR file, the ESIC contribution file, professional tax and LWF checked against the state's own slabs, and the 24Q and Form 16 datasets. The company's own book, and the labour registersWhat the Registrar asks of a company — directors, shareholders, auditors, charges, related parties, the capital — kept as registers that raise their own filing when something changes; and the establishment's licences, minimum wages and statutory registers. Asking for a purchase, contract rates and what other hotels payThe front of the buying chain: a store asks, somebody approves, and only then is a purchase order raised — at the vendor's contracted rate. Beside it: the rate cards, the price variance, what the same item costs at every hotel, and the MSME clock. What the reports cannot do yetFixed reports, run and exported by hand. There is no report builder and no scheduling. When goods leave the hotel: delivery notes and e-way billsA hotel sells rooms and food and neither moves — but stock transferred between two stores, goods sent for repair, and equipment sold do. Each is a delivery note, and above the state's threshold it needs an e-way bill before it travels. The company's own tax: the estimate, the instalments and the demandsThe year's taxable income worked out from the books line by line — what is added back, what is deducted, the credits already suffered — then the four advance-tax instalments with their shortfall and interest, the challans posted, and any demand tracked to its end. The money ahead, who may see what, and every call in and outWhat is coming in and going out for the next weeks, from documents that already exist, with the first day the balance goes short; a masking policy that shows a number without showing whose it is; and one log of every outbound and inbound call with a queue for what failed. The hotels compared on what mattersEvery measure the owner asks about — occupancy, ADR, RevPAR, GOPPAR, payroll and food cost as a share, utilities per occupied room, distribution cost — for one hotel, a city, a company or the group, with each hotel against the group's median. Bank accounts, cash and chequesEach bank account and petty cash float has its own ledger; the till's cash is deposited to a named account; a company's cheque is deposited, clears, or bounces — and the books follow each step. Bank reconciliation — the statement and the books, line by lineImport the bank's statement, let the rules match it to the books, finish the rest by hand, and read the reconciliation statement: books, plus what the bank has not seen, less what the books have not seen, equals the bank. Banquet finance — an event is a ledger of its ownDeposits by milestone, the fee when a client lets go, the florist's bill and the food issued tagged to the function, the salesperson's cut — and the margin each event made. Cash position — what is in the bank, what leaves, what comes in, day by dayEvery bank account with the books' balance and the bank's, what neither side has seen, the sanctioned limit; every rupee owed or held, dated; the balance for the next thirty days; who may sign; funding a sister hotel. Collections — reminders, write-offs and the provisionPast-due bills are chased by mail on a schedule, each is assigned to somebody with a promise date, a debt is forgiven only with a second signature, and the books carry a provision for what may not come. Commission bills and the group's own feesA travel agent that invoices the hotel for commission gets its month's bill raised from the bookings it sent; the management fee or franchise royalty is raised from the month's revenue by a rule. Connectors — a batch leaves the books once, and says where it wentMap the chart to the other system's ledgers, build a batch of journals for a period with control totals and a hash, send it (Tally bridge, Zoho, QuickBooks, a file), read back what the other side said; issue keys for systems that post into the books, and read the rejection queue. Cost of sales — the stock ledger in the booksWhat the kitchen used is the cost of the day; what sits on the shelf is an asset. From the day you switch it on, the night audit reads the stores. CSV, QuickBooks, webhooks and the warehouse feedA batch as a CSV with the mapped codes; QuickBooks Online through the same batch machinery; signed webhooks for posted, recorded, approved and paid events; the nightly line-level CSV for a warehouse. E-invoices — the B2B invoice is registered with the IRP and carries its signed codeAbove ₹5 crore a B2B invoice is registered with the Invoice Registration Portal the moment it closes; the IRN, acknowledgement and signed QR come back and print on the invoice; cancel within 24 hours, else a credit note. Fixed assets — a thing the hotel owns is numbered, and wears outEvery asset is a row with a tag, a cost, a life under two books, an insurance date and a history; depreciation is a monthly run; a count says what could not be found. Gateway settlements — what Razorpay, PhonePe and the card machine paid, and what they keptImport (or pull) the gateway's settlement, match each line to the payment the desk took, post one journal per settlement: the bank gets the net, 5060 gets the fee with its input GST, and the card / UPI receivable comes down by the gross. GST returns — GSTR-1 and GSTR-3B from the books, frozen when prepared, amended by the differencePrepare GSTR-1 (the portal's JSON) and GSTR-3B (the tables) for a registration and a month from the documents, the bills and the channels' TCS; download; mark filed with the ARN; read what changed since as next month's amendments; check that the ledger's output tax agrees. OTA and aggregator statements — what the channel collected, what it kept, what it paidImport MakeMyTrip's, Booking.com's, Agoda's, Zomato's or Swiggy's payout statement; every line is matched to its booking's invoice (or the order's payment); posting settles the invoices through the receivable — commission, GST on it, TCS, TDS and the net — or, for an aggregator, writes one journal. Packages, free nights, gift cards — revenue the books read rightA CP rate is a room and a breakfast; the books split it, the bill does not. A free night is an expense with an approver's name on it. A gift card is money held, until it is spent or it expires. Paying vendors — the payment runVendors are paid in runs: one person proposes what is due, another approves, the money goes with its UTR, the books and the bills follow; advances, debit notes and failed payments have their own doors. Purchase matching — the credit is only what the supplier declaredImport the month's GSTR-2B from the portal; every line is matched to the bills by GSTIN and invoice number; mismatches are named in words; accept, reject or keep pending each line (IMS) and export the actions; write to the supplier from the row. Receivables — who owes what, bill by billEvery bill moved to a company or an agent is an invoice with a due date; record what they paid against it, with the TDS they deducted; the ageing reads by due date. Tally — the day lands once, and Tally's GSTR-1 equals oursJournals go as Journal vouchers by the mapped ledger names; documents go as Sales / Credit Note / Receipt / Purchase / Payment vouchers with the party's GSTIN and the tax ledgers by rate; every voucher carries our id so a re-send alters instead of duplicating; the Tally Bridge on the accountant's PC moves the batches and reads Tally's ledger list back. TDS returns — the deduction is returned on 26Q, the credit is claimed against 26ASForm 26Q for the quarter in the RPU's text from what was deducted and deposited; the 16A certificates customers send, matched to the receipts; Form 26AS imported and reconciled on both sides; the channels' TCS against GSTR-2X. TDS — the deduction is a dated rule, and the threshold is per yearThe rates and thresholds are rows with effective dates; the year's aggregate is what the threshold is tested against; every deduction, challan and the 26Q rows are reports. The accounting API — the routes the pages use, for anyone who signs inEvery screen of the ledger, receivables, payables, bank, tax and connectors is a versioned REST route under /api with a capability; the same routes serve an integration that holds a session or an integration key. The booksEvery closed day is posted, two-sided, into a ledger you can read as a journal, a trial balance, a P&L and a balance sheet — and hand to Tally. The revenue reportThe money of a period, one row per bill, narrowed every way the owner asks. Vendor bills — matched before they are owedA vendor's bill is captured for the hotel, a goods bill is matched against the GRN and the PO, and approval is the moment it is owed: TDS held back, one journal posted. Vendors — who the group buys from, and the two-person rule on their bank accountA vendor belongs to the group, says who it is for GST and TDS, and its bank account is changed only by a proposal that a second login approves. Zoho Books — the books are mirrored, each day onceStore the Zoho organisation and its OAuth refresh token under the vault key; pull Zoho's chart into the mapping; send journals, invoices, customer payments (with the TDS withheld), credit notes and bills as batches; Zoho's answers and ids come back to the batch.

When the system refuses

Every sentence it can refuse with, why, and what to do about it

It refused. Start here.How to read a refusal, and the three kinds this system gives. That room is already occupied for those datesSomebody else is in it for at least one night of the range. There is no override. The folio carries an outstanding balanceMoney is owed at check-out. The settle window is where it is collected, discounted, waived or left on account. This guest is already booked here for these datesA live booking for the same name or phone overlaps these nights. Find it — it is usually the channel booking you could not see. An administrator may book anyway. The room is vacant-dirtyHousekeeping has not released it. A manager may override, and housekeeping is told. Cannot amend: minimum stay, maximum stay, closed, stop sellThe dates you asked for hit a restriction on the rate plan. A manager may override. Cannot move, and the administrator overrideRoom moves refuse for four reasons. Two can be overridden and two cannot. That room is blocked for those nightsSomebody blocked the room from the chart. The refusal says the dates, the purpose and who. Open the block or pick another room. The rate comes from somewhere you cannot type overA contract or a channel set this price. That is the system protecting an agreement. A reason is requiredCancellations, voids, comps, overrides and moves all need one, and it comes from a list. Day end will not close the dayEither the day has not happened yet, or a shift is still open. That module is not part of this subscriptionThe hotel group does not hold that module. Only Asar can switch one on. That link is not liveOne sentence for three cases: unknown, already used, and lapsed. Wrong hotel code, username or passwordOne sentence for all three, and the one people actually get wrong is the hotel code. The guest owes more than the desk may waive"The guest owes ₹1,240, which is more than the ₹500 this hotel lets the desk waive at check-out." Collect it, discount it, or a manager waives it. The Aadhaar or PAN is not validA format check at the desk, not a lookup against any government service. It needs a company or an agent firstA booking billed to somebody else needs that somebody on file. The dish, category or outlet will not saveEvery one of these is a field the form needs and does not have. The night audit has not been run, so the hotel is still on that date"… would be checked in on a day that is already over. Close the day first." Close the day, then check in. Late check-out charge due — post it or waive it, then check out"Late check-out charge due: left at 14:30, 3½ hours after check-out time 11:00 (50 per cent of 4,200). Post the charge to the folio, or have a manager waive it, then check out." A discount of 15 per cent needs a manager"A discount of 15 per cent needs a manager; this hotel lets the desk give 10 per cent without one." Pick a manager under Approved by, or stay within the limit. The close checklist is not finished"The close checklist is not finished — every day audited (pending)." A month locks only when its mandatory tasks are done; it reopens only with an approved request once the account has the rule. The person who asked for this cannot sign it"The person who asked for this cannot sign it." · "You have already signed this." · "This needs a manager or higher to sign." An approval needs a different person, once, of the right role.