> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baselayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clearer Closure Taxonomy for Fraud Consortium Records

> Aug 20, 2026

The closure information reported with Fraud Consortium records is now split into three distinct
concepts, so a reported closure is easier to file and easier to act on:

* **Closure status**: what happened to the money at closure (written off, settled, or closed\
  with no loss).
* **Closure reason**: the specific cause (for example first-party fraud, identity fraud,\
  synthetic identity fraud, bankruptcy, business closed, unable to pay, or a compliance exit).
* **Closure family**: the bucket the reason falls into (**fraud**, **credit**, or **compliance**). Exclusion match results from `GET /businesses/{id}/exclusions` now include a derived `closure_family`, so you can tell at a glance whether a hit is fraud-driven.

`closure_family` is derived from the reason rather than reported separately, so the two can never disagree.

**Integration impact:** if you contribute records to the consortium, "paid in full" is no longer an accepted closure value - report a no-loss closure with the appropriate status and reason instead. Reading exclusions requires no changes. See [The Baselayer Fraud Consortium](https://docs.baselayer.com/docs/the-baselayer-fraud-consortium.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.