# Product Release Notes June-July 2024 - SAP Concur, New Integrations & Reporting Upgrades

* **\[Carbon Reporting]**

  • Unlimited carbon reports quota setting for eligible clients.

  • Added energy scope to CO₂ Emissiefactoren NL.

  • Added support for string list input in “emissions from CSV” in Carbon Report Builder.
* **\[Trust Page]**

  • Second retirement link for retired purchases.

  • Adjustments for improved display and usability.
* **\[Purchase Details]**

  • New purchase detail screen.

  • Payment reference ID now included in purchase export.

***

**📈 Improvements**

* Updated EPA factors for more accurate calculations.
* Enhanced Carbon Report Builder functionality and resolved edge-case errors.
* Expanded admin panel with additional info.
* Standardized logging and metrics across services.
* Purchase history CSV export refinements (removing ambiguous columns).
* Aligned purchase filters and icon styles in purchases table.
* Added fallback to CAR US-EPA.
* Trip data now includes more specific per-type details.
* Performance boosts to internal purchase index endpoint.
* Infrastructure and dependency maintenance.

***

**🐞 Bugfixes**

* Fixed carbon credit “canceled” state display.
* Corrected user role assignment in sandbox.
* Fixed flight number parsing issues.
* Resolved payment status and invoice price mismatches.
* Fixed customer-facing issues with sandbox switch and confirmations.
* Added fuel\_type validations for CAR BASIC methodology.
* Corrected CO₂ transaction status sync in Salesforce.
* Mapped Salesforce `Payment_Date__c` to `paid_on` in invoices.
* Fixed staging image base URLs for projects.
* Corrected type conversion errors in Carbon Report Builder.


---

# Agent Instructions: 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:

```
GET https://docs-integration.squake.earth/notable-changes/release-notes/2024/2024-jul.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.