A framing guide for independent ILECs and CLECs — how to think about NECA settlements, LATA compliance, and FCC filings when you modernize the switch, without assuming anything about how any specific settlement will be treated.
If you’re an independent ILEC or CLEC considering switch modernization in 2026, the question that lands on the CFO’s desk faster than any other is some version of: “What happens to our settlements?” It’s the right question. For many rural and independent telcos, NECA settlement flows and associated cost recovery are a meaningful portion of annual revenue. Nobody wants a modernization project that looks great technically but puts the balance sheet in a worse place.
The honest answer is: we don’t know in advance. Neither do you. Neither does any vendor — and any vendor who tells you they can guarantee your settlements will be preserved is telling you something they can’t actually back up. The answer depends on a dozen variables that only your own NECA advisor and state PUC counsel can model for your specific situation.
What this post covers: the categories you need to think about, the framing your NECA advisor will likely use, and the items to keep intact during modernization so that your position — whatever it turns out to be — isn’t worse than it needs to be.
The three separate things people call “settlements”
One reason these conversations get confusing is that “settlements” covers several distinct mechanisms. A good starting point is to separate them:
- Interstate access cost pools (NECA common line and traffic-sensitive pools). These are the FCC-jurisdictional cost recovery mechanisms that average-schedule and cost-based carriers may participate in. The rules and composition of these pools have been subject to ongoing FCC review.
- State switched access, reciprocal compensation, and state USF. State-level mechanisms that compensate carriers for originating or terminating traffic. These vary dramatically by state, and many states are independently revisiting the rules.
- High-cost universal service support. Federal support programs (successor programs to legacy high-cost support and A-CAM) that distribute funds to rural carriers that meet specific broadband and service obligations. These programs have their own rules about eligible costs and service offerings.
Each of these is subject to its own rulemaking, its own timelines, and its own treatment of how modernized voice traffic fits in. When you hear a concern about “settlements,” the first job is to figure out which one(s) the conversation is actually about.
Why we can’t make predictions
Several reasons honest operators and advisors decline to predict outcomes:
- Rulemakings are in flight. The FCC has periodically revisited how IP-delivered voice fits into legacy cost pools and access charge frameworks. Proposed rules, comment periods, and final orders move on their own schedules.
- State regulators are independent. Even where federal rules move one direction, state PUCs set their own pace and often their own rules for intrastate access charges and state USF.
- Tariff-specific facts matter. A carrier’s specific tariff language, its cost studies, and its traffic mix can put it in a different position than an otherwise similar operator next door.
- Rollout timing is uncertain. Even where rules have been adopted, implementation dates can be deferred, phased, or modified through waiver petitions.
- Precedent is thin for modernized hybrid architectures. The specific question of “how are settlements treated when a carrier runs a hybrid of legacy class-5 and modern IP voice overlay” is newer than most precedent, and different state regulators may treat it differently.
Read that list carefully. Every item is a reason that a carrier in State A can have a very different settlement outcome from a seemingly similar carrier in State B, even if they run nearly identical network topologies. This is why the advice is always “work the specific facts with your advisor” rather than “here’s what will happen.”
What to keep intact regardless of how the rules evolve
You can’t predict how the rules evolve. You can structure your modernization program so that you preserve optionality — so that whatever the rules end up being, your records, tariffs, and authority position are in good shape to respond.
Keep your authority filings current
State CLEC certificates, FCC operating authority, Section 214 authorizations (where applicable), and filed tariffs should all be in good standing before you modernize. Modernization is not a good time to discover a lapsed certificate.
Keep your cost study methodology consistent
If you participate in NECA pools or develop your own cost-based rates, consistent methodology year over year is what makes the data usable when rules change. Introducing new categories of costs or reclassifying existing ones at the same time you change the switch makes it significantly harder to defend your position later. Where possible, decouple the switch modernization from cost study methodology changes.
Keep clean records of what traffic moved where, and when
If you migrate specific trunk groups, number ranges, or customer classes to a new platform in waves, log the cutover date, the traffic type, and the volumes. When a rule is eventually clarified or a regulator asks, the carrier with a clean before/after record is in a much better position than the carrier reconstructing from memory.
Keep your NECA advisor engaged throughout
This is the most important one. Your NECA tariff advisor should be in the discovery phase of your modernization project — not read in at the end. If your advisor sees the planned topology before it’s built, they can flag traffic reclassifications, cost allocations, and reporting changes early. Some of what they flag might cause you to sequence the project differently. That’s the point.
Keep LATA boundaries and interconnection clean
LATA (Local Access and Transport Area) boundaries still matter for how access charges and some jurisdictional questions are resolved. If your modernization changes where calls physically originate and terminate — for example, by routing through a new SBC that sits in a different LATA — your jurisdictional reporting may change. That’s a fact-specific analysis for your advisor.
Keep the FCC filings on time
Form 499-A (annual), Form 499-Q (quarterly), CPNI certification (March 1), Robocall Mitigation Database refresh, and any state-level filings — stay current. Modernization is disruptive enough without missing a filing deadline.
Common framing your advisor may use
Below is a set of questions we’ve seen NECA advisors and regulatory counsel use during modernization scoping. These are not answers. They’re the questions that lead to the right specific analysis:
| Area | Questions to map |
|---|---|
| Cost pool participation | Does the modernization change the costs eligible for inclusion? Does it change traffic-sensitive minute of use reporting? Does the hybrid topology still meet the cost pool eligibility framework? |
| State switched access | Does the planned topology change the jurisdictional classification of any call flow? Does it change PIU/PLU reporting inputs? |
| Reciprocal compensation | Do any new interconnection agreements or trunk groups change the compensation arrangement with any specific peer? |
| State USF | Does the service offering change in a way that affects eligibility or the calculation basis? |
| High-cost support | Does the modernized service meet the broadband and voice service obligations that support the existing support designation? |
| Tariff language | Does the planned architecture still match the services described in the filed tariff? |
| Regulatory reporting | Do the new platform’s CDRs provide the same granularity needed for existing reporting, or do reports need to be restructured? |
Notice what every row has in common: the answer depends on facts that only a careful, current analysis for your specific operation can determine.
What OneCloud does (and doesn’t) promise
When we scope a switch migration for an independent telco, we are clear about what’s in and out of scope:
- We do design the technical topology of the modernized voice stack and document how subscriber traffic flows through it before and after.
- We do accommodate phased cutovers specifically so that your NECA advisor and state counsel have time to review each wave.
- We do preserve configurable reporting and CDR outputs that your advisor tells us are needed for current regulatory filings.
- We don’t guarantee that any specific settlement, cost pool draw, or regulatory compensation will be preserved, changed, or affected in any particular way by the modernization. That depends on facts and rulemakings outside our lane.
- We don’t replace your NECA tariff advisor or your state PUC counsel. They’re at the table from day one.
That split — technical execution on one side, regulatory analysis on the other, run in parallel from discovery onward — is what we’ve seen produce the cleanest modernization outcomes for our carrier partners.
Modernizing the switch, with your regulatory team in the loop from day one
OneCloud’s carrier team runs phased switch migrations for independent ILECs and CLECs. We bring the technical architecture; your NECA advisor and PUC counsel bring the regulatory analysis; nobody makes promises outside their lane.
Visit our Carriers page for the switch migration and CLEC expansion overview.
Frequently asked questions
If we modernize the switch, will we lose our NECA settlements?
We don’t know, and we won’t try to tell you. The answer depends on the specific traffic, costs, and tariffs involved, and on how applicable rules are implemented in your state. This is exactly the question your NECA tariff advisor is equipped to model. Bring them into the planning process before you change the switch configuration.
Why won’t anyone give us a straight answer?
Because a straight answer would be misleading. Settlement treatment varies by state, by tariff, by traffic composition, and by rulemaking timing. An advisor or vendor who issues a blanket “you’ll keep it” or “you’ll lose it” is making a claim they can’t support. The responsible answer is fact-specific analysis.
Can we modernize gradually to reduce risk?
Phased migration is our recommended approach for several reasons, and one of them is exactly this: it gives your regulatory team time to evaluate each wave before the next one moves. Our phased switch migration playbook covers the technical side in detail.
What if our state’s rules change mid-project?
Rules do change mid-project. The best defense is keeping good records, keeping your advisor engaged, keeping your tariffs current, and building a topology that is flexible enough to accommodate re-classification if needed. Inflexible architectures age badly when rules change.
Where do we start if we want to think about this responsibly?
Start with a call to your NECA tariff advisor and your state PUC counsel. When you’re ready to scope the technical side in parallel, OneCloud’s carrier team does a two-week discovery that produces a written migration plan your advisors can review. Call (844) 450-3527 or visit our Carriers page.
Related: our phased switch migration playbook, our 2026 compliance checklist, and our business voice retention playbook for defending the commercial book during modernization.
