- Where can Sub-CPOs be created in be.ENERGISED?
- How to enable automated credit run for Sub-CPOs?
- According to which prices are the credit notes created and what has to be set where?
- Summary: What needs to be considered?
- Option "Alternative self-billing-address"
In be.ENERGISED there is a function to send automated credit notes to your Sub-CPOs at the end of the month. If you activate this function, a credit note is automatically generated at the end of the month to all Sub-CPOs recorded in your instance.
Please note that in order to use the credit run for Sub-CPOs, the associated rights are required. Not every be.ENERGISED subscription has access to these rights. Therefore, check whether your subscription includes the respective right and whether you need to enable it for your user group, if applicable. More information about the general rights management can be found here.
Where can Sub-CPOs be created in be.ENERGISED?
Sub-CPOs or sub-entities are created in be.ENERGISED under User Management/Companies/ Registered Companies and can then be viewed there accordingly. In this view you have the possibility to map your company structure by defining superordinate entities and subordinate entities.
Entity is generally the name for a unit of your company structure. For example, an entity can be a user, or as in this case, one of your Sub-CPOs.
How to enable automated credit run for Sub-CPOs?
To enable the automated credit run for Sub-CPOs, first go to Finance/Tariffs & Invoicing/CPO Crediting process in be.ENERGISED.
CPO crediting process
To enable automated crediting to Sub-CPOs, please click on "inactive". You will be asked again if you want to activate the credit run. You will also be informed that this is a chargeable service.
SETTINGS FOR CREDIT RUN
CPO CREDITING PROCESS ACTIVE
If activated, an automatic credit run will be started at the end of the month to the owners of the charging stations.
AUTOMATIC MAIL SENDING
Automatically sends the created credit notes by email.
ALLOW ZERO-AMOUNT CREDIT-NOTES
If this field is set to "YES", credit notes with an amount of 0.00 EUR (or other currency), will also be created for the respective month.
Defines the language of the credit note.
TAX AND PAYMENT CONDITIONS
CREDIT NOTE CONFIGURATION
Defines from which invoice number range the automatic credit notes are created. Only invoice number ranges for which Valid for document type "Credit note" has been selected are available for selection here.
You can configure your invoice number ranges under Finance/Settings/Invoicing numbers. You can find more detailed information about invoice number ranges here.
Defines the tax account for credit notes, which in turn is drawn from the tax types created.
Under Finance/Settings you can create and edit the tax rates. For detailed instructions, see the article Configuring Accounts and Tax Rates.
DISCOUNT ON COMMUNITY CHARGING PROCESSES
Defines the discount in percent on COMMUNITY charging processes. This discount affects the payout according to the COMMUNITY rates set at the stations in percent.
Example: At a station of your Sub-CPO, the COMMUNITY tariff COM144 is used at charging point A with a certain payout amount per kWh. You have entered the value "10" (10%) in the above field. If a COMMUNITY charging process now takes place at charging point A, 90% of the total payout in this case goes to your Sub-CPO.
Defines the revenue account for credit notes. If you have any questions regarding this, please contact your accounting department.
START DATE FOR CREDITING
The date from which credit notes for charging processes are created.
For example, if the charging processes are to be automatically credited from the month of October, set the date to 01.10.2022.
According to which prices are the credit notes created and what has to be set where?
In general, it should be noted that the credit notes are created based on the purchase prices of the charging processes for which the respective Sub-CPOs are configured as owners of the charging station.
However, there are two use cases to distinguish here, which are explained in more detail below.
Case 1: "External" charging processes - the roaming case
The charging station is located in your be.ENERGISED instance, the identification medium is created automatically as a roaming charging card.
Example: One of your Sub-CPOs owns a charging station. The charging station must be assigned to an entity (in the charging station data sheet under Edit/Basic information, your Sub-CPO is registered as the owner).
At a charging point of this station, a charging process is started via app, scanning of the QR code (Direct Payment) or external charging card. These authorizations are authentication media unknown to you, which is why we are talking about "external" roaming charging processes here.
A charging process via the be.ENERGISED Hub via COMMUNITY is also considered an external charging process. In the first instance, the "charge point rate" stored at the connectors is applied. Otherwise, the COMMUNITY tariff is used.
For "external" charging, the credit amount is based on the "charge point rate", more precisely according to the purchase cost rate deposited there. In general, it is recommended to store a charge point rate, as this allows you to define the payout amount more precisely and you are not bound to the "DISCOUNT ON COMMUNITY CHARGING PROCESSES" (see below) function, which is applied globally.
If no charge point tariff is stored, the COMMUNITY tariff selected by your sub-CPO at the respective charge point will be used. The purchase price of the COMMUNITY tariff is the payout price for the charging station owner, in this case your sub-CPO.
If you have set a "DISCOUNT ON COMMUNITY CHARGING PROCESSES" as described above, the payout amount will be adjusted accordingly.
Case 2: "Internal" charging processes
We refer to "internal charging processes", where both the authentication media owner and the charging station are located in your be.ENERGISED instance. For such a charging process it is necessary to create a corresponding EMP sales tariff/EMP sales tariff (managed by eMSP.OPERATIONS) with a purchase cost rate, which is then used to credit your Sub-CPO.
The following example will illustrate this.
As Company XY, you have your own be.ENERGISED instance through which you manage the charging stations of other companies. One of these companies is Company A, which has three charging stations. There is also Company B in your company structure. Company B's customers (EV drivers) want to charge at Company A's charging stations.
1. You create an EMP sales tariff/EMP sales tariff (managed by eMSP.OPERATIONS) with sales cost rate. Here it may be necessary to specify an exact pricing configuration. In the above case, for example, this would be the "Operator" price configuration (but other price configurations such as Charge point, Connector type, etc. can also be used). Company B is specified here as the operating company, since Company B is the issuing company for the authentication medium.
2. You add a purchase cost rate in this tariff. This will be used in the crediting process to your Sub-CPO, i.e. Company A. Again, a more specific pricing configuration can be created. In this case, that would also be "Operator", but this time with Company A, since Company A is the owner of the charging station.
3. Assign the just created tariff to the authentication medium. In this example, Company B is to be entered as the issuing company in the authentication medium.
Summary: What needs to be considered?
- You have activated the function CPO Crediting process.
- You have created an invoice number range for credit notes and added it accordingly in the menu item CREDIT NOTE CONFIGURATION.
- The charging station is assigned to the Sub-CPO and/or the authentication medium is also assigned to the corresponding entity.
- A charge point rate is stored at the station (or at least a COMMUNITY tariff)
Again for explanation: If a charge point rate with a purchase cost rate is stored at the charging station, more precisely at a connector, then it overwrites the settings regarding DISCOUNT ON COMMUNITY CHARGING PROCESSES and the stored purchase price in the COMMUNITY tariff during COMMUNITY charging processes.
A charge point rate should be used if you wish to freely determine the purchase price yourself, regardless of what is specified in the COMMUNITY tariff.
For bilateral roaming (be.ENERGISED Hub or own interfaces) a charge point rate incl. purchase prices is required. A discount on COMMUNITY tariffs is no longer applicable!
- The corresponding EMP sales tariff/EMP sales tariff (managed by eMSP.OPERATIONS) is assigned to the authentication medium.
- The EMP sales tariff/EMP sales tariff (managed by eMSP.OPERATIONS) has a sales cost rate and purchase cost rate assigned and, if applicable, the corresponding price configurations configured.
- If you do not use a charge point rate: if necessary, fill in the DISCOUNT ON COMMUNITY CHARGING PROCESSES field.
Option "Alternative self-billing-address"
As described above, you use these settings to create self-bills for the respective sub-entities in your company structure. If your company structure is very branched and your Sub-CPOs are assigned to superordinate entities and you want the respective self-bill of the Sub-CPO to be issued to the superordinate entity, then you can make this adjustment via the field Alternative self-billing-address.
To do so, enter be.ENERGISED and go to User management/Companies/Registered Companies.
In the following example, the superordinate entity "Demonstration Company" has subordinated the Sub-CPOs "Test XY", "Test 12" and "Test 34".
Generally, each of these Sub-CPOs would receive a self-bill. However, in order to issue the self-bill of these Sub-CPOs to the superordinate entity, you must select the superordinate entity in the field Alternative self-billing-address, which can be accessed under Update Data. In this example, the entity "Demonstration Company" is selected.
These settings would need to be made for all Sub-CPOs whose self-bill is to be issued to a superordinate entity.
These settings will then be applied to the next invoice run.
Version: 2022-11-15 09:32:20 UTC
Article is closed for comments.