# BRD-173 — One brand per tax ID

> At most one brand may be registered against a given tax ID.

- **Rule ID:** BRD-173
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.ein across the registry`
- **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:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Bandwidth, Telnyx, Bird, SignalWire, AWS, Sinch
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-173/

## Why this rule exists

The tax ID is what the carriers attribute reputation and volume against, so a second brand on the same EIN splits the identity of one business in two and pools its allowances anyway (BRD-235). Businesses create the second one for entirely sensible reasons — a new division, a new agency, a fresh start after a rejection — and the duplicate is refused against a record they cannot see.

## How to fix it

Run several campaigns under one brand rather than several brands under one EIN — the campaign is the unit that describes a programme, and there is no penalty for having many. Where a second brand is genuinely needed, at least one provider will accept it with a written business justification; ask before submitting.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `711` | yes |
| Twilio | `30898` | yes |

## Check this yourself

**Does a brand already exist against this tax ID anywhere — at any provider, including one a former agency used?**

1. Ask the customer who has sent SMS on their behalf, ever. The refusal will not tell you where the existing brand is.
2. Plan for one brand per legal entity and several campaigns beneath it — there is no penalty for many campaigns.
3. Where a second brand is genuinely needed, at least one provider accepts it with a written business justification. Ask before submitting.

*What wrong looks like:* A new division, a new agency, or a fresh start after a rejection produces a second brand on the same EIN. It is refused against a record the business cannot see, and the allowances were pooled anyway.

## Notes

Absorbs BRD-176, the tenant-local case of the same uniqueness rule. The strictest model is kept: several providers allow exactly one brand per EIN, and one allows a second with written justification. What the user has to establish is whether a brand already exists on this EIN anywhere — including at a former agency — because the refusal will not say where the existing one is.