Excel or a hotel program? When a small property outgrows the spreadsheet

A spreadsheet is a good ledger and a poor booking system. Move to a hotel program, a property management system (PMS) that holds rooms, guests, bills and compliance in one place, when a second sales channel, shared logins, guest identity data or an editable bill appear. Before then, keep the spreadsheet and keep it clean.

The file is called rezervasyon2026final_v3.xlsx and it is open on two screens at once. Nothing has gone wrong yet, which is exactly why the owner keeps it. This article is about the moment that changes: how to tell, from five concrete signals, when the spreadsheet has stopped being a tool and started being the risk. You will also learn what free software really costs, and how to clean the file so the eventual move is short.

What does a spreadsheet do well for a small hotel?#

It is cheap, immediate and completely under the owner's control, and for a property with one source of bookings that is often enough. A pension with a dozen rooms can start the same afternoon: no subscription, no installation, no training. The file can be mailed to an accountant, opened offline, printed and pinned behind reception.

The spreadsheet also mirrors the owner's own logic. The columns the owner chose, a formula for agency commission, a tab per month, a colour for paid. Change is instant: adding a column takes a second, while a hotel program asks you to open a settings screen or call a vendor. For a single owner who answers every booking personally, that flexibility is a real advantage, not a compromise.

The limit is structural, and it is worth naming precisely. A spreadsheet stores values and enforces nothing. It has no idea what a room is, so it cannot refuse a booking, hold a room for ten minutes or notice that two rows claim the same night. It is a ledger, and a ledger can only record.

The decision rule follows: keep the spreadsheet while one person owns the file and one channel feeds it. The problem is that both conditions fail quietly. Nobody announces the second typist; the second channel arrives as a phone call from an agency one afternoon.

When does a second sales channel make a spreadsheet dangerous?#

The moment a room can be sold somewhere the file cannot see, the file stops being a record and becomes a guess. This is the first signal in the hotel spreadsheet vs PMS question, and it usually arrives before the owner is looking for it.

Consider the mechanism. A phone call and an online travel agency booking arrive four minutes apart. Each person opens the file, both see the room free, both write a row. A spreadsheet has no hold: a hotel program can hold a room for a few minutes while a quote is confirmed and release it if nothing happens, but a cell cannot hold anything. When both people save, last write wins. The second save overwrites or duplicates the first row silently, and nothing in the file flags the conflict.

Shared cloud files reduce the risk but do not remove it. Two people can still read the same state before either one saves; the file only warns after the collision has already happened. Channel managers and booking engines need something stricter: a machine-readable inventory with a rule for what is available. A spreadsheet is a picture of availability, not a source of it.

The test is simple. Ask how you would know if two people sold the same room in the same minute. If the answer is that you would find out at check-in, standing in front of a tired guest, that is your signal. For a fuller treatment of the failure modes, see our guide to hotel double bookings across channels: causes and prevention.

Where does guest identity data end up in a spreadsheet?#

Usually in a second file, a photo on a phone or a message thread, outside any rule about who may see it or how long it is kept. Start from the duty, in general terms: in Türkiye, every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK).

In practice, the data scatters. Passport photos in a messaging thread, an ID scan folder on the reception computer, a copy on a staff member's personal phone, a tab nobody remembers creating. None of this is dramatic on any single day. The problem appears when someone asks a question about it a year later.

What a hotel program does that a file cannot is control and evidence: one record per guest, access tied to a named user, a record of who opened what, and retention periods built into the data model rather than remembered by a person. The problem is not the tool itself. A spreadsheet can hold personal data; it cannot show who copied it, why it was kept or when it was deleted.

Describe your own duty with an adviser: which data you must notify, how long you may keep it, how you answer a guest request. Dates, penalties and thresholds change and depend on your case. A simple check you can run today: list every place a guest's identity document exists in your operation. If the list is longer than you expected, that is the signal. Our article on KVKK for hotels: notices, consent, staff access and retention goes into the detail.

Can a bill be changed after the fact in a spreadsheet?#

