MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Transformer Stations
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Transformer Stations
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Monitoring & Visualization

    • Real-Time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits and Curtailment
    • Efficiency Detection (PRRC)
    • Local Network Inspector
    • Access Monitoring
    • KPI Dashboard
    • Graph Visualization
  • Data Management

    • Events
    • Alarm Levels and Notifiable Events
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Alert Manager
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN: Address Conflicts
    • Proxy (Web Access to Plant Devices)
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Temporarily Locked
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Permission Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation

Contracts

Your contract with Mirox is concluded entirely on the platform. A contract administrator of your organization enters the company data, downloads and reviews the documents, and signs the framework agreement with a code sent by e-mail. The contract is effective the moment the signature completes — there is no paper, no countersignature and no waiting for a manual release. Project companies that operate individual plants join the agreement afterwards through an accession, signed the same way.

The Path at a Glance

  1. An organization Admin designates one or more members as contract administrator (Team tab).
  2. The contract administrator opens the Subscription page and completes the company data on its Contract tab.
  3. They review and download the documents — the framework agreement, its annexes and the generated party page.
  4. They sign with a 6-digit code sent to their e-mail address. The contract is effective immediately and the confirmation arrives by e-mail.
  5. Optionally they set up SEPA direct debit for the main company.
  6. They add project companies and declare each one's accession together with its SEPA direct-debit mandate.
  7. They assign the plants to the right company and, where it fits, group small plants into payment bundles.

Contract Administrator

Only a contract administrator can sign or change anything on the Subscription page. The designation is a label on an existing membership, not a separate role:

  • An organization Admin sets it in the Team tab: open the member's actions menu, select Edit Role and switch on Contract administrator. Admins can designate themselves.
  • Any member who has joined can be designated, whatever their organization role — except External members.
  • Designated members show a Contract admin badge in the team list. The label ends when the membership ends; an Admin can remove it at any time.
  • Mirox does not take part in the designation — whom your organization authorizes is your decision.

Admins without the label

Organization Admins who are not contract administrators can still open the Subscription page. On the Contract tab they see only a hint explaining how to designate a contract administrator in the Team tab and a one-line contract status (signed, not signed or terminated). They see none of the cards — company, payment, project companies, documents — and cannot download anything. On the Parks tab they see the plant list but cannot change it. Managing the contract is up to the contract administrators. All other members do not see the page.

See Managing Member Permissions for the Edit Role dialog.

The Overview

Above its two tabs, the Subscription page sums up your subscription:

  • Contract — the state of your framework agreement: no contract, draft, ready to sign, signed (with the date it started or starts), notice given (with its last day) or terminated.
  • Onboarded parks — how many plants of your organization are already onboarded, that is, their data collection has been started, for example "12 of 15".
  • Subscriptions — your billing units for solar and battery storage plus your wind turbines, broken down by subscription model.
  • Yearly cost — what all plants of your organization cost per year as they are set up now (subscription model and bundles), at the prices of the current price list, net of VAT. Plants that are not onboarded yet count too. Below it you see the same amount per month.
  • Cost per MW — the yearly cost divided by the installed capacity; solar MWp, storage MWh and wind MW count 1:1. A part whose capacity is unknown, and a wind farm without a rated power or without turbines, counts on neither side.

Notes below the figures point out where they are approximate — for example, a part without a known capacity counts as one billing unit and is left out of the cost per MW, and a wind farm without turbines costs nothing yet. The price list the figures are based on is named next to them; its info icon (i) shows the yearly prices. How the figures are calculated is described under Prices.

The Contract Tab

Open Subscription from your user menu. Open in Mirox The page has two tabs: Contract, where it opens, and Parks, where you assign plants and manage payment bundles.

The Contract tab shows the status of your framework agreement and everything needed to sign it, in the order you work through it.

Company

The company is your organization's own legal entity — the party that appears in the contract. You enter:

  • Company name and legal form (for example GmbH, GmbH & Co. KG, AG)
  • Address — street and house number, postcode, city, country
  • Commercial register — the register court (for example "Amtsgericht Hamburg") and the register number (for example "HRB 123456")
  • Authorized representatives — the person or persons who legally represent the company, exactly as they should appear in the contract
  • E-mail (invoices) — the company's e-mail address; invoices and the signed documents go there
  • VAT ID

