Time, weekends, currency and holidays

Your property's day

MAYA counts days on your property's calendar. "Today" is the date at your property, in its time zone, at the moment MAYA checks. The docs call that a hotel day.

Everything that counts nights starts from it:

• Tonight is night 0 of the booking window, and tomorrow night is night 1. Booking window
• The 396-night window your rules price is tonight and the next 395 nights. Every night in it is priced again once a day, in the first cycles after midnight at your property. How rules work together
• A typed price can be set from tonight onwards, never on a night that has passed. Setting a price yourself
• Past day, past week and past month in booking speed are counted in hotel days. See how they are counted.
• Waits and pickup lookbacks are counted in hotel days too. See how.

Which time zone

MAYA reads your property's time zone when you connect.

If your system gave none, or it could not be read when you connected, MAYA uses universal time (UTC) until we set yours, or on Cloudbeds until the daily read finds it. The PMS tab shows the time zone MAYA has, under Time zone and currency, and says so in plain words when it is UTC. It cannot be changed from the app. Email us to change it.

It matters for sending. If your system and MAYA disagree about when tonight ends, your system can refuse tonight's price in the hours between the two midnights. When your property system does not accept a price has the signs to look for.

Whose clock you see

• Pricing always uses your property's date, and so does the day detail's "revenue on the books", which reads "revenue" from your property's midnight.
• Times on screen use your own browser's clock: the time of each run in the Change Log (with its zone, such as PDT), the "Updated" time on the calendar, and Last sync on the PMS tab. Two people in different places see different clock times for the same run.
• The month the calendar opens on follows universal time (UTC). At a property in the Americas it moves to the next month in the evening of a month's last day. The calendar

Past day, past week and past month

These are the choices under Measured over in a booking speed rule. They count booking dates. A rule that raises counts today so far; a rule that cuts counts whole days only, ending yesterday:

So Past day is not the last 24 hours. For a rule that raises, shortly after midnight at your property it has almost nothing in it yet, and it fills up through the day. Booking speed

Booking dates. A booking counts on the date it was made:

If a booking's date looks a day off from what your system shows, email us with the booking and we check it.

Waits and pickup lookbacks: whole days

Both are counted in whole hotel days:

• A rule's wait. After a booking speed or pickup rule changes a night, it leaves that night alone for its wait: 1 day to 2 weeks, or a pickup rule's lookback window, set in Then waits (advanced). A pickup rule waits its lookback window unless you choose another, and a 14- or 30-day lookback starts on 1 week. A wait of 2 days from a change made at any time on Monday is over as Wednesday begins at your property. After a rule acts
• A pickup lookback. A rule set to Greater than counts today so far and the days before it: 3 days is today, yesterday and the day before. A rule set to Less than counts the 3 full days up to yesterday. Pickup count

Daylight saving

Hotel days follow your property's local calendar, so the change to or from daylight saving time moves no night: tonight is still tonight. Waits and pickup lookbacks count hotel days too, so they still end at midnight at your property. The day of the change is 23 or 25 hours long, and nothing else moves.

Weekends

Weekends are Friday and Saturday nights, and Sunday night counts as a weeknight. MAYA uses that when it picks similar past nights, reads momentum and reads the weekly shape of your seasons: away from holidays, a weekend night is never compared with a weeknight. Weekends

Rules you build have no weekday or date setting, so they run every night. The exceptions: a starter rule copied from your own weekend or weekday moves runs only on those days, and a rule imported from PIE with dates covers only those nights; the "?" in the rules list shows which. For a weekend price, type it on those nights. What rules cannot do yet

Holidays

MAYA uses 17 US holidays: New Year's Day, Martin Luther King Jr. Day, Valentine's Day, Presidents' Day, St. Patrick's Day, Easter, Mother's Day, Memorial Day, Father's Day, Juneteenth, Independence Day, Labor Day, Indigenous Peoples' Day, Halloween, Veterans Day, Thanksgiving and Christmas. Each has a stretch of days around it.

A holiday never changes a price by itself, and there is no holiday rule. It changes which past nights a night is compared with: the Saturday after Thanksgiving is compared with the Saturday after Thanksgiving in earlier years, not with the same date. Booking speed and booked so far vs usual both compare that way. A holiday night is compared with the same holiday in each of the last three years, and booked so far vs usual needs all three, so with less than three years of history it stays quiet on holiday nights. Similar nights has each holiday's stretch.

Outside the US, or for a local festival, set the past night aside with the reason for a holiday and say it happens every year. Once you have reported it from 2 different years, that stretch is left out of comparisons every year. Handle a holiday MAYA does not have

Seasons

Seasons are stretches of your year that book differently, found from your own history, never set by hand. They only ever show inside an explanation under Show the numbers. Similar nights

