Virginia's Data Center Electricity Tax: What the $0.011-per-kWh Charge Means for Your Colocation and Cloud Bills

If your website, app, or online store runs on servers housed in Virginia — and statistically, it probably does — your next hosting invoice could quietly include a new line item you never budgeted for. Not a sales tax. Not a rate hike from your power company. A state electricity consumption tax aimed squarely at data centers, charged by the kilowatt-hour, and every operator in Data Center Alley will be writing a check to the State Corporation Commission starting this summer.

Whether you rent a single rack in Ashburn, run a SaaS on a Northern Virginia cloud region, or simply pay a managed hosting provider who does, this is a pass-through cost that will find you. The good news: the math is transparent, the effective date gives you time to prepare, and a small amount of bookkeeping discipline now will keep the new charge from disappearing into your general "hosting" expense forever.

What Virginia Actually Passed — and When It Takes Effect​

After months of divided budget negotiations, Virginia's General Assembly passed its biennial budget bill HB 30 with a compromise that surprised both the industry and ratepayer advocates. Lawmakers left one big incentive on the table and added a completely new tax.

The $0.011-per-kWh Charge​

Beginning July 1, 2026, and currently scheduled through July 1, 2028, every data center operator in Virginia will pay an electricity consumption tax of $0.011 per kilowatt-hour (kWh) on all electricity consumed at each data center each month.

That is roughly one cent for every kWh — about a 10% increase in effective electricity rates for most data center operators, according to power-sector consultants who modeled the impact.

The tax applies regardless of where the electricity comes from:

• power supplied by a regulated utility like Dominion Energy
• power purchased through a competitive retail provider
• self-generated power, including behind-the-meter generation such as on-site gas turbines, fuel cells, or solar paired with storage

In other words, moving generation behind the meter does not move you outside the tax.

The State Corporation Commission (SCC) will collect the tax monthly and was directed to develop implementation guidelines within 60 days of the budget's passage. The first collection is expected in September 2026, covering consumption from July 1 forward.

Who Actually Owes the Tax​

Legally, the taxpayer is the data center operator — the entity operating the facility that houses servers — not the colocation tenant or the cloud customer directly.

Practically, almost every colocation Master Services Agreement and cloud hosting terms of service includes a provision for pass-through of taxes, regulatory charges, or power-cost adjustments. If your provider has metered power, an electricity surcharge clause, or a general right to adjust pricing for increased operating costs, expect this cost to appear on your invoice either as an explicit surcharge or baked into a rate increase later this year.

The statutory definition of "data center" is written to exclude traditional telecommunications facilities, but it captures hyperscale campuses, enterprise data centers, multi-tenant colocation facilities, and large edge sites that meet the threshold.

The $600 Million Cap and Refund Twist​

Here is the unusual part: collections are capped at $600 million per fiscal year. Budget documents estimate the tax will generate exactly that — about $1.2 billion over the two-year budget cycle.

If collections exceed $600 million in any fiscal year, the excess is not kept by the general fund. It is placed in a special fund and refunded to data center operators on a pro-rata basis in proportion to the taxes they paid, after the fiscal year closes.

For operators, that means the tax is not quite a flat $0.011 forever. In a high-growth year where statewide data center consumption keeps climbing, the effective net rate after the refund could be slightly lower. For tenants, it adds a wrinkle: any refund goes to the operator first. Whether and how quickly you see it depends entirely on your contract. Do not assume a refund automatically flows to you unless your agreement says it does.

The original Senate proposal looked very different — a tax on backup generator permitted capacity projected to raise roughly $1.8 billion over the biennium. Negotiators scrapped that in favor of the consumption-based approach at about two-thirds the revenue.

The Sales Tax Exemption Survives — For Now​

Virginia has long offered one of the country's most valuable data center incentives: a retail sales and use tax exemption on qualifying computer equipment, software, and related infrastructure. First approved in 2008 and implemented in 2010, the exemption was extended by the legislature to run through 2035.

The Senate budget would have ended it on January 1, 2027, eight years early. The final compromise preserved it.

The numbers explain why this was contentious. A legislative watchdog report found that data centers received about $2.7 billion in state sales tax relief from 2010 through early 2025, with the annual exempted amount reaching $1 billion in fiscal 2024 alone. The new electricity tax was explicitly described by budget negotiators as an offset — the subsidy stays, but a new consumption charge partially pays for the infrastructure that growth demands.

A House proposal would have kept the exemption but added new environmental and energy-efficiency conditions to qualify. That conditional approach did not make the final budget.

Why a Virginia Power Tax Matters Even If You've Never Been to Ashburn​

You don't need a cage in Loudoun County to be affected. Northern Virginia's "Data Center Alley" — centered on Ashburn and stretching through Loudoun, Prince William, and Fairfax counties — is the largest data center market on the planet.

