Changelog

Vote on feature requests in Monta Hub

See what other operators have asked Monta for, and vote for the features that matter to you. A new Feature requests board sits next to the Roadmap under What's New in Monta Hub. Send a request from the Helpdesk: tell Monta why you need it, what you need and by when. Monta reviews every request: it's added to an existing request or becomes a new one, rewritten so it reads clearly for every customer. Vote on the board: requests that apply to many customers are published on the board, ranked by how many people back them. Vote for the ones you need. Follow and get updates: each request has its own page with the full description, updates from Monta and how many operators back it. Followers hear when Monta posts an update and when a request ships. Until now, a feature request was a ticket only you could see, and there was no way to tell whether others needed the same thing. The board turns one-off asks into shared requests: you can add your voice to what's already there, and Monta sees how many customers need each one when planning the roadmap. Browse and vote: in Monta Hub, go to What's New → Feature requests and select the vote button on a request. Send a new request: select Helpdesk → New → Feature request, and fill in Summary, Why, What and When. Follow a request: open it and select Follow. Voting follows it automatically. Only requests written by Monta appear on the board. Your own ticket text is never shown to other operators, and other operators' names are never shown. Voting tells Monta how many customers need a feature. It doesn't guarantee when or whether it ships. How do feature requests and voting work in Monta Hub? How do I report a bug or request a feature in Monta Hub?

Track every bug report and feature request to Monta in the Helpdesk

You can now report bugs and request features to Monta from Monta Hub, and keep track of every one of them in one place. The Helpdesk shows all your tickets to Monta with a live status, so you always know what's been received, what's confirmed, what's planned and what has shipped. And our promise: every ticket gets a reply from Monta within 5 business days. A reply within 5 business days: Monta replies to every bug report and feature request within 5 business days, so no ticket is left waiting without an answer. All your tickets in one overview: Helpdesk in the sidebar lists every bug report and feature request your organisation has sent to Monta, with its status, type and last activity. Search, filter by status and export the list. Follow every status: each ticket moves through clear statuses: Received, In review, Needs your input, Confirmed (we agree it's a bug), Planned, In progress and Shipped, or Answered and Not planned with the reason in the ticket. Get notified: you follow the tickets you raise automatically and get an email and a Hub message when Monta replies or changes the status. Follow a colleague's shared ticket to get the same updates. Unread news is marked in the list and counted in the sidebar. The full story on every ticket: a timeline shows every status change, and the conversation with Monta stays on the ticket, so anyone on your team can catch up. Bug reports and feature requests: attach screenshots and screen recordings to bug reports. Feature requests ask for the product area, the impact on you and your current workaround, and go straight to Monta's product team. Share feedback opens a ticket: the Share feedback button now starts a bug report or feature request to Monta, so your feedback gets a reply. Until now, bugs and ideas reached Monta by email, calls and survey forms, and it was hard to know what happened next. Now your teams can see every open bug and request at a glance, know when Monta needs their input, and see when a fix or feature has shipped, without chasing anyone. In Monta Hub, select Helpdesk in the sidebar to see all your tickets. Select New, or Share feedback on any page, and pick Bug report or Feature request. Open a ticket to see its timeline, reply to Monta, or Follow it for updates. A good bug report says what you did, what you expected and what happened instead. A screenshot or short recording helps us fix it faster. Monta's product team reads every feature request, but can't promise when or whether it ships. How do I report a bug or request a feature in Monta Hub?

A new look for the Monta map, in light and dark

