UB-04 field locators: what an institutional claim actually captures.
The UB-04 has 81 form locators to the CMS-1500's 33 boxes, and the gap isn't padding. It exists because an institutional claim is describing an entire episode of care — who's billing, what kind of bill it is, what happened and when, what it's worth — not a single office visit. This guide walks through the blocks of form locators that have no CMS-1500 equivalent at all, anchored by the two form locators every institutional biller learns first: FL 1 and FL 81.
Key takeaways
- 81 form locators, not 33 boxes. The UB-04 describes an institutional episode, not a single encounter, and its extra field count reflects that directly.
- Condition, occurrence and value codes have no CMS-1500 equivalent. A professional claim for one visit never needs to describe an episode's circumstances, dated events or dollar values.
- FL 1 and FL 81 bookend the form. Billing provider identification opens it, taxonomy and qualifier close it, and everything in between builds out the episode.
- More fields means more places for one wrong entry to cascade. Structural complexity is the trade-off for the richer administrative detail an institutional claim requires.
Why 81 fields for one claim
A CMS-1500 has to answer a relatively contained question: who's billing, who was treated, what was done, and why. A UB-04 has to answer that same question plus a second one layered on top of it: what kind of institutional stay or encounter is this, what administrative circumstances surround it, and what dated events and dollar values does the payer need to adjudicate it correctly. That second layer is what the extra fields exist for, and it's the reason the UB-04's field count isn't just "more of the same kind of information" — it's genuinely a different, wider category of information than a professional claim ever has to carry.
The two form locators worth learning first as orientation points are FL 1 and FL 81, because they bookend the form conceptually even though they sit far apart on the page. FL 1 carries the billing provider's name and address — the institutional equivalent of what box 33 does on a CMS-1500 — and it sits at the top of the form because every other field on the claim is ultimately read in reference to who is billing. FL 81 sits at the far end of the form and carries the taxonomy code and qualifier that further identifies the billing provider's specialty designation to the payer, refining the same "who is billing" question FL 1 opened with additional specificity. Between those two bookends sits everything else: bill classification, dated occurrences, condition flags, dollar values, revenue and procedure detail, and diagnosis coding for the episode.
Type of Bill and revenue codes: classifying the claim itself
Before a payer even looks at what was billed, it needs to know what kind of claim this is, and that's what the Type of Bill code (a three-digit code) does — identifying the facility type, the bill classification, and whether this is an original claim, a correction, or a void. It functions as a routing instruction as much as a data field: get any one of the three digits wrong, particularly the frequency digit that says whether this is new or a correction, and the payer's system can misroute or reject the claim before it ever evaluates the clinical content.
Revenue codes do a related but distinct job further down the form: they identify which department or service category each charge line belongs to — pharmacy, laboratory, a specific type of room and board, operating room time, and so on. A professional claim doesn't need this because a physician's service line is already fully described by its CPT or HCPCS code; an institutional claim needs it because a single stay can generate dozens of charge lines across entirely different departments, and the payer needs each one categorized correctly to price and audit the claim as a whole, not line by line in isolation.
Condition, occurrence and value codes: the episode-level detail
This is the block of the UB-04 with the cleanest "no CMS-1500 equivalent" story, because these three code sets describe things a single office visit simply doesn't have. Condition codes flag circumstances that affect how the claim should be processed — a beneficiary-requested billing situation, a mid-stay change from inpatient to outpatient status, and similar administrative circumstances that change how a payer needs to handle the claim. Occurrence codes record specific dated events tied to the claim — an accident date, the admission date itself — giving the payer a timeline of events relevant to the episode rather than just the diagnosis and procedure codes describing what happened clinically. Value codes carry dollar amounts or quantities the payer needs for adjudication, separate from the itemized charge lines, covering things like coordination-of-benefits amounts between payers.
| Code set | Describes | Why a professional claim doesn't need it |
|---|---|---|
| Condition codes | Circumstances affecting how the claim should be processed | A single office visit has no mid-episode status changes to flag |
| Occurrence codes | Specific dated events tied to the claim | The date of service already fully describes when a professional service happened |
| Value codes | Coded dollar amounts or quantities for adjudication | A professional claim's charge amount is already a single line item, not an episode-level total |
None of these three code sets exist because someone wanted the UB-04 to be more complicated than it needs to be — they exist because an institutional stay genuinely has more moving administrative parts than an office visit does, and the payer has no other structured place on the claim to capture them.
Why this makes institutional claims structurally more complex
Put the pieces together and the structural difference between the two forms comes into focus: a CMS-1500 describes one service, rendered by one identifiable provider, on one date, supported by one or a small handful of diagnoses. A UB-04 describes an episode — potentially spanning days, multiple departments, multiple charge lines, administrative status changes partway through, and dated events that happened before or during the stay — and it has to hold all of that together on a single claim that adjudicates as one unit. Every additional category of information is also an additional place where a single wrong entry can cascade into a rejection, which is exactly why UB-04 rejection patterns tend to cluster differently than CMS-1500 rejection patterns: it's rarely one field in isolation, it's more often one field that contradicts another field describing the same episode from a different angle.
That's also why UB-04 review has to be structural in a way CMS-1500 review doesn't. Checking whether the diagnosis and procedure codes are individually correct is necessary but nowhere near sufficient — the Type of Bill has to agree with the claim's own history, the revenue codes have to agree with the HCPCS billed alongside them, and any condition, occurrence or value code entered has to be internally consistent with the rest of the episode being described. A biller who only checks the clinical codes on a UB-04 is checking a fraction of what the payer is actually going to evaluate.
Institutional claims denying for reasons that don't add up?
We scrub UB-04 claims field-block by field-block — Type of Bill, revenue codes, condition and occurrence codes included — before submission, not after a denial.
Frequently asked questions
What's the difference between a UB-04 form locator and a CMS-1500 box?
They're the same idea under different names, but the UB-04 has 81 form locators against the CMS-1500's 33 boxes because it's describing an entire institutional episode of care rather than a single office encounter. Blocks like condition codes, occurrence codes and value codes have no CMS-1500 equivalent at all, because a professional claim for one visit never needs to capture that kind of episode-level detail.
Why does the UB-04 need condition, occurrence and value codes if the diagnosis and procedure are already on the claim?
Diagnosis and procedure codes describe what was clinically wrong and what was clinically done. Condition, occurrence and value codes describe the administrative circumstances around the claim itself — a status change mid-stay, a dated event like an accident or admission, a dollar amount the payer needs for coordination of benefits. A payer can't correctly adjudicate an institutional claim from clinical codes alone; it needs this administrative layer too, which is exactly what a professional claim for a single encounter doesn't carry.
What are FL 1 and FL 81 used for?
FL 1 carries the billing provider's name and address, sitting at the very top of the form because every other field is read in reference to who is billing. FL 81 sits at the opposite end and carries the taxonomy code and qualifier that further identifies the billing provider's specialty designation to the payer. Between those two bookends sits the entire structure of the claim — identification, bill classification, dated occurrences, condition flags, dollar values, and clinical detail.
Confirm before you rely on this. Claim form requirements and payer-specific field rules change. The process information on this page reflects standard industry practice as of August 2026 and is provided for general education — verify current requirements against the current NUCC CMS-1500 and NUBC UB-04 instructions before relying on it.