This article describes how to register and activate a Server Energia for Italian EV-charging fiscalisation and how to complete the corresponding configuration in the RetailForce Portal.
For this article, the CPO is assumed to be the Soggetto Obbligato (Obligated Person), meaning the Italian VAT-taxable person that provides the charging service to the final consumer and collects the corresponding consideration. The Server Energia framework applies to the electronic storage and telematic transmission of consideration data under Article 2(1-ter) of Legislative Decree No. 127/2015 for charging transactions performed through charging stations where the customer is not identified.
The Server Energia framework’s registration process consists of two connected parts:
- registration and activation of the Server Energia instance with the Agenzia delle Entrate (AE); and
- configuration of the Server Energia instance and the associated Charging Sockets (EVSE - Electric Vehicle Supply Equipment) in the RetailForce Portal.
Under the Italian fiscalisation architecture, the Server Energia receives the transaction data relating to the identified Charging Sockets, serves as the first point at which the fiscal data is electronically stored, consolidates the data, generates and seals the required fiscal files, and transmits them to AE.
The individual Charging Sockets are not registered separately with AE as fiscal devices. They are configured within the RetailForce environment and associated with the relevant Server Energia, while each Charging Socket is identified through its EVSE ID and geographic coordinates.
1. Prerequisites
Before starting the Server Energia registration, the following information and access must be available:
- the CPO's Italian VAT number;
- access to the AE Fatture e Corrispettivi portal for the CPO or its authorised intermediary;
- completed accreditation of the CPO as Gestore Energia (Energy Operator) in the AE portal;
- registration of the relevant Charging Sockets in the PUN (Piattaforma Unica Nazionale – National Single Platform);
- access to the relevant Organisation in the RetailForce Portal; and
- the EVSE ID, latitude and longitude in decimal format of each Charging Socket to be associated with the Server Energia instance.
The EVSE ID used within RetailForce must correspond to the identifier under which the Charging Socket is registered in the PUN.
2. Create the Server Energia in RetailForce
Each Server Energia requires its own unique identifier, cryptographic key pair and AE-issued device certificate.
Create the Server Energia instance within the relevant CPO organisation in the RetailForce Portal.
The Server Energia instance receives a unique identifier, referred to as the matricola, consists of 15 characters:
- the first 11 characters are the Italian VAT number of the taxable person (CPO); and
- the final four characters are a progressive number, right-aligned and zero-padded where necessary.
For example:
- Italian VAT number: 12345678901
- Server Energia progressive number: 0001
- Server Energia matricola: 123456789010001
A Server Energia may process the fiscal data of multiple Charging Sockets. A separate Server Energia is therefore not required for each EVSE or charging location.
Where a CPO operates multiple Server Energia instances for administrative, regional or capacity-related reasons, each Server Energia must have its own progressive number, and each EVSE must be associated with the appropriate Server Energia within the RetailForce configuration.
3. Generate the key pair and CSR in RetailForce
Generate a cryptographic key pair for the Server Energia instance in the RetailForce portal.
Under the official AE specifications, the private key must remain within the secure Server Energia environment and must not be extracted or duplicated. For this reason, the RetailForce service instead generates a PKCS#10 Certificate Signing Request (CSR) file for the corresponding key pair and makes it available for download. The CSR contains the Server Energia matricola in its CN (Common Name) field.
Download the CSR file from the RetailForce Portal for submission to AE.
4. Register the Server Energia with Agenzia delle Entrate (AE)
Using the downloaded CSR, the CPO or its authorised intermediary logs in to the AE Fatture e Corrispettivi portal.
Ensure that the relevant CPO is selected as the utente di lavoro (working taxpayer/account) and that the CPO has completed the required Gestore Energia (Energy Operator) accreditation.
Open the Server Energia registration functionality and start the registration of a new Server Energia.
Upload the PKCS#10 CSR generated through RetailForce.
AE registers and activates the Server Energia in association with the VAT number of the taxpayer selected as the utente di lavoro (working taxpayer/account) and generates the corresponding device certificate in a file for download.
The resulting Attivato (activated) state is linked to the Server Energia registration and certificate-request process and is distinct from the subsequent operational In Servizio status.
5. Download the AE certificate
After AE has successfully processed the CSR, download the device certificate issued for the Server Energia from the AE portal.
The Server Energia device certificate is valid for eight years.
The downloaded certificate must remain associated with the Server Energia for which the corresponding CSR and private key were generated.
6. Upload the certificate to RetailForce
Return to the relevant Server Energia configuration in the RetailForce Portal and upload the certificate received from AE.
RetailForce reconciles the AE-issued certificate with the corresponding private key and stores the certificate within the secure Server Energia environment.
Once the certificate has been successfully configured, the Server Energia has the cryptographic credentials required to seal and transmit its fiscal files to AE.
7. Place the Server Energia into service in the AE portal
Once the Server Energia has been activated, its certificate has been configured and the Server Energia is ready for operation, return to the AE portal and change its status to:
In Servizio (in service / active)
Only a Server Energia whose AE status is In Servizio can successfully transmit fiscal data to AE.
8. Configure the Charging Sockets in RetailForce
The individual Charging Sockets do not require separate registration with AE. They must instead be configured and associated with the relevant Server Energia instance within the RetailForce environment.
For each Charging Socket, provide:
- EVSE ID (correspond to the identifier registered in PUN)
- Latitude, expressed in decimal degrees
- Longitude, expressed in decimal degrees
Example:
- EVSE ID: IT*ABC*E1234567
- Latitude: 41.81504840699597
- Longitude: 12.481030179698337
Where the CPO operates several Server Energia instances, associate each EVSE with the Server Energia responsible for fiscalising its transactions.
RetailForce may also support automated or bulk onboarding of Charging Sockets. Where this option forms part of the applicable RetailForce service, the EVSE configuration can be created through the supported onboarding process instead of entering each Charging Socket individually in the Portal. Contact RetailForce for the available onboarding option.
9. Transaction data required during operation
For each charging operation, the Server Energia must receive the prescribed transaction data relating to the relevant Charging Socket, including:
- Charging Socket identifier;
- latitude and longitude;
- charging start date and time;
- charging end date and time;
- energy delivered in kWh;
- gross amount including VAT;
- VAT rate;
- electronic payment type;
- Terminal ID where settlement is processed through a Payment Terminal;
- payment date and time;
- payment authorisation code; and
- payment amount.
Where penalty time applies, the Server Energia must additionally receive the relevant parking duration, gross penalty amount, VAT rate or exemption nature, and corresponding payment information.
The Server Energia stores the transaction details, consolidates the required daily fiscal data and generates, seals and transmits the corresponding fiscal files to AE.
10. Adding, changing or removing EVSEs
Changes to the Charging Socket estate are managed within the RetailForce configuration.
AE registers the Server Energia rather than the individual Charging Sockets. Therefore, adding, updating or removing an EVSE from the RetailForce configuration does not require a separate Server Energia registration or deregistration with AE.
Where an EVSE ID changes, the identifier configured within RetailForce must remain consistent with the identifier registered for the Charging Socket in the PUN.
11. Server Energia status changes and decommissioning
The CPO or its authorised representative must promptly update the status of the Server Energia through the AE portal whenever its operational status changes.
The relevant statuses are:
- In Servizio (in service / active) – used when the Server Energia is ready to transmit fiscal data.
- Fuori Servizio (out of service) – used when the Server Energia is temporarily unable to store and/or transmit daily fiscal data while its certificate remains valid.
- Dismissione (decommissioned) – used when the Server Energia is permanently taken out of operation. Its signing certificate is revoked and the Server Energia can no longer be used for fiscal storage and transmission.
- Richiesta di ripristino (restoration request) – used when the Server Energia certificate becomes unusable due to expiry or loss of integrity. A new key pair and CSR must then be generated to obtain a new certificate from AE.
12. Outage Operations and Edge Cases
The Italian Server Energia framework separates the Charging Socket from Server Energia data transfer, the daily fiscal aggregation performed by the Server Energia and the statutory deadline for transmission to AE.
Server Energia temporary outage
Where a Server Energia becomes temporarily unable to store and/or transmit fiscal data while its certificate remains valid, its status must promptly be changed to Fuori Servizio (out of service) in the AE portal.
The AE specification does not establish a maximum period for which the Server Energia may remain in this status. Once normal operation resumes, the Server Energia must be returned to In Servizio (in service) before further fiscal data can be transmitted.
The Fuori Servizio status does not extend the statutory AE transmission deadline.
Fiscal aggregation and AE transmission
The Server Energia determines the fiscal data daily for each Charging Socket, covering the transactions performed between 00:00:00 and 23:59:59 on the relevant date.
The daily fiscal data does not need to be transmitted to AE on the same day. Under the ordinary transmission timetable, data relating to transactions performed during a particular month must be transmitted no later than the last day of the following month.
For example, transactions performed in July 2026 must be transmitted by 31 August 2026.
Delayed Charging Socket data
The AE specification does not establish a separate fixed deadline within which a Charging Socket must transfer its transaction data to the Server Energia.
Where transaction data reaches the Server Energia after a communication interruption, it must remain attributable to the original transaction date and be incorporated into the corresponding fiscal data.
For example, where several days of transaction data reach the Server Energia one week later, the transactions remain attributable to their original transaction dates and must still be processed in time to meet the applicable AE transmission deadline.
Charging Socket outage threshold
The AE rules do not establish a fixed outage threshold, such as 24, 48 or 72 hours, after which a Charging Socket must be disabled because it cannot communicate with the Server Energia.
Any stricter shutdown or offline threshold may therefore be implemented as an additional operational control within the CPO's service architecture.
Failed transmission to AE
Where transmission from the Server Energia to AE fails for technical reasons other than rejection of the submitted file, the Server Energia must retry the transmission during the same day, using a minimum interval of 15–30 minutes between attempts, until the file is accepted by the AE system.
A failed transmission does not automatically require the Server Energia to be placed into Fuori Servizio. This status applies when the Server Energia is actually no longer able to perform the required storage and/or transmission functions.
Comments
0 comments
Please sign in to leave a comment.