MobilityPlus V1 connector

Use your MobilityPlus charging data for reporting, automation and AI.

Data Panda pulls your MobilityPlus charging sessions, charging cards and stations and lines them up with the rest of your fleet, payroll and accounting stack. From one place, we turn it into dashboards, automations, AI workflows and custom apps your fleet, finance and HR teams use every day.

About MobilityPlus V1

The Ghent EV-charging operator behind Belgian B2B fleets, depots and home-charging programmes.

MobilityPlus is a Belgian e-mobility service company headquartered in Ghent and active in Belgium and France. They install and operate EV-charging hardware for B2B customers (offices, depots, parkings and employee homes) and run the charging-card and reimbursement layer on top, with roaming access to a wide European network of public charge points. Named customers on their site include Roularta, Umicore, Mensura, Gimv and EY Belgium.

For a fleet manager or HR lead, MobilityPlus is the system of record for who charged how much, on which station, on which card, and what the employer owes the employee for the kWh they pulled out of their own home meter. The portal handles a single session view well. The harder questions, like cost per driver per month next to the leasing line, station load across depots, or which home-charging reimbursements are still open, sit between MobilityPlus and the systems around it. Pulling sessions, cards, users and stations into a warehouse is how those numbers stop being a portal export forwarded as a screenshot.

This connector is wired against the V1 generation of the MobilityPlus API. Current customers on a newer endpoint version should ask us to point the pipeline at the right one before they start drafting reports on top.

What your MobilityPlus V1 data is for

What you get once MobilityPlus V1 is connected.

Charging reporting

Sessions, cards, stations and reimbursements joined to the payroll, leasing and accounting data the rest of the business already trusts.

kWh per driver per month next to the leasing and fuel-card lines
Station usage per depot, ranked by hours and energy
Open home-charging reimbursements per employee per pay period

Process automation

Turn sessions and reimbursement runs into the nudges payroll, finance and fleet would otherwise chase by hand.

Push monthly home-charging amounts to payroll on the right employee line
Book station and roaming costs in accounting per cost centre
Alert fleet when a depot station drops below an uptime threshold

AI workflows

Use the session history to predict where the network will be stretched and which drivers or sites need attention.

Forecast monthly kWh per depot against installed capacity
Score driver-card pairs on cost variance per kilometre driven
Flag home chargers where reimbursed kWh keeps drifting above the team norm

Custom apps on your data

Small fleet, finance and HR tools that sit on MobilityPlus data instead of another portal export.

Driver-charging cockpit with sessions, cost and reimbursements per month
Station-uptime view per depot for the fleet team
Reimbursement-status app for HR with paid, open and disputed lines

Use cases

Use cases we deliver with MobilityPlus V1 data.

A list of concrete reports, automations and AI features we have built on MobilityPlus V1 data. Pick the one that matches your situation.

kWh per driverEnergy charged per driver per month, ranked across the fleet.

Home vs depotShare of monthly charging done at home, depot and on-the-road per driver.

Station loadHours and energy delivered per station per week, per depot.

Reimbursement queueOpen home-charging reimbursement lines per employee per pay period.

Card costCost per charging card per month, including roaming charges.

Roaming shareSessions on third-party networks against sessions on owned stations.

Cost per kilometreCharging cost per kilometre driven, joined to fleet odometer data.

Off-hours chargingSessions outside contracted working or off-peak hours.

Card-driver mismatchCards used on stations not paired to the assigned driver or vehicle.

Depot capacity checkEnergy delivered against installed capacity per depot per week.

Real business questions

Answers you will finally get.

What did each driver cost in charging this month, all sources combined?

Sessions per card joined to the driver and vehicle, with home, depot and roaming costs added on the same line. Finance and fleet read one number per driver per month next to the leasing line, instead of opening the MobilityPlus portal, the home-charging reimbursement export and the lease invoice side by side.

Which home-charging reimbursements are still open at the end of the pay period?

Reimbursement lines per employee per period, with paid, open and disputed status pulled out. HR closes payroll on a real list of who still needs to be paid for kWh out of their own meter, instead of chasing the same MobilityPlus export every month and hoping no one slipped through.

Are our depot stations earning their installed capacity?

Hours and kWh delivered per station per week against the installed power per depot. The fleet team sees which sites sit half-idle and which ones queue up at 17:00, so the next round of installations or contracts is scoped on real station load instead of last year's headcount plan.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Charging cost per driver per month next to leasing, fuel card and salary lines, instead of three exports stitched together. Cost-per-kilometre on the EV fleet becomes a monthly conversation with numbers behind it, not a hand-wave when the CFO asks how the electrification business case is holding up.