Consider the scale:

• More than 4,900 megawatts of commissioned capacity as of early 2025, more than twice the size of the next-largest global market, with an estimated 70% of global internet traffic passing through the region each day.
• Data centers today consume about a quarter of all electricity delivered in Northern Virginia, and statewide commercial electricity sales have soared in direct parallel with the buildout. Federal energy data through 2024 and preliminary 2025 figures show Virginia leading national growth in commercial power sales, driven overwhelmingly by this sector.
• The state hosts roughly 35% of the world's hyperscale facilities — the 10,000-square-foot-plus, 100-megawatt-plus campuses that power cloud and AI workloads.
• Nationally, the Department of Energy estimated in a 2024 report that data centers could consume between 6.7% and 12% of total U.S. electricity by 2028, roughly double their share at the start of the decade, with Virginia as the leading edge of that curve.

That concentration is why the first per-kWh data center electricity tax anywhere in the U.S. is a national event, not a local one. Even if your business is in Denver, Portland, or Tampa, there is a meaningful chance that some part of your stack — your cloud region (us-east-1 is Northern Virginia for every major provider), your CDN, your email platform, your backup provider — touches capacity that will be taxed.

How the Tax Becomes Your Hosting Bill​

The path from SCC assessment to your books has three stops:

1. Operator pays the SCC. The operator meters total kWh consumed at each site for the month — including IT load, cooling, lighting, and losses — and remits $0.011 per kWh.

2. Operator recovers from customers. Most colocation contracts have one of two mechanisms: metered power billed at cost plus a power-usage-effectiveness (PUE) multiplier, or a flat per-kW-of-critical-capacity rate with an annual power-cost reconciliation. Cloud providers have broader discretion to adjust list prices by region. In both cases, the operator will decide whether to show the charge as a separate "VA Electricity Consumption Tax Surcharge" line item or to absorb and reprice.

3. You record it. The dollar amount is small per server but not per rack, per cabinet, or per terabyte of monthly egress when aggregated across a year.

One market illustration cited during the debate: a continuously operating 500-megawatt facility at typical utilization would owe roughly $48 million per year under the tax. A 1-gigawatt campus would approach $100 million before any cap-related refund. Those are operator-level figures, but they explain why even a partial pass-through changes the economics of Virginia siting.

For a small business, the translation is more modest but still worth modeling before your provider decides how to bill it.

How Much Could It Cost You? A Realistic Math Framework​

You do not need precise facility-level data to estimate your exposure. You need your power footprint — or a reasonable proxy — and the $0.011 rate.

If You Rent Colocation​

Many small and mid-sized businesses rent a quarter rack, half rack, or full rack on metered power. The math is straightforward:

• A single rack provisioned for 5 kW of critical capacity, running at 70% average utilization, consumes roughly 2,520 to 3,024 kWh for the metered IT load in a 30-day month (5 kW × 0.70 × 720 hours). Add cooling and overhead at a typical PUE of 1.3 to 1.5, and the facility-level consumption attributable to that rack is about 3,300 to 4,500 kWh.

• At $0.011 per kWh, the direct tax on that consumption is roughly $36 to $50 per rack per month before any operator markup, management fee, or gross-up.

A two-rack deployment at 8 kW each would be roughly $115 to $160 per month. A private cage with 50 kW critical could be $650 to $900 per month.

Ask your provider two questions in writing: Will the charge be shown as a separate, auditable line item tied to metered kWh, and will any statewide refund be passed through? The answer determines whether you will be able to reconcile it at all.

If You Are Cloud-Hosted​

If you run on a public cloud region in Northern Virginia, you will not see a kWh figure on your invoice. Providers aggregate power, cooling, and infrastructure across millions of customers. Expect one of two outcomes: a regional price adjustment or a general price increase with a footnote referencing regulatory costs.

What you can do is request a regional differential estimate. Even a simple statement such as "no change to us-east-1 pricing at this time" or "a 3–5% regional surcharge effective October 1" gives you a number to budget. If your architecture is portable, comparing the all-in cost of an alternative region (Ohio, Texas, Oregon) for non-latency-sensitive workloads — batch processing, backups, analytics — is a rational exercise, but factor in data-transfer fees and replication costs before you move.

Why 10% Matters​

A one-cent surcharge sounds trivial until you put it against today's industrial rates in Virginia, which hover near $0.08 to $0.11 per kWh for large commercial customers depending on time of day, demand charges, and contract structure. Adding $0.011 is, as consultants told trade press, a little more than a 10% increase in the effective price of electricity for data center use.

