# BRD-027 — EIN must be old enough to have propagated to IRS records

> A newly issued EIN is not yet present in the records vetting providers query; registration fails until it propagates.

- **Rule ID:** BRD-027
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.ein`
- **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:** External record we cannot query — reported as a warning to verify; Human check — only someone holding the document can settle it
- **Fix type:** Wait on an external system or a required interval
- **Required by:** AWS, Twilio, Bandwidth
- **Applies:** Applies when the brand is NOT a sole proprietor.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-027/

## Why this rule exists

A newly issued EIN is not yet visible to the databases vetting providers query, so verification fails against a record that does not exist yet. No form correction fixes this — the only remedy is time, which is worth knowing before paying a non-refundable vetting fee.

## How to fix it

If your EIN was issued in the last 90 days, wait before submitting. No form correction fixes this — vetting queries a record that does not exist yet.

## Check this yourself

**Was this EIN issued more than 90 days ago?**

1. Find the issue date printed on the CP-575 confirmation letter.
2. Count the days to today. Under 90, wait rather than submit — providers publish windows from 30 to 90 days and the longest is the one worth planning against.

*What wrong looks like:* An EIN issued three weeks ago matches nothing, and the rejection says the business could not be found rather than that the EIN is too new — so a perfectly correct name and address get edited over and over.

## Notes

Providers publish different windows (AWS 30 days, Twilio 30-90, Bandwidth 90). Strictest kept per the strict-superset model.