Can Deferred Tax Assets and Liabilities Be Netted? (w/Examples) + FAQs

Yes – but only under specific conditions.

If a company has deferred tax assets and liabilities within the same tax jurisdiction and tax-paying entity, U.S. accounting rules allow (and in fact require) these to be offset (netted) against each other on the balance sheet. This means you present a single net deferred tax amount (either an asset or a liability) rather than two separate numbers. However, you cannot net deferred tax items that arise in different jurisdictions or from different entities.

For example, you can’t offset a state tax deferred asset against a federal deferred liability, or a U.S. deferred tax against a foreign one – those must be reported separately. In short, netting is allowed only when the deferred taxes share the same jurisdictional home. Below, we’ll dive deeper into how this works, with clear examples, scenarios, and nuances across federal and state lines.

According to a 2024 Deloitte survey, over 68% of CFOs say that accounting for income taxes (including deferred tax assets and liabilities) is one of their most confusing financial reporting challenges. It’s no wonder – the rules surrounding deferred tax assets (DTAs) and deferred tax liabilities (DTLs) can be complex. One burning question many finance professionals ask is: Can deferred tax assets and liabilities be netted on the balance sheet?

📊 Exactly how GAAP (ASC 740) says you should net deferred taxes (and when you can’t).
⚖️ Why the IRS doesn’t “see” deferred taxes – and what that means for your books.
🌍 State tax twists in California, Texas, and New York that can change your deferred tax strategy.
💡 Real-world examples of netting in action (with pros, cons, and eye-opening scenarios).
🚫 Costly mistakes to avoid when handling deferred tax assets – plus a handy glossary and quick FAQs.

Deferred Tax Assets vs. Liabilities: Can They Really Be Netted?

Let’s start with the core issue: What does netting even mean here? Deferred tax assets represent future tax reductions (tax benefits you’ll receive later, like from losses or deductible differences), while deferred tax liabilities represent future tax increases (tax you’ll owe later due to taxable differences).

Netting means offsetting these against each other to show a single net amount per jurisdiction. In other words, if you have a deferred tax asset and a deferred tax liability that will both affect taxes in the same place (say, at the U.S. federal level), you present only the net balance.

Yes, you can net deferred tax assets and liabilities – but only when they pertain to the same tax jurisdiction and entity. For example, if your company has a $100 deferred tax liability (DTL) from accelerated depreciation and a $40 deferred tax asset (DTA) from a net operating loss, and both are related to U.S. federal taxes, you would report a net $60 deferred tax liability on the balance sheet. The logic is that, in the future, the $40 tax benefit will offset $40 of the tax owed, so showing a single net $60 liability gives a clearer picture of the expected outcome.

However, deferred taxes that arise in different jurisdictions cannot be netted. Each tax jurisdiction stands on its own. For instance, you might have a deferred tax asset from State A and a deferred tax liability from State B – those must be reported separately, because a tax benefit in one state can’t directly offset tax due in another state. The same goes for federal vs. state: a federal DTA won’t offset a state DTL on the financials. In practice, this means companies often calculate and present deferred taxes jurisdiction by jurisdiction.

Why net at all? Netting within a jurisdiction is actually required under U.S. GAAP because it makes the balance sheet simpler and more meaningful. It prevents double-counting by not listing a large asset and a large liability that will essentially cancel out when taxes come due. Instead, you show the net amount which reflects the future tax impact on that jurisdiction after all those timing differences play out.

Netting deferred taxes (when allowed) provides investors a clearer view: a single net deferred tax liability means “overall, we expect to pay more tax in the future,” while a net deferred tax asset means “overall, we expect to pay less tax in the future (we have tax benefits saved up).” Crucially, netting is just about presentation – it doesn’t change the underlying tax outcomes or cash flows, but it aligns the financial statement presentation with the reality that, for a given tax authority, deferred tax assets will reduce some deferred tax liabilities before any tax payment ever happens.

Deferred tax assets and liabilities can be netted, but only within the same tax jurisdiction (and usually within the same consolidated tax-filing group). They cannot be netted across different jurisdictions or different taxpaying entities. Next, we’ll explore exactly what the accounting rules say, how the IRS views this, and special twists for various states and scenarios.

GAAP Netting Rules (ASC 740): How FASB Wants It Done

Under U.S. Generally Accepted Accounting Principles (GAAP), the Financial Accounting Standards Board (FASB) lays out clear guidelines for income tax accounting in ASC 740 (Accounting Standards Codification Topic 740). When it comes to netting deferred tax assets and liabilities, ASC 740’s message is straightforward:

Net deferred taxes within each tax jurisdiction – and present that net amount as a single figure.
Do not net deferred taxes across different jurisdictions or entities.

In technical terms, FASB requires that deferred tax balances be determined separately for each tax-paying component in each tax jurisdiction. A tax-paying component usually means a particular entity or consolidated group that files a tax return. A tax jurisdiction means an authority with its own tax laws – for example, the U.S. federal government, each U.S. state, each foreign country, etc. Once you compute all your deferred tax assets and liabilities for a given jurisdiction (say, U.S. federal), you offset them to arrive at one net number for that jurisdiction. The same goes for each state or country: offset within that bucket, but keep different buckets separate.

If they’re in the same jurisdiction – net them. If not – keep them separate. This is the golden rule. So, if your U.S. federal deferred tax assets total $300 and liabilities total $500, you report a net $200 deferred tax liability for U.S. federal taxes. Meanwhile, if you have a German subsidiary with €50 of deferred tax assets and €20 of deferred liabilities (under German tax law), that subsidiary would show a net €30 deferred tax asset for Germany. These two amounts (U.S. and Germany) would not be combined with each other – they belong to different jurisdictions, so they stay separate on the consolidated balance sheet (one as part of overall deferred tax liability, one as an asset). Essentially, each jurisdiction’s deferred tax position is like its own ledger that shouldn’t be mixed with others.

Balance Sheet Presentation: Thanks to a simplification in accounting rules a few years back, all deferred tax amounts are reported as non-current (long-term) on the balance sheet. (The FASB issued an update in 2015 that eliminated the tricky split of deferred taxes into “current” vs “non-current”.) Now, companies either show a single net Deferred Tax Asset or Deferred Tax Liability (whichever is larger in total) as a long-term item.

If you have multiple jurisdictions, this can result in showing both a deferred tax asset and a deferred tax liability on the balance sheet – for example, if you have a net liability in one jurisdiction and a net asset in another. In that case, you’d list one as “Deferred tax asset” and the other as “Deferred tax liability,” because netting across those jurisdictions isn’t allowed. (Before the rules changed, companies often split deferred taxes into current and non-current, which was confusing and could hide netting issues – now it’s thankfully simpler: all deferred taxes are non-current, making netting rules easier to apply.)

Disclosure: Even though netting is done on the face of the balance sheet, GAAP still requires detailed disclosure in the footnotes. Companies must disclose the components of deferred tax assets and liabilities (e.g. depreciation differences, loss carryforwards, allowances, etc.), often showing the gross amounts before netting. They also disclose any valuation allowances (reductions to deferred tax assets if not likely to be realized – more on that later). Importantly, firms usually break out deferred tax amounts by major jurisdictions in the notes. For instance, a company might reveal how much of its deferred tax asset comes from U.S. federal vs. state vs. foreign. This gives readers visibility into how much is netted where. Regulators like the SEC pay close attention to these disclosures.

The SEC (Securities and Exchange Commission) expects companies to apply the netting rules correctly and not obscure significant deferred tax items. If a company tried to improperly net things that shouldn’t be (say, offset a U.S. liability with a foreign asset), it could draw a sharp SEC comment or even require a financial restatement. In practice, there have been instances where companies expanding into new jurisdictions missed this detail – their accounting systems kept netting all deferred taxes together, and auditors had to fix the presentation to isolate, say, a new foreign deferred tax liability separate from U.S. amounts. The lesson: follow ASC 740’s netting rule to the letter.

What about IFRS? (International Financial Reporting Standards): For those curious, IFRS (specifically IAS 12) also allows offsetting deferred tax assets and liabilities only when they relate to the same taxpayer and tax authority and there is a legally enforceable right to offset current tax payments. In practical terms, IFRS ends up in a similar place as GAAP – deferred taxes are netted by jurisdiction if appropriate. The nuances differ (IFRS, for instance, looks at intent and legal right to settle net), but the outcome (no netting across different countries or different companies) is essentially the same. Since this article focuses on U.S. rules, we’ll stick mostly to GAAP, but rest assured IFRS isn’t giving a free-for-all netting permission either.

In summary, FASB’s ASC 740 requires netting deferred taxes within jurisdictions to produce a cleaner one-line item, but forbids netting between different tax jurisdictions or different tax-filing entities. Always compute and consider deferred taxes on a jurisdiction-by-jurisdiction basis. Next, let’s contrast this accounting view with the perspective of the tax collector – the IRS – and see why deferred taxes are an accounting construct that doesn’t exactly exist in a tax return.

IRS vs. GAAP: Two Different Worlds for Deferred Taxes

From the IRS’s perspective, there’s actually no such thing as a “deferred tax asset” or “deferred tax liability” on your tax return. These terms are purely creations of accounting. The IRS (and other tax authorities) deal with actual taxes: the income, deductions, credits, and payments for each year. They don’t keep an account on their books saying “Company X has a deferred tax asset to use later.” That’s an internal accounting thing companies do to match tax effects with the right time periods in financial statements.

So, when we talk about netting deferred tax assets and liabilities, we’re living in the realm of accounting for income taxes, not the process of filing taxes with the IRS. On your company’s tax return (e.g., the U.S. Form 1120 for corporations), you either owe tax or you don’t for the year, potentially reduced by carryforwards like NOLs or tax credits. There’s no schedule that literally nets a deferred asset against a deferred liability – instead, what happens in real life is that certain tax law provisions allow “netting” of sorts across years (like using a prior loss to offset future income). Those provisions create the need for deferred tax accounting on the books.

