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

# Reseller Checks with Experian AU

> If you perform Experian AU credit header checks on behalf of another reporting entity, that entity's ABN needs to be supplied with each check. This guide shows how to pass the ABN via the individual's custom attributes.

## Overview

Some customers act as a **reseller** — they run KYC checks on behalf of another business, and that business (not the reseller) is the AML/CTF reporting entity for the check.

Experian AU requires the ABN of that end business to be supplied with every credit header check, so the enquiry can be attributed to the correct obligated entity. FrankieOne collects this ABN as a custom attribute on the individual and forwards it to Experian as `AMLObligatedEntityABN`.

<Info>
  This applies only to **Experian AU credit header checks** performed through the
  Experian v2 connector. It has no effect on other data sources, and it is not
  needed by customers who are the reporting entity for their own checks.
</Info>

***

## Enabling the feature

Reseller ABN passthrough is enabled by FrankieOne on a per-configuration basis. Enabling it does two things:

* Makes the `CustomerChannelReferenceIdentifier` custom attribute visible and mandatory in the FrankieOne Portal, so the ABN can be captured for profiles created manually.
* Makes the attribute **required** for API-created entities — a check submitted without it fails validation before it reaches Experian.

<Callout icon="star" color="#3DD892" iconType="regular">
  Contact [help@frankieone.com <Icon icon="arrow-up-right-from-square" size={12} />](mailto:help@frankieone.com)
  to have reseller ABN passthrough turned on for your configuration. Until it has
  been enabled, the attribute is stored on the entity but not forwarded to Experian.
</Callout>

***

## Supplying the ABN

Set a custom attribute named `CustomerChannelReferenceIdentifier` on the individual, with the end business's ABN as the value.

The attribute can be set when [creating the individual](/docs/managing-individuals) or added later with an update — it simply needs to be present on the entity at the time the workflow runs.

```http HTTP Request theme={null}
POST /v2/individuals
```

```json JSON Request Body theme={null}
{
  "individual": {
    "name": {
      "givenName": "Jane",
      "familyName": "Citizen"
    },
    "dateOfBirth": {
      "year": "1992",
      "month": "08",
      "day": "15"
    },
    "addresses": [
      {
        "type": "RESIDENTIAL",
        "streetNumber": "123",
        "streetName": "Exhibition",
        "streetType": "Street",
        "locality": "Melbourne",
        "subdivision": "VIC",
        "postalCode": "3000",
        "country": "AUS"
      }
    ],
    "customAttributes": {
      "CustomerChannelReferenceIdentifier": {
        "type": "STRING",
        "value": "11111111111"
      }
    },
    "consents": [
      {
        "type": "GENERAL"
      },
      {
        "type": "CREDITHEADER"
      }
    ]
  }
}
```

### Field reference

| Field          | Value                                | Notes                                                                                                                   |
| :------------- | :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------- |
| Attribute name | `CustomerChannelReferenceIdentifier` | Case-sensitive — it needs to match exactly.                                                                             |
| `type`         | `STRING`                             | The ABN is sent to Experian as a string.                                                                                |
| `value`        | The end business's ABN               | 11 digits, no spaces. This is the ABN of the business the check is being performed **for**, not the reseller's own ABN. |

<Callout icon="bell" color="#FFCA16" iconType="regular">
  Credit header consent is still required for Experian AU checks. The reseller
  ABN is in addition to — not a replacement for — the `CREDITHEADER` consent.
  See [Creating & Managing Individuals](/docs/managing-individuals#consents).
</Callout>

***

## What FrankieOne sends to Experian

The attribute is forwarded in the request payload as an additional detail:

```xml theme={null}
<RequestData>
  <AdditionalDetail>
    <DetailName>AMLObligatedEntityABN</DetailName>
    <Detail>11111111111</Detail>
  </AdditionalDetail>
</RequestData>
```

The value sent is also recorded against the check in the audit trail.

***

## Behaviour when the ABN is missing

| Configuration                     | Attribute supplied? | Result                                                                                               |
| :-------------------------------- | :------------------ | :--------------------------------------------------------------------------------------------------- |
| Reseller passthrough **enabled**  | Yes                 | ABN forwarded to Experian as `AMLObligatedEntityABN`.                                                |
| Reseller passthrough **enabled**  | No                  | The check fails validation. No request is sent to Experian, and no credit header result is produced. |
| Reseller passthrough **disabled** | Either              | The attribute is ignored and nothing is forwarded.                                                   |

<Callout icon="thumbtack" color="#1A6CFF" iconType="regular">
  Because a missing ABN stops the check before it reaches Experian, set the
  attribute on the entity **before** executing the workflow. See
  [Error Handling](/docs/error-handling) for how validation failures are surfaced.
</Callout>