# BRD-024 — The identifier value must match the type declared for it

> The business-registration identifier value must be in the form its declared type requires.

- **Rule ID:** BRD-024
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.business_registration_identifier + brand.ein`
- **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:** AWS, Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-024/

## Why this rule exists

Declaring EIN and supplying a Canadian business number — or the reverse — sends a well-formed number to the wrong register, and the answer comes back as "business not found" rather than as a type error. It is a common integration defect precisely because both values are nine digits and both fields validate.

## How to fix it

Check the two fields against each other: the type names the document, the value is the number printed on it. If they disagree, correct whichever one is wrong rather than changing both. Done when the number is the one the named register issued.

## Example of a compliant value

```text
business_registration_identifier: EIN · ein: 12-3456789 — nine digits, because that is what an EIN is
```

## Notes

Distinct from BRD-019, which asks only whether a US EIN has nine digits. This rule asks whether the value fits the type that was DECLARED for it, which is a different failure and produces a different fix. A type outside the enum is BRD-023 and is left to it.