Sole proprietor brand and campaign both require a reference ID

The requirementstatement

referenceId is mandatory — not optional — on both the brand and the campaign for the sole proprietor tier.

Severityseverity
BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
brand.reference_id + campaign.reference_id
Where it liveslayer
Brand ↔ campaignCROSS
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass
Fix the fieldRETRY_FIELD
A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities
TCR
When it appliesapplicabilityText
Applies when the brand is a sole proprietor.

Why this rule existsrationale

The reference ID is how the sole proprietor tier ties a brand and campaign to the verified mobile number behind them, which is the only identity check that tier has. It is optional everywhere else, so integrations built against the standard flow omit it and fail here.

How to fix itremediation

Populate referenceId on both the brand and the campaign with your own stable identifier for this customer.

A compliant exampleexample

referenceId: acme-sp-2026-0041

Notesnotes

Catalog BRD-077 / CMP-022.

Rules you will hit next

Other brand ↔ campaign rules at the same severity. A registration is judged as a whole, not rule by rule.

All brand ↔ campaign rules

XBC-005 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.