> For the complete documentation index, see [llms.txt](https://docs-integration.squake.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-integration.squake.earth/notable-changes/release-notes/2025/2025-sep.md).

# Product Release Notes September 2025 – Audits, Reporting Suite & Smarter Cars, Hotels, and Integrations

* 🧾 **\[Audits] Auditable entities for CVP & audit mode**

  • Added **auditable entities models & controllers** so you can attach detailed context (CVP, contracts, etc.) to audits.

  • Publicly documented here and ready to use with **audit mode** (API consumers + auditors will care).
* 🚗 **\[Calculations – Car / US-EPA]**

  • **Car US-EPA now versioned** — allows explicit factor set selection and future-proofing.

  • Added `number_of_days` support to **car calculations** to estimate distance in km when only duration is known (great for car rentals / mobility budgets).
* 🛫 **\[Calculations – Flight]**

  • Removed distance correction for **Flight CO₂-Emissiefactoren** to better align with the official dataset.
* 🏨 **\[Calculations – Hotel] CRC hotel code lookup**

  • Added **CRC hotel code** lookup for hotel calculations, improving hotel mapping and automation for specific partner feeds.
* 🧮 **\[Carbon Report Builder] Green Travel Pledge – Train**

  • **Green Travel Pledge (train)** methodology added as an option in the Carbon Report Builder.
* 📊 **\[Reporting] New reporting suite**

  • Brand-new **Reporting Suite** released, bringing more structured analytics and improved UX for Flight/Hotel/Train/Car & transaction views (client-facing ✅).
* 🔌 **\[Integrations] Travexis**

  • **Travexis** added to the **Integrations tab**, making it easier to connect and manage this data source.
* 🛍️ **\[Dashboard & Orders]**

  • New **product cards** on the orders page — clearer layouts and better readability.

  • You can now create **orders smaller than 1 EUR** (useful for tests, pilots, or micro-contributions).
* 💶 **\[Money Collection] Metadata support**

  • Money collection purchases now support **custom metadata**, and clients can set it directly — helpful for internal allocation, cost centers, or campaign tags.

**📈 Improvements**

* 🌍 **\[Calculations & Methodologies]**

  • For **BASE-EMPREINTE**, we now fall back to the **resolved origin/destination country** when explicit country is missing.

  • Updated **fare class data** for airlines to better match reality.

  • Updated **BASE\_EMPREINTE mapping for Flight** for more consistent results.
* 🧮 **\[Train & Hotel Calculations]**

  • More **train operators** added and improved error handling in **versioned train** calculations.

  • Fixes and refinements for hotel types and star handling from earlier bug reports (see below).
* 📊 **\[Carbon Connect & Carbon Reports]**

  • Carbon Connect now renders the **correct project unit price** for transactions.

  • Carbon Reports no longer show **duplicated parameters** in the UI.
* ⚙️ **\[App & Product Pages]**

  • **App start time** improved — faster initial load.

  • Product Pages UI issues cleaned up for a smoother experience.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-integration.squake.earth/notable-changes/release-notes/2025/2025-sep.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.