Here’s an example: Suppose a company had a tax loss last year, resulting in a Net Operating Loss (NOL) carryforward of $1 million. The IRS lets the company carry that NOL forward to offset taxable income in future years (with some limits). In accounting, that carryforward is recorded as a Deferred Tax Asset (because it’s expected to save taxes in the future – essentially a benefit you earned by having that loss). Now, say this year the company has taxable income. On the tax return, the company will use the NOL to reduce this year’s taxable income – effectively netting last year’s loss against this year’s profit. The IRS just sees a lower taxable income and thus a lower tax bill. On the books, as that NOL is used, the deferred tax asset gets drawn down.

From the IRS viewpoint, nothing was “deferred” – it’s just applying the rules (carryovers, etc.). From the GAAP viewpoint, we had a deferred tax asset that we’re now using to offset a current tax liability. That’s the kind of netting that happens across periods thanks to tax law. But crucially, the IRS doesn’t require or recognize any special combined account for deferred taxes. The financial statements do all the tracking so that each period’s earnings reflect the taxes related to that period’s book income, even if cash taxes will be paid in a different period.

Federal vs. State vs. Foreign on Tax Returns: Each jurisdiction is separate in the eyes of the law. You file a federal return, and (if applicable) separate state returns, and maybe foreign returns. You cannot use a credit from your federal taxes to directly pay a state tax liability, or vice versa. Similarly, you can’t take an NOL from one state and apply it to income in another state (unless those states have a combined agreement, which is rare or limited). This hard separation is exactly why GAAP says “don’t net across jurisdictions” – because legally, a deferred tax asset in one jurisdiction won’t help you pay tax in a different jurisdiction. The IRS doesn’t care that you have, say, excess deductions in California – that won’t reduce your federal taxable income (except indirectly, because state taxes are sometimes deductible on the federal return, but that’s a different concept and limited by law). The point is, each tax authority’s rules stand alone, and any netting of tax benefits against tax costs happens only within that authority’s domain.

Tax Cuts and Jobs Act (2017) – A quick illustration of IRS vs GAAP: When the Tax Cuts and Jobs Act (TCJA) slashed the U.S. corporate tax rate from 35% to 21% (effective 2018), it didn’t change any past deferred tax assets or liabilities in the eyes of the IRS – the IRS doesn’t have those accounts. But for GAAP, companies had to revalue every deferred tax asset and liability to the new rate. This caused some dramatic accounting effects. For example, a company with a $100 deferred tax asset at 35% (worth $35 of future tax benefit) suddenly found that at 21% tax rate, that asset is only worth $21. They had to book a one-time hit to earnings for the $14 drop in value. One famous case: a major U.S. bank with large loss carryforwards took a multi-billion-dollar charge to reduce its deferred tax assets when TCJA passed. On the flip side, companies with big deferred tax liabilities (like those with lots of accelerated depreciation) got an earnings boost, since their future tax bills would be lower. The IRS, however, didn’t “refund” anyone or send a bill – it was all accounting adjustments to align deferred tax balances with the new laws. This highlights that deferred tax accounting is a parallel universe: it mirrors what the IRS will eventually do under current law. When the law changes, the mirror image (deferred taxes) changes immediately on the books, even though the actual cash taxes will be paid or saved over years.

IRS Limitations and Deferred Assets: Another example of IRS rules affecting deferred tax assets: The TCJA also introduced an 80% limitation on NOL usage for losses arising in 2018 and after. That means even if you have a huge NOL carryforward, in any future year you can only use it to offset up to 80% of taxable income (you must pay tax on at least 20% of your income). For accounting, this doesn’t prevent recording an NOL deferred tax asset, but it does mean you might not be able to fully utilize it quickly. If a company expects to continually hit that 80% cap, it might need a valuation allowance against some of its NOL DTA (because part of the NOL might never get used if income keeps growing). The IRS created that rule to ensure every profitable company pays at least some tax each year, and GAAP has to adapt by possibly reducing the recognized benefit of very large NOLs.

In summary, the IRS (and other tax authorities) operate on actual taxable income and laws like carryforwards, but they don’t track “deferred taxes” per se. Deferred tax assets/liabilities are the company’s way (under GAAP) of bridging the timing gap between when something hits the books and when it hits the tax return. When it comes to netting, the IRS world enforces that you can only offset within a given year and jurisdiction according to tax law. The accounting world reflects this by only netting within the same jurisdiction’s deferred taxes, never between. Always remember: a deferred tax liability isn’t a bill from the IRS, and a deferred tax asset isn’t a check from the IRS – they are accounting representations of future tax effects under current laws. Next, we’ll see how this plays out in the multi-jurisdiction context, especially for state taxes.

State Tax Twists: How CA, TX, and NY Change the Deferred Tax Equation