Yes, silently, and that is the difference that matters: a hotel program voids and reverses, a spreadsheet overwrites. Correcting a minibar charge by typing over the old number destroys the evidence of the correction. The guest's copy and the hotel's copy then disagree, with no way to tell which one changed.

Accounting practice is the opposite of this. Corrections are voided and reversed, so the original line stays visible, and a night audit closes the business day so yesterday cannot move. This is not a software fashion; it is how financial records have been corrected for a century, and it is the standard an auditor or tax office will expect.

Keep two things apart. The fiscal document, an invoice or e-document issued through a licensed integrator, is one thing. The guest bill, the running record of charges during the stay, is another. The bill must survive edits, because disputes arrive after checkout, not before. Without a user and a timestamp on every row, a dispute becomes memory against memory, and the person with the loudest voice usually wins.

The check: pick a charge from last month and try to reconstruct who entered it, when, and whether it was corrected. If you cannot, that is the signal. The mechanics of doing this properly are covered in how to void a folio charge without breaking the audit trail.

What do several people typing and a slow month-end tell you?#

That the file has become a shared workspace without rules, and that you rebuild the same report every month instead of reading it. Concurrency leaves copies: reservationsmart, reservationsmartfinal, reservationsmart_final2. Nobody knows which one is current, so people merge by hand, and the merge itself becomes a job.

There are no roles. The person who cleans rooms can also change a rate, and nothing distinguishes reading from writing. Month-end is rebuilt from several tabs: commission reconciled by hand, differences explained verbally, totals that do not match the bank. The real cost is not the hours. It is the decisions taken on numbers nobody fully trusts, such as a rate change made on a total that was two days old.

If closing a month takes more than a day, or needs one specific person who knows the file, the file has become the constraint.

What does a free hotel program cost?#

Free usually means paid in something other than money, in limits, exports, support or your own data, and the price appears after you have moved. Free tiers often cap rooms, users or bookings, and the cap arrives in high season, which is the worst week to discover it.

Export is the question that decides everything. Can you take every booking, guest and invoice line out in a readable file, without asking permission and without a fee? Support is the second: who answers at 23:00 in July, in which language, and is that included in the free tier or in a paid one? Then ask where the data sits and who can see it: hosting location, backups, and whether your staff accounts are named or shared.

Ask also what you give in return. Advertising in the guest's view, use of your data in aggregate, a commission on bookings taken through the tool, or terms that make leaving expensive. The comparison is never free against paid. It is the total cost of leaving against the total cost of staying, and leaving is the number nobody quotes.

How do you prepare the spreadsheet so the move is clean?#

Treat the file as data to be migrated, not as a document to be copied: one row per booking, stable identifiers and codes that mean exactly one thing. The work of moving is in the cleaning, not in the import, and every vendor will ask you for the same export.

One row per booking, not per room-night. A five-night stay is one row with an arrival date, a departure date and a room type. Dates as real dates, one currency column with a currency code, amounts as numbers with no letters typed in. Text that looks like a number is the most common reason an import fails.

Stable identifiers matter more than people expect. A booking number that never changes, and a guest record keyed to a document type and number rather than to a spelling of a name, because names get spelled three ways by three channels. Codes need one meaning each: room type, rate plan, channel, source. Write the list down before you clean, because the new system will ask for exactly that list.

Remove what a program will not take: merged cells, totals inside data rows, colour used as a status, notes typed into a comment. Keep past years as a read-only archive and migrate the current year plus open future bookings. Then check a sample by hand against the old file. The fuller checklist is in our guide to PMS data migration: what to move, check and leave behind.

What to do next#

Write down the five signals and mark the one that has already happened at your property; that is your trigger, not a feeling about technology. Then clean the file as if you were handing it to a stranger, because you soon will be, and compare programs on export, limits and support before you compare screens. To turn that comparison into a structured document, use a requirements document for hotel software: a template that makes vendor offers comparable. What a small property actually needs from software is a separate question, covered in our guide to software for a pension or small hotel.