Currency

Your property's currency is read when you connect: from Cloudbeds or ThinkReservations, and set with you for Mews. If none could be read, MAYA uses US dollars until we set yours. MAYA never converts anything. Every price is a number in your own currency.

On Cloudbeds, MAYA checks the currency again once a day. While your property is in simulation it follows a change to a currency it works in, and the change log says "Your currency changed from USD to CAD, to match Cloudbeds. Amounts in MAYA are now in CAD; nothing was converted." Once you are live it never changes the currency by itself, since your floors, ceilings and every price sent are in the one you have. Our team is alerted instead.

Which currencies MAYA works in. For now, dollar, euro and pound style currencies: ones with two decimal places, whose prices run in the same range as US dollars. That is US, Canadian, Australian, New Zealand, Singapore, Bahamian, Bermudian, Cayman Islands, Barbados, Belize, East Caribbean and Fiji dollars, euros, pounds sterling and Swiss francs (USD, CAD, AUD, NZD, SGD, BSD, BMD, KYD, BBD, BZD, XCD, FJD, EUR, GBP, CHF). When you connect Cloudbeds or ThinkReservations and your system uses any other currency, MAYA stops there with "Your property's system uses KRW. MAYA doesn't price in KRW yet, so nothing was set up or imported. Email us and we'll tell you when it does." (with your currency's code). Nothing about the property is kept: no connection, no import. If you had already paid, the message adds "Reply to your receipt and we'll sort out your payment." In a Cloudbeds group, the properties in other currencies are left out and the rest connect; the sign-in page then says how many were left out, for example "2 of your properties use a currency MAYA doesn't price in yet, so they weren't connected." A property already in MAYA is never checked.

The symbol depends on the screen:

• Your currency's symbol on the calendar's day cards and day detail, the room type cards and their badges, the typed-price box, the Rate Simulator, the change log (each change's sentences and prices), the Price Change column on the Rules tab, the rule builder's fixed amount box, the amounts in Import from PIE, the Rules that keep adjusting banner and the typed-price messages. That is $ for US dollars, € for euros and £ for pounds, and the three-letter code in front of the amount for any other.
• Always $, whatever your currency, on a fixed amount in the change log's bold line, such as "+$25.00", and in the grey "still applies" note under a change, such as "Weekend bump's +$25.00 still applies." The number is still yours. The change log

Your MAYA subscription is billed in US dollars, whatever your property's currency. What it costs

To check which currency MAYA has for your property, open the PMS tab: Time zone and currency shows it by its code and sign, such as "EUR (€)". The currency cannot be changed from the app. If MAYA has the wrong one, email us.

The default floor and ceiling are numbers in your currency. Every room type starts with a floor of 1.00 and a ceiling of 99,999.99, whatever the currency. In the currencies MAYA works in they stop nothing, because no night costs anywhere near 99,999.99. That is one reason a currency where a night costs 150,000 (won, rupiah or dong, for example) cannot connect yet: the default ceiling would hold every price down to 99,999.99. Read Floors and ceilings.

Typing amounts. The price box on the calendar and the amount and threshold boxes in the rule builder are your browser's number boxes. Type a point for decimals, as in 180.50, and no thousands separator, as in 1250. Whether a box also takes a comma (180,50) depends on your browser and its language. If it cannot read what you typed, the box counts as empty: Save stays greyed out, or the rule is not added, so nothing wrong is saved.

Rounding, and currencies without cents

MAYA works out every price to two decimal places, whatever the currency, and sends it that way. A price you type, a floor and a ceiling are rounded to two decimal places too. There is no setting to round to whole units. Every currency MAYA connects in has two decimal places, which is the other reason a currency without cents, such as Japanese yen, cannot connect yet.

A percentage rule can still produce cents where your rates have none. MAYA sends that number as it is. If your system keeps whole units, it rounds the price its own way. When MAYA reads the rate back, a whole number less than 1 away from the price MAYA sent counts as MAYA's own price, rounded, and not as a rate you changed. So the rounding never turns into a manual price, and MAYA does not keep sending the price again.

To keep prices whole, set rules to change by a fixed amount rather than a percentage, and use whole numbers for floors, ceilings and typed prices. As long as your own rates are whole, prices then stay whole. The starter rules change prices by percentages, so they can produce decimals.

This applies to Cloudbeds and ThinkReservations. Nothing is sent to Mews yet.

How far ahead MAYA looks

• Bookings: each read covers 30 days back to about 13 months ahead. A booking for a stay further out is picked up once its night comes into that range.
• Rules: tonight and the next 395 nights.
• Typed prices: up to 399 days ahead. One 396 or more nights ahead is priced and sent when its night enters the window. Setting a price yourself