# BRD-200 — A suspension follows the tax ID to the next brand

> After a suspension, new brands created on the same tax ID should be expected to be restricted.

- **Rule ID:** BRD-200
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.ein after a suspension`
- **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; Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-200/

## Why this rule exists

The suspension attaches to the EIN rather than to the brand or the account, so it follows the business across providers — which means switching CSP does not reset it, and the new provider cannot lift it either. Businesses change provider precisely because the old one suspended them, and arrive at the same restriction with a second onboarding already paid for.

## How to fix it

Resolve the original suspension rather than moving. If the business genuinely has a new programme, expect the new brand to carry restrictions from the start and be ready to evidence what changed — the review will ask.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `21731` | no |

## Check this yourself

**Has this tax ID ever been suspended, at any provider?**

1. Establish the suspension history for the EIN before starting a new registration. It attaches to the tax ID, not to the brand or the account, so changing provider does not reset it.
2. Where a suspension exists, resolve it rather than moving — the new provider cannot lift it either.
3. If the business genuinely has a new programme, be ready to evidence what changed. The review will ask.

*What wrong looks like:* A business changes provider precisely because the old one suspended it, and arrives at the same restriction with a second onboarding already paid for.

## Notes

Absorbs OPS-181, which states the same EIN-level scope across CSPs. Suspension history is not visible in a registration. What the user has to establish is whether this EIN has ever been suspended anywhere — the answer determines whether a new registration is worth attempting at all, and a provider change will not help.