For sales leaders

For sales leaders running a field team in EVs: charging cost and time per rep per region, joined to the visits the rep made. The territory review stops being about who picked the wrong charging stop and starts being about which territories carry the highest cost-per-visit, on real sessions instead of expense claims.

For operations

Station uptime, depot capacity and home-charger health on one dashboard per fleet manager. Operations and HR read the same picture, so the Monday call is about which depot needs another wallbox and which driver needs a service visit, not about whose portal export is right.

Ideas

What you can automate with MobilityPlus V1.

Pair with Exact Online

Book MobilityPlus charging costs in Exact Online per cost centre

Monthly station and roaming charges from MobilityPlus flow into Exact Online as purchase invoices booked on the right cost centre per depot, with the kWh and session count carried as analytical detail. Finance closes the month with charging cost sitting on the same general-ledger account structure as fuel and leasing, instead of one line dumped under general expenses.

Pair with MS Dynamics 365 Business Central

Push MobilityPlus reimbursement runs into payroll prep in Business Central

Approved home-charging reimbursements per employee per period flow into Business Central as the right liability line per employee, ready for the payroll export. HR runs the period close on a paid-or-open status per line, not on a portal export that gets re-keyed into a payroll spreadsheet by hand.

Pair with Yuki

Reconcile MobilityPlus invoices against the energy lines in Yuki

Monthly MobilityPlus invoice lines per depot are matched against the energy and mobility cost bookings already in Yuki, with the gap per depot pulled out. The finance team closes the month with each depot either in tolerance or flagged with the exact delta, instead of opening a portal invoice and a Yuki ledger view side by side.

Pair with HubSpot

Surface field-team charging stops in HubSpot next to logged visits

Charging sessions per rep per day flow into HubSpot as activity on the rep record, with location and duration per stop. The sales manager sees how the charging schedule sits next to the visit log, so route conversations are about real stops between real meetings, not about an expense claim that arrives a week later.

Pair with Silverfin

Pull MobilityPlus charging cost into the Silverfin closing file per period

kWh and cost per depot per period flow into the Silverfin closing file as the analytical breakdown behind the energy and mobility lines, with the source detail traceable per session. The accountant signs off the file with charging cost reconciled to the operating data, instead of accepting one supplier total without a breakdown.

Data model

Tables we make available.

These are the 30 tables we currently pull from MobilityPlus V1 into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Agreements
Charging Evses
Charging Location Markers
Charging Locations
Common Admin Budgets
Common Admin Customers
Common Admin Invoices
Common Admin Users
Common User Budgets
Cpo Admin Charging Points
Cpo Admin Contract Templates
Cpo Admin Contracts
Cpo Admin Devices
Cpo Admin Downtimes
Cpo Admin Sessions
Cpo Admin Tokens
Credit Transactions
Customer Mandates
Customer Users
Customerpayments
Debit Notes
Host Invoices
Msp Admin Charging Sessions
Msp Admin Contract Templates
Msp Admin Contracts
Msp Admin Private Budgets
Payment Requests
Payment Transactions
Pricing Policies
Token Authorizations

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your MobilityPlus V1 data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From MobilityPlus V1 to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

MobilityPlus V1 connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Why does the slug say V1 and what does that mean for us?

MobilityPlus exposes more than one generation of API. This connector is wired against the V1 endpoints, the older generation that has been live the longest and where the majority of the existing pipelines we run are pointed. If you set up your MobilityPlus account recently or have already migrated to a newer endpoint version, ask us to point your pipeline at the right one before you start drafting reports on top, otherwise you may pull a smaller field set than your account exposes.

Does the V1 pull separate home charging from depot and roaming sessions?

Yes. Sessions carry the station and the card that paid for them, so home, depot and roaming are derivable on the warehouse side by joining station ownership and reimbursement status. That is the slice that lets you build the per-driver cost view and the home-charging reimbursement queue from the same source, instead of running two reports out of the portal.

Do roaming sessions on third-party networks come through with the same detail as our own stations?

Roaming sessions arrive with the kWh, cost and timestamp that MobilityPlus receives from the roaming partner, plus the card that paid for them. The level of station detail depends on what the roaming partner forwards, so own-station sessions are usually richer than third-party ones. The connector exposes both; how much you can slice on third-party data is a function of the partner network, not of the connector.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your MobilityPlus V1 setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors