Skip to content
Monday, November 16, 2026Newsletter
Advertisement
VoIP & Unified Communications

Annual Robocall Mitigation Database recertification due March 1

VoIP and other voice providers must recertify Robocall Mitigation Database filings each year, in a window that opens Feb. 1 with a March 1 deadline.

By

Founder

4 min read

ShareLinkedInXEmail
Photograph: Mobile phone spam in Viet Nam
Photo: Phó Nháy / Wikimedia Commons, public domain. Cropped from the original.

Voice service providers, intermediate providers, VoIP resellers and other filers in the Robocall Mitigation Database must recertify their filings each year. The FCC set an annual deadline: each existing filing must be recertified by March 1 every year.

The same rules require multi-factor authentication to log in, updates within 10 business days of any change, and base forfeitures of $10,000 for false or inaccurate entries and $1,000 for late updates. Here is what the FCC notice and the official filing guide say, and how a provider can meet the deadline.

Key facts

Background

In Public Notice DA 26-72, released January 22, 2026, the FCC Wireline Competition Bureau reminded filers that the new rules require them to recertify by March 1, 2026. The same notice said the first recertification window would open on February 1, 2026.

The legal basis is 47 CFR § 64.6305(h), which requires providers to certify each year, on or before March 1, that everything they put in the database is true and correct. The Bureau said that rule took effect on February 5, 2026, 30 days after it ran in the Federal Register on January 6, 2026. OMB completed its review on August 11, 2025.

Advertisement

Penalties changed at the same time. An amendment to 47 CFR § 1.80, effective February 5, 2026, raised the base forfeiture to $10,000 per violation for false or inaccurate entries. It also set a $1,000 base forfeiture for failing to update the database within 10 business days. Under the notice, a violation keeps running until it is fixed and can be assessed daily up to the statutory maximum.

A separate amendment, also effective February 5, 2026, requires CORES registrants to update their FRN details within 10 business days of a change.

What it means for you

The filing duty is broad. According to the notice's FAQ, last updated January 20, 2026, all voice service providers and intermediate providers, including gateway providers, must file. Any business that fits those definitions, such as a VoIP reseller or a mobile virtual network operator, is covered.

Advertisement

Corporate structure matters too. An affiliate or subsidiary that meets the provider definitions on its own should submit its own filing. Each provider also needs its own 10-digit FCC Registration Number (FRN) from CORES, and only a business-type FRN can be used to file.

Every filer must name at least one principal, and that principal must be an individual.

A changed filing starts a 10-business-day clock for an update, apart from the yearly recertification.

The VoIP and unified communications page explains business calling options. Teams that run busy call queues can also look at the contact center options. Related call compliance rules are covered in what businesses can do about opt-out rules.

Advertisement

Practical steps

The July 2026 filing instructions lay out the recertification process. The steps below follow that guide.

  1. Confirm access. Submitting a filing needs an FCC Username account and a business-type FRN.
  2. Set up multi-factor authentication. Filers must now use MFA and may choose a phishing-resistant method. Login steps are in the filing instructions.
  3. Wait for the window. Recertification can only be done during the yearly window, which opens each year on February 1.
  4. Log in to the database at the web address listed in the filing instructions, open the filing, and select the "Recertify" button. Per the same guide, that button appears only during the window that starts February 1.
  5. Review the entry, make any needed edits, fill in the Declaration section, and select Submit, as the guide describes.
  6. A filing can be recertified only once during the window.
  7. Finish by March 1. That is the yearly deadline for existing filers.

For login, username or FRN problems, the filing instructions point filers to the CORES help desk, open Monday through Friday from 8 a.m. to 6 p.m. ET. The same guide says CORES details must be updated within 10 business days of any change.

Anyone who spots a deficient filing can report it to RMD-Reporting@fcc.gov. The Bureau said useful reports include the business name, FRN, RMD number and a short note on the problem.

What happens next

A fee is still pending. As of the January 22, 2026 notice, a $100 application fee for initial submissions and yearly recertifications under an amendment to 47 CFR § 1.1105 had not yet taken effect. The FCC said it would publish a notice when the fee starts. Routine updates to reflect changed information carry no application fee.