The Monta web map has a new design, with light and dark themes. It now reads at a glance: what's free, how fast, how much and how far. This applies to maps.monta.app and to the map you embed on your own website. https://maps.monta.app Light and dark themes: the map follows the driver's device setting, and drivers can switch with the sun and moon button. Embedded maps without controls stay light. Pins that tell you more: every pin shows the charging speed and, for sites, how many chargers are free, for example "22 kW 9 free". Overlapping sites stack instead of turning into numbered circles. Nearby list: on desktop, the sidebar lists the chargers in view, nearest first, with availability, speed, connector, distance and price. Quick filters: Only available, Fast 23+ kW, Ultra fast 100+ kW and Find Best Price are one tap away. The full filter panel opens from Filters. Clearer details: a site leads with "9 of 12 free right now", key facts show as pills, and Start charging stays at the bottom of the panel. Built for phones: drivers swipe through cards for the nearest chargers, tap a card for the full details and get directions from every card. Fixes: shared charger links now open on a first visit, addresses no longer show "null", and long charger names no longer push the price off the card. Drivers decide where to charge in seconds. Showing free chargers, speed and price on the map itself, instead of numbered circles, gets them to an available charger faster. For you, that means fewer drivers arriving at a busy site and a map on your website that looks current. If you embed the map: the filter panel is now closed by default, with quick filters above the list. Links with filter_ui=1 still open it. Embeds without a map_style now use the colourful light map. Add map_style=silver to keep the previous look. Your marker colours and marker style settings still apply, on the new pins. maps.monta.app How do I build an embeddable charge point map for my website?

See which charge keys roaming partners refuse, and why

A Roaming conflicts tab on Charge keys and a Roaming partners tab on each key show when an RFID UID clash stops a key working on partner networks.

What's new Available now in early access: Hub shows when a charge key's RFID UID is in conflict on roaming networks, and what that means for the key. A new Roaming conflicts tab on Charge keys lists every open conflict across the keys in your selected accounts. A new Roaming partners tab on each key shows whether every roaming partner accepted it, with the partner's last error. Charge keys → Roaming conflicts lists every open conflict across your keys. Why it matters A charging station only reads a card's RFID UID, so each network can link a UID to just one eMSP. When another eMSP holds the same UID, your key is refused on partner networks, and until now nothing in Hub told you why. Your support team can now answer "my card works at home but not on partner X" in Hub, and see which keys aren't reaching partners at all. Who it's relevant for Operators who issue charge keys that drivers use on roaming partner networks. How to use it Open Charge keys (EMP / Fleet) and select the Roaming conflicts tab. Filter by status, conflict type, partner or account. For example, pick a partner to see every key it refused. Select a row to open the key's Roaming partners tab. It shows each partner's status (Accepted, Retrying, Rejected, UID conflict or No data), when the key was first and last accepted, and what the partner sent back. After you change a key, use Push to partners to send it to every partner again. A key's Roaming partners tab explains each conflict and shows every partner's answer. Each conflict is labelled by who holds the RFID UID. Held by other eMSP means another eMSP holds it, so the key isn't sent to any partner. Refused by partner means one partner won't accept the key. Claimed by other eMSP and Between other eMSPs don't stop Monta sending your key to partners, but because another eMSP also uses the RFID UID, the key may not work on every part of a partner's network. While another eMSP holds the RFID UID, the key isn't sent to partners and Push to partners is unavailable. To work through conflicts offline, export the Charge Key Roaming Conflicts dataset from Analytics → Data exports. Availability Accounts on the Early access release track have it already. On any other track, an operator admin can turn on Charge key roaming conflicts in Release channel, or try it on one login first with Try myself. Learn more How do I find charge keys with roaming conflicts in Monta Hub?

Idle fee grace periods by weekday and on public holidays

Grace periods now follow your week. Choose the days each idle fee grace period applies on, waive the fee all day, and include public holidays, so you can say "no idle fee overnight on weeknights, and none at all on weekends and public holidays" in one price group. Days per grace period: pick Mon–Sun for each grace period, or use a preset: Every day, Weekdays, Weekends, or Weekends and public holidays. All day: waive the idle fee for the whole day with one toggle. Public holidays: turn on Public holidays to waive the fee on holidays too. Each charge point uses the public holidays of the country it's in, so one price group works across countries. Your own holiday calendar: national public holidays are kept up to date automatically. Add your own days, like a local festival or a company closing day, or remove a holiday you stay open on, under Public holidays in your operator settings. Week at a glance: see exactly when the fee is waived on each weekday and on public holidays, including overnight periods that run into the next morning. Clashing periods are flagged before you save. Clear prices for drivers: the public price shows the days next to each grace period, for example "22:00 → 06:00 Mon–Thu". Idle fees keep chargers free when people are waiting, but nobody is waiting at an office car park on a Sunday or at a residential site on Christmas Day. Until now a grace period applied every day, so your teams had to choose between charging drivers when it made no sense or giving up the fee altogether. Now the fee works only when it should. Open a price group, go to the Idle fee and open Grace periods. Add a grace period, set the times or turn on All day, then pick the days and, if you want, Public holidays. Select Public holidays to see the holiday dates for any country, and Change holidays in operator settings to adjust them. An overnight grace period belongs to the day it starts on: a Friday 22:00–07:00 period also covers early Saturday morning. A public holiday also gets the grace periods of the weekday it falls on. How do I create additional charging fees?

