# BRD-043 — The business-type field takes its own enum, not the entity type

> Where a business_type is declared, it must be one of Co-operative, Corporation, Limited Liability Corporation, Non-profit Corporation or Partnership.

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

## Why this rule exists

This is a second classification field with a different vocabulary from entityType, on the same form, describing the same company. Populating it from the entity type — PRIVATE_PROFIT, NON_PROFIT — produces values that are not in its enum, and the submission fails validation on a field the user believed they had already answered further up the page.

## How to fix it

Set business_type to the legal form of the company — an LLC is "Limited Liability Corporation", an Inc is "Corporation" — and leave entityType as the TCR classification. Done when the two fields hold values from their own lists rather than from each other's.

## Example of a compliant value

```text
business_type: Limited Liability Corporation · entity_type: PRIVATE_PROFIT — for Acme Coffee Co, LLC
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30701` | yes |

## Notes

Twilio Trust Hub carries this field and TCR does not, so it is checked only where it is populated: a registration that never declares one passes. Where the submission target is Twilio the field is mandatory, and the check says so rather than passing silently.