Introduction
A rate in RentVisie never stands on its own. It sits where two things cross: a period — a stretch of the calendar, such as Summer 2026 — and a duration band, a range of rental lengths, such as up to 3 days. Miss either and the price comes back as zero.
Both live inside a price list, on two tiles: Periods for the calendar stretches and Global rules for the duration bands. Each opens a table with a New button above it and three small icons at the end of every row.
You come here when:
- Next year's calendar is agreed and you need a 2027 period before you can enter 2027 rates.
- Every price is coming out at zero and you are working out why.
- Rentals of a week or more should be cheaper per day, so they need a band of their own.
- Next year's rates should be this year's plus a few percent, without retyping them.
Terms used on this screen
| The screen says | It means |
|---|---|
| Periods | A stretch of the calendar, with a start and an end date |
| Global rules, Customer Global periods | Duration bands — both names are the same screen |
| From in Hours, To in Hours | The length of rental the band covers, counted in hours |
| Applicable on | The days of the week a band accepts, judged on the pickup day |
| Priority | A yes/no switch, not a ranking number |
Neither tile has a separate menu entry, so you always start from the price list — see Set up a price list if you have not made one yet.
How to use
Configuration
There is nothing to switch on elsewhere: both screens are configuration in their own right.
Before you start: creating, editing and deleting periods and duration bands all need the Company admin role. An ordinary Employee account can read both tables but the New and Save buttons will not work. Your company must already have at least one price list — everything here belongs to the list you opened it from, and a second price list has its own separate periods and bands.
Using the Periods and Global rules screens
From the main menu, open your settings and administration area and go to the pricing section, headed Pricelist overview. Double-click the price list you want, then pick either Periods or Global rules from the tiles.
1. Create a period. On the Periods tile, click New Pricing period. Three fields:
| Field | Starts as | What it does | What it accepts |
|---|---|---|---|
| Name | Blank | What you call this stretch, e.g. Summer 2026 | Any text up to 200 characters |
| Date from | Blank | First day the period covers | A date, required |
| Date to | Blank | Last day the period covers | A date, required, later than Date from |
Click Save. Anything wrong comes back in red under the field: "Name is empty", "Date from is empty", "Date to is empty", "Date from should be before Date to.", or "Dates overlap with other periods". That last one also raises a red banner reading "Pricing period overlaps with other pricing periods".
2. Edit or remove a period. Use the pencil icon on the row; double-clicking does nothing here, even though it works on the price list table. The bin icon deletes without asking you to confirm, but a period with rates attached refuses, with "Cannot delete PricingPeriod as its linked to PriceRules."
3. Roll a period forward into next year. The third row icon is a percent sign. It opens Pricing period New Indexation, which copies that period's rates into a new period, multiplying them on the way:
| Field | What to put in it |
|---|---|
| Period from, Period to | The dates of the new period |
| Base indexation factor | The multiplier for the daily rates — 1.05 puts them up 5% |
| Mileage indexation factor | The same, for the mileage rates |
| Extra indexation factor | The same, for extras and insurance |
Click Save. You get "Success!" and a new period named after the old one with the base factor on the end, so Summer 2026 indexed at 1.05 becomes Summer 2026 - 1.05, and a daily rate of €80.00 becomes €84.00.
4. Create a duration band. On the Global rules tile, click New Customer Global periods. Fill in the top four fields first:
| Field | Starts as | What it does | What it accepts |
|---|---|---|---|
| Priority | Off | Turn on to make this band beat every ordinary one | A yes/no switch |
| Name | Blank | What you call the band, e.g. Up to 3 days | Any text up to 200 characters |
| From in Hours | 1 | Shortest rental the band covers | Whole hours |
| To in Hours | 7 | Longest rental the band covers | Whole hours |
These two boxes are hours, not days. The starting values of 1 and 7 make a band covering rentals of one to seven hours, which is almost never what you want. A band for rentals up to three days is 1 to 72.
5. Add cut-off times, if you need them. Under "Fill in the below to set up cutoff times." sit Pickup after hours and Return before hours, both whole numbers on the 24-hour clock. The screen's example is "pickup should be after 16 (hours) or return should be before 11 (hours)." An empty box means no cut-off.
6. Choose which pickup days the band accepts. At the bottom, Applicable on has a switch for each of Monday to Sunday, all on to start with.
Click Save. Nothing is checked here, so a band with an impossible range saves quietly and never matches anything.
Key details
How the app picks a period and a band
The period is chosen on the pickup date alone. If Summer runs 1 April to 30 September and a customer collects on 28 September and returns on 5 October, the whole rental is priced from Summer. Both end dates count as inside.
The band is chosen on the rental's total hours, and both ends count. With a band of 1 to 72 hours, a rental of exactly 72 hours matches; 73 hours does not, and unless another band covers 73 upwards that booking prices at zero.
Priority overrules. If any matching band has Priority switched on, every ordinary band that also matched is thrown away. Two priority bands matching at once are not ranked against each other.
The day switches only look at the pickup day. Whether the customer keeps the car over a Sunday makes no difference to which band is used.
A worked example
Your price list has one period, Summer 2026, running 1 April to 30 September, and two bands: Short at 1 to 72 hours, priced at €80.00 a day, and Week+ at 73 to 336 hours at €65.00 a day. A customer collects a compact car at 10:00 on Saturday 20 June and returns it at 10:00 on 23 June — 72 hours.
20 June sits inside Summer 2026. The 72 hours land in Short, at its top edge. Neither band has Priority on, and Saturday is switched on, so the rental prices at 3 × €80.00 = €240.00. One extra hour makes it 73 hours: it leaves Short for Week+ and the same booking comes to €65.00 a day. Switch Saturday off on Short and that band drops out with nothing to replace it — Week+ does not reach down to 72 hours — so the price comes back as zero.
What to do next
Get the periods in first, then the bands: rates cannot be entered until both exist. Then open Asset gr. pricing in the price list to enter the rate for each vehicle class at each crossing of a period and a band. Check the Global rules table for gaps first — every rental length you sell needs a band covering it, with no hours uncovered between one band's top and the next one's bottom.
Q&A
Why is a price coming out as zero even though I entered a rate? Three causes, in the order worth checking. The pickup date may fall outside every period — a booking for January when your only period runs April to September finds nothing. The rental length in hours may fall in a gap between two bands, or above the highest one. Or the rate may be attached to a period or band you have since deleted. Open Periods and Global rules and check that the pickup date and the rental's hours each land inside a row.
Why did rates disappear after I deleted a duration band? Deleting a band does not delete the rates attached to it, and nothing warns you. Those rates survive but no longer have a band to be found through, so the app stops seeing them and the price falls to zero. Periods are protected this way and bands are not, so treat the bin icon on Global rules as the dangerous one. Recreating a band with the same name and hours does not reconnect the old rates — enter them again under Asset gr. pricing.
I set a band to 1 and 7 for "one to seven days" and nothing prices. Why? Because those boxes are hours. A band of 1 to 7 covers rentals between one and seven hours, so a one-day booking at 24 hours misses it. Multiply your days by 24: one to seven days is 24 to 168.
Why does a band with only Saturday switched on still match a booking picked up on a Tuesday? Because the day switches are skipped altogether once a rental reaches seven days. On a fortnight's booking every band matches on days regardless of what you switched off, so a band you meant for weekend hires only can pick up long rentals as well. If that band must never apply to long rentals, cap its To in Hours at 167 so the length keeps it out instead.
Can I have two periods that meet on the same day? The app allows it — the overlap check lets one period end on the same date another begins. Avoid it anyway: a pickup landing exactly on the shared boundary matches both periods and the app takes whichever it finds first, so the rate applied is not predictable. End one period the day before the next one starts.
What do the two extra fields under Apply day restraint do? Switching Apply day restraint on reveals two more boxes, Pickup day restraint and Dropoff day restraint, both whole numbers, with the screen noting "Sunday = 0, Monday = 1, Tuesday = 2 … Saturday = 6". Only the pickup one changes anything. Once Apply day restraint is on, the return side is judged against your pickup settings instead, and Return before hours stops being applied. Use Apply day restraint only to relax the pickup cut-off, and leave Dropoff day restraint at 0.
Should I switch on Apply day of week adjusments? Only if someone has set up the per-weekday factors for this price list. The switch, spelled as you see it on screen, turns those factors on for this band and nothing else. It starts off, and off is right until those factors exist.
The overlap warning I get in Dutch talks about dates being in the wrong order. Is that the right message? No — the Dutch text on that one warning repeats the date-order message by mistake. If you are working in Dutch and see "De datum van moet vóór Datum tot zijn." while your dates are clearly in the right order, read it as the overlap warning and check your dates against the other rows in the Periods table.
Can I copy a whole set of bands to another price list? Not from these screens. Duration bands are copied once, automatically, when a new price list is created — see Set up a price list. After that the two lists are independent and a band added to one has to be added to the other by hand.
Related pages:
- Set up a price list — the list these two screens live inside, and what a new list starts with
- Search for an available vehicle — where a missing period or band first shows up, as a price of zero