A 527 organisation needs a token and its filing reference on record

The requirementstatement

A 527 political organisation must hold a Campaign Verify token, and must record the FEC ID or state filing URL used to obtain it.

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
the Campaign Verify token + the filing reference
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
External recordEXTERNAL_DATA
The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
What the fix involvesfailureClass
Supply evidenceTERMINAL_EVIDENCE
Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities
InfobipCampaign VerifyTCR
When it appliesapplicabilityText
Applies when the use case is POLITICAL.

Why this rule existsrationale

The token proves the organisation was verified; the filing reference proves which organisation it was verified as. Keeping only the token leaves a claim nobody can retrace when a carrier asks, and political programmes attract exactly that kind of question — usually in the last fortnight before an election.

How to fix itremediation

Obtain the Campaign Verify token, and store the FEC committee ID or the state filing URL beside it in the same record. Done when both can be produced together in a single reply to a carrier query.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

ProviderCodeResubmit
Infobip9001Yes

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Are the Campaign Verify token and the FEC committee ID or state filing URL stored together, retrievable in one reply?

  1. 1Record the filing reference beside the token at the moment you obtain it — it is easy to find while applying and surprisingly hard to reconstruct six months later.
  2. 2Test it: ask whoever answers carrier queries to produce both, now.

What wrong looks like: Only the token was kept. It proves an organisation was verified and not which one, and the question arrives in the last fortnight before an election.

Notesnotes

Neither artefact is visible in a registration. What the user has to do is keep them together at the point they are obtained — the filing reference is easy to find while you are applying and surprisingly hard to reconstruct six months later.

Rules you will hit next

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

All brand rules

BRD-243 is one of 196 brand 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.