Apply a global price group as the default for many accounts at once

You can now apply one of your global (operator) price groups as the default price group for many accounts at once. Everyone who joins those accounts later, with the join code, an invitation or an import, gets it automatically, so new members never land on the wrong price or charge for free. Set default price group, in bulk: select accounts on the Accounts list, pick one of your member price groups and set it as the default for all of them in one step. Accounts in a different currency are skipped and counted, so nothing is set by mistake. Apply to → New members (account default): open a global member price group, select Apply to and choose New members to make it the default for the accounts you pick. Existing members still moves the people who are already members. Set as default on a single account: on an account's Price groups tab, global price groups can now be set as the account's default too, with a confirmation that names the price group you're replacing. See what new members get: under the join code on the account's Settings tab, Hub shows which price group new members get, or warns you when no default is set. You can't always control who joins an account or when. Until now, a global price group couldn't be an account's default, so your teams had to copy the same price group onto every account, or use an account setting as a workaround. Now one global price group can be the joining price for every account that needs it, set in a single step. Go to Accounts, select the accounts, then select Set default price group. Or open a global member price group under Pricing & Growth → Price groups, select Apply to, then New members (account default). For a single account, open its Price groups tab and select Set as default on the price group. Existing members keep their current price group. If an account uses an account setting that names a default member price group, that one still decides what new members get. You can set the default on up to 500 accounts at a time. How do I apply a price group as the default for new account members?

Price + Market: pricing recommendations that read your local market

A second signal that holds a price move when the local market says it won't pay off

What's new — a second pricing recommendation that reads your local market, not just your price. Until now, pricing recommendations used one signal: where your price sits against nearby chargers, nudged toward the local median. Price + Market adds a second signal — how the local market is structured — and uses it to shorten a suggested move toward "leave it as it is" when moving wouldn't pay off. It never reverses a move or makes one bigger. The Price + Market model can recommend hold whereas the Price model would recommend a price cut in these cases: You already set the going rate — you're the local leader, so a cut only starts a race to the bottom. A larger operator sets the going rate nearby — moving wouldn't shift the market, only your margin. Nearby prices have converged — there's no room to move without breaking out of the local band. Switch models in one click — a model selector at the top of Pricing benchmarks and Apply recommended prices switches the whole page between Price and Price + Market. Both read the same daily snapshot, so the switch is instant, and your choice is kept in the page link so you can share the view. On Pricing benchmarks A verdict for every site — Room to raise, Priced above the market, Leave it as it is, or why a move was held: You set the going rate, Held to the local leader, Prices here have converged. The suggested price has its own column. Counts that follow the model — held sites move from raise or lower into hold, so you can see how much the market changes the picture. A detail view built around the market — what the price alone suggested, what the market check changed, what we found about the local market (for example "A larger operator sets the going rate nearby"), and how sure we are, based on how many comparable sites back the reading. Map of your market — the area around a site with every nearby charging location, as individual markers or a density view. Closer chargers count more — recommendations now weigh nearby chargers more than those further out, and each charger in the nearby list shows how much it counts. On Apply recommended prices Ranked by market-adjusted opportunity — a raise the market held drops down the list instead of ranking on a value it no longer shows. Market position and a map for every price group — the market conditions behind the group's verdict, and a map of all its locations. Apply, split and editor hand-off work as before — only the recommendation they act on changes. Ask Monta AI about it — ask why a site's recommendation was held, which sites the market says to hold, or what is shaping prices in an area. Activate it in Release channel, then open Pricing benchmarks or Apply recommended prices in Hub and pick Price + Market at the top of the page.

A public roadmap of what Monta is building

See what we're exploring, building and have shipped, in Monta Hub and on the Monta Updates site.

