July’s releases sharpen two things operators care about most: getting paid cleanly for the business they do, and keeping the network healthy without hunting for what is broken. Two main capabilities lead this edition: issuing B2B partner invoices straight from your settlement data and finding faulted or disconnected sites on the Locations map in the backend. Around them sit updates across corporate billing, payments, tax compliance in two more markets, and the EV driver app.
Featured this month: Issue partner invoices straight from your settlement data
Operators running b2b partner relationships already get settlement reports that total up what each partner owes or is owed. Turning one of those settlements into an actual invoice was a manual part. The figures had to be exported and rebuilt in a separate accounting system, one partner at a time, exactly when the books needed to close.
Why it matters
AMPECO can now generate a formal B2B partner invoice directly from one or more settlement reports, without leaving the platform. When a settlement report is ready, you run the Issue partner invoice action, and the platform builds the invoice from the settlement amounts, calculates the tax from the stored values, and links the finished invoice back to the report it came from. It works for a single report in the back office and for many reports at once, and it is available through the Public API.
How it works
Each eligible settlement report moves through a clear set of states, from Ready to invoice, to In progress, to Invoiced, so you always know what has been billed and what has not. Line items and tax come straight from the settlement data rather than being re-entered, which keeps every invoice consistent with the report behind it. Issuing in batch lets a finance team clear a whole set of partners in one pass at period close. The one prerequisite is a B2B invoice processor configured in your billing settings; with that in place, settlement reports become invoiceable.
What you get
No more re-keying partner figures into a separate tool, and no more invoices that drift from the settlement they are meant to match. Billing partners is faster, and every invoice goes out sooner and stays reconciled to the settlement behind it. The audit trail stays intact, and when you run b2b partner relationships at scale, you can issue across all of them in a single action instead of partner by partner.
Also new: Find faulted and offline sites on the Location map
A charge point can fault or lose its connection at any time. Detecting that is easy. The harder part is seeing where the problems cluster so you can plan an efficient maintenance run. On a large network, that usually meant reading down a status list and mapping the addresses in your head or in an external tool.
Why it matters
A new Faults and connectivity loss filter on the Locations map shows only the sites that need attention, plotted geographically. In a single view, an operations team can see where faults and dropped connections are concentrated and plan maintenance around the real distribution of problems rather than a flat list.
How it works
Apply the “Only locations with faults or connectivity loss” filter on the Locations map, or jump straight to it with View on map from your charge points list. The map then shows locations with at least one charge point that has reported a fault, gone unavailable, lost its connection for an extended period, or has a faulted or unavailable connector. The same filtered set is available as a table through View as list. Because this runs on the Locations map, you can pair it with the map’s area selection and export: draw the region a technician will cover, and export the faulted sites inside it as their route for the day.
What you get
When several sites go down at once, the cluster is visible immediately, so triage is faster. A technician can cover a whole region in one trip instead of chasing addresses off a spreadsheet, and fewer visits are wasted on sites that did not actually need the work.
Corporate billing and business accounts
Two updates give operators tighter control over how business accounts are billed.
- Individual spending limits enforced during the session: A corporate driver’s individual spending limit now applies while a session is running, not only when it starts. As the session continues, the platform tracks the employer-covered amount against the driver’s remaining allowance for the billing period, and once that allowance is used up, employer coverage stops. If the driver has an eligible personal payment method or balance, charging carries on with the extra billed to them; if not, the session ends. Usage from the driver’s other active corporate sessions counts toward the same limit, so the cap holds even across simultaneous charges.
- Company receipts for business drivers: Drivers who charge for work can now receive receipts made out to their company instead of themselves. The driver turns on company details in their profile and enters the company name, tax ID, and address, and receipts issued through EFSTA E-Receipts or the built-in receipts then name the company as the recipient, falling back to personal details if anything is missing. Operators switch it on per receipt integration.
Payments and billing
Worldline operators get a fuller set of saved payment options, and a billing safeguard rounds out the set.
- More ways to pay with Worldline: Operators using Worldline can now offer drivers a fuller set of saved payment methods, so more of them can pay without entering a card each time. The newest addition is SEPA Direct Debit, for operators whose currency is the euro. A driver authorizes the mandate once in a Worldline-hosted flow, then pays straight from their bank account (shown as a saved Bank transfer (SEPA) method) across sessions, top-ups, voucher purchases, subscriptions, and auto-top-ups. Bancontact joins the same set of saved methods for that market, and Apple Pay and Google Pay are available as tokenized wallet options, stored after a single device authentication and reused across sessions, top-ups, subscriptions, and payment retries.
- Post-session idle fees, now available to every operator: Idle fees can keep accruing after a session ends while the vehicle stays plugged in, so operators can apply overstay policies more accurately when a tariff includes an idle fee. It is controlled entirely from your own settings: turn on Idle period detection, then enable idle-fee billing while the vehicle is still connected after the session finishes.
- Billing paused when a session points at a disabled charge point: A new validation rule catches sessions linked to an EVSE that has been disabled or deleted, a situation that can arise during real-time roaming authorization, and suspends billing before an unreliable price is applied. Session start is unaffected, so authorization approval rates hold, and billing simply waits until the record is corrected.
Compliance across new markets
Two releases extend where operators can meet local tax and reporting rules directly from the platform.
- Automatic regulatory reporting for Italy (PUN): Operators using the NAP (PUN Italy) integration no longer have to resubmit regulatory data by hand after every change. When a supported field on an EVSE changes, such as its POD ID or smart-charging capability, AMPECO now sends the updated data set to PUN automatically in the background, grouping related edits made within a few minutes into a single submission. It builds directly on June’s manual sync by taking the manual step out.
- E-invoicing for Greece (AADE via Impact): A new integration with Impact fiscalizes invoices for Greece’s AADE myDATA system automatically as they are issued, covering both business and retail invoices. If Impact or AADE is briefly unavailable, invoices fall back to an offline mode with a temporary QR code and reconcile automatically once the connection returns. It is available to any operator with an active Impact contract.
Back office and network operations
A handful of smaller controls make everyday back-office work faster and more precise.
- Dynamic values in charge point configuration: Configuration templates and the bulk Set configuration key(s) action can now hold placeholders that the platform fills in per charge point, such as each connector’s identifier inside an ad-hoc charging portal URL. One template produces the right value on every charger, so operators running a custom portal across a fleet no longer configure the same key device by device.
- One payment terminal integration across many operators: Tenants that run several operators can set up a CCV or Payter payment terminal integration once at the tenant level, receive all the terminals through that single connection, and assign each one to the right operator when it is ready. A visibility setting controls who sees terminals that are not yet assigned, and a terminal can be moved between operators later.
- A standard way to honor marketing opt-outs: Support and operations teams can now revoke a user’s marketing consent directly from the back office, or through the Public API, when an opt-out request arrives by email or phone. The action turns off the user’s marketing preference and records the change in the audit trail, giving operators a consistent, logged way to handle these requests instead of a one-off task.
In the driver app
Filter the map by price: Operators can now let drivers narrow the map to locations at or below a maximum average price they are willing to pay. Because exact prices vary by session, operators assign a representative average price to each location, and once the filter is enabled the app returns only the locations at or under the driver’s chosen figure. It gives price-conscious drivers a faster way to shortlist where to charge before they set off.
What’s next
AMPECO ships updates every week, and this edition pulls out the ones worth a closer look. More is on the way across billing, payments, and the driver app in the coming weeks. If you already run AMPECO, your account team can walk you through switching any of these on. If you are evaluating the platform, book a demo to see them in action.