Electricity is already 30% to 50% of the cash operating cost of a typical leased-data-center facility. A 10% increase in that single input is a 3% to 5% increase in facility operating cost — the kind of margin that gets passed through in a thin-margin colocation business, not absorbed.

Your 5-Step Checklist Before July 1​

You have a window between now and the first metered month to get ahead of the invoice.

1. Pull Your Contracts This Week​

Locate the sections on taxes, regulatory cost recovery, power billing, and annual rate adjustments in every data center, colocation, managed hosting, and Infrastructure-as-a-Service agreement that touches Virginia.

Flag language like "pass-through of any new tax, levy, or regulatory charge," "electricity cost adjustment," or "operator may adjust pricing upon 30 days' notice." Note the notice period and whether adjustments require a contract amendment or can be implemented by schedule change. Calendar the notice deadlines so you are not agreeing by silence.

2. Get a Written Estimate From Each Provider​

Send a short, documented request:

• Do you plan to pass through the Virginia electricity consumption tax as a separate line item or as part of a general rate increase?
• What meter or allocation methodology will you use for my account?
• What is your estimated monthly amount for my current footprint, and when will it first appear?
• Will any statewide refund of excess collections be credited to customers, and on what schedule?

A provider that answers in specifics is easier to budget for than one that answers in generalities. Keep the responses with your contract file.

3. Model Two Scenarios in Your Budget​

Build a simple monthly row for "Virginia Power Tax Surcharge" alongside your existing hosting line:

• Scenario A — Separate surcharge: Your current hosting rate stays flat; a new variable line appears each month tied to your consumption or allocation. Model it as $0.011 times your estimated facility-attributable kWh, plus any operator markup your contract permits.

• Scenario B — Absorbed increase: The provider raises the base rate. You will not see kWh, but you can still track the increase against your prior baseline to measure drift.

Run both through December 2027 so the biennial window is visible. The point is not precision to the penny — it is to avoid surprise when three providers make three different choices at three different times.

4. Evaluate Portability Without Overreacting​

Moving out of Virginia is the obvious emotional response and often the wrong financial one. Transfer costs, latency to East Coast customers, and inter-region data-transfer fees can quickly exceed the surcharge. A disciplined alternative is partial portability: keep latency-sensitive production in Northern Virginia, but evaluate whether backups, dev environments, or batch analytics can run economically in a lower-cost region.

If you do compare, compare all-in cost per workload, not just headline per-kWh tax.

5. Prepare Your Bookkeeping Structure Now​

Set up the categories before the first invoice arrives. When a new charge has no dedicated account on day one, it inevitably gets lumped into the nearest large account and you lose the ability to benchmark, challenge, or forecast it.

Bookkeeping: How to Track the New Cost Without Losing Visibility​

This is where small finance teams lose leverage — not in negotiating the tax itself, which you cannot, but in proving what you were charged, why, and whether it reconciles.

Give the Tax Its Own Account​

Create a dedicated expense account for the charge. In a chart of accounts, two patterns work well:

• Sub-account of hosting: Expenses:Hosting:VA Power Tax Surcharge
• Sub-account of power/regulatory: Expenses:Regulatory Surcharges:VA Data Center Electricity Tax

Do not post the surcharge to generic Hosting or Cloud Services simply because it arrived on the same invoice. When you keep it separate, three things become possible: you can sum it by provider and by quarter, you can tie it to the underlying consumption when the provider itemizes kWh, and you can reverse or credit it cleanly if a refund materializes.

Reconcile Monthly, Even If the Amount Is Small​

Establish a simple monthly reconciliation that takes no more than 10 minutes per provider:

• Record the invoice date, billing period, reported kWh (if shown), surcharge amount, and any markup rate.
• Recalculate the expected amount: reported kWh × $0.011. Flag variances over a small tolerance — a few percent — for inquiry. Common causes are PUE multipliers applied before the tax, rounding by rack or by facility, or minimum charges.
• If the provider does not report kWh, record the surcharge as reported and add a memo note: "provider-billed, not independently verifiable." Over time, this paper trail is what gives you a factual basis to ask for an audit or a methodology disclosure.

Treat Refunds as a Receivable, Not a Windfall​

If statewide collections exceed $600 million and operators receive a pro-rata refund, that refund is traceable in the budget cycle — fiscal year ends June 30, refunds follow. For an operator, the correct treatment is to accrue a refund receivable when the cap is clearly exceeded, not to wait for cash.

For you as a tenant, do not book income you have not received. If your contract entitles you to a pass-through of refunds, set a memo or contingent note for the expected period (likely late summer after fiscal year-end) and only book it when you receive a credit memo that identifies the billing period and the kWh base it covers. If your contract does not pass through refunds, the ledger should reflect that reality so you do not overstate anticipated savings.

Watch for the Classic Mislabelling​

