> 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-oct.md).

# Product Release Notes October 2025 – Reporting Superpowers, FLIX Bus & Audits Go Visual

* 🔌 **\[Integrations] Travexis in the UI**

  • **Travexis** is now visible in the **Integrations tab**, making it easier to discover, connect, and manage the integration.
* 🧾 **\[Trips & Hotels] Richer trip context**

  • **PNR** added to trip records.

  • **Hotel name** surfaced on hotel entries.

  → Easier reconciliation between TMC data, invoices, and SQUAKE reporting.
* 🚌 **\[Calculations] FLIX Bus methodology**

  • New **FLIX Bus–specific methodology** added, enabling more accurate emissions for FLIX Bus travel.
* 📊 **\[Reporting] New controls & exports**

  • Brand-new **advanced filters** in the Reporting Suite.

  • **Export options** added to Reporting, so users can pull data for BI tools or offline analysis.

  • **Car usage type charts** introduced for better insight into how cars are used (e.g. rental vs. private, etc.).
* 📊 **\[Reporting] Make Reporting the default home (feature-flagged)**

  • New **feature flag** to make the **Reporting page the default screen** after login (opt-in per client / environment).
* 🧾 **\[Audits] First UI for audit data**

  • **Auditable Entities view** added – see which entities are tied to a given audit.

  • **Audit details view** added – inspect individual audits in more detail.

  • (Currently staged / rolling out gradually 📝)
* ✈️ **\[TIM Flights] Lat/Lng support & flexible inputs**

  • You can now use **lat/lng** to calculate flight emissions with **Google TIM**, in addition to `distance_in_km`.

  • Works regardless of whether `departure_date` is provided.
* 💰 **\[Money Collection] Cancelable purchases**

  • Money Collection purchases now support a **cancel** action, aligning them with other transaction flows.

**📈 Improvements**

* ✈️ **\[Flights & Calculations]**

  • Improved handling of **coordinate formats** in flight calculations.

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

  • Updated **fare class data** for airlines for more realistic mappings.
* 🧮 **\[Carbon Report Builder & Methodologies]**

  • **Green Travel Pledge – train** methodology added to the Carbon Report Builder.

  • Mapping for **Flight BASE\_EMPREINTE** updated for better consistency.
* 📊 **\[Reporting Suite] Better defaults & more accurate queries**

  • Default date range now always matches the actual data window.

  • Reporting URLs now always include relevant params & filters → **shareable, reproducible views**.

  • Train reporting now uses **kilometers instead of miles** and corrects date usage when querying.

  • Filters with no underlying data are automatically **disabled**, so you always see results.

  • Queries now consistently use **trip start & end dates**, improving accuracy for multi-day trips.

  • Further query & data-fetching optimizations for better performance on reporting pages.
* 🧭 **\[Travel Data]**

  • Travel Data API improvements for more robust responses.

  • Added **missing travel data fields**, improving analytics granularity.
* 🧩 **\[Dashboard & UX]**

  • Orders page now uses **better product cards** for clearer information density.

  • You can now place **orders smaller than 1 EUR** (great for testing / micro-contributions).

  • Environment banner updated and made more visible & friendly.


---

# 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-oct.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.