When you move from federal taxes to state taxes, the deferred tax netting rules get even more interesting. Each U.S. state with an income tax is its own jurisdiction with its own tax rules, rates, and quirks. That means a company must calculate deferred tax assets/liabilities for each state separately, and (just as with federal vs. foreign) you cannot net deferred tax amounts between different states or between a state and the federal amount.

Multiple jurisdictions, multiple nets: If your company operates in, say, California, Texas, and New York (three very different tax regimes), you’ll end up with deferred tax computations for each. California might show a net deferred tax asset (perhaps due to state NOLs or temporary differences), Texas might show a small deferred liability (maybe due to its unique tax base), and New York might have another deferred asset or liability. Under GAAP, you keep each of these separate. You might present them aggregated by category (often companies combine all state deferred taxes into one net “state deferred tax asset/liability” line in disclosures), but you do not offset a California deferred asset against a New York deferred liability. Why? Because in reality, a tax benefit in California doesn’t reduce what you owe in New York – those states have separate tax returns and no mechanism to offset each other’s taxes.

Let’s look at specific nuances in these key states:

California (CA): California has a corporate income tax (around 8.84% for most C-corps) and famously decouples from some federal tax rules. For example, California often does not allow full federal bonus depreciation. So a company might depreciate assets slower for CA taxes than for federal – resulting in a deferred tax asset for California (because CA taxable income is higher in early years, but CA will allow those deductions later). California also has had quirks like temporarily suspending NOL usage during certain years for budget reasons. In 2020, for instance, CA disallowed using NOL carryforwards for certain large companies for tax years 2020-2022. What does that mean for accounting? If you had a California NOL deferred tax asset, you couldn’t use it in those years – effectively it was “on hold.” Companies had to consider whether that delay meant any portion of the DTA was not realizable or if it was just deferred a bit longer. Generally, since the NOL usage was reinstated later, it meant the DTA’s timing of utilization changed, but not necessarily that it was un-usable. The key takeaway for California: its deviations from federal law (like different depreciation rules, NOL suspensions, credit usage caps) create unique temporary differences and carryforward rules. You must track a California-specific deferred tax calculation. You net all California-sourced deferred tax assets and liabilities with each other (since they’re under one jurisdiction – the California Franchise Tax Board), but keep CA separate from federal or other states. California’s high tax rate also means deferred tax amounts can be significant – e.g. an expense not yet deductible in CA gives a bigger DTA at ~8.84% state rate (often slightly less after considering federal benefit) than in states with lower rates.
Texas (TX): Texas is interesting because it does not have a traditional corporate income tax. Instead, Texas imposes a franchise “margin” tax on businesses (essentially a tax on gross margin or a simplified profit metric). For GAAP purposes, here’s the twist: If a tax is based on income (even in a broad sense), it falls under ASC 740. Texas’s margin tax, while not called an income tax, is considered sufficiently based on income to count. So companies do record deferred tax assets/liabilities for Texas timing differences. However, Texas’s tax base is different from federal taxable income (for example, it starts with revenue and allows deduction of either cost of goods or compensation, with certain limits). If your company has, say, an expense that is recognized in the financials now but only deductible in the margin tax calculation later, that creates a deferred tax asset for Texas. The Texas tax rate is about 1% (varying by type of business), so the deferred tax amounts might be smaller in magnitude. Still, from a netting standpoint, Texas is its own jurisdiction. You would net Texas deferred tax assets and liabilities with each other, but you wouldn’t net Texas with federal. It’s worth noting that some taxes not based on income are outside ASC 740 entirely – for example, Washington State’s B&O (Business & Occupation) gross receipts tax is not considered an income tax, so no deferred taxes are calculated for it (companies just treat B&O as an expense when incurred). Texas’s tax, by contrast, is treated as an income tax for accounting, which means Texas introduces deferred tax considerations despite having “no income tax” in the traditional sense. This can surprise folks – a company based in Texas might think “no state income tax, no deferred taxes,” but if they pay the franchise tax, GAAP says otherwise.
New York (NY): New York State has a corporate income tax (~6.5% currently), and New York City imposes its own separate tax on corporations (~8% for many businesses). This means a company operating in NYC faces two local jurisdictions on top of federal. Each of those (NY State and NY City) requires separate deferred tax calculations. New York in recent years has aligned more with federal rules in many areas (after a 2015 reform), but differences remain (like certain decoupling or special add-back rules). For example, NY State might not fully conform to some federal deductions or has its own credit programs. Additionally, combined reporting is required for related entities in NY if certain ownership tests are met, meaning you file one return for the group in NY (which allows netting income and losses among those combined members for NY tax purposes). If you have separate subsidiaries, whether they can net deferred tax positions depends on filing method: if two subsidiaries file a combined NY return, you can effectively consider them one tax-paying group for NY (and thus net their deferred taxes together for NY). If they file separately, each has its own NY deferred tax calculation and you wouldn’t net between them. The main point for New York: multiple layers of tax (state vs city) require careful jurisdictional separation. A deferred tax asset from New York State NOLs can’t offset a deferred tax liability for New York City (different jurisdiction), and neither can directly offset federal. Companies often disclose “State and local” deferred taxes aggregated, but internally they must track NY State vs NY City vs others, especially since rates and rules differ.

