Skip to main content

SDLA Compliance Resource

Manage E-Rate FY2026 Recurring Services

A full-year delivery, billing, change-control, and evidence cycle for each committed recurring-service Funding Request Number.

  • E-Rate
  • Funding Year 2026
  • Recurring Services
Date(s)July 1, 2026–June 30, 2027
Applies toSchools, libraries, consortia, and service providers with committed FY2026 recurring-service FRNs

In Plain Language: For every FRN, verify the committed service began, remains eligible and delivered to approved recipients, matches the contract and funding decision, and is supported by invoices, payments, changes, CIPA compliance, and reimbursement controls throughout the funding year.

Why this matters

E-Rate support follows the approved FRN—not merely the vendor contract. Unreported service changes, ineligible use, unsupported quantities, unpaid non-discount share, or delivery outside July 1–June 30 can reduce recovery or create audit exposure.

Primary ownership

Primary owner: E-Rate applicant lead. Partners: technology/network, procurement, fiscal/accounts payable, CIPA compliance lead, service provider, site contacts, records custodian, and authorized EPC users.

From funding decisions to a BEAR/SPI support package: the SDLA ITO workflow

Each committed recurring-service Funding Request Number (FRN) needs a full-year cycle of delivery, billing, change-control, and evidence. This SDLA ITO (Input, Transformation, Output) graphic shows how the funding decisions, contracts, and vendor bills become the FRN register, reconciled bills and payments, change and compliance records, and the BEAR/SPI support package.

SDLA ITO: twelve steps from the funding decisions, contracts, and vendor bills, through the FRN control register, start and compliance checks, monthly reconciliation, change control, and the June 30 close, to the FRN register, reconciled bills and payments, change and compliance records, and the BEAR/SPI support package.
Read down each column, then move to the next: Input identifies what to collect; Transformation covers the FRN control register, start and compliance checks, monthly reconciliation, change control, and the June 30 close; Output covers the FRN register, reconciled bills and payments, change and compliance records, and the BEAR/SPI support package. Calculate each invoice deadline at the June 30 close.

Open the full-size workflow graphic

Operational workflow

  1. Build an FY2026 FRN control register from FCDLs/RFCDLs, contracts, service dates, committed amounts, and applicant share.
  2. Confirm service start, eligible recipients/locations, CIPA status, and FY2026 Form 486 requirements.
  3. Reconcile monthly vendor bills, service evidence, credits, applicant payments, and remaining commitment by FRN.
  4. Process supported post-commitment changes and preserve USAC decisions before claiming affected amounts.
  5. Close June 30 delivery, calculate each invoice deadline, and hand off a complete BEAR/SPI support package.

Implementation pathway

FRN register
Start/compliance
Monthly reconcile
Change control
June close/invoice

Evidence to retain

  • FCDL/RFCDL and FRN register
  • Contracts, bids, and service evidence
  • Invoices, credits, and applicant-share payments
  • CIPA/Form 486 and post-commitment records
  • June 30 close and invoice-deadline calculation

Official guidance and help

Source review completed August 30, 2026. Verify current USAC, FCC, CRDC, EPC, funding-year, FRN, procurement, and local records before acting.