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

# Experian UCC Filings

## Experian UCC Filings

Use this service to retrieve Uniform Commercial Code (UCC) filing summaries, trends, and filing details associated with an Experian business.

## Requirements

| Application field | Requirement | Notes |
| - | - | - |
| Business country | Required | Provide the business country code. This service supports United States business information. |
| Business legal name | Conditional | Required when the application does not already have a Business Identification Number (BIN). |
| Business city | Conditional | Required when the application does not already have a BIN. |
| Business state | Conditional | Required when the application does not already have a BIN. Use the two-letter state code. |
| Business street, ZIP code, telephone, and EIN | Optional | These fields can improve Business Match results when Lendflow must obtain a BIN. |
| Business Identification Number (BIN) | Conditional | Required to run UCC Filings. If it is unavailable, Lendflow runs Experian Business Match and uses the result with the highest numeric reliability code. The service does not run if Business Match returns no result. |

## API flow

The dashboard starts a manual run with `PUT /api/int/applications/{application_id}/enrich` and provider `experian_uccs`. This is an internal dashboard route, not a supported public integration endpoint.

1. Add the `experian_uccs` attribute to a published Data Orchestration template.
2. Call `POST /api/applications/{application_id}/data_orchestration/execute` through [Execute Data Orchestration](/api-reference/data-orchestration/execute-data-orchestration) with a bearer token, `template_id`, `application_id`, and `stage_id` when required.
3. The endpoint schedules the orchestration and returns `{"data":{"executed":true}}`, not the Experian result.
4. Retrieve the result with `GET /api/applications/{application_id}/commercial_data` through [Get Commercial Data](/api-reference/workflow-management/get-commercial-data), using `services[]=experian_uccs`. Read the provider result from `data.commercial_data.experian.uccs`, status from `data.statuses.experian.uccs`, latest date from `data.dates.experian_uccs`, and stored request from `data.request_data.experian.uccs`.

The orchestration attribute checks saved UCC data first. If its required value is absent, it runs the Experian prerequisite synchronously. Data Orchestration requests detail and disables summary by default; Lendflow can retain previously stored top-level UCC result sections when a later run returns another section.

| Value | Dashboard data path |
| - | - |
| Response | `commercialData.experian.uccs` |
| Status | `commercialData.statuses.experian.uccs` |
| Submitted request | `commercialData.request_data.experian.uccs` |

The provider request always includes `bin` and `subcode`. A normal direct service run requests `uccFilingsSummary: true` and `uccFilingsDetail: true`.

## Data Orchestration availability

| Capability | Availability |
| - | - |
| Primary attribute | `experian_uccs` (`UCCS`) |
| Prerequisite behavior | Runs Experian UCC Filings only when the needed saved section is absent |
| Execution | Synchronous prerequisite |
| Reuse | Existing saved data is reused when it satisfies the selected attribute |

## What the service returns

| Result area | What it contains | How to interpret it |
| - | - | - |
| `businessHeader` | Identity data for the business associated with the BIN. | Confirm that the result belongs to the intended business. |
| `uccFilingsSummary` | Total filing count and time-bucketed filing trends. | Trend buckets separate original, derogatory, released, continued, amended, and assigned activity. |
| `uccFilingsDetail` | Filing action, location, collateral, secured party, assignee, and original filing linkage. | Each array item is one provider record. |
| `uccFilingIndicator` | Top-level indicator used by Data Orchestration. | `true` means UCC information is reported. |

## Representative response

```json theme={"system"}
{
  "businessHeader": {
    "bin": "000000000",
    "businessName": "SAMPLE INDUSTRIES",
    "address": {"city": "AUSTIN", "state": "TX", "zip": "78701"},
    "customerDisputeIndicator": false
  },
  "uccFilingsSummary": {
    "uccFilingsCount": 2,
    "uccFilingsTrends": [
      {
        "date": "2024-06-30",
        "count": 2,
        "derogatoryCount": 0,
        "releasesAndTerminationsCount": 1,
        "continuationsCount": 0,
        "amendedAndAssignedCount": 0
      }
    ]
  },
  "uccFilingsDetail": [
    {
      "dateFiled": "2024-02-15",
      "legalType": "UCC",
      "legalAction": "Original Filing",
      "documentNumber": "SAMPLE-UCC",
      "filingLocation": "TX",
      "collateralCodes": [{"code": "4", "definition": "Machinery and Equipment"}],
      "securedParty": "SAMPLE SECURED PARTY",
      "assignee": null
    }
  ],
  "uccFilingIndicator": true
}
```