Beyond these three examples, every state has its idiosyncrasies: different tax rates (some states are ~3% or ~5%, some over 9%), different carryforward periods for NOLs (20 years, or now some conform to the federal unlimited but with 80% limit, etc.), and various credits. No two states are exactly alike, which means your deferred tax assets for state taxes must be assessed state by state. And because of that, no netting across states is allowed in the financials. You can’t use a DTL from one state to hide a DTA from another; each state’s net position should stand on its own.

One more twist: Some states don’t levy corporate income tax at all (e.g., Nevada, Wyoming – no income tax; or Ohio which has a gross receipts tax). In those places, you simply won’t have deferred income taxes for that state (since there’s no income-based tax to create timing differences). This can sometimes make a company’s overall deferred tax balance appear as an asset in one region and a liability in another, reflecting where they operate.

Practical presentation: In practice, companies often aggregate all their state deferred taxes into one net number for the balance sheet (and all foreign into another, etc.), because listing dozens of separate state deferred tax line items would be impractical. How can they do that if netting across states isn’t allowed? They do it carefully: If a company has multiple state net deferred assets (and no state net liabilities), they can sum those assets together into one “Deferred tax asset – state” figure. Likewise, if multiple states each have net liabilities, those might be summed as one “Deferred tax liability – state” figure. But if some states are net assets and others net liabilities, the company can’t offset those against each other. They might present the net liabilities of certain states combined as one liability line, and net assets of other states combined as an asset line. The key is that they’re not arbitrarily offsetting an asset from State A against a liability from State B – they’d show one as an asset and one as a liability if needed. This is a bit of an aggregated approach but still compliant with the rule. The footnotes then spell out the details by jurisdiction.

State tax rate benefit (federal effect): One nuance: State income taxes are deductible expenses for federal tax purposes (within certain limits). This means a state deferred tax asset or liability also slightly affects the federal deferred tax calculation. Often, companies compute a “blended” effective tax rate for certain temporary differences that consider federal+state (e.g., if a temporary difference will reverse in a state-taxable context, the combined tax rate might be something like 25% consisting of 21% federal + 4% state net of federal benefit). While this is getting into the weeds, the takeaway is that even when doing that, the deferred tax is still recorded in the separate jurisdictions (federal vs state), just the measurement might factor in interplay. But presentation-wise, you still segregate by jurisdiction at the end of the day.

In short, state taxes introduce a patchwork of rules that can create multiple deferred tax assets and liabilities which must each be tracked separately. California, Texas, New York (and every other state) each bring their own flavor to the tax cookbook – but GAAP’s netting rule ensures you keep those flavors from mixing on the financial plate. Next, let’s solidify our understanding with some concrete examples and scenarios, including the pros and cons of netting in each case.

Deferred Tax Netting in Action: 3 Examples (Pros, Cons & Scenarios)

To see how netting works in real life, let’s walk through three common scenarios. These examples will illustrate when netting is allowed, when it isn’t, and the reasoning behind it. We’ll also highlight the pros and cons of each scenario and provide a quick example for clarity.

Netting Scenario	Details (Pros, Cons, Example)
Scenario 1: Single Jurisdiction (e.g. U.S. Federal) – Netting Allowed (All deferred taxes under one tax authority)	Pros: Simplifies balance sheet by showing one net number; reflects that DTA will offset DTL when taxes come due in that jurisdiction. Cons: Few cons here – this is standard practice. (One possible downside is that the gross amounts are not on the face of the balance sheet, but they are disclosed in the notes.) Example: Company has $500 DTL (from accelerated depreciation) and $300 DTA (from warranty reserves) for U.S. federal taxes. On the balance sheet, it nets these to report a single $200 Deferred Tax Liability (net) for federal. This indicates an overall future tax obligation of $200 (after using the $300 of future tax benefits against the $500 of future tax costs).
Scenario 2: Different Jurisdictions (e.g. Federal vs. State or US vs. Foreign) – Netting Not Allowed (Deferred taxes span multiple tax authorities)	Pros: Keeping them separate provides transparency – stakeholders see that, say, a $100 DTL in one jurisdiction isn’t mitigated by a $100 DTA elsewhere, since in reality they can’t offset when paying taxes. It prevents overestimating how much one deferred benefit can help overall. Cons: Displays more line items (or at least two net figures) on the balance sheet, which can be a bit more cluttered. Users have to sum across lines to see total deferred tax position. Example: Company has a $100 deferred tax liability for federal taxes and a $40 deferred tax asset for state taxes. These pertain to different jurisdictions (IRS vs. state), so the company cannot net them. It might present “Deferred tax liability – net (federal) $100” and “Deferred tax asset – net (state) $40” separately. The $40 state DTA will reduce future state taxes, but the company still shows the full $100 federal liability it owes to Uncle Sam.
Scenario 3: Multiple Entities & Tax Filing Groups – Depends on Filing Status (Consolidated vs. separate tax filings, unitary state groups, etc.)	Pros: If entities file a combined return in a jurisdiction, they can net deferred taxes between them for that jurisdiction – which maximizes the use of DTAs (one entity’s losses can offset another’s profits). This yields a clearer net position for the group. Cons: If entities file separately, no netting between them is allowed – each must stand alone. Not recognizing this can lead to error (e.g., thinking one subsidiary’s DTL can cover another’s DTA when legally it can’t). Maintaining separate calculations for many entities can be complex. Example: Parent Co. has a subsidiary, each filing separate state tax returns in State X. Parent has a $50 DTL (taxable temporary differences), Sub has a $30 DTA (NOL carryforward) in State X. Because they file separately, Parent Co. will report a $50 deferred tax liability and Sub will report a $30 deferred tax asset – they do not net to $20, since Parent can’t use Sub’s losses on its return. Now, if State X allowed them to file a combined return as a single tax-paying group, it would be a different story: the $30 DTA of Sub could offset $30 of Parent’s DTL, and together the group would show a net $20 DTL for State X. The ability to net in this case hinges on the tax filing method. GAAP mirrors the legal reality – combined tax filers are treated as one (netting permitted among them), separate filers are treated as separate (no cross-netting).

