Skip to main content

Datastructure Gridware to ERP Next - ER Modell + Use Cases ENG

drawing-11-1771238007.png

RULES: 

WerWho erhältreceives Rechnung:the invoice:
Contractor = Customer (Organisationorganization oderor Individuum)individual) /Vertragskunde odercontractual Ad-Hoc-Endkundecustomer or ad-hoc end customer

Who receives a credit note / payout:
Wer bekommt eine Gutschrift/Auszahlung? = Supplier (CPO) oderor Customer (beiin Dienstwagen)the company car use case)

Who only uses the service:
Wer nutzt nur? = End User (mussoften oftexists nuronly fürfor Zuordnung/Reportingassignment/reporting existieren)

purposes)

Geldströme:MONEY FLOWS: 

A) EinnahmenRevenue (Money-In)

    -

    EndkundeEnd customer / Vertragspartnercontractual zahltpartner fürpays Ladevorgängefor
      charging sessions
      via Invoice/SEPA,SEPA, oderor Direct Payment (Payter/Stripe/Payter / Stripe / PayPal), oderor Pay-as-you-go Contract Giver zahlt für Ladepunkte/Service (Miete/Betrieb/Backend/Hardware)

      B) Ausgaben (Money-Out)

        becharged zahlt Gutschrift an den- Contract Giver
          pays typischerweisefor “Energieumsatzcharging infrastructure / Standortanteil”services
          (e.g., rent / operations / backend / hardware)

          B) Expenses (Pass-Money-Out)

          - becharged pays a credit note / payout to the Contract Giver

          - Typically: energy revenue / location share (pass-through)

          -

          Optional: becharged zahltpays Erstattungenreimbursements

          C) MargeMargin

          becharged verdienttypically indoes dernot Regelearn nichton ampure “reinenpass-through Durchlauf”energy (Energie)revenue, sondernbut an:rather on:

          - Service / platform fees
          Example: M100035 – Operations management fee 10%

          - Subscription payments
          Example: Charge & Share

          - Charging hardware operation fees
          Example: M100213 – Operation of charging infrastructure

          Important for ERP: clearly separate

          • Service-/Plattformgebühren: M100035:

            Pass-through Kostenamounts Betriebsführung(transitory 10%items

          → Abonnement-Zahlungen:paid Chargeout & Sharelater) Hardware Ladepunkt-Gebühren:

          Own Bspw.revenue M100213:(service/platform Betriebsführungfees)

          von Ladeeinrichtungen

          Wichtig für ERP: sauber trennen
          - Pass-through (durchlaufender Posten → Auszahlung später)
          - Eigener Umsatz (Fee)

          USE CASES :

          USE CASE 1: LadenCharging imat Unternehmen/beima Mandantencompany / tenant location
          (Mitarbeiter/Vertragskunde)Employee -/ contractual customer)

          Contract "type: “Usage Contract (billable)"”

          BEISPIELexample Unternehmen:Company: https://cloud.becharged.de/backoffice/contracts/251 
          BEISPIELexample Kunde: 
          BEISPIELexample Wohngesellschaft/Vermieter:landlord: https://cloud.becharged.de/backoffice/contracts/306 

          drawing-11-1770797781.png

           

          drawing-11-1773221761.pngdrawing-11-1773221761.png

          USE CASE 2: LadenCharging imat Unternehmen/beim MandantenCompany/Mandate (Besucher/Visitors, E-Fahrer)car drivers) - Public Charging - Contract: "Adhoc usage contract"

          BEISPIEL:Example: https://cloud.becharged.de/backoffice/contracts/286 

          drawing-11-1770793527.pngdrawing-11-1773390159.png

          Use Case 3:Charging Ladenat im Unternehmen/KundeCompany/Mandate (Besucher/E-Fahrer)Car Driver) - Roaming übervia Hubject EMP-VertragContract
          BEISPIEL:example: ? 

          drawing-11-1770793425.pngdrawing-11-1773693798.png

          USE CASE 4: DienstwagenCompany Car - Employee receives charging box at his home, charges at home - supplies with electricity, company pays for electricty 
          BEISPIEL:Example: https://cloud.becharged.de/backoffice/contracts/484 

          drawing-11-1770793399.pngdrawing-11-1773694328.png

          TRANSLATE: 

          RULES:

          Who receives the invoice: Contractor = Customer (organization or individual) / contract customer or ad-hoc end customer
          Who receives a credit note / payout: Supplier (CPO) or Customer (in the company car use case)
          Who only uses the service: End User (often only needs to exist for assignment/reporting)

          Money flows:

          A) Revenue (Money-In)

            End customer / contract partner pays for charging sessions
            via invoice/SEPA, or direct payment (Payter/Stripe/PayPal), or pay-as-you-go

            Contract giver pays for charging points/services (rent/operations/backend/hardware)

            B) Expenses (Money-Out)

              BeCharged pays a credit note to the contract giver
              typically “energy turnover / site share” (pass-through)

              Optional: BeCharged pays reimbursements

              C) Margin
              BeCharged typically does not earn on the “pure pass-through” (energy), but on:

                Service/platform fees: M100035: operations management cost 10%

                Subscription payments: Charge & Share

                Hardware/charging point fees: e.g. M100213: operations management of charging infrastructure

                Important for ERP: separate clearly

                  Pass-through (clearing account → payout later)

                  Own revenue (fee)

                  USE CASES:

                  USE CASE 1: Charging at the company / at the client (employee / contract customer) — Contract “Usage Contract (billable)”

                  Example company: https://cloud.becharged.de/backoffice/contracts/251
                  Example customer:
                  Example housing association/landlord: https://cloud.becharged.de/backoffice/contracts/306

                  drawing-8-1770201371.png