# BRD-272 — The end-business block must be complete, not partly filled

> On a toll-free verification, every end-business detail must be populated rather than a subset of them.

- **Rule ID:** BRD-272
- **Layer:** Brand (`BRAND`)
- **Checks:** `the end-business block`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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:** Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-272/

## Why this rule exists

A partly filled end-business block is rejected as a whole rather than field by field, and the reviewer cannot tell an omission from a business that has no answer. It arrives from integrations that map whichever fields their own record happens to hold, so the gaps are wherever the source system was thin rather than wherever the business is.

## How to fix it

Fill every end-business field before submitting: legal name, address, contact name, phone, email and website. Where a value is genuinely unknown, get it from the customer rather than leaving the field out — a partial submission costs a full review cycle.

## Example of a compliant value

```text
company_name, street, city, state, postal_code, country, rep first/last name, phone, email and website — all populated
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `TFV 1105` | yes |

## Notes

Scoped to the toll-free path, where the end-business block is submitted as a unit and rejected as one. The equivalent completeness requirement for a 10DLC brand is spread across BRD-001, BRD-017, BRD-091 and BRD-102, each of which names its own field — so this rule does not repeat them.