> ## 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.

# Equifax Business Match

## Equifax Business Match

Equifax Business Match checks whether the application business matches a record in Lendflow's connected Equifax business dataset. The **Equifax KYB** Workflow Builder block exposes the `equifax_business_match` service for business entities.

## Requirements

| Application field | Requirement | Notes |
| - | - | - |
| Business legal name | Required | Compared with the Equifax name and legal-name fields. |
| Business telephone numbers | Optional | Normalized and unformatted variants are considered during matching. |
| Owner email addresses | Optional | Compared with the email on the Equifax record. |
| Business address line | Optional | Compared when present. |
| Business address city, state, and ZIP | Optional | Used to narrow the match when present. |

## Run Equifax Business Match

Call [Enrich Business Credit Application](/api-reference/workflow-management/enrich-business-credit-application) with `provider` set to `equifax_business_match`, then poll [Get Commercial Data](/api-reference/workflow-management/get-commercial-data) with `services[]=equifax_business_match`.

```json theme={"system"}
{
  "provider": "equifax_business_match"
}
```

The result appears at `commercial_data.equifax.kyb_search`, the lifecycle message appears at `statuses.equifax.kyb_search`, and the stored match inputs appear at `request_data.equifax.kyb_search`.

<Note>
  Equifax Business Match is not included in the current Data Orchestration service catalog.
</Note>

## What the service returns

| Response area | Meaning |
| - | - |
| Equifax business record | The complete matched row from the connected Equifax business dataset. |
| `efx_name` and `efx_legal_name` | Names used to identify the Equifax business. |
| Contact and address fields | Equifax telephone, email, address, city, state, and ZIP values. |

## Representative response

```json theme={"system"}
{
  "efx_name": "EXAMPLE BUSINESS",
  "efx_legal_name": "EXAMPLE BUSINESS LLC",
  "efx_phone": "+15125550100",
  "efx_email": "owner@example.com",
  "efx_address": "100 MAIN ST",
  "efx_city": "AUSTIN",
  "efx_state": "TX",
  "efx_zipcode": "78701"
}
```

The production response is the matched Equifax dataset row and can contain fields beyond this example. The fields shown are the ones Lendflow currently uses for matching.

## Response attributes

| Attribute | Type | Meaning | Possible values or units | When returned |
| - | - | - | - | - |
| `efx_name` | String or null | Business name on the Equifax record. | Provider text. | When present in the matched row. |
| `efx_legal_name` | String or null | Legal business name on the Equifax record. | Provider text. | When present. |
| `efx_phone` | String or null | Telephone on the Equifax record. | Provider-controlled telephone text. | When present. |
| `efx_email` | String or null | Email on the Equifax record. | Email text. | When present. |
| `efx_address` | String or null | Street address on the Equifax record. | Provider text. | When present. |
| `efx_city` | String or null | City on the Equifax record. | Provider text. | When present. |
| `efx_state` | String or null | State on the Equifax record. | State text or code. | When present. |
| `efx_zipcode` | String or null | ZIP code on the Equifax record. | String; preserve leading zeroes. | When present. |

## Errors and statuses

If no row satisfies the business-name and available contact/address criteria, Lendflow records `No Business found - {business name}`. `Success` means that Lendflow stored a matched record; it is separate from any risk or credit conclusion.

## FAQ

<AccordionGroup>
  <Accordion title="Is this an Equifax credit report?">
    No. This service performs business matching. Equifax report products are separate services.
  </Accordion>

  <Accordion title="Which field is required?">
    Business legal name is the primary required match input. Contact and address data improve matching when available.
  </Accordion>

  <Accordion title="Can this service run in Data Orchestration?">
    It is not included in the current Data Orchestration service catalog.
  </Accordion>
</AccordionGroup>