> For the complete documentation index, see [llms.txt](https://developers.bloomcredit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bloomcredit.io/changelog/2024.md).

# 2024

Bloom Credit releases, improvements, and fixes from 2024.

{% updates format="full" %}
{% update date="2024-12-10" %}

## [Release Notes | December 10, 2024](/changelog/release-notes-december-10-2024.md)

New releases, features, improvements, fixes, and more!

### 🚀 New Releases/Features

* Finalized email and SMS notifications for Bloom+

<br>

### 🐛 Improvements and Fixes

* Fixed all identified bugs in Bloom+
  {% endupdate %}

{% update date="2024-11-26" %}

## [Release Notes | November 26th, 2024](/changelog/release-notes-november-16th.md)

New releases, features, improvements, fixes, and more!

### 🚀 New Releases/Features

* Gold attributes released

<br>

### 🐛 Improvements and Fixes

* Implemented support for Metro2 base segment generation for previous months, removing the requirement to generate current month statements when backdating updates. This allows for more flexible and efficient reporting adjustments.
* Security vulnerability updates
* Added regression test to MGTS
* Updated validations for Installment accounts during statement creation
  {% endupdate %}

{% update date="2024-11-12" %}

## [Release Notes | November 12, 2024](/changelog/release-notes-november-13-2024.md)

New releases, features, improvements, fixes, and more!

### 🚀 New Releases/Features

**Core Infrastructure Support for Bloom+:**

* Multi-Institutional Financial Institution Support: Introduced the ability to support multi-institutional sign-ups, allowing users to manage accounts across multiple financial institutions seamlessly.
* Enablement Services: Added infrastructural support for new enablement services which will allow FIs to building their own UIs for user signups while also leveraging Bloom+ transaction ingestion/processing and metro2 generation.
* Subscriptions: Added support for reporting subscription tradelines in Bloom+.
* Resolved Order Status Alignment: Addressed an issue where the order status and status message were occasionally misaligned with the order status code. This fix ensures all status elements are accurately synchronized for clearer tracking and updates.
* Enhanced Batch AR Stability: Improved stability to reduce connectivity issues, ensuring more reliable batch processing.

### 🐛 Improvements and Fixes

**Account Enhancements:**

* Enhanced account create/update validation to ensure that each account is linked to an appropriate portfolio.
* Updated charge-off validations to allow for reversals without required fields.
* Improved the speed of account creation.

**Security Enhancements and other improvements:**

* Addressed several security vulnerabilities and reinforced system integrity.
* Minor bug fixes and performance optimizations to enhance system stability and user experience.
  {% endupdate %}

{% update date="2024-10-31" %}

## [Release Notes | October 31, 2024](/changelog/october-31-release-notes.md)

New releases, features, improvements, fixes, and more!

### 🚀 New Releases/Features

Batch Account Review

* Score reasons are now returned as part of the Batch Account Review process. These score reasons provide more detail on how the model calculated the score

### 🐛 Improvements and Fixes

Batch Account Review

* Added stability/scaling update to reduce potential errors in the subscription processing workflows

Consumer Service

* Consumer Service creation/update timeouts have been extended

Furnishment Service

* Base Segment Generation: Increased generation optimization and resolved several issues to improve accuracy and data consistency.
* General Stability Improvements: Enhanced stability through comprehensive regression testing, ensuring reliability.
* Account Status: Statement balance rounding for more accurate status calculations.

**Other**

* Applied multiple security patches addressing recently identified vulnerabilities, enhancing system resilience and user data protection.
  {% endupdate %}
  {% endupdates %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bloomcredit.io/changelog/2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
