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
    • 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
  • 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
    • 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
  • 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
  • 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

Accounting & Billing

Accounting brings the commercial side of your plants into the platform: you manage billing contacts, payment methods, signed contracts and invoices in one place, and every plant you monitor is billed according to the price list — monthly, or prepaid for 3 or 5 years; see Prices. There is no spreadsheet to keep in sync — plant assignments, mandates and invoices all follow the plants you actually run.

Concept

Billing in Mirox is organized around a small set of building blocks that sit inside your organization:

  • Billing contact — the legal entity that pays: your main company or one of your project companies. It carries the company name, tax and VAT identifiers, billing address and a payment method.
  • Plant assignment — which company pays for each plant, and which small plants are grouped into a payment bundle. See Assigning Plants.
  • Payment method — how the contact pays: a SEPA bank transfer (you receive an invoice and pay it) or a SEPA direct debit (Mirox collects automatically, backed by a signed mandate).
  • Invoice — the issued, downloadable record of what was charged.
  • Framework agreement — your contract with Mirox, signed online by a contract administrator on the Subscription page. See Contracts.

The platform keeps these consistent: you cannot delete a project company while plants are still assigned to it.

Info

Billing here covers your Mirox service subscription — what you pay to run the platform. It is distinct from the power-market contracts (EEG, PPA, Direktvermarktung) that describe how your plants earn revenue. Those live under Market & Tariffs.

Billing Contacts

A billing contact is the company that will be invoiced — your main company or a project company, both entered on the Subscription page (see Contracts). For each contact you record the company name, billing address, billing email and the relevant tax identifiers, and you choose how it pays.

VAT Validation

For customers outside Germany, a VAT registration ID is required, and the platform validates it against the EU VAT Information Exchange System (VIES):

  • You can check a VAT ID on demand before saving the contact, or re-check an existing contact at any time.
  • A valid EU VAT ID for a non-German customer automatically enables tax-free (reverse-charge) invoicing.
  • The most recent successful validation is stored with the contact for your records.

Warning

The VAT check depends on the external EU VIES service. If VIES is temporarily unavailable, the check may not complete and the contact stays unvalidated until you re-run it — it does not silently mark the ID as valid.

IBAN and BIC Checking

When you enter bank details, the platform validates and tidies them for you:

  • The IBAN is checked for structural validity and returned in its properly formatted form.
  • The BIC and bank name are resolved automatically from the IBAN, so you don't have to look them up.

This applies to both payment-method types and reduces the chance of a failed transfer or a rejected direct debit.

Payment Methods

Each billing contact uses one of two SEPA payment methods:

  • SEPA bank transfer — Mirox issues an invoice and you pay it from your bank.
  • SEPA direct debit — Mirox collects the amount automatically. This requires a signed direct-debit mandate before any collection can take place.

You can switch a contact's payment method at any time. Switching to direct debit prepares a draft payment and a draft mandate that then have to be confirmed through electronic signing (see below) before collection becomes active.

SEPA Direct-Debit Mandates

A direct-debit mandate is your authorization for Mirox to collect payments from your account. The platform manages the full mandate lifecycle:

  • A mandate is created through the payment processor once you have completed electronic signing.
  • It moves through clear states — from draft and pending to valid once active, and revoked when you withdraw it.
  • You can download the signed mandate document as a PDF for your records at any time.
  • You can revoke a valid mandate, which stops future automatic collection.

Warning

Mandate setup relies on an external payment processor. If that service is briefly unavailable, mandate creation can fail and should be retried — your existing valid mandates are unaffected.

Electronic Signing

Contracts and direct-debit mandates are confirmed with Advanced Electronic Signing (AES) — a lightweight, auditable signing flow that runs entirely in the browser and your inbox. The same flow is used for the framework agreement, project-company accessions and SEPA mandates.

The steps are always the same:

  1. Start the signing session for the document you want to sign.
  2. Accept the confirmation checkbox to acknowledge the document.
  3. The platform emails you a 6-digit verification code; you enter it to verify your identity. A new code can be re-sent if it expires.
  4. Complete the signing.

When you complete a mandate signing, the platform activates the prepared direct-debit payment, registers the mandate with the payment processor, generates the official mandate document, and emails you a confirmation. Signing the framework agreement and project-company accessions is described in Contracts.

Tips

The verification code is sent to the e-mail address of the signing person's own Mirox account, so make sure that person can receive mail there. The code is single-use and time-limited.

Plants and Payment Bundles

Which company pays for each plant, and which plants are grouped into a payment bundle, is set on the Parks tab of the Subscription page. A plant you have not assigned is paid for by the company that signed the framework agreement. See Assigning Plants and Payment Bundles.

Invoices

Invoices are the issued billing records. You can list and open every invoice for your organization and download each one as a PDF. Each invoice shows its voucher number and status, the net, tax and gross amounts, the currency, and the due and paid dates together with its payment status.

Info

Invoices are generated by Mirox on your billing cycle — you do not create them yourself. The platform is where you review and download them.

Contracts

Your contract with Mirox — the framework agreement with its annexes, and the accessions of your project companies — is concluded on the Contract tab of the Subscription page by a designated contract administrator. The contract is effective as soon as the e-mail-code signature completes; a confirmation and the documents are e-mailed to you and remain downloadable.

The full flow — designating contract administrators, entering company data, the documents, signing, SEPA for the main company, project companies and termination — is described in Contracts.

Info

The framework agreement is the commercial agreement with Mirox. It is separate from power-purchase agreements and other market contracts, which describe how your plants sell energy — see Market & Tariffs.

Security and Control

Accounting is a commercial responsibility, so it is restricted to the people who carry it:

  • Everything on the Subscription page — the framework agreement, project-company accessions, payment details, mandates and plant assignments — is managed only by contract administrators: members an organization Admin has designated in the Team tab. See Contracts.
  • Organization Admins without the label see the contract status and the plant list, but cannot change anything.
  • Electronic signing ties each signed contract and mandate to a verified email confirmation, giving you an auditable record of who authorized what and when.
  • Sensitive bank details are reduced to a recognizable ending in list views rather than shown in full.

For the full picture of who can do what across your organization, see the Permission System.

Distinction From Related Features

Several features touch "contracts" and "money," and they are easy to confuse. This table shows where each one lives.

FeatureWhat it coversWhere it lives
Accounting & Billing (this page)Your Mirox service subscription: billing contacts, SEPA payments, mandates, invoices, the framework agreement (Contracts)Organization billing
Market & TariffsHow your plants earn: EEG bands, power-purchase agreements, grid-operator and tariff configurationPer-plant market config
ReportsFinancial and technical reporting documents derived from your plants and market settingsReporting

In short: Accounting is what you pay to run Mirox, Market & Tariffs is what your plants are paid for the energy they produce, and Reports turns both into downloadable documents.

Related Features

  • Contracts — framework agreement, project-company accessions and contract administrators
  • Market & Tariffs — EEG, PPA and tariff configuration that drives plant revenue and financial reports
  • Reports — technical and financial reporting derived from your plants
  • Onboarding — where contract and billing setup fits in onboarding
  • Permission System — controls who in your organization can manage billing
Prev
How Revenue Is Calculated
Next
Contracts
© 2026 Mirox Verwaltungs GmbH. All rights reserved. | Privacy Policy