It’s the first Monday of the month. The California Energy Commission is waiting for its flat file. A fleet manager is expecting the quarterly breakdown of their drivers’ sessions, costs, and charging locations. An investor wants utilization numbers for the board deck. And the maintenance team is still pulling downtime logs by hand.
AMPECO’s Report Builder is built for this: define each report once, set the schedule, and the platform handles delivery. Below is what that looks like: the data sources it draws from, the regulatory frameworks it covers out of the box, and the other use cases where the same mechanism applies.
The data responsibilities that come with running a network today
Of all the audiences expecting structured data from your network, regulators are the most demanding: on format, cadence, and completeness.
Among the regulatory frameworks AMPECO supports today: the UK’s Public Charge Point Regulations require operators of rapid charge points (50 kW and above) to demonstrate 99% annual reliability, reported in a specific format to OZEV. The US NEVI program sets a 97% uptime threshold for federally funded infrastructure. California mandates monthly flat files from EVSE manufacturers and network operators. Germany’s National Access Point reporting under the EU’s Alternative Fuels Infrastructure Regulation became mandatory in April 2026. Australia’s National Electric Vehicle Strategy ties government support to 98% per-site EVSE uptime. Five distinct data structures, five delivery requirements, five markets covered.
Beyond regulators, the list continues. Investors want quarterly performance summaries. B2B clients hosting your charge points expect billing data they can reconcile against their own records. Fleet managers need session-level breakdowns for reimbursement and cost allocation. Maintenance teams want a weekly list of faults, not a screen they have to check.
Each of these is a recurring obligation. The question is whether each one requires a manual extraction process, or whether the platform handles it on schedule.
What your network data actually contains
Operators often hold far more structured data than they realize. The Report Builder draws from data sources that cover every operational dimension of a charging network: charging sessions, charge points, EVSEs, clock-aligned charging periods (15-minute intervals), session-based charging periods, charge point downtime, EVSE downtime, operational availability, transactions, and EV driver records. These are the sources currently available through the module, and the list continues to expand.
Each source contains far more than the surface-level data visible in the back-office interface. Session records hold not just start and stop times but energy delivered, peak power drawn, connector type, tariff applied, session cost, and authorization method, among dozens of other attributes. Transaction records capture invoice references, payment method, refund tracking, settlement breakdowns, and partner-level attribution. EV driver records include subscription tier, charging allowance, driver group membership, and partner associations.
The operational availability data source deserves specific mention. It does not export raw uptime figures that someone has to process separately. Instead, it calculates reliability scores using the exact measurement formulas defined by three regulatory authorities: UK PCPR, US NEVI, and Australian NEVS, each with its own treatment of exempt time and downtime periods. The computation happens in the platform; the operator receives a result ready for submission.
Across these sources, an operator has access to everything their network generates: structured, filterable, and ready to be assembled into any report any audience requires.
How AMPECO translates regulatory requirements into ready-to-run templates
Data availability doesn’t solve the formatting problem. Each regulatory authority expects a specific column structure, field labeling, and file type. For the most demanding compliance use cases, the Report Builder has already done that work.
It includes five predefined templates, each built to match the exact requirements of a specific authority, working with any OCPP-compliant hardware on the network: National Grid (utility program), the California Energy Commission (CEC), the New Jersey Department of Environmental Protection (NJDEP), the New York State Energy Research and Development Authority (NYSERDA), and the UK Public Charge Point Regulations (PCPR). These are not data subsets with a compliance label; they match the column structure, field labeling, calculation logic, and file format each authority requires.
The UK PCPR template makes this concrete. It generates a three-sheet ODS file: one sheet for EVSE inventory, one for downtime events, one for exemption periods. The DfT’s reliability formula is applied automatically, using the correct definitions of exempt time and downtime. The operator generates the file and submits it. No formula transcription, no reformatting, no risk of calculation error.
The California integration goes a step further. The platform generates two flat files monthly (Charging Session Data and Interval Data) and sends them automatically to a designated email address. The operator configures it once under the National Registries integration; from that point, the monthly submission cycle runs without further input.
For Germany, the Mobilithek integration handles reporting to the national access point under AFIR using DATEX II format and mTLS certificate authentication, with built-in certificate expiry monitoring to prevent reporting interruptions. For CPOs under the AFIR mandate in Germany, this means the national submission is automated end-to-end: the platform manages the connection, handles authentication, and tracks certificate status. No upload step, no integration to maintain.
The list of supported regulatory frameworks will continue to expand. For operators already active in the UK, the US, Germany, or Australia, the templates needed for compliance are in the platform today.
Operating in one of these markets? Speak with the AMPECO team to see how the Report Builder handles your specific regulatory requirements.
The audiences your data already serves beyond regulators
Regulatory compliance sets the floor, but the same data extraction and delivery capability applies to every other audience that needs structured information from the network. Three use cases come up consistently among operators who have moved past manual reporting.
The first is financial reconciliation with B2B clients. Operators running multi-tenant networks (commercial sites where a landlord, parking operator, or fleet company has a billing agreement) need to send invoices backed by session-level detail. The Transactions data source includes invoice references, charge point identifiers, EVSE assignments, energy delivered per session, VAT breakdowns, and partner-level attribution, consolidating everything a client needs for reconciliation in one place rather than requiring the operator to pull from multiple screens.
The second is investor and board reporting. A CPO with capital behind it will be asked every quarter to demonstrate network performance. Monthly utilization by location, revenue per charge point, session volumes, reliability figures: defined once as a quarterly template and auto-delivered on the first day of each quarter. The mechanism that sends NJDEP data to a state agency sends performance summaries to an investor inbox on exactly the same schedule.
The third is maintenance and network operations. The downtime period data sources allow a network operations manager to receive a weekly report of all EVSEs with unplanned faults, sorted by duration with location details included. Rather than checking a back-office screen at irregular intervals, the team works from a structured list that arrives every Monday morning without anyone triggering it.
Each of these uses the same template-and-schedule mechanism as regulatory reporting. The only difference is the data selection and the recipient.
Define the template once, let the platform deliver it
All three use cases share identical mechanics. A report template defines what data to pull (the data source and specific attributes), any filters to apply (by country, partner, charge point tag, or regulatory utility), and how to format the output. Once that is set, generation and delivery are automated.
Automatic reports run at 1:00 AM UTC on the selected cadence: daily, weekly, monthly, quarterly, or yearly. The report appears in the Generated Reports tab without anyone needing to trigger it. If the reporting period was the previous month, the report covers it. If the cadence is weekly, it covers Monday through Sunday.
Email delivery connects the output to the people who need it. Each template accepts a recipient list, a custom subject line, and a configurable message body. The generated file is delivered as a download link valid for 30 days. For a California regulatory submission or a quarterly investor update, the file arrives in the right inbox on the right date, with no manual step between generation and delivery.
Three export formats serve different audiences. CSV feeds data pipelines and BI tools. XLSX works for finance teams. ODS covers regulatory submissions that require it, including the UK PCPR. The underlying data is the same; the format matches what the audience can actually use.
The first of the month, handled
The scenario at the start of this post (four audiences, four manual processes, one Monday morning) describes how many CPOs currently operate. It is not a technology gap. The data exists. It is a configuration gap: reports that have not been set up to run on their own.
AMPECO’s Report Builder is built on a simple premise: every recurring data obligation an operator carries should be configured once and then handled by the platform. Whether that obligation runs to a regulatory body, an investor, a B2B client, or an internal team, the mechanism is the same. Define the template, set the schedule, assign the recipients.
The data obligations attached to running a charging network will grow as markets mature and new regulatory frameworks take effect. Getting ahead of them with structured, automated delivery is the difference between reporting as a recurring operational burden and reporting as something that simply happens.
Ready to see how the Report Builder works for your markets? Book a demo with the AMPECO team.
