Release notes April 2026

Large Inventory Pivot; SECR & MITECO Reports; UBA DE; Steam, Heat, and Cooling now fully support dual reporting; and Enhanced column mapping during Excel imports

The Pivot functionality now supports large inventories

We have made big improvements to how data is fetched to the Pivot found under Dashboards. Previously, this view was not available to companies with inventories exceeding 5000 inventory lines. This limit is no more. We have no new limit enforced and during testing, Pivot functioned as expected using inventories with more than 100,000 lines.

We also added fields to the Pivot. GHG Protocol and ISO 14064-1 can now be shown using references or reference groups.

Reports now support MITECO

We now support MITECO reporting in line with Spain’s Royal Decree 214/2025, enabling compliance with Spanish national carbon footprint and reporting requirements. The report also includes an ISO 14064-1 aligned appendix provided in Spanish.

You can find the MITECO reports under the Reports section.

Updates to the SECR Report

The SECR report has been updated to include a dedicated section outlining which activities are covered in the GHG inventory, along with revised terminology aligned to the latest SECR reporting guidelines and standardized number formatting.

You can find the updated SECR reports under the Reports section.

Release of UBA DE 2024 v1.1 and 2025 v2.1

We have integrated comprehensive emission factor databases from the Umweltbundesamt (UBA), Germany’s Federal Environment Agency. This extensive update covers a wide range of activity types, including Electricity, Fuels, Goods by Mass, Heat and Steam, Industrial Emissions, Transport, and Waste.

The new dataset is characterized by its robust coverage of biogenic emissions and detailed supply chain stages. Users can now rely on a high degree of consistency and coherence across all categories, ensuring that your German-specific reporting aligns perfectly with local regulatory standards and scientific data. Version 2025 v2.1 (released Feb 2026) is available as preferred source, all versions are available in the emission factor library.

Dual reporting for Steam, Heat, and Cooling

We have updated our calculation engine to fully support the Market-Based (MB) and Location-Based (LB) split for Steam, Heat, and Cooling categories. Market- and location-based preferences are now centrally controlled for all scope 2 entries in boundaries. All reporting formats support dual reporting for both electricity and steam, heat, and cooling.

Enhanced column mapping during excel import

We’ve significantly improved our column mapping capabilities to make data imports more resilient and user-friendly. The system can now intelligently detect and handle common issues such as typos in column names or missing column headers. Even when column labels are incomplete or slightly incorrect, the algorithm can accurately infer the intended mapping.

This enhancement also marks an important step toward supporting highly unstructured or “raw” Excel files. Users can now import datasets with less manual preprocessing, as the system is better equipped to interpret and organize imperfect data automatically.

Minor updates & fixes

Fixes

  • Transport Mode data now maps correctly during import.

API Updates

What's New

  • GET /accounts/v2/companies/{company_id}/reporting-settings - Get Company Reporting Settings V2
  • PUT /accounts/v2/companies/{company_id}/reporting-settings - Put Company Reporting Settings V2
  • POST /measurements/v1/imports/map-columns - Post Import Map Columns
  • POST /results/v2/pivot-query - Post Pivot Query

What's Deprecated

  • GET /accounts/v1/companies/{company_id}/reporting-settings - Deprecation: 2026-10-27 - Sunset: 2027-01-25
  • PUT /accounts/v1/companies/{company_id}/reporting-settings - Deprecation: 2026-10-27 - Sunset: 2027-01-25

What's Changed

  • GET /reports/v1/reports/{report_id}/presigned-url
  • GET /accounts/v1/companies/{company_id}/reporting-settings
    • Response
      • Changed response: [403] — User access rights insufficient
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
  • PUT /accounts/v1/companies/{company_id}/reporting-settings
    • Response
      • Changed response: [403] — User access rights insufficient
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
  • POST /accounts/v1/users
    • Request
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • GET /accounts/v1/users/{user_id}
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • PUT /accounts/v1/users/{user_id}
    • Request
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • PUT /accounts/v1/users/{user_id}/send-invite
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • PUT /accounts/v1/users/{user_id}/cancel-invite
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • PUT /accounts/v1/users/{user_id}/activate
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • PUT /accounts/v1/users/{user_id}/deactivate
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Added property: language   (, optional)
        • Default value: EN  
  • POST /reports/v1/reports
    • Request
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: language   (['string']   → ['string']  )
        • Enum values changed: added PT, EN, NL, ES, IT, SV, FR, CS, DA, FI, DE  
        • Default value changed: en   → None  
        • Description changed
      • Changed property type: reportType   (['string']   → ['string']  )
        • Enum values changed: added MITECO  
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: language   (['string']   → ['string']  )
        • Enum values changed: added PT, EN, NL, ES, IT, SV, FR, CS, DA, FI, DE  
        • Description changed
  • GET /reports/v1/reports/{report_id}
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: language   (['string']   → ['string']  )
        • Enum values changed: added PT, EN, NL, ES, IT, SV, FR, CS, DA, FI, DE  
        • Description changed
  • PUT /reports/v1/reports/{report_id}
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: language   (['string']   → ['string']  )
        • Enum values changed: added PT, EN, NL, ES, IT, SV, FR, CS, DA, FI, DE  
        • Description changed
  • POST /value-mappings/v1/value-mappings
    • Request
      • Changed body: application/json  
      • Changed property type: field   (['string']   → ['string']  )
        • Enum values changed: added transportMode  
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: field   (['string']   → ['string']  )
        • Enum values changed: added transportMode  
  • POST /value-mappings/v1/value-mappings/{value_mapping_id}/ai-suggest
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: field   (['string']   → ['string']  )
        • Enum values changed: added transportMode  
  • PUT /value-mappings/v1/value-mappings/{value_mapping_id}
    • Request
      • Changed body: application/json  
      • Changed property type: field   (['string']   → ['string']  )
        • Enum values changed: added transportMode  
    • Response
      • Changed response: [200] — Successful Response
      • Schema incompatible
      • Changed body: application/json  
      • Changed property type: field   (['string']   → ['string']  )
        • Enum values changed: added transportMode  
  • PUT /accounts/v1/users/{user_id}/invite-url
    • Response
      • Changed response: [200] — Successful Response
      • Changed body: application/json  
      • Changed property type: user   (['object']   → ['object']  )
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.