## Response attributes

### Summary and trends

| Attribute | Type | Meaning | Possible values or units | When returned |
| - | - | - | - | - |
| `businessHeader.bin` | String | Experian BIN. | Experian identifier. | When Experian identifies the business. |
| `businessHeader.businessName` | String | Name associated with the matched record. | Business name. | When available. |
| `uccFilingsSummary.uccFilingsCount` | Number | UCC filings on file. | Count. | When summary was requested and returned. |
| `uccFilingsSummary.uccFilingsTrends` | Array | Periodic UCC activity. | Experian trend buckets. | When trend data is available. |
| `uccFilingsTrends[].date` | String | End date for the trend bucket. | `YYYY-MM-DD`. | For each trend bucket. |
| `count` / `derogatoryCount` | Number | Original filings and those classified as derogatory. | Count. | In each trend bucket when supplied. |
| `releasesAndTerminationsCount` | Number | Released or terminated filings. | Count. | In each trend bucket when supplied. |
| `continuationsCount` | Number | Continued filings. | Count. | In each trend bucket when supplied. |
| `amendedAndAssignedCount` | Number | Amended or assigned filings. | Count. | In each trend bucket when supplied. |
| `uccFilingIndicator` | Boolean | Whether UCC information is reported. | `true` or `false`. | When supplied by Experian. |

### Filing details

| Attribute | Type | Meaning | Possible values or units | When returned |
| - | - | - | - | - |
| `uccFilingsDetail[].dateFiled` | String | Filing date. | `YYYY-MM-DD`. | For each filing when available. |
| `uccFilingsDetail[].legalType` | String | Record type. | `UCC`. | For each filing. |
| `uccFilingsDetail[].legalAction` | String | Current action. | `Original Filing`, `Amended`, `Assignment`, `Partial Release`, `Full Release`, `Released`, `Terminated`, or `Continuation`. | When available. |
| `uccFilingsDetail[].documentNumber` | String | Filing identifier. | Jurisdiction-specific identifier. | When available. |
| `uccFilingsDetail[].filingLocation` | String | Filing state or office. | State code or office. | When available. |
| `uccFilingsDetail[].collateralCodes` | Array | Collateral classifications. | Code and definition pairs. | When collateral data is supplied. |
| `uccFilingsDetail[].securedParty` | String or null | Party holding the secured interest. | Name. | When available. |
| `uccFilingsDetail[].assignee` | String or null | Party receiving an assigned interest. | Name. | For assigned filings when available. |
| `uccFilingsDetail[].originalUCCFilingsInfo` | Object or null | Original action linked to the current filing. | Action, state, document number, and date. | For amendments, assignments, releases, or continuations when supplied. |

Experian fixtures contain historical naming variants such as `dateField` and `collateralCode`; current consumers should tolerate provider fields being absent or variant rather than manufacturing values.

## Statuses and errors

| Signal | Meaning |
| - | - |
| Commercial-data status is `Started` | The service started but has not completed or failed. |
| Commercial-data status is `Success` | The latest run completed; inspect `data.commercial_data.experian.uccs`. |
| Commercial-data status contains an error | The run failed and the status includes its error message. |
| Orchestration status `6`, `1`, `5`, `2`, `4`, or `3` | Scheduled, started, paused, finished, missing data, or error, respectively. |
| No Business Match result | Lendflow stops before the UCC request because it could not obtain a BIN. |
| Invalid credentials, subcode, or provider response | The service records the failure and normalizes an Experian error message when available. |

An empty detail array means no records were returned. A missing or null field is unknown and must not be treated as an explicit zero or false.

## FAQ

<AccordionGroup>
  <Accordion title="Does Data Orchestration always call Experian?">
    No. It reuses saved UCC data when the selected attribute's prerequisite is already satisfied.
  </Accordion>

  <Accordion title="Why can the summary be absent in a Data Orchestration run?">
    The Data Orchestration prerequisite requests detail and disables summary by default. A normal direct run requests both.
  </Accordion>

  <Accordion title="Does this service require an Experian BIN?">
    Yes. Lendflow automatically runs Experian Business Match when the BIN is missing.
  </Accordion>

  <Accordion title="Is a UCC filing automatically derogatory?">
    No. Experian reports a separate `derogatoryCount`; do not classify every filing as derogatory.
  </Accordion>
</AccordionGroup>