The FA Universe: How CMS Audits Your Formulary at the Pharmacy Counter
Sevana Health Team
May 15, 2026
Formulary Administration (FA) is the audit protocol that asks a simple question with uncomfortable answers: when a member shows up at the pharmacy counter, does your plan actually administer the formulary the way the CMS-approved formulary says it should?
FA gets less attention than ODAG and CDAG, partly because it's newer to many compliance teams and partly because the data lives almost entirely inside the PBM's claim adjudication system. But the financial exposure is real. FA audits surface coverage gaps, unauthorized utilization management edits, missed transition fills, and notification failures that don't show up anywhere else.
This post walks through what FA actually validates, the universe data CMS expects to see, and the patterns that produce most of the findings we see when plans run their files through the scrubber.
FA and CDAG, side by side. FA and CDAG are tightly linked. FA is about what the plan's point-of-sale logic did automatically. CDAG is about what happened after a human looked at the case. The same prescription can appear in both protocols at different stages of the lifecycle, and the universes have to tell consistent stories.
What FA Actually Tests
FA looks at three connected questions:
1. Formulary Match
Is the plan's point-of-sale adjudication consistent with the CMS-approved formulary? Drugs that should be covered are being covered, and drugs not on the formulary are being handled the right way.
2. UM Edit Authorization
Are prior authorization, step therapy, and quantity limit edits actually present in the CMS-approved formulary? Plans sometimes apply edits that were never filed with CMS, or apply them to the wrong drugs.
3. Transition and Notification
When a new enrollee or an LTC resident hits a formulary issue, did the plan provide the required transition supply and the required written notice on time?
Every line item in the FA universe answers one of these questions. The fields you need to populate, the cross-references CMS expects, and the validation issues we see all line up with those three buckets.
The Rejected Claims Universe
The biggest piece of the FA submission is the rejected claims data: every Part D pharmacy claim during the audit review period where the plan's adjudication system returned a rejection for a formulary or utilization management reason. CMS reviews this universe to understand what members were being told at the counter.
Reject Reason Codes
The reject reason field is the most consequential single field in the FA universe. It tells CMS what the pharmacy saw when the claim was rejected. The codes are NCPDP-standard and need to be reported exactly as the adjudication system returned them.
| Common Reject Code | What It Means | Why CMS Cares |
|---|---|---|
| 75 | Prior authorization required | Did a PA actually exist in the approved formulary? Was the member offered the path to request one? |
| 76 | Plan limitations exceeded (quantity) | Was the quantity limit on the approved formulary? Was a coverage determination triggered? |
| 569 | Provide notice (CMS standardized notice) | Did the pharmacy actually give the member the standardized notice? Was the right notice given? |
| 70 | Product/service not covered | Is the drug genuinely off the formulary, or was the rejection logic misconfigured? |
| 88 | DUR reject error | Was the drug utilization review edit appropriate? Did it match clinical guidelines? |
Reject code accuracy matters more in FA than in any other protocol. A claim rejected with code 75 (PA required) where no PA exists on the approved formulary is a direct finding. A claim rejected with code 70 (not covered) for a drug that is on the formulary is a direct finding. CMS will reconcile the universe against the approved formulary file, so misalignment is visible immediately.
The Fields That Cause the Most Validation Issues
| Field | What Goes Wrong | Impact |
|---|---|---|
| NDC | NDC truncated, formatted with dashes, leading zeros stripped by Excel. NDC active at adjudication time but obsoleted later. | IDS risk on format |
| Date of Service | Date of fill confused with date of adjudication. Reversal entries dated to the reversal, not the original service. | Timeline reconciliation failures |
| Reject Reason Code | Generic codes used when more specific codes apply. Internal PBM codes used instead of NCPDP standard codes. Code reported as numeric when CMS expects text formatting. | IDS risk, code-formulary mismatch |
| Quantity Dispensed | Quantity in units that don't match the approved formulary's quantity limits (mL vs tablets, days' supply vs total quantity). | Validation against approved limits fails |
| Days' Supply | Field populated for paid claims but missing for rejected claims. Days' supply outside reasonable bounds (negative, zero, >100). | IDS risk, transition fill validation impossible |
| Pharmacy NPI | NPI missing, invalid, or pointing to a closed pharmacy. NCPDP pharmacy ID submitted in the NPI field. | Network validation issues |
| Prescriber NPI | DEA number submitted instead of NPI. Practice NPI submitted instead of individual prescriber NPI. | Cross-reference failures |
The NDC formatting issue is worth its own warning. NDC is an 11-character numeric field, but PBM systems and pharmacy systems freely use 9, 10, 11, and dashed formats internally. When the data hits Excel during transformation, leading zeros disappear and the 11-digit value becomes 10. We see this pattern in roughly every other plan's first file. Spot-check the NDC column for length-10 entries before submission.
Transition Supplies
Transition supplies are one of the most-audited and most-misunderstood FA elements. The regulatory requirement is straightforward in principle and complicated in practice.
The Rule in Plain Terms
Plans must provide a transition fill when a new enrollee tries to fill a Part D drug that the plan doesn't cover or that has a UM restriction the member can't immediately meet, within the first 90 days of enrollment. The transition fill is a one-time supply intended to give the member time to either switch to a covered alternative or request a coverage determination. Specific rules apply for long-term care residents (longer transition period, different supply requirements) and for current enrollees affected by mid-year formulary changes.
Where Transition Universes Go Wrong
Transition Not Triggered
A new enrollee hits a formulary rejection in their first 30 days, the pharmacy reverses the claim, and the member walks away without their drug. The PBM system should have offered the transition fill automatically. Universes that show normal rejections in this scenario, instead of transition fills, surface the gap directly.
Days' Supply Wrong
Transition fills have specific minimum supply requirements. The universe field for days' supply on transition claims has to match. A transition fill that adjudicated as a 7-day supply when the requirement was 30 days is visible to anyone reading the data.
Member Status Misclassified
LTC residents and community-dwelling members have different transition rules. PBM systems that classify residence based on stale enrollment data will apply the wrong rule. Plans need to confirm the residence flag on the claim matches the actual residence status on date of service.
Transition Fills After Day 90
Transition fills should generally not be issued past the transition window. If the universe shows transition-flagged claims at day 110 or day 150, the PBM's logic is wrong, the enrollment date is wrong, or the flag is being mis-applied. All three are findings.
Beneficiary Notifications
Almost every FA action that affects a member's access to a drug triggers a notification requirement. CMS audits whether those notifications went out, whether they went out on time, and whether they contained the right content. The notification universe ties FA back to member-facing operations.
Notifications CMS Looks At
Transition Notices
Written notice to a member who received a transition fill, explaining that the drug isn't on the plan's formulary and describing the member's options. Must be sent within three business days of the transition fill adjudication.
Formulary Change Notices
Written notice to members affected by mid-year formulary changes (removals, tier increases, new UM restrictions). Required at least 30 days in advance under most circumstances.
Point-of-Sale Standardized Notice
The notice the pharmacy is required to provide when a claim is rejected for a coverage reason and the member is at the counter. The plan needs evidence the notice was delivered.
Coverage Determination Outcome Notices
Notices following a CD decision. These cross over into the CDAG universe but show up in FA when CMS reviews the full notification trail for a specific member.
The Three Things That Go Wrong with Notifications
Notice Date Logged but Not Sent
The universe shows a notification date, but the print and mail vendor never actually mailed the letter. The gap between “system generated” and “envelope postmarked” is where plans get hurt during validation audits.
Wrong Notice Template
CMS publishes standardized notice templates. Plans that use modified versions, or that send a generic letter where a CMS-specific template was required, fail content validation even when the timeliness is fine.
No Evidence of Delivery
For point-of-sale notices, the plan needs to be able to show the pharmacy delivered the standardized notice to the member. Most plans don't track this directly and rely on attestations or sampling. CMS knows this and probes the weakness during audits.
Cross-Universe Consistency
FA doesn't exist on its own. CMS reads FA in combination with CDAG and the approved formulary file to build a complete picture of member access. The consistency checks that matter:
FA Rejections to CDAG CDs
A high volume of code 75 rejections (PA required) in FA should correlate with a commensurate volume of CDs for those drugs in CDAG. If FA shows thousands of PA rejections but CDAG shows almost no PA-related CDs, the plan isn't capturing pharmacy-triggered coverage determinations.
FA Rejections to the Approved Formulary
Every rejection that cites a UM edit (PA, ST, QL) must correspond to an edit on the CMS-approved formulary for that drug. Edits applied at point of sale but not present in the approved formulary are unauthorized restrictions. Findings are immediate.
Transition Fills to Notification Records
Every transition fill should have a transition notice within three business days. If FA shows 1,200 transition fills but the notification universe only shows 1,050 notices, the difference is a measurable findings rate.
Member Identifier Consistency Across FA, CDAG, and Enrollment
MBI in FA needs to match MBI in CDAG, which needs to match MBI in the enrollment file. PBM systems sometimes hold cardholder IDs that map indirectly to MBI through translation tables. When those tables drift, members effectively become invisible across universes.
FA Sits Almost Entirely with the PBM
Of all the CMS audit universes, FA is the one most exclusively produced by the PBM. The plan's internal systems rarely have the data needed to build FA independently. That creates a specific risk profile.
- 1The plan can't independently verify the file is right. Unless the plan has its own pharmacy claim feed and the analytical capability to compare against the approved formulary, the PBM's file goes in as-is.
- 2Different PBMs structure FA universes differently. The CMS spec defines the required fields and formats, but PBM internal data models vary, and the transformation to CMS format is where errors get introduced.
- 3Specialty pharmacy data often lives elsewhere. Limited distribution drugs, specialty pharmacy fills, and certain biologics may be adjudicated through a separate system. Those claims need to be unified into the FA universe.
- 4Mid-year formulary changes are a stress test. When the plan changes its formulary mid-year, the PBM has to update point-of-sale logic on time and produce notifications on time. Late or missed updates show up cleanly in FA.
What to Do Before Your Next FA Submission
Compare FA reject codes to your approved formulary file.
Every UM-related rejection should map to an edit that exists on the approved formulary for that drug. The reconciliation can be automated and should run before submission.
Spot-check NDC length and formatting.
Run a quick count of NDC values by character length. Anything other than 11-character numeric is a format issue. Excel transformations are the most common culprit.
Reconcile transition fills against transition notices.
Every transition fill should have a matching notification within three business days. The gap between the two volumes is your notification compliance rate.
Cross-check FA rejections against CDAG case volumes.
High-volume rejection categories should correspond to commensurate CD activity. Large mismatches indicate pharmacy-initiated cases not being captured in CDAG.
Track residence status accurately for transition logic.
LTC versus community-dwelling status drives different rules. The PBM's view of residence has to match the actual residence on date of service.
Validate the PBM's file. Don't just submit it.
If the PBM produces the FA universe and the plan submits it without independent validation, the plan is accepting the PBM's data quality as its own. Most of the FA findings we see could have been caught by validating before submission.
Validate Your FA Universe Before Submission
The CMS Universe Scrubber validates FA files against the current CMS specification: reject code formatting, NDC validity, transition fill rules, days' supply consistency, and cross-universe checks against CDAG. Catch IDS-triggering errors before CMS does.