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

# Product Release Notes November 2025 – AI Insights, CVP Certificates & Audit-Ready Everything

* 🤖 **\[AI Insights] First public release**

  • **AI Insights** is now live – surfacing insights on top of your data (usage/details depend on your plan & configuration).
* 🧾 **\[CVP] Certificates & Auditable Entities UI**

  • **CVP Certificate** released – dedicated, audit-ready certificate format.

  • **Auditable Entities UI**: visual view for CVP entities linked to audits (projects, policies, contracts, etc.).

  • **Audit details page** improved, now tighter with CVP and auditable entities.
* 📊 **\[Reporting] UX polish & context**

  • **ALO index banner** added to **Hotel reporting** to give clearer context for interpretation.

  • **Personal vs Company** pie chart is automatically hidden when one side is 100% (no more misleading “slices”).

  • **Rental days** tile hidden when value is zero to reduce noise.
* ✈️ **\[TIM & Calculations] Easier inputs**

  • **TIM calculations can now be run *****without***** flight number and airline** – helpful when only OD pair is available.

  • **Activities now support `external_reference`** and multiple calculations per activity via that reference (better mapping between your systems and SQUAKE).
* 🧾 **\[Audits] In-product guidance**

  • **Help button** added to Audits UI to guide users through audit mode & auditable entities.

***

**📈 Improvements**

* 🔍 **\[Reporting Suite] Query & UX refinements**

  • Fixed and improved **reporting page queries** for more reliable results.

  • Filters now behave correctly and no longer duplicate methodologies.

  • Filters on reporting now **respect client scoping** (trips per client) so you don’t mix tenants.
* 🧾 **\[CVP & Audits]**

  • Further improvements to **audit details pages** (layout, data clarity).

  • `VAT_number` is **no longer required** for `AuditableEntity` – fewer false blocking validations.

  • Audits now store extra IDs for better traceability:

  – `external_policy_id` on **trips**

  – `external_employee_id` on **travelers**
* 🧮 **\[Calculations & Methodologies]**

  • `external_reference` now stored on **activities**, enabling multiple related calculations and better traceability.

  • **base\_empreinte** methodology version updated for Flights and **US-EPA car versions** added.

  • Added missing **EVA codes** for trains & buses.

  • **UIC stations** updated to the latest data.

***

**🐞 Bugfixes**

* 📊 **\[Reporting]**

  • Fixed reporting page queries and filters not working correctly.

  • Fixed duplicated methodologies showing up in filters.
* 🧾 **\[Purchases & Checkout]**

  • Fixed checkout page flow and status bubble display in the purchases table.

  • Fixed failures in **certificate generation** for purchases.
* 🧮 **\[Calculations & Travel Data]**

  • Fixed Travel Data API for **hotels**.
* 🧾 **\[Audits]**

  • Fixed audit records that could **load endlessly**.

  • Fixed methodology source URL not being saved on API audit creation.

  • Audit mode fixed for multiple methodologies (including train).
* 🔌 **\[Integrations & Sync]**

  • Fixed duplicate transactions errors during **Salesforce** sync.

  • Improved handling of **Airplus ZIP files**.

  • Fixed DB schema in Travexis read model.
* 👥 **\[Users & Roles]**

  • Fixed projects cache to ensure the **correct role** is used.

  • Fixed user invitation mailer failing for users without an associated client.


---

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