What Is a BEN? Billed Entity Numbers Explained, and How to Look One Up

Every E-Rate record you will ever read starts with the same question: who is the customer? The answer, in USAC's data, is a number. It is called the Billed Entity Number, or BEN, and once you know how to read one you can connect a Form 470 to a funded request, a funded request to a district, and a district to its neighbors.

This is a short primer for service providers. It covers what a BEN is, how the parent and child structure works, how to look one up, and what to do with it once you have it.

What a BEN is

USAC assigns a BEN to every entity that pays service providers for products and services delivered to eligible schools and libraries. It is the applicant-side counterpart to the provider's SPIN. Where a SPIN tells you who is selling, a BEN tells you who is buying and paying.

You will see the phrases "BEN" and "entity number" used as if they were the same thing. Mostly they are. USAC's guidance says there is no visible difference between a number assigned as a BEN and one assigned as an entity number, and the terms are now used interchangeably. The practical distinction is the role: the BEN is the entity named as the billed entity on an application.

A BEN shows up in three places you care about:

• Form 470: the BEN on the posting ties the bid request to a specific applicant.
• Form 471 and the FRN: the funding request is filed by, and paid on behalf of, a billed entity.
• USAC's entity records: name, entity type, parent entity, and physical and mailing location all hang off the number.

That last link is what makes the number useful. On a Form 470, the BEN is how you get from a line of text to an actual district with an enrollment count and a location, and those are the signals that size a deal.

Parents, children, and consortia

USAC organizes entities in a hierarchy, and the hierarchy explains most of the confusion providers run into.

Two consequences follow. First, an application filed by a district covers its buildings, so the district's BEN is usually the one you want when you are sizing an account. Second, a district or library system cannot file as a consortium on its own BEN. If it wants to lead a consortium, it needs two BENs and two organization accounts in EPC, one for the district or system and one for the consortium.

That second point matters for the provider lens. A statewide or regional buy can be posted under a consortium BEN that looks nothing like the districts that will actually receive service. When a bid comes from a consortium, look at its members before you decide it is too small or too far away to chase. If you sell into shared purchasing vehicles, our guide to competitive bidding for providers covers how those postings get evaluated.

How to look up a BEN

USAC publishes the lookup itself. The E-Rate Entity Search Tool lives on USAC's Open Data portal at opendata.usac.org. It returns entity name, number, type, parent entity, and physical and mailing location. You can narrow a search by entity type (school district, school, library, or all types) and download the results.

A workable routine:

1. Search by the name on the Form 470 or FRN, and set the entity type to school district first. Many names repeat across states, so confirm the city and state.
2. Read the parent entity field. If you landed on a single school, step up to its district BEN.
3. Save the BEN, not the name. Names change with mergers and renamings; the number is the stable key.

If an entity has no BEN at all, it has not been set up yet. Schools and libraries not registered in the E-Rate Productivity Center (EPC) have to contact USAC's Customer Service Center to create an EPC account, designate an account administrator and obtain a BEN. That is the applicant's job, not yours, but it is worth knowing when a prospect tells you they have never filed.

What providers do with a BEN

The number is a join key. Once you have it, you can pull every funded request tied to an applicant, see which provider held each one, and tell an incumbent from a newcomer. The same approach works in reverse. Take a competitor's SPIN, list the distinct BENs on its funded requests, and you have its customer book with names, states and entity types attached. One caution: on consortium FRNs the BEN is the consortium that filed, not the schools or libraries served, so expand those to their member recipients before you count customers. We walk through that workflow in how to research an E-Rate provider, and you can find a provider by SPIN in the SPIN lookup.

FRNHQ joins these records ourselves. Our entity master, refreshed from USAC's supplemental entity dataset, holds more than 240,000 entities keyed by BEN, and it is what lets us show enrollment and entity type next to an open bid. In a big state such as Texas, the BEN is what separates a large district's postings from the small ones in the same search results.

Three habits keep BEN work clean:

• Match on the number and confirm with the name. Two districts can share a name.
• Roll children up to parents before you count accounts, or one district will look like forty.
• Treat consortium BENs as their own category, and check the members.

Where to go next

Understanding the BEN is the first step in reading any E-Rate record. From here, the E-Rate hub shows how the pieces fit together, and the free tools show what a BEN looks like once it is attached to a live bid.

If you want the entity, the bid and the incumbent in one place instead of three, create a free FRNHQ account and search by applicant.