The VAT ID is checked against the EU VAT Information Exchange System (VIES):

  • Companies in Germany: the VAT ID is optional. If you enter one, it is checked; an invalid result shows a warning but does not stop you.
  • Companies outside Germany: the VAT ID is required and must be confirmed as valid by VIES before you can sign, because tax-free invoicing depends on it.

The tab lists which fields are still missing. Signing becomes available once the list is empty.

Warning

The VAT check relies on the external EU VIES service. If VIES is temporarily unavailable, try the check again later — the ID is never marked as valid without a successful check.

Documents

The Documents section lists the complete contract set:

  • the Mirox framework agreement (Rahmenvertrag)
  • Annexes 1–7: service description, price list, service level agreement (SLA), requirements, data processing agreement, change process, and data & AI rights
  • the party page, generated from your company data, with both parties and the signature blocks

Every document can be downloaded before you sign, so you can review it and store it permanently. Each one carries a document ID and a checksum (a fingerprint of the file's exact content). The party page lists the IDs and checksums of all documents in the set, so it is always clear which version you signed.

If you change company data before signing, the party page is generated again with the new data. You always sign exactly the documents that are shown.

Signing the Framework Agreement

When the company data is complete, the contract administrator selects Sign contract:

  1. Confirm the declaration: you are authorized to bind the company, and you have read the documents.
  2. A 6-digit code is sent to the e-mail address of your Mirox account. The code is valid for 10 minutes and allows 5 attempts; you can have a new code sent at any time.
  3. Enter the code. The signature completes.

The framework agreement is effective immediately. There is no countersignature step — Mirox's acceptance is part of the generated documents. You then receive by e-mail:

  • the contract confirmation, which records the time of signing, the signing account, its e-mail address, the IP address and the checksum of the signed documents
  • the signed party page

Both are also available for download on the Contract tab at any time.

Tips

The code goes to the e-mail address of the contract administrator's own Mirox account. Make sure the person who signs can receive mail at that address. If another contract administrator starts a new signing, it replaces the previous unfinished one.

Payment for the Main Company

Setting up payment for the main company is optional. You choose between:

  • SEPA bank transfer — you receive an invoice and pay it from your bank.
  • SEPA direct debit — Mirox collects the amount automatically.

A direct-debit mandate is signed with the same e-mail-code procedure as the contract: you enter the IBAN and account holder, confirm, and enter the code. The bank and BIC are determined from the IBAN automatically. The signed mandate can be downloaded as a PDF at any time.

The payment card is always shown on the Contract tab. A mandate can be set up or changed only while a framework agreement is signed — including one that starts in the future — or while a terminated one is still within its notice period. You can also enter the SEPA details in the company dialog on the way to signing.

Project Companies and Accessions

Many plants are owned by separate project companies (Projektgesellschaften). Once the framework agreement is signed, the contract administrator can add them so that each one joins the agreement through its own accession agreement (Beitrittsvertrag).

To add a project company:

  1. Add a new project company and enter its company data — the same fields as for your main company, plus the invoice e-mail address to which its invoices are sent.
  2. Enter its SEPA direct-debit details: IBAN and account holder. Project companies always pay by direct debit.
  3. Review the summary: company, invoice e-mail, masked IBAN and creditor details. The accession agreement, the framework agreement and the annexes are available for download before you sign.
  4. Sign with the e-mail code. The accession and the direct-debit mandate are declared in one signature.

The accession is effective immediately. The accession confirmation (Beitrittsbestätigung) and the documents are stored on the Contract tab and sent to you by e-mail.

Good to know:

  • Each project company can have one active accession at a time.
  • Your organization — the original customer — remains the operational platform administrator for the project company.
  • If you close the dialog before signing, the project company stays in the list as a draft; you can continue or discard it later.
  • Open a project company in the list to see its documents, the signing record and its mandate.

Termination

Contract administrators can terminate:

  • The framework agreement — with three months' notice to the end of a month. Terminating the framework agreement ends every accession with it.
  • A single accession — with three months' notice to the end of a month. The project company's direct-debit mandate is revoked.

A termination takes effect at the end of the last day of the third month after the month in which you give notice — for example, notice given in March ends the agreement on 30 June. This last day is shown before you confirm and afterwards in the history. Terminated contracts and accessions remain in the history with all their documents and confirmations.

A new framework agreement can be signed already during the notice period. It starts on the day after the old one ends; until then it is shown with Starts on and its start date.

Terminating an agreement that has not started yet

A framework agreement signed during its predecessor's notice period has not started yet. If you terminate it, it is not terminated but deleted — it never applied. It disappears from the history, the previous agreement continues until its end, and the existing direct-debit mandate stays in place. You can replace the mandate from the payment card.

What Changes After Signing

The company data printed in the contract is locked while a signed contract or accession refers to it: company name, legal form, address, register court and number, authorized representatives and VAT ID can no longer be edited. The invoice e-mail remains editable.

Once the contract is terminated — already during the notice period — the data becomes editable again for the next contract. The signed documents keep the data exactly as it was at signing.

Your Records

For every signature — framework agreement, accession or mandate — the platform keeps a permanent record:

  • the exact documents and their checksums
  • the time of signing
  • the signing account and its e-mail address
  • the IP address from which the signature was made

This is what makes the signature an advanced electronic signature: anyone can later verify who signed which version of which documents, and when.

Assigning Plants

Every plant of your organization is paid for either by your main company — the one that signed the framework agreement — or by one of your project companies. You set this on the Parks tab of the Subscription page. Mirox system administrators can open the page for any organization.

The list has one row per billed part of a plant. A solar plant, a battery storage system (BESS) and a wind farm are one row each. A solar plant or wind farm with its own battery has two rows — the plant part and the battery — told apart by the icon in the Type column. Each part has its own paying company and its own bundle. Inactive plants are listed too. Plants your organization only sees through a cooperation are paid for by the organization that owns them and are not listed.

  • Default: the contract company. A part you have not assigned is paid for by the company that signed the framework agreement. This also applies to every plant you add later, so nothing needs to be done for a new plant. The table shows the contract company's name, marked Contract company.
  • Project companies. If a plant belongs to a project company, choose Assign company… in the row menu of its part. You can choose the main company or any project company whose accession is signed and still running. Project companies that are still drafts can't be chosen.
  • Several rows at once. Select the rows and choose Assign company in the bar that appears. Choosing the contract company removes an explicit choice again: the parts then follow the contract company, also when it changes.
  • Locked plants. The paying company of a plant on 3 or 5 years can no longer be changed — see Subscription Model below.
  • Before signing. Until a framework agreement is signed, the plants show No contract yet.

A project company can't be deleted while parts are still assigned to it — move them to another company first.

When an accession ends

If a project company's accession ends, its parts go back to the contract company automatically and are marked Fallback. Your choice is kept: if the project company signs a new accession, its parts return to it. When the framework agreement itself ends, the plants have no paying company until a new agreement is signed.

Subscription Model

Each plant is billed Monthly (the default), for 3 years or for 5 years. The Subscription model column shows the model of each plant, and its filter lists the plants on a given model. To change it, choose Change subscription model… in the row menu, or select several rows and use the same button in the bar.

Plants linked through payment bundles always share one model. This includes a plant whose solar part and battery are in different bundles: it links both bundles. A change therefore applies to the whole group — the dialog lists every affected plant and asks you to confirm, and then all of them change together.

Prices

Prices follow the price list (annex 2 of the framework agreement). All prices are net, plus VAT.

Subscription modelSolar / battery storage, per billing unitWind, per turbine
Monthly€150 per month (€1,800 per year)€45 per month (€540 per year)
3 years, paid in advance€4,860 (€135 per month)€1,260 (€35 per month)
5 years, paid in advance€6,000 (€100 per month)€1,500 (€25 per month)

How many billing units a plant needs:

  • Each billed part counts as a plant of its own: the solar part and the battery of a hybrid plant are billed separately.
  • A solar part counts with its DC peak power (MWp), a battery part with its storage capacity (MWh).
  • A part up to 100 MW is one billing unit. Above that, every started 100 MW adds one more — 250 MW are three billing units, on every subscription model.
  • Parts below 4 MW can share one billing unit in a payment bundle: up to 4 parts with at most 4 MW together. A small part that is not bundled is one billing unit of its own.
  • A part whose capacity is not known yet counts as one billing unit.
  • Wind farms are billed per turbine, whatever their size. The battery of a wind farm is a battery storage billing unit of its own.

3 and 5 Years Lock a Plant

Choosing 3 or 5 years is final. From then on the plant is locked:

  • its subscription model can never be changed again,
  • the paying company of each of its parts — main company or project company — can no longer be changed,
  • its payment bundles can no longer be adjusted: no part joins or leaves, and a bundle can be neither renamed nor dissolved.

The lock applies to the whole group of plants linked through bundles, because they share one model. That is why, when you select 3 or 5 years and save, the dialog asks once more: it states these facts, lists every affected plant and asks whether you are sure. Only after you confirm is the model changed.

Locked plants show a lock next to their model in the Subscription model column. Their row menu no longer offers changes, and their bundle can only be viewed. If a locked plant must be changed after all, contact Mirox — only Mirox can lift a lock.

Payment Bundles

Small parts can be grouped into a payment bundle, so that they are handled as one unit for payment. Bundles are also managed on the Parks tab.

The rules for a bundle:

  • A bundle holds 2 to 4 parts, and each part can be in only one bundle.
  • Solar parts and battery parts can be bundled, also mixed in one bundle. Nothing of a wind farm can be bundled — not even its battery.
  • Together the parts may have at most 4 MW. A solar part counts with its DC peak power, a battery part with its storage capacity; MWp and MWh count 1:1.
  • The parts in a bundle may be paid for by different companies — for example one by your main company and three by a project company.
  • A battery part needs its storage capacity in the park's core data — otherwise the values from the battery datasheets of all its boxes; a solar part needs a known DC peak power. Until then the part shows Capacity unknown and can't be bundled.
  • Only on the monthly model. Bundles can be created, changed or dissolved only while every plant involved is on the monthly model. Once the plants are on 3 or 5 years, their bundle is locked: it can no longer be changed, renamed or dissolved.

The Power / Storage column shows the value that counts for a bundle. The Bundle column shows the bundle's name and, below it, its number of parts and its total, for example 3 / 4 and 3.2 / 4 MW. The info icon (i) in the column header explains the badge, the totals and the Over limit mark.

  • Create a new bundle. A part that is not in a bundle is marked Bundle eligible when it can form a new bundle with another free part on the monthly model without exceeding 4 MW; the column's filter lists these parts. Click the badge to open the dialog for a new bundle: it offers only compatible parts and shows the running total against 4 MW and the number of parts against 4. The same dialog opens from Bundle with other parks… in the row menu of an eligible part; you can also select several free parts and choose Group into bundle in the bar.
  • Change an existing bundle. Click the bundle's name in the Bundle column of one of its parts. There you add a part with Add a park — only parts that still fit are offered — remove parts, rename the bundle or choose Dissolve bundle. The parts keep their paying companies. Edit bundle… in the row menu of a bundled part opens the same dialog; on monthly parts the row menu also offers Remove from bundle.

A bundle that no longer fits

A bundle can drift over its limits later — for example when a part's capacity grows. The bundle is then marked Over limit in the table. Nothing changes automatically: adjust the bundle yourself.

Invoices

Invoices and payment methods are described in Accounting & Billing.

Related Features

  • Accounting & Billing — payment methods and invoices
  • Managing Member Permissions — the Edit Role dialog where contract administrators are designated
  • Permission System — organization roles and what each may do
  • Onboarding — where signing the contract fits in getting started
Prev
Accounting & Billing
Next
Service Certificates & Invoices
© 2026 Mirox Verwaltungs GmbH. All rights reserved. | Privacy Policy