The most common mistake with new regulatory surcharges is also the most avoidable: the amount gets coded to Sales Tax Paid or Utilities because the name contains "tax" or "electricity."

This is not sales tax. Do not code it to a sales-tax-payable liability account. Do not post it to Utilities unless you are the direct utility customer. For a colocation or cloud customer, this is a regulatory surcharge that is part of the cost of the hosting service — an operating expense, deductible as an ordinary business expense in the period incurred, not a tax you remit to the state yourself.

A second common error is capitalizing the cost as part of a server asset. Power surcharges, like power itself, are period costs. Capitalize the server, expense the electricity and the tax on that electricity as you consume it.

Keep the Source Documents​

Save three artifacts with each month's close:

• the invoice showing the surcharge line (or the rate-increase notice with its effective date)
• the provider's kWh report or methodology note, if any
• your SCC reference — the budget bill language and the SCC implementation guideline when published — so a future reviewer or auditor can trace why the charge exists without hunting for news clippings

In plain-text accounting, this is a simple tag or link: ; document: provider-invoice-2026-09.pdf ; scc-guideline-2026-08.pdf. The habit costs seconds and avoids hours of reconstruction next year.

What Virginia Didn't Fix — and What Other States Are Watching​

Budget compromises leave threads hanging, and Virginia left several.

The budget includes a utility rate carveout for certain large-load customers — manufacturing, industrial, and distribution facilities with electric demand of at least 25 MW and at least 200 employees — capped at 150 MW of aggregate participation unless the commission finds a higher limit in the public interest. Data centers are explicitly excluded from that carveout. Trade observers noted that excluding a whole industrial class from an industrial rate is unusual and will likely keep the debate over cost allocation alive.

Former state and federal utility regulators have also questioned whether a per-kWh tax, by itself, protects residential ratepayers from the broader cost-shifting associated with building new generation and transmission to serve relentless load growth. The tax generates revenue for the general fund; it does not directly reform how utilities commit to expensive upgrades before large-load customers have fully committed to taking the power — a gap that one grid consultant flagged as the missing piece in the otherwise pragmatic budget deal.

For small businesses elsewhere, the precedent matters more than the policy details. No other state has enacted a per-kilowatt-hour consumption tax specifically on data centers — Virginia is the first. But more than two dozen states are actively debating data-center-related legislation this cycle, ranging from equipment tax incentives to use-tax exemptions to clean-energy procurement mandates. Three states that offer equipment sales tax exemptions have recently paused or suspended those programs while they reassess. Expect other legislatures to study Virginia's consumption-tax structure closely, especially if collections hit the cap and the refund mechanism operates as intended.

If you operate multi-region infrastructure, the forward-looking bookkeeping habit is to tag hosting costs by facility state — Hosting:Virginia versus Hosting:Ohio — now. If a second state adopts a similar mechanism, you will already be able to quantify the differential without rebuilding history.

Common Pitfalls to Avoid​

• Assuming the sales tax exemption means you are unaffected. The equipment exemption is intact, but the power tax is new. One does not cancel the other, and both can affect you — one through your provider's capital cost, the other through monthly power recovery.

• Ignoring behind-the-meter power. If your provider markets "on-site generation as resilience," that power is still within the tax base. Do not accept an assertion that self-generated kWh are excluded.

• Letting three providers bill three different ways with no common ledger view. The fastest way to lose control is to code one provider's surcharge to hosting, a second to utilities, and a third to fees. Standardize the account on your side regardless of invoice labeling.

• Booking on cash when the period is monthly. The tax accrues as electricity is consumed, not when the invoice is paid. If you are on accrual basis, the surcharge belongs to the usage month, even if the invoice arrives the following month. This keeps margins by workload accurate.

• Forgetting the sunset. The current law applies through July 1, 2028. Diarize a review in Q2 2028 for extension, modification, or expiration — and keep the surcharge account active until you have confirmation, not speculation.

Keep Your Infrastructure Costs Visible​

New taxes rarely announce themselves loudly on a vendor invoice. They appear as a new line, a footnote, or a quiet adjustment to a rate card. The businesses that handle them best are not necessarily those with the most negotiating power; they are those that can see the change, name it in their ledger, and model it forward.

Start with two concrete moves this month: ask each Virginia-tied provider for a written pass-through estimate tied to your real footprint, and create a dedicated account for the surcharge before the first bill arrives. With that visibility, you can evaluate portability on economics rather than emotion, reconcile each month in minutes, and enter next year's budget cycle with evidence instead of assumptions.

Simplify Your Financial Management​

As you absorb new pass-through costs like Virginia's electricity surcharge alongside hosting, cloud, and regulatory fees, maintaining clear and consistent financial records becomes even more important. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.