> 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/readme.md).

# 2026

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

{% updates format="full" %}
{% update date="2026-08-18" %}

## [Release Notes | August 1 - 18, 2026](/changelog/release-notes-june-24-2026.md)

### Furnishing

■ WHAT'S NEW\
**Expanded CRA reporting: SBFE and Innovis**\
Furnishing clients can now report to the Small Business Financial Exchange (SBFE) and Innovis, in addition to the existing bureaus Equifax, Experian, and TransUnion. Reach out to your Bloom Credit account team to if you're interested in more information about reporting to either Credit Reporting Agency.\
NO ACTION REQUIRED

**Enhanced handling of reporting accounts with deceased primary consumer**\
The following changes were made to adhere to CRRG(c) reporting standards and making it seamless for our clients to continue reporting active accounts, even when the primary consumer passes away.

Deceased-only accounts now stop reporting automatically\
If a primary consumer is the only consumer on an account and passes away, we report the deceased status (ECOA code X) once, then automatically discontinue reporting that account going forward, even if statements continue to be submitted.\
NO ACTION REQUIRED

When a primary consumer on a furnished account passes away, we now automatically move any joint liable secondary consumer (co-borrower, co-maker/guarantor, or maker) into the primary consumer role in the base segment. The deceased consumer is reported once with ECOA code X, then reporting continues under the new primary consumer with no manual account updates needed.\
NO ACTION REQUIRED

<br>
{% endupdate %}

{% update date="2026-04-01" %}

## [Release Notes | April 1, 2026](/changelog/release-notes-april-1-2026.md)

New features, improvements, fixes, and more!

### 🚀 New Features

* **Expanded Reporting Capabilities for Furnishing** New Account Support (8B): We’ve added support for Deposit Accounts w/ Overdraft Protection (Account Type 8B).

### 🔧 Improvements and Fixes

* **Furnishing Compliance** Secure Bureau Submissions: We have updated our transmission protocols to align with the latest Experian and TransUnion Metro2 secure file transfer requirements.

\
\
\ <br>
{% endupdate %}

{% update date="2026-03-04" %}

## [Release Notes | Mar 4, 2026](/changelog/release-notes-mar-4-2026.md)

New features, improvements, fixes, and more!

### 🔧 Improvements and Fixes

* **Data Access Updates**
  * Foreclosure Insights: We’ve added a new is\_foreclosure boolean field (true/false) to the report. This allows for instant identification of foreclosure status on tradelines.
* **Furnishing Improvements**
  * Bankruptcy Compliance: Expanded reporting logic to ensure bankruptcy status is accurately reflected for consumers associated with business accounts.
  * Collateral Event Handling: Enhanced the furnishing engine to support reporting "Charge-Off" statuses specifically for repossessions.
  * Data Integrity Guards: To prevent reporting errors, we’ve implemented stricter validation "rails." The Open Date on an account is now locked during updates to prevent accidental or invalid changes.
    {% 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/readme.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.