# BRD-023 — The identifier type must be one of the supported values

> Where a business-registration identifier type is declared, it must be one of EIN, DUNS, CBN, CN, ACN, CIN, VAT, VATRN, RN or Other.

- **Rule ID:** BRD-023
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.business_registration_identifier`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Twilio
- **Applies:** Applies when the brand is NOT a sole proprietor.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-023/

## Why this rule exists

The type tells the registry which register to look the number up in, so an unrecognised value does not degrade to a best guess — the lookup never runs and the brand stays unverified. Integrations produce this by passing through whatever their own CRM calls the field, and the value looks perfectly reasonable right up to the point where nothing happens.

## How to fix it

Set the identifier type to the code for the document the number came from: EIN for a US employer identification number, CBN for a Canadian business number, VAT or VATRN for a European VAT registration, and Other only when none of them fits. Done when the value is one of the ten codes, in upper case.

## Example of a compliant value

```text
business_registration_identifier: EIN · ein: 12-3456789
```

## Common mistakes

- "TAX_ID", "FEIN" and "Federal Tax ID" all mean EIN and are all rejected — the enum takes the short code, not the name people use.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30701` | yes |
| Twilio | `30799` | yes |

## Notes

A US EIN passes without an explicit type because the value is unambiguous and TCR infers it, so the check only reports a value that is present and outside the enum. Declaring it anyway is worth doing: the Twilio Trust Hub API takes the field directly and rejects the submission when it is missing.