# BRD-216 — An imported vet must match the brand exactly, and carry its token

> On a vet import, the legal name and entity type must match the vetting report exactly, and the vetting token must be supplied.

- **Rule ID:** BRD-216
- **Layer:** Brand (`BRAND`)
- **Checks:** `the vet import payload`
- **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:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-216/

## Why this rule exists

The import attaches somebody else's examination to this brand, so the registry checks that the two describe the same company before accepting it — and it compares strings. A report issued to "Acme Coffee Company" cannot be imported onto a brand registered as "Acme Coffee Co, LLC" even though everyone involved knows they are the same business.

## How to fix it

Compare the report against the brand field by field before importing, and correct whichever is wrong — usually the brand, since the report reflects what the vetting provider verified. Supply the verification certificate token with the import. Done when name and entity type match character for character and the token is attached.

## Example of a compliant value

```text
vet report legal name: Acme Coffee Co, LLC · brand company_name: Acme Coffee Co, LLC · token: supplied
```

## Common mistakes

- Correcting the brand name to match the report is itself an identity change (BRD-044), so do it before the import rather than during it.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| TCR | `538` | yes |
| TCR | `520` | yes |