CoverageDistrict of Columbia
District of Columbia 911 surcharge remittance
We fill EMERGENCY 911 FEE REMITTANCE REPORT in the state's own workbook, its formulas and layout untouched. You review it, sign it, and send it to Office of Unified Communications.
The state publishes a workbook and this product fills it in place, leaving its formulas, styles and layout exactly as the state issued them. The workbook recalculates its own totals when it is opened.
The District publishes an Excel workbook as a public download, and the product fills that same file, leaving its formulas, styles, drawing, comments and printer settings untouched. The fill is tested by reopening the filled file and comparing it with the state’s blank. The agency still prints an instruction in three places asking providers to e-mail for a copy of the template; the download exists and is what the tier claim rests on.
The rate in force now
- Rate
- $0.76 per line per month · Wireline exchange access line, wireless telephone number, or interconnected-VoIP line, trunk or path; $0.62 per line per month · Centrex line; $4.96 per line per month · PBX trunk
- Effective
- 2008-08-16 → current
- Cite
- D.C. Official Code §34-1803(a)(1) and (a)(2), as enacted by D.C. Law 17-219 §3002(b)
- Form rev.
- rev10-2025
- Retrieved
- Thu, September 3, 2026 · two independent fetches agree
Cadence
“Each local exchange carrier shall submit the tax imposed under subsection (a) of this section to the Mayor on a quarterly basis.”
The statute compels a quarterly submission and the agency invites a more frequent one: the procedures document reads “Providers are asked to remit the 911 Fee to the Washington, D.C. Treasury monthly, but no later than quarterly.” Either satisfies the statute, so the product offers both and the provider’s registration carries which one they file on.
The charge underneath is monthly — §34-1803(a)(1) calculates it on each individual telephone line for each month — which is why the District’s own workbook carries three month rows and one total, and why a quarterly filing here is three monthly counts rather than one quarterly figure.
Due dates
911 Fee Remittance Report and payment
- To
- Office of Unified Communications (report) and the Office of the Chief Financial Officer (payment)
- Rule
- the 15th of the month after the period ends
- Weekends
- the date shown is not moved for a weekend or holiday
- Applies to
- Monthly · Quarterly
“When to Remit: The 15th of the month following the reporting period, due at least quarterly but may be paid monthly.”
The report and the payment are due together on the same date, to two different District offices.
The statute states no due date at all. The fifteenth comes from the agency’s own procedures document and from the filing instructions printed on the face of the workbook, which agree word for word — a collecting agency’s own publication, but worth showing on the page as an agency instruction rather than a statutory deadline.
The procedures document prints the same rule as a table: January 15 for October through December, April 15 for January through March, July 15 for April through June, and October 15 for July through September.
The District publishes no weekend or holiday rule for this deadline, so the engine moves no date.
Counting rule
A monthly charge on each line, by service class, calculated on each individual telephone line. The District charges $0.76 on a wireline exchange access line, $0.76 on a wireless telephone number with a District billing address, $0.76 on an interconnected-VoIP line, trunk or path, and $0.62 on a Centrex line and on a PBX station. The PBX charge is converted to a per-trunk charge by statute at eight stations to one trunk, which makes a PBX trunk $4.96 a month. No cap of any kind appears in the statute, in either procedures document or on the form.
For interconnected VoIP the unit is each line, trunk or path that can access, connect with or interface with 911 service, sourced by the customer’s primary place of use. That wording reaches a trunk or a path directly rather than through an equivalency table, so a hosted or SIP trunk group is counted by the paths that can reach 911 rather than by the direct-inward-dial numbers riding on it. A VoIP provider that also sells Centrex-comparable or PBX service reports those on their own columns at the lower station rate, with the statutory eight-to-one conversion applied to trunks.
Per-customer cap
None. No per-customer or per-location cap was found by any of the three research passes, in the statute, in the procedures documents or on the form.
“The PBX tax per station shall be converted into a per-trunk tax based on a ratio of 8 PBX stations to one PBX trunk.”
Collection allowance
The District grants a provider no collection allowance and no retained percentage on this fee. All three research passes read §34-1803 and the surrounding sections and found none, and the workbook has no deduction row: its NET FEE DUE cell is the total fee due, unreduced. One adjacent provision is not this and must never be applied here — §34-1803.02(f) lets a prepaid wireless seller retain three percent of what it collects at the point of sale, which is a different charge, a different remitter and a different section.
D.C. Official Code §34-1803, read in full by all three research passes and by the adjudicator
Rate history
The engine resolves the window that covers the filing period, never the latest one. A back period therefore prices at the rate that was in force for it.
2008-08-16 → current
$0.76 per line per month · Wireline exchange access line, wireless telephone number, or interconnected-VoIP line, trunk or path; $0.62 per line per month · Centrex line; $4.96 per line per month · PBX trunk
D.C. Official Code §34-1803(a)(1) and (a)(2), as enacted by D.C. Law 17-219 §3002(b)
https://code.dccouncil.gov/us/dc/council/code/sections/34-1803 · retrieved Thu, September 3, 2026
D.C. Law 17-219 §3002(b) was enacted on August 16, 2008 and rewrote §34-1803(a)(1) into its present form, introducing the interconnected-VoIP category at $0.76. D.C. Law 18-223 (2010) added the prepaid-wireless carve-out and moved no dollar figure. Nothing has moved since.
In force from August 16, 2008. The enacted text of D.C. Law 17-219 sets every amount in this window in its Title III, Subtitle A (§3002(b)), and that subtitle carries no applicability clause of its own, unlike the several subtitles of the same act that apply “as of October 1, 2008”; the act takes effect under its §10002 after congressional review. The Council’s page for the law states that it “became effective on August 16, 2008”, and the codified section’s history dates the amendment the same day. Both were fetched from the Council’s code site on September 26, 2026. Periods beginning before that date are refused.
Every figure was confirmed three ways: on the face of the statute, on the face of the agency’s procedures document, and inside the District’s own workbook, whose Fee per Line row carries 0.76, 0.76, 0.76, 0.62 and the literal “($0.62)*8”.
Zero-report rule
Zero report · not on record
The District does not say whether a period with no District lines or no fee collected still requires a filed report. The workbook has no zero-liability box and no separate declaration for one, and its totals compute to zero on empty rows, so a zero report is mechanically submittable — but no District source states that one is required or that it may be skipped. No sworn zero-report declaration exists here to surface, and none may be composed.
Searched: D.C. Official Code §§34-1801 through 34-1806, the Office of Unified Communications 911 Fund page, both the current and the superseded remittance procedures documents, and every field of the workbook. All three research passes reached the same absence.
Record retention
Record retention · not on record
The District publishes no record-retention period for a provider’s own 911 fee records. Title 34, Chapter 18 is silent and neither procedures document addresses it. Title 47’s general tax record rules were deliberately not borrowed, because whether they reach this fee is itself unconfirmed, and presenting a duration the District has not stated for this fee would be a manufactured regulatory fact.
Searched: D.C. Official Code §§34-1801 through 34-1806 in full, the 911 Fund page, and both procedures documents.
Registration
Registration · not on record
The District publishes no registration step and no provider account portal, and no evidence was found that it issues a provider account number. The workbook nevertheless asks for an “Operating Co. Number”, and no published process for obtaining one was found — so that field is left for the provider on every filled form rather than filled with a guess. The route to an answer is the Office of Unified Communications at 911fee@dc.gov, or Yolanda Taylor-Weems at (202) 645-9333.
Searched: The Office of Unified Communications 911 Fund and publication pages, both remittance procedures documents, the workbook’s own fields, and D.C. Official Code §§34-1801 through 34-1806.
The state’s own workbook
- Form
- The state publishes no form identifier. The District assigns this report no number. It is identified by title alone: the publication page calls it the “911 (E911) Fee Remittance Report”, the procedures document calls it the “911 Fee Remittance Report”, and the workbook’s own title cell reads “EMERGENCY 911 FEE REMITTANCE REPORT”.
- Title
- EMERGENCY 911 FEE REMITTANCE REPORT
- Revision
- rev10-2025 (from the served filename; the package carries no internal revision marker)
The workbook is completed, signed and e-mailed to 911fee@dc.gov with the provider name on the subject line. Payment travels separately: the District states that wire transfer or ACH credit is preferred, and a provider paying by check mails the report with the check to the Office of the Chief Financial Officer.
Remit to
- Agency
- Office of Unified Communications
- Division
- Payment is received by the Office of the Chief Financial Officer, Public Safety & Justice Cluster
- Payee
- DC Treasurer, written “District of Columbia Treasurer” elsewhere in the same procedures document
- Address
- District of Columbia Treasurer, Attn: Monica Swann, OCFO, Public Safety & Justice Cluster, 899 North Capitol Street, NE, Suite 8200A, Washington, DC 20002. A copy of the report goes by e-mail to 911fee@dc.gov in every case, whether the money moves by wire, ACH or check.
- Contact
- 911fee@dc.gov · Yolanda Taylor-Weems, Yolanda.Taylor-Weems@dc.gov, (202) 645-9333
- Rate set by
- The Council of the District of Columbia, by statute. No agency sets or adjusts the amount.
Out of scope
What this page does not cover.
The prepaid wireless E911 charge
D.C. Official Code §34-1803.02 imposes a separate charge of two percent of the retail sales price, collected by the seller at the point of sale and remitted by the seller. A different remitter and a different section, and the three percent a seller may retain there never reaches this filing.
A local or ward-level 911 charge
There is none. The District has no county layer and no sub-District 911 charge for a provider to remit alongside this one, which is worth stating plainly because a compliance desk used to county splits will look for one.
Everything else this record does not know
Rate history · not on record
The pre-2008 rate schedule was not recovered. It is not in the current codified text or its amendment notes, and the amounts have not moved in eighteen years, so every period a provider could plausibly bring is covered by the single window this record carries.
Searched: The codified text of §34-1803 and its amendment notes.
Form revision · not on record
The revision on this record is derived from the served filename. The text in the workbook’s cells holds no revision marker, so a republication under the same filename would not change it. The product therefore also tracks the file by its fingerprint and compares the workbook’s own rate cells with the rate on this page, so a silent republication is caught.
Searched: The text in the workbook’s cells and its document properties. Print-footer strings reading “Rev. 6-1-2008” and “Rev. April 2010” sit in a non-default custom sheet view of the worksheet; they are stale template leftovers, not the current revision, and do not appear in any cell.
Portal address · not on record
Whether the District’s MyTax portal offers any filing path for this fee is neither confirmed nor ruled out. It is a JavaScript-rendered application that returns only a cookie shell to an automated fetch, and no research pass reached it. If it turns out to accept this fee, the vehicle and the tier would both need revisiting.
Searched: The Office of Unified Communications 911 Fund page, the publication page, both procedures documents, and the portal itself.
Sources
Every fact above traces to one of these, retrieved Thu, September 3, 2026.
The record was reached by independent research passes whose disagreement a third pass and an adjudication settled. Each source below opens at the address it was read from, with the date it was read.
Council of the District of Columbia — D.C. Law 17-219, enrolled text
The Emergency Communications Funding Amendment Act of 2008 (Title III, Subtitle A, §3002(b)) rewriting §34-1803(a)(1) with the $0.76 and $0.62 amounts, with no applicability clause in that subtitle, and the act’s effective-date section.
Retrieved Sat, September 26, 2026
Council of the District of Columbia — D.C. Law 17-219
The law’s legislative history and its effective date: “D.C. Law 17-219 became effective on August 16, 2008.”
Retrieved Sat, September 26, 2026
Council of the District of Columbia — D.C. Official Code §34-1803
The rate schedule by service class verbatim, the eight-to-one PBX conversion verbatim, the quarterly submission duty verbatim, the invoice line-item authorization, and the codification history.
Retrieved Thu, September 3, 2026
Office of Unified Communications — EMERGENCY 911 FEE REMITTANCE REPORT (rev10-2025)
The workbook this product fills: its printed title, its rate constants, its live formulas and calculation chain, its three-month grid, its filing instructions and due-date rule, its remit-to block, its certification block, its provider-type list, and the two federal-lines questions.
Retrieved Wed, September 9, 2026
Office of Unified Communications — 911 Fee Remittance Procedures (2025)
The rate schedule by service class, the quarterly due-date table, the instruction to remit monthly but no later than quarterly, the wire and ACH banking block, and the check payee and mailing address in both places they appear.
Retrieved Thu, September 3, 2026
Office of Unified Communications — 911 (E911) Fee Remittance Report publication page
That the workbook is a live public download and that it is the single attachment the District publishes for this filing.
Retrieved Thu, September 3, 2026
Office of Unified Communications — 911 Fund
Which procedures document the agency links today, which is what settled the dispute between two vintages of that document and everything downstream of it, including the remit-to address.
Retrieved Thu, September 3, 2026
- D.C. Official Code §34-1801
- Definitions for the District’s 911 and 311 assessments
- D.C. Official Code §34-1802
- The Emergency and Non-Emergency Number Telephone Calling Systems Fund, administered by the Office of Unified Communications
- D.C. Official Code §34-1803
- The assessment itself — the per-line amounts by service class at (a)(1), the eight-to-one PBX station-to-trunk conversion at (a)(2), the quarterly submission duty at (b), and the authorization to itemize the fee on a customer invoice at (d)
- D.C. Official Code §34-1803.02
- The prepaid wireless charge, cited only to mark the boundary of what this record covers
- D.C. Official Code §34-1805
- The Office of Unified Communications report to the Council
- D.C. Law 17-219 §3002(b)
- The 2008 act that rewrote the rate schedule into its present form and introduced the interconnected-VoIP category
Notes carried on this record
The District’s own workbook is missing one formula, and a VoIP filer is the one it hurts. Cells C32, D32, F32 and G32 each sum their three month rows for the Wireline, Wireless, Centrex and PBX columns; E32, the VOIP total, is empty, while E34 computes the VOIP fee as E32 times E33. A provider who fills only the monthly VOIP counts therefore opens the District’s file showing a zero VOIP fee beside real line counts. The product writes the provider’s own confirmed three-month VOIP total into that cell and flags the missing formula for review with the counts behind it. Nothing computed by this product is written into any cell the workbook computes for itself.
The template ships with July, August and September in its month rows. The filled form carries the months of the period actually being filed; leaving the published quarter in place would put the right numbers on the wrong quarter.
The workbook pre-populates its own rate cells, which is both a gift and a risk: the product checks them against the rate on this page, so a District rate change is caught the moment the agency republishes.
The certification block is the District’s own, printed on its form, and the provider signs it. The product leaves the signature, title, date, typed name and telephone number blank and never composes anything to accompany them.
Two federal-lines questions sit on the face of the form — whether the provider supplies local service to the federal government as defined in §34-1803, and whether the remittance includes federal lines. They are marked by hand and are left for the provider.
Never read a cached formula result out of this workbook. It computes on open, and the amounts this product displays come from the engine.