Fleet Charging Management: A Practical Guide for Fleet Managers

Electrifying a fleet changes more than the vehicles. Fuel cards, fuel receipts and monthly fuel reports are replaced by charging sessions, kWh readings and charger uptime. The fleet manager suddenly needs to know which driver charged which vehicle, where, how much energy was used and who pays for it.

This guide explains how fleet charging management works in practice: where fleet vehicles charge, how drivers and vehicles are identified, how energy quotas control consumption, how costs are allocated, and how to connect charging data to the systems your finance and operations teams already use. It ends with a practical rollout plan.

What is fleet charging management?

Fleet charging management is the set of processes and software a company uses to operate, monitor and account for the charging of its vehicles: hardware, driver and vehicle identification, charging rules, reporting and cost transfer to accounting.

The technical foundation is usually OCPP (Open Charge Point Protocol). OCPP-compliant chargers connect to a central system, called a CSMS (Charging Station Management System), which receives every status change, authorization request and meter reading. Because OCPP is an open standard, a fleet can mix charger brands and still manage them from one dashboard.

Where fleet vehicles charge: depot, workplace and home

Most fleets use a combination of charging locations, each with different control options.

Depot charging

Depot charging is the easiest to control. The priority is readiness: every vehicle should leave with enough energy for its route. A live view of connector status helps the team find faults before the morning shift.

Workplace charging

Workplace chargers are often shared between company cars and private vehicles. Define which cards may use which chargers, and whether private charging is free, limited or recorded for settlement.

Home charging

When a company installs an OCPP-compliant charger at a driver's home and connects it to the same CSMS, every home session is measured and reported just like a depot session. This is usually more accurate and easier to audit than reimbursing based on household electricity bills.

Identifying drivers and vehicles

A charging session without identity is only an energy number. To allocate costs and enforce rules, each session must be linked to a driver and, ideally, to a vehicle.

• RFID cards: The most common method. The charger reads the card UID and sends it to the CSMS as an idTag in an Authorize request. The CSMS accepts or rejects it. Read more in our guide to RFID charging card authorization.
• Driver-to-vehicle links: Linking each driver to one or more vehicles (with license plates) lets the system write the plate to the session record.

In Üreticy, RFID cards are assigned to drivers, vehicles are registered with their plates and linked to drivers, and the plate is written to each session. Cards can be suspended or blocked at any time, and every rejected authorization is listed with its reason.

Energy quotas: controlling consumption with kWh limits

Energy quotas are the most practical tool for fleet cost control. Instead of approving each session, the fleet manager sets a kWh budget per driver or per vehicle for a period, and the system enforces it automatically.

• Period: daily, weekly or monthly, depending on how vehicles are used.
• Hard limit: when the quota is reached, charging stops automatically and new sessions are rejected.
• Soft limit: charging continues, but a warning is raised so the manager can review the case.
• Allowed stations: a driver may be allowed to charge only at specific locations, such as the depot and their own home charger.

Soft limits suit a pilot, because they show real consumption without blocking anyone. Hard limits suit pool cars and capped private use. Üreticy supports both types per driver or per vehicle, and drivers can see their sessions and remaining kWh quota in the driver mobile app. See how kWh quota rules work.

Note that a kWh quota controls how much energy is used over a period. It does not control how much power is drawn at the same moment. Managing peak power at a depot is a separate topic, covered in our smart charging guide.

Cost allocation per driver, vehicle and cost center

Finance teams usually want charging costs allocated in the same way that fuel costs were allocated. Common models include:

1. Per vehicle: energy is booked to the vehicle, which fits total-cost-of-ownership reporting.
2. Per driver: energy is booked to the employee, which fits company-car policies and private-use settlement.
3. Per cost center or department: drivers or vehicles are mapped to cost centers, and totals are rolled up for each department.
4. Per site: energy is booked to the location, which fits facility budgets and electricity invoice checks.

The CSMS provides the measured energy per session. The price per kWh comes from your electricity contract or an internal transfer price. The calculation and the cost-center mapping are usually done in a spreadsheet or the ERP system.

Reporting that fleet managers actually use

Useful reports include:

• Energy by station, driver, vehicle and date range.
• Session history filtered by station, connector, driver, card, plate or date.
• Rejected authorizations, to find lost cards, misconfigured rules or unauthorized attempts.

Üreticy provides these reports with CSV export for spreadsheets and branded PDF export for management reports. Alerts for faults, disconnections, command timeouts and limit warnings help the team react before drivers are affected.

Integrating with fleet management and ERP systems

Once the pilot is stable, manual exports become a bottleneck. Integration sends charging data automatically to the systems that already hold vehicle and cost data.

• Fleet management systems: add energy per vehicle to telematics and maintenance data.
• ERP and accounting: post monthly charging costs per cost center.
• BI tools: combine charging data with route and utilization data.

A REST API lets these systems pull data on a schedule, and webhooks push events such as "session started" or "session stopped" in near real time. Üreticy offers a REST API with keys managed in the dashboard and HMAC-signed webhooks; see the charging API and webhooks page for details.

A practical rollout plan

1. Define the policy. Decide who may charge where, whether private charging is allowed, and how costs will be allocated.
2. Choose OCPP-compliant hardware. Require OCPP 1.6J at minimum, and prefer chargers that support OCPP 2.0.1 for new purchases.
3. Connect chargers to the CSMS. Enter the CSMS URL and charge point ID on each charger and confirm that it reports status correctly.
4. Register drivers, vehicles and cards. Link each card to a driver and each driver to their vehicles.
5. Start with soft limits. Observe real consumption for a few weeks before switching to hard limits where needed.
6. Set up alerts and team roles. Give operations staff operator access and give finance read-only or accounting access.
7. Automate reporting. Move from manual exports to scheduled API pulls or webhooks once the data model is stable.

Frequently asked questions

Üreticy is a cloud OCPP platform for fleets, with RFID cards, vehicles with plates, kWh quota rules and reports per driver and vehicle. See how Üreticy supports fleet charging or contact our team to plan your rollout.