As these scenarios show, netting deferred tax assets and liabilities is straightforward in concept: same bucket, you net; different bucket, you don’t. The “buckets” are defined by tax law jurisdiction and taxpaying entity/group. The pros of netting (where allowed) include cleaner presentation and a focus on the true net obligation or benefit. The cons of netting only appear if someone misapplies it – like netting when you shouldn’t, which can mislead by implying one area’s tax benefit can cover another area’s tax cost.

In practice, most companies aim to use all their deferred tax assets to offset deferred tax liabilities wherever possible, which is why showing net by jurisdiction makes sense. But they also have to be careful not to over-net across lines that shouldn’t cross. Next, we’ll discuss some pitfalls and mistakes companies should avoid in this realm – essentially, how to ensure you’re netting correctly and not introducing errors in your tax accounting.

Avoid These Costly Mistakes

Accounting for deferred taxes is complex, and there are common pitfalls that even seasoned professionals can stumble on. Avoid these costly mistakes when considering netting of deferred tax assets and liabilities:

🚫 Netting Across Jurisdictions: Mistake: Combining deferred tax balances from different jurisdictions (e.g., netting a foreign DTL with a U.S. DTA) in your presentation. Why it’s wrong: Each jurisdiction’s taxes are settled independently – a future tax benefit in one country can’t pay the tax bill of another. Consequence: This can misstate your liabilities or assets and will draw regulator and auditor scrutiny. Always separate deferred taxes by jurisdiction, no exceptions.
🚫 Ignoring Separate Entity Considerations: Mistake: Netting deferred taxes between entities that don’t file a consolidated tax return. For example, assuming a subsidiary’s deferred tax asset can offset the parent’s deferred liability when those entities file separately. Why it’s wrong: If they don’t file a combined return, there’s no legal mechanism to share tax attributes. Consequence: You might overestimate how much benefit you can realize. Make sure to evaluate deferred taxes on an entity-by-entity (or tax-filing-group) basis before netting.
🚫 Forgetting Valuation Allowances: Mistake: Assuming that a deferred tax liability automatically means you can realize a deferred tax asset, and thus not considering a valuation allowance. Why it’s wrong: It’s true that future taxable income from reversing DTLs can help use up DTAs – but only if timing and jurisdiction align. Some DTLs (like those from indefinite-lived assets such as goodwill) might not reverse when needed to absorb DTAs (like NOLs that could expire). Consequence: You could fail to record a needed valuation allowance on a DTA, overstating assets. Always assess DTAs gross, then use DTLs (that truly will reverse and create taxable income in time) as one factor in deciding if a valuation allowance is needed. Don’t assume every DTL is a free pass – especially if it won’t reverse in the foreseeable future or is in a different jurisdiction than the DTA.
🚫 Outdated Tax Law Assumptions: Mistake: Not updating deferred tax calculations and netting approach when laws change. Examples include TCJA 2017 changes (new rate, NOL limitations), or state law changes (like NOL suspension in California). Why it’s wrong: Tax rules define deferred tax values. If the rate drops or usage of losses is curtailed, your deferred tax assets/liabilities need re-measurement and perhaps re-evaluation of realizability. Consequence: If you miss a law change, you might carry deferred taxes at incorrect values or continue netting in a way that’s no longer appropriate. For instance, after TCJA’s 80% NOL rule, some companies needed a valuation allowance on portions of their NOL DTAs – missing that would inflate assets. Keep abreast of tax law updates in every jurisdiction you operate and reflect those in your deferred tax accounting promptly.
🚫 Poor Disclosure or Lack of Transparency: Mistake: Failing to clearly disclose deferred tax components, especially when netting obscures big numbers. For example, not breaking out how much of your net deferred tax asset is from state NOLs or how much of your net liability is from accelerated depreciation. Why it’s wrong: Investors and auditors need to understand what makes up your deferred tax balances and where they come from. Lack of transparency can be seen as a red flag. Consequence: The company might face SEC comment letters or audit findings. It can also lead to misinterpretation of the financial health – e.g., large deferred tax assets might indicate future tax benefits, but if hidden, stakeholders can’t tell if you have potential tax savings or not. Always disclose significant deferred tax assets and liabilities (and any valuation allowances) by type and jurisdiction in the footnotes, even though the balance sheet shows net amounts. This way, you avoid any impression of hiding liabilities or overhyping assets.

