If you sell software, a digital download, or a subscription to anyone in Washington, D.C., your invoices are about to get more expensive — and it has nothing to do with your pricing strategy. On October 1, 2026, the District's general sales tax rate rises from 6% to 7%, and unlike many states, D.C. taxes digital goods and Software-as-a-Service the same way it taxes a lamp or a laptop. If you haven't touched your tax settings since the last D.C. rate change, this is the moment to check.
The Rate Change, in Plain English
The District of Columbia's Budget Support Act of 2024 originally scheduled a jump straight from 6% to 7% on October 1, 2025. The D.C. Council later passed the Sales Tax Increase Delay Amendment Act of 2025, which pushed that increase back by a full year. The practical result: the general rate has stayed at 6% through most of 2025 and 2026, and it steps up to 7% for any period beginning on or after October 1, 2026.
That 7% rate applies broadly — to the gross receipts from sales of tangible personal property, digital goods, and most taxable services delivered into the District. A few categories sit outside the general rate and follow their own schedule (restaurant food and beverages at 10%, vehicle and utility trailer rentals at 10.25%, hotel rooms at 15.95% through September 2027), but for the vast majority of retailers, contractors, and software companies selling into D.C., 7% is the number that matters starting this fall.
Why This Hits Software and SaaS Companies Specifically
Plenty of states still exempt cloud software from sales tax, or tax it only when sold to consumers rather than businesses. D.C. does neither. Since the Internet Sales Tax Emergency Amendment Act of 2018 expanded the District's definition of taxable goods, digital products — e-books, streaming media, digital applications, downloaded software — and SaaS subscriptions have been treated as taxable sales at the standard rate. Critically, D.C. draws no distinction between a subscription sold to a consumer and one sold to a business: B2B and B2C SaaS are taxed identically. A law firm buying an enterprise contract-management subscription pays the same rate as an individual paying for a streaming service.
That means every SaaS company with customers in D.C. — whether it's a three-person startup billing a handful of District clients or a larger platform with a national customer base — needs to apply the new 7% rate to any invoice covering a billing period that starts on or after October 1, 2026. If your billing system charges annually or on a fiscal-year cycle rather than calendar-month, pay close attention to which invoices straddle the change; the rate that applies is generally the one in effect for the period the charge covers, not the date you happen to run the invoice.
Do You Even Have to Collect D.C. Tax? Check Your Nexus First
Before worrying about the rate, confirm you have a collection obligation in the District at all. If you have a physical presence in D.C. — an office, employees, or a warehouse — you have nexus automatically. If you don't, you may still be required to register and collect under D.C.'s economic nexus rule: once your gross revenue from sales delivered into the District exceeds $100,000, or you complete more than 200 separate retail sales delivered into D.C., in the current or prior calendar year, you're required to obtain a retail license and collect and remit District sales and use tax.
Two details trip up SaaS companies in particular:
- Digital products and subscriptions count toward both thresholds. A recurring SaaS charge to a D.C. customer counts as a "sale" the same as a one-time purchase would, so a handful of enterprise subscriptions can quietly push a small vendor over the transaction count even if the dollar total looks modest.
- The obligation doesn't reset automatically. Once you cross a threshold, D.C.'s guidance treats your registration obligation as continuing into the following calendar year even if that year's sales end up below the threshold. If you registered because of a strong 2025, don't assume a quieter 2026 lets you deregister without checking the rule first.
If you've never checked whether your District sales cross these lines, now — before the rate change forces a closer look at every D.C. invoice anyway — is a good time to run the numbers.
A Compliance Checklist Before October 1
- Confirm your nexus status. Pull a year-to-date total of revenue and transaction count for customers billed to D.C. addresses. If you're near either threshold, register before you cross it — D.C.'s own guidance expects registration by your next transaction after the threshold is hit, not at year-end.
- Verify your tax engine or billing platform updates automatically. If you use a sales tax automation tool, confirm it has the October 1, 2026 rate change loaded and that it's mapped to D.C. digital goods and SaaS as taxable, not exempt. If you calculate and apply D.C. tax manually, update your rate table directly — a stale 6% rate charged after October 1 is an under-collection you'll have to make up out of your own margin.
- Check subscription and contract language. If your contracts state a flat total price "including applicable taxes" rather than tax added on top, a rate increase changes your effective revenue per contract, not just the invoice total the customer sees. Decide now whether you'll absorb the difference or pass it through, and notify affected D.C. customers before the change lands on an invoice unannounced.
- Audit historical collection, not just future rates. If this rate change is the first time you've looked closely at D.C. sales tax on your product, take the opportunity to confirm you've been collecting correctly at the 6% rate all along. Businesses that discover a gap often have access to voluntary disclosure programs that limit look-back exposure — a much better outcome than waiting for an audit to find it for you.
- Flag any straddling billing periods. Annual, multi-year, or mid-cycle invoices that span the October 1 transition need a documented policy for which rate applies. Pick a rule (typically: the rate in effect when the service period begins) and apply it consistently, so you're not making case-by-case judgment calls under audit scrutiny later.
The Bigger Pattern: Sales Tax on Software Isn't Going Away
D.C.'s approach — tax digital goods and SaaS at the same rate as everything else, with no B2B carve-out — is becoming more common, not less, as states and jurisdictions look for revenue in an economy where more spending happens on subscriptions and less on shelved goods. If your business sells into multiple jurisdictions, a D.C. rate bump is a reasonable prompt to review your full sales tax nexus footprint, not just this one city.
Keeping that footprint straight starts with keeping clean records of exactly what you collected, from whom, and at what rate — something that's much easier when your books distinguish tax liability by jurisdiction from day one rather than getting reconstructed after the fact during an audit. Beancount.io's plain-text accounting approach makes it straightforward to tag transactions by tax jurisdiction and rate, version your books as tax rules change, and see exactly when a rate update took effect in your ledger history — no black-box spreadsheet macros to untangle later.
Simplify Your Financial Management
Tracking a mid-year tax rate change across every D.C. invoice is exactly the kind of detail that's easy to get right once and then forget to revisit. Beancount.io gives you plain-text accounting that's transparent, version-controlled, and easy to audit — so a rate change like this one shows up clearly in your books instead of getting lost in a spreadsheet. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
