What is the difference between BEAR and SPI in E-Rate?

Under BEAR (FCC Form 472), the applicant pays the provider the full, undiscounted invoice amount and then requests reimbursement from USAC for the discount share. Under SPI (FCC Form 474), the provider bills the applicant only the non-discounted share up front and invoices USAC directly for the rest. BEAR puts the float and the reimbursement wait on the applicant; SPI puts it on the provider.

Who decides whether an FRN uses BEAR or SPI?

The applicant selects the invoicing mode per FRN when filing the FCC Form 471. A service provider can only be paid through SPI if it has also filed the annual FCC Form 473 (Service Provider Annual Certification, or SPAC) for that funding year; without it, SPI isn't available even if the applicant wants it.

Can a provider and applicant change the invoice method after the Form 471 is filed?

Yes. In EPC, under the funding request's Related Actions, there's a Manage Invoice Mode Change option. It requires uploading a document signed by both a full-rights applicant user and the service provider, so a provider can't be switched out of a method without signing off.

Does the SAM.gov banking requirement affect both invoicing methods?

Yes, but through different registrations. SPI payments ride on the provider's own FCC Form 498 and SAM.gov UEI. BEAR reimbursements ride on the applicant's Form 498 and UEI, since USAC pays the applicant directly, not the provider. USAC postponed the original August 10, 2026 cutover to this requirement and has not yet announced a new date; see our full checklist for details.

What does a service provider need to file to use SPI?

An active FCC Form 473 (SPAC) for the funding year, filed by the provider. Providers with a high volume of FRNs can also use USAC's Electronic Invoicing process for bulk upload instead of filing individual invoices in EPC.

SPI vs. BEAR: How E-Rate Service Providers Actually Get Paid

Ask a service provider which E-Rate invoicing method they use and most will say "whatever the customer picked." That's technically correct and also the least useful way to think about it. The applicant does choose BEAR or SPI, per FRN, on the Form 471. But that choice decides who floats the cash for weeks or months, who is exposed if a reimbursement gets delayed, and how much of your own paperwork sits between delivering service and getting paid. It's worth understanding well enough to have an opinion the next time a customer asks which one you'd recommend.

The Two Methods, Side by Side

	SPI (Form 474)	BEAR (Form 472)
Who files it	Service provider	Applicant
What the applicant pays upfront	Only the non-discounted share	100% of the invoice
Who USAC pays	The provider, for the discount share	The applicant, as reimbursement
Provider's certification role	Files the annual Form 473 (SPAC) to be SPI-eligible	Certifies the applicant's claimed amount in EPC before USAC pays the reimbursement
Where the float sits	With the provider, waiting on USAC	With the applicant, waiting on USAC

Both still run on the same 120-day invoice deadline machinery, tied to the service end date or the Form 486 notification letter, whichever is later; that mechanic is the same regardless of method and we cover it in full in the E-Rate filing deadlines calendar.

The Real Difference: Who Carries the Float

This is the part that gets glossed over in most explainers. Under BEAR, the applicant pays you in full, on your normal invoice terms, before USAC enters the picture at all. Once that payment clears, you're done. The applicant then files the Form 472 and waits on USAC to reimburse the discount share, which can be a real wait during a busy invoicing season, but it's the applicant's wait, not yours.

Under SPI, you never see the discounted portion from the applicant. You bill them the non-discount share, and you separately invoice USAC for the rest through the Form 474. That means your revenue for every SPI-invoiced FRN has two payers and two timelines, and the USAC portion is the one you don't control. If USAC's processing queue backs up, or your own Form 498 and SAM.gov registration have a mismatch, the discount share is stuck on your books, not your customer's.

Neither method is strictly better. SPI is the more common choice for larger providers because it's less friction for the customer, who never has to front the discount share and never has to remember to file a reimbursement claim. BEAR shifts more administrative work onto the applicant but gets a provider paid in full on a normal commercial timeline, with no direct dependency on USAC's own processing speed. If you've had a customer whose BEAR filing habits are inconsistent, or a district that's historically slow to submit its own paperwork, that's a real factor in which method actually gets you paid faster in practice, regardless of which one looks cleaner on paper.

The Provider's Role Isn't Passive in Either One

A provider that treats invoicing as purely the applicant's problem is leaving money on the table in both directions.

For SPI, you need an active Form 473 on file every funding year. The SPAC (Service Provider Annual Certification) is what makes a provider SPI-eligible at all. Miss it, and an applicant who wants to pay you through SPI can't, no matter what they selected on their Form 471. Providers with a large FRN volume can also use USAC's Electronic Invoicing process to submit invoices in bulk rather than filing them one at a time in EPC, which is worth setting up if you're managing more than a handful of funding requests.

For BEAR, you have a certification checkpoint too. Before USAC pays the applicant's reimbursement, the provider certifies in EPC that the amount claimed on the Form 472 matches what was actually billed. Skip or delay that certification and the applicant's reimbursement stalls behind you, even though you already have their money. It's a small task with an outsized effect on your customer relationship if it slips.

Changing the Method Isn't Locked In

If a customer picked BEAR on the Form 471 and later wants to switch to SPI, or the reverse, it's not a re-file. In EPC, under the funding request's Related Actions, there's a Manage Invoice Mode Change option that walks through the switch. It requires a document with both a full-rights applicant signature and a service provider signature, so the provider has to actively sign off, not just find out after the fact. If a customer's invoicing habits are creating friction under their current method, raising a switch is a legitimate, low-effort conversation to have mid-relationship rather than waiting for the next Form 471 cycle.

Where SAM.gov Fits Into Both

Both invoicing methods now run through the same federal identity infrastructure, just on different registrations. SPI payments are tied to the provider's own FCC Form 498 and SAM.gov Unique Entity Identifier. BEAR reimbursements are tied to the applicant's Form 498 and UEI, because USAC pays the applicant directly. A provider who only checks its own SAM.gov status has covered the SPI side of its book and none of the BEAR side; the BEAR exposure sits with your customers' administrative hygiene, not yours, which is one more reason a slow-paying BEAR customer is worth a direct check-in rather than a guess about what's wrong.

That cutover, originally set for August 10, 2026, was postponed by USAC on the day it was supposed to take effect, with a new timeline expected in September. The requirement itself hasn't gone anywhere. The full SAM.gov checklist and update log covers what to verify on both the provider and applicant side before whatever date USAC lands on next.

Choosing a Default, and When to Break From It

There's no universal right answer, but a few patterns hold up across most books of business. High-volume providers who can use Electronic Invoicing generally prefer SPI: it's less friction for the customer and scales better across dozens or hundreds of FRNs. Smaller providers, or providers working with a new district that hasn't built E-Rate invoicing muscle yet, sometimes prefer BEAR specifically because it gets them paid in full on a normal commercial timeline instead of splitting revenue across two payers. If a customer's preferred method keeps producing late payments, that's worth diagnosing directly rather than assuming it's just how E-Rate works. It usually isn't; it's how that particular customer, or that particular provider's own certification hygiene, is handling the process.

FRNHQ tracks funding status and invoice activity by FRN across every state, so you can see which committed funding requests are invoice-eligible without cross-referencing EPC by hand. See your active E-Rate pipeline inside FRNHQ, or start with E-Rate activity in your state and the competitive bidding guide for how those FRNs get won in the first place.