Submit the US EIN hyphenated
The requirementstatement
A US EIN must be submitted in the hyphenated XX-XXXXXXX form.
- 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.ein
- Where it liveslayer
- BrandBRAND
- 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
- TwilioTelnyxSinch
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Reformat the EIN as two digits, a hyphen, then seven digits. Done when the value reads 12-3456789 rather than 123456789.
A compliant exampleexample
ein: 12-3456789
Notesnotes
Rules you will hit next
6 other rules read brand.ein. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
BRD-020 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.