We're introducing a new public roadmap that shows where Monta is heading. Every item sits in one of three stages: Exploring, Building or Live. You're able to filter the roadmap by stage and by theme, such as Energy management, Payments and billing, or Roaming and interoperability. You can see what's coming next and what has already shipped, in one place. Live items link straight to the changelog posts that describe them, and items in progress will show their latest changelog updates, so you can follow a feature from idea to release. The roadmap is available in two places: in Monta Hub under What's New → Roadmap, and on the Monta Updates site at updates.monta.com/roadmap, next to the changelog. Each roadmap item will also get its own page that you can share with your team.

Set your own kWh limit for guest charging

Operators can now set their own kWh limit for guest charging, instead of Monta's regional default of 80 kWh (110 kWh in North America). For many locations that default reserves far more on the guest's card than the charge needs. A new kWh limit per guest session setting under Admin → Settings, between 30 and 300 kWh. It sets both the pre-authorisation on the guest's card and the point where the session stops. It applies to drivers who charge without a Monta account: payment terminals, web checkout and App Clip, and RFID cards not linked to an account. Leave it empty to keep Monta's regional default. A smaller hold on the guest's card means fewer declined or abandoned payments. A higher limit lets vehicles with large batteries charge fully in one session. How do I set the kWh limit for guest charging?

Lower the charge limit automatically when a location is busy

You can now lower the charge limit on DC charge points automatically while a location is busy, so fast charge points free up faster for the next driver. Add rules to a location, such as while at least 75% busy, limit charges to 90% and while at least 90% busy, limit charges to 80%. When the location quiets down, the limit is removed again. Monta measures how busy the location's DC charge points were over the last hour. Occupancy history shows every measurement and which limit applied, and each DC charge point shows why its default charge limit is locked. Above about 80%, most cars charge much more slowly. At a full location, those last minutes block a fast charge point while other drivers wait. Lowering the limit only at peak times turns charge points over faster without capping charging the rest of the day. Operators with busy public DC locations, such as highway and retail fast-charging hubs. Open a location and go to Settings → Configuration → Busy-location charge limit. Add your rules, or select Use recommended rules, then save. Check Occupancy history to see how busy the location was and adjust the rules. It applies to DC charge points only, at locations with at least two DC charge points. Only charges that start while a rule applies are affected, and drivers who set their own charge limit keep it. Available now in early access. Read more in the help centre. Hub → Location → Settings → Configuration → Busy-location charge limit.

E-documents in Monta Hub: see your DGFiP e-reports, now live in France

A new Finance section shows French operators every e-report Monta files on their behalf, with e-invoices appearing as soon as they are issued.

What's new French e-invoicing and e-reporting are mandatory as of September 2026. Monta files the required DGFiP transaction reports for you every ten days, and you can now see what was submitted in Finance → E-documents in Monta Hub. The E-reports tab lists every report filed for your operator and for the accounts underneath it. For each report you can see: The reporting period it covers and the date it was submitted, with filters for both Who it was issued by — your operator or one of your accounts — with a filter to narrow the list to a single account The reported total, including tax, per currency Its status — delivery and acceptance by the DGFiP Open a report to see the detail drawer: domestic B2C sales grouped per day and per VAT rate, and cross-border sales with net, tax, rate and total. Where a filing has been corrected, the earlier revision stays listed alongside the new one as an audit trail. Coming soon: E-invoices The E-invoices tab will show the e-invoices Monta issues on your behalf as soon as they are sent: invoice number and format, counterparty and SIREN, date, net amount and transmission status, newest first. Click an invoice to see both parties, the lines with their VAT rate, a per-rate VAT breakdown, and the compliance details. Why it matters E-documents gives you the proof of filing and the figures behind it in the same place you manage the rest of your finances. Who it's relevant for Operators and businesses based in France. Access is governed by your finance permissions. Where to find it Hub → Finance → E-documents. Read more about French e-invoicing.

See who has access to your operator, and remove people who have left

A dashboard overview to navigate your members in one place and revoke access for people who are no longer with your organisation.