By steering clear of these mistakes, you ensure that your deferred tax accounting remains solid and that the netting of DTAs and DTLs is done correctly. The overarching theme: stay true to the jurisdictional and entity boundaries, keep your calculations updated with current laws, and be transparent about what’s behind the numbers.

Key Tax Terms Demystified

To navigate deferred tax discussions confidently, it helps to understand the jargon. Here are some key tax terms (many we’ve touched on) explained in plain English:

Deferred Tax Asset (DTA): A future tax benefit on your balance sheet. It’s like a “prepaid tax” or credit you can use later. Arises from deductible temporary differences (you’ve paid more tax now or had losses that you can use to save tax in the future). Example: an NOL carryforward or an expense recognized in books now but deductible for tax later creates a DTA – meaning you’ll owe less tax in the future than book income would suggest.
Deferred Tax Liability (DTL): A future tax obligation on the balance sheet. It’s essentially tax you’ll have to pay later for things that gave you a break today. Arises from taxable temporary differences (you’ve saved on taxes now or underpaid relative to book income, but will pay more in the future). Example: accelerated tax depreciation (tax law lets you deduct more now, so you pay less tax upfront – but later, when book depreciation continues and tax depreciation is zero, you’ll pay more tax). A DTL means down the road your taxes will be higher than your book income alone would indicate.
Temporary Difference: The difference between an asset or liability’s book value and its tax basis, which will reverse in the future. It’s “temporary” because it eventually goes away – causing a taxable or deductible amount in a future period. These differences are what create DTAs and DTLs. For example, depreciation methods cause temporary differences: book depreciation vs tax depreciation differ, but ultimately total depreciation evens out after the asset’s life (the difference in each period is temporary).
Permanent Difference: A difference between book income and taxable income that never reverses. This arises from items that are in book income but never in taxable income (or vice versa) permanently. Example: fines or penalties might be an expense in the financials but are not tax-deductible – that expense is permanently not tax-deductible, so it reduces book income but never reduces taxable income. Permanent differences do not create deferred taxes because they don’t result in future tax consequences; they affect the effective tax rate but not the balance sheet.
ASC 740: The section of U.S. GAAP that governs accounting for income taxes. It covers how to recognize and measure current and deferred taxes, how to present them (including netting rules), and how to disclose them. When we mention ASC 740, think “accounting rules for taxes.” (It was formerly known under terms like FAS 109 and FIN 48 for specific parts, but now all codified as ASC 740.)
FASB: The Financial Accounting Standards Board – the organization that sets U.S. accounting standards (GAAP). They issue rules like ASC 740. FASB’s rulings are why we net deferred taxes within jurisdictions and classify them as non-current. Essentially, FASB is the rule-maker behind all the accounting treatments discussed.
IRS: The Internal Revenue Service – the U.S. federal tax authority. The IRS collects taxes and administers the Internal Revenue Code. In our context, remember that the IRS cares about your actual tax returns and payments, not your GAAP entries. Many deferred tax issues come from differences between what the IRS taxes and what GAAP reports in a given year.
Tax Cuts and Jobs Act (TCJA) 2017: A major U.S. tax law overhaul, effective mainly in 2018. Key impacts: reduced corporate tax rate from 35% to 21%, introduced the 80% limitation on NOL usage (for post-2017 losses), eliminated carryback of NOLs (corporations can no longer carry losses backward for a refund, except for a brief COVID-19 exception), allowed immediate expensing (100% bonus depreciation) for a few years, and brought in new concepts like GILTI (tax on certain foreign income) and BEAT (an alternate minimum tax for certain payments). For deferred taxes, TCJA’s rate cut caused immediate revaluation of DTAs/DTLs in 2017 (as discussed), and changes like the NOL rules affected how companies assess the usability of deferred tax assets.
Net Operating Loss (NOL): A tax term for when a company’s tax-deductible expenses exceed its taxable revenues in a year – in other words, a tax loss. NOLs can often be carried forward to offset future taxable income (and historically, sometimes carried back to get refunds from prior years). In accounting, an NOL carryforward is recorded as a deferred tax asset (it will save taxes in the future). NOL DTAs are subject to valuation allowances if you might not have profits to use them. TCJA changed federal NOLs to be carried forward indefinitely but limited to 80% of income per year (and eliminated general carrybacks). States have varying NOL rules (some no carryback, 20-year carryforward, some shorter or with quirks like CA’s suspensions).
Valuation Allowance (VA): A reduction against deferred tax assets, reflecting that some or all of those assets may not be realized (used). GAAP requires a “more likely than not” test – if it’s more than 50% likely that you won’t be able to use some deferred tax asset, you must put up a valuation allowance to reduce the asset to the amount you expect to use. Essentially, a VA is a contra-asset that says “we might not earn enough taxable income (or have the right kind of income) to use this deferred tax asset, so we won’t count it fully.” Valuation allowances often come into play for companies with cumulative losses, approaching expiry of losses/credits, or when certain deferred tax assets are dependent on future events that are uncertain. They are assessed separately for each jurisdiction – you might have a VA on state DTAs even if federal doesn’t, or vice versa, depending on prospects in each tax area.
Combined Reporting / Unitary Group: These terms relate to state taxes. A combined report means a group of related companies file one consolidated state tax return (typically to prevent income shifting among affiliates). A unitary group is a set of companies with interdependent operations that a state requires to file together. Why this matters: if companies are in a combined/unitary group, their deferred taxes for that state can be considered together (netting within that group). If they’re separate filers, each stands alone. So, combined reporting can expand the scope of netting within that state. Not all states have combined reporting, and those that do might have specific criteria.
FIN 48 (Accounting for Uncertain Tax Positions): Part of ASC 740 that deals with tax positions that might be challenged by tax authorities. While not directly about netting, it’s worth knowing: companies must accrue a liability if a tax position (say, a deduction or tax credit) is not more-likely-than-not to be sustained on audit. This ensures the financials don’t fully recognize tax benefits that might not survive. FIN 48 liabilities are recorded separately from deferred taxes (usually as an income taxes payable or a reduction of deferred tax assets in some cases). They do not get netted against DTAs/DTLs; rather, they’re an additional consideration. For instance, you might have a deferred tax asset for an NOL, but if part of that NOL is under dispute, you might record an uncertain tax position liability for the portion that might be disallowed.

