# BRD-217 — Some vet classes cannot be imported at all

> An Authentication+ class vet must not be submitted for import — the class does not support it.

- **Rule ID:** BRD-217
- **Layer:** Brand (`BRAND`)
- **Checks:** `the vet import class`
- **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-217/

## Why this rule exists

Authentication+ verifies a live second factor rather than producing a transferable report, so there is nothing to import and the attempt is refused rather than queued. It is a reasonable thing to try: every other class can be imported, and the API takes the same shape for all of them.

## How to fix it

Order the Authentication+ vet directly on the brand instead of importing one. Where you already hold a report from elsewhere, only the standard and political classes can be brought across. Done when no import is attempted for the Authentication+ class.

## Example of a compliant value

```text
vet import class: STANDARD — Authentication+ is ordered directly on the brand instead
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| TCR | `525` | yes |