The sources do not say whether that fee notice has since been published. They also do not report enforcement actions or late-filing counts after the first deadline.

Frequently asked questions

When is the yearly recertification deadline?
Existing filers must recertify by March 1 each year . The window to do so opens on February 1.
Do VoIP resellers have to file?
Yes, if they meet the provider definitions. The FCC's FAQ says VoIP resellers and MVNOs that fit those definitions must file.
How fast must a filing be updated after a change?
Filers must update their entries within 10 business days of any change. Missing that window carries a $1,000 base forfeiture.
Is there a fee to recertify?
A $100 fee was not yet in effect as of the January 22, 2026 notice. The FCC said it would announce when the fee starts.

Sources

  1. The FCC set an annual deadline: each existing filing must be recertified by March 1 every year . fcc.gov (accessed 2026-11-12)
  2. Existing filers must recertify each year by March 1, and the window to do it opens each year on February 1 . fcc.gov (accessed 2026-11-12)
  3. Filers must update their database entries within 10 business days of any change . docs.fcc.gov (accessed 2026-11-12)
  4. Logging in to the database requires multi-factor authentication . fcc.gov (accessed 2026-11-12)
  5. The base forfeiture for false or inaccurate entries is $10,000 for each violation , and failing to update on time carries a $1,000 base forfeiture. docs.fcc.gov (accessed 2026-11-12)
  6. VoIP resellers and mobile virtual network operators that meet the provider definitions must file . docs.fcc.gov (accessed 2026-11-12)
  7. In Public Notice DA 26-72, released January 22, 2026 , the FCC Wireline Competition Bureau reminded filers that the new rules require them to recertify by March 1, 2026. docs.fcc.gov (accessed 2026-11-12)
  8. The same notice said the first recertification window would open on February 1, 2026 . docs.fcc.gov (accessed 2026-11-12)
  9. The legal basis is 47 CFR § 64.6305(h) , which requires providers to certify each year, on or before March 1, that everything they put in the database is true and correct. docs.fcc.gov (accessed 2026-11-12)
  10. The Bureau said that rule took effect on February 5, 2026 , 30 days after it ran in the Federal Register on January 6, 2026. docs.fcc.gov (accessed 2026-11-12)
  11. OMB completed its review on August 11, 2025 . docs.fcc.gov (accessed 2026-11-12)
  12. An amendment to 47 CFR § 1.80, effective February 5, 2026 , raised the base forfeiture to $10,000 per violation for false or inaccurate entries. docs.fcc.gov (accessed 2026-11-12)
  13. It also set a $1,000 base forfeiture for failing to update the database within 10 business days. docs.fcc.gov (accessed 2026-11-12)
  14. Under the notice, a violation keeps running until it is fixed and can be assessed daily up to the statutory maximum . docs.fcc.gov (accessed 2026-11-12)
  15. A separate amendment, also effective February 5, 2026 , requires CORES registrants to update their FRN details within 10 business days of a change. docs.fcc.gov (accessed 2026-11-12)
  16. According to the notice's FAQ, last updated January 20, 2026 , all voice service providers and intermediate providers, including gateway providers, must file. docs.fcc.gov (accessed 2026-11-12)
  17. Any business that fits those definitions, such as a VoIP reseller or a mobile virtual network operator, is covered . docs.fcc.gov (accessed 2026-11-12)
  18. An affiliate or subsidiary that meets the provider definitions on its own should submit its own filing . docs.fcc.gov (accessed 2026-11-12)
  19. Each provider also needs its own 10-digit FCC Registration Number (FRN) from CORES, and only a business-type FRN can be used to file. docs.fcc.gov (accessed 2026-11-12)
  20. Every filer must name at least one principal , and that principal must be an individual. docs.fcc.gov (accessed 2026-11-12)
Advertisement

Thinking about changing your business phones?

Book a free 30-minute call. We will talk through what you have today, what you want to keep, and which options fit, with no pressure to buy anything.

Book a free phone system call

Related service: VoIP & Unified Communications

Junious Digital Labs logo

Joshua Junious

Founder of Junious Digital Labs, a veteran-owned IT consultancy. Army National Guard veteran and former IT director. About Joshua

Reach readers across the Junious Media Network. Advertise with us →