These terms frequently come up in discussions of deferred taxes and netting. By demystifying them, you can better understand the mechanics behind the numbers and communicate with clarity. Now, to wrap up, let’s address some frequently asked questions on this topic.

FAQs: Deferred Tax Netting – Quick Answers

Q: Can I offset deferred tax assets and liabilities on the balance sheet?
A: Yes. If they relate to the same jurisdiction and tax-filing group, GAAP says to present them net. This results in one net deferred tax asset or liability per jurisdiction, simplifying the balance sheet presentation.

Q: Can a deferred tax asset in one state offset a deferred tax liability in another state?
A: No. Each state’s taxes stand on their own. You cannot use a deferred tax asset from State A to reduce a deferred tax liability in State B – those must be reported separately (no cross-jurisdiction netting).

Q: Did the 2017 Tax Cuts and Jobs Act affect deferred tax assets and liabilities?
A: Yes. The TCJA’s lower corporate tax rate (21%) meant companies had to revalue all deferred taxes (assets dropped in value, liabilities dropped as well). It also changed rules (like NOL limitations) that influence how and when deferred tax assets can be used.

Q: Are deferred tax assets and liabilities always classified as long-term now?
A: Yes. Under current GAAP, all deferred tax assets and liabilities are reported as non-current (long-term). This rule change (ASU 2015-17) simplified financial statements by removing the current vs. non-current split for deferred taxes.

Q: Can deferred tax assets expire unused?
A: Yes. If the underlying tax attribute (like an NOL or tax credit) has an expiration date and the company doesn’t earn enough taxable income to use it in time, that deferred tax asset can expire. In such cases, a valuation allowance is usually recorded to anticipate the non-use.

Q: Does having a deferred tax liability mean I’ll definitely pay more tax in the future?
A: Yes, generally. A deferred tax liability indicates you’ve received a tax benefit now (or in prior years) that will reverse later, causing higher taxable income in the future. It’s essentially tax that’s been deferred to future periods – assuming tax laws remain the same, when that difference reverses, you’ll pay that tax.

Q: Is a deferred tax asset like a tax refund or prepayment I can collect?
A: No. A deferred tax asset isn’t cash or a refund from the IRS – it’s an accounting representation of a future tax reduction. It will materialize as lower tax payments in future years if and when you have sufficient taxable income to absorb it. Think of it as “store credit” with the tax authorities for future use, not a check in hand today.

Q: Do all companies net deferred taxes the same way?
A: Yes, if following GAAP. Any GAAP-prepared financials should net deferred tax assets and liabilities by jurisdiction. Minor differences might occur in presentation (some aggregate certain jurisdictions), but the fundamental rule is consistent. Any deviation (like netting across jurisdictions) would be a GAAP violation. Internationally, IFRS-based companies also follow a similar netting concept with slightly different criteria.