As people join and leave your organisation, access to your operator builds up: leavers who still have a login, admins who never signed in, invites that were never accepted. It has been hard to see who should still have access. Under Admin → Members → Overview you now get one place to navigate everyone with access to your operator. It puts the access worth reviewing first (people who have left, stale invites, admins who never signed in, personal email addresses instead of company ones, and look-alike duplicates) so you can spot who no longer belongs and revoke their access in a few clicks. Alongside it, you get a breakdown of access by role and by email domain. Overview surfaces what needs review. The All members tab is where you manage everyone day to day: search and filters, single or bulk invite, per-member role and access-expiry, and bulk set-role, set-expiry and remove.

Location layout: arrange your charge points on a site plan

Place each EVSE on a schematic grid or satellite map so drivers can find an open stall

Location layout lets you arrange a site's charge points on a visual plan, so a driver can see at a glance where each stall sits and which one is free. You build it once in Monta Hub, on the location's Layout tab. Two backdrops are available: a schematic grid for a clean diagram, or a satellite map where stalls are pinned to real coordinates. Alongside the stalls you can drop orientation markers that don't charge — entrance, exit, building, ground areas and amenities — so the plan matches what a driver actually sees on arrival. Stalls and markers can be resized and rotated, and a station's EVSEs can be grouped and moved as one unit. A driver preview sits next to the editor and shows live availability — which stalls are available, in use, reserved or unavailable, and which is nearest — so you can check the plan reads correctly before you publish it. On a large site, a driver arriving at a location has no way to tell which stall is free without driving the rows. A layout turns the site into something they can read at a glance, and it gives your team an accurate picture of where each EVSE physically sits rather than just a list of IDs. Operators running multi-stall sites, especially larger locations where finding an open stall is not obvious from the entrance. In Monta Hub, open the location and go to the Layout tab. Pick a backdrop: schematic grid or map. Drag your EVSEs onto the plan and position them; group a station's EVSEs where relevant. Add any reference markers — entrance, exit, building, amenities. Save, then use the driver preview to check what drivers will see. If you add or remove EVSEs later, the layout reconciles automatically: new EVSEs appear as unplaced so you can drop them in, and removed ones fall away. Available now in Monta Hub. In this first edition the layout is not shown in the Monta mobile app yet — you build and publish it in Hub, and drivers view it through the shareable web preview. Bringing the layout into the mobile app is planned for a later release. Hub → CPO/Network → Locations → open a location → Layout

Spending limits for your drivers

Cap how much your drivers spend, how often they charge, what price they pay and when

Spending limits let you put guardrails on how your drivers charge — how much they can spend, how often they can charge, what price they may pay, and when they can charge. You build a reusable spending rule once and assign it to the accounts, drivers, vehicles or charge keys it should govern. A rule can combine any of the four dimensions below, and each one is optional. How much — total spend per period plus a cap on any single charge, for example €300 per 30 days, €50 per day, €60 per charge. You decide which cost components count: energy, minimum price, idle fee and session fee. How often — number of charges per period and number of simultaneous charges, for example 4 charges per day, 1 at a time. What price — maximum price per kWh, set separately for AC and DC, plus caps on session fee and idle fee. When — which weekdays charging is allowed, measured in the driver's local timezone. Caps can be measured over a calendar period or a rolling window, and multiple caps stack — a charge is refused as soon as any one of them is reached. As you build a rule, Hub shows a live plain-English summary of what it will do. Today a sponsored driver can charge without limit. There is no way to bound what they spend, how often they charge, or what they pay per kWh — which means runaway costs, unpredictable monthly spend, and no protection against one expensive fast-charge draining a budget or an abusive repeat pattern going unnoticed. Spending limits turn that into a budget you configure once and apply wherever it belongs, with refusals recorded so you can explain afterwards why a charge was stopped. Fleet operators and employers who sponsor charging, and the finance teams that own the budget. Go to EMP / Fleet → Spending limits in Hub and select New to create a spending rule. Turn on the dimensions you need (spend, frequency, price or weekdays), set each cap and the period it is measured over (daily, weekly, monthly or rolling 30 days), and choose which cost components count toward your spend caps. New rules are saved as drafts. Activate a rule to start enforcing it at charge time. Apply the rule to the accounts, drivers, vehicles or charge keys it should govern, or attach it to a policy. A rule limits nobody until it is activated and applied. Available now in early access. Hub → EMP / Fleet → Spending limits.