PLR 200234008: Company may switch to current deductions for software development costs

Number
200234008
Outcome
Approved
Document type
Private Letter Ruling
IRS subject
From Amortization to Current Deduction
Code sections
§ 174
Ruling dated
April 23, 2002
Publicly released
August 23, 2002

Apply this to your situation

This page covers one taxpayer's ruling, issued in 2002, which can't be cited as precedent. Ask about your situation and see what the current Code and IRS guidance say, with citations.

Currency note: this determination was released in 2002
Statutory amendments, regulation changes, court decisions, or later IRS guidance may have changed the analysis since then. Treat this page as historical context, not current tax advice. Verify current law before relying on any specific rule, threshold, or position mentioned here.
Not precedent. Under 26 U.S.C. § 6110(k)(3), this written determination may not be used or cited as precedent. It resolved one taxpayer's situation on its specific facts, and identifying details were redacted by the IRS before release. The official IRS release (linked on this page as a PDF) is the authoritative source.
About this page: The plain-English summary and ruling snapshot below were written by Ezel based on the official IRS release. The full text is the IRS's own document.
View official IRS release (PDF)

Plain-English summary

A company that had capitalized and amortized its software development costs asked to switch to deducting new costs as current expenses for its 1999 tax year. The IRS consented under Rev. Proc. 69-21, which then allowed treatment similar to the rules for research expenses under IRC § 174. The company had to keep supporting records and deduct all qualifying software development costs consistently, including costs incurred by third parties when it bore their risks. Costs capitalized before the change would continue to be amortized under the existing method. The IRS left the classification of individual costs for examination of the return.

Ruling snapshot

  • Question: May the company change from amortizing software development costs to deducting new costs currently?
  • Outcome: Approved, subject to recordkeeping and consistent treatment
  • Key authorities: IRC § 174; Rev. Proc. 69-21

Full text (IRS public release)

Internal Revenue Service
Department of the Treasury

Number: 200234008
Washington, DC 20224
Release Date: 8/23/2002
Index Number: 174.05-02
Person to Contact:

Telephone Number:

Refer Reply To:
CC:ITA:2 PLR-105767-02
Date:
Attn: April 23, 2002

X=

Y=

Dear :

This refers to a request filed by X (the taxpayer) for consent to adopt the current expense method of deducting all computer software development costs pursuant to the provisions of Rev. Proc. 69-21, 1969-2 C.B. 303, for the tax year beginning January 1, 1999 (year of adoption/year of change).

The taxpayer represents that it currently capitalizes and amortizes ratably all computer software development costs pursuant to an election under Rev. Proc. 69-21. The taxpayer represents that its software development costs are incurred for projects developed by the taxpayer and for projects developed by third parties for the taxpayer. Where projects are developed by third parties, the taxpayer bears the risks incurred. As of the first day of the year of change, the total amount of capitalized (but unamortized) software development costs was Y.

Section 3.01-1 of Rev. Proc. 69-21 states that the costs of developing software by a taxpayer (whether or not the software is patented or copy-righted) in many respects so closely resembles the kind of research and experimental expenditures that fall within the purview of section 174 of the Internal Revenue Code as to warrant accounting treatment similar to that accorded such costs under that section. Accordingly, it was stated that the Service would not disturb a taxpayer’s treatment of costs incurred in developing software where all of the costs properly attributable to the development of software by the taxpayer are consistently treated as current expenses and deducted in full in accordance with rules similar to those applicable under section 174(a) of the Code.

Likewise, section 3.01-2 of Rev. Proc. 69-21 states that the Service will not 2

disturb a taxpayer’s treatment of costs incurred in its developing software where all of the costs properly attributable to the development of software by the taxpayer are consistently treated as capital expenditures that are recoverable through deductions for ratable amortization, in accordance with rules similar to those provided by section 174(b) of the Code.

Rev. Rul. 68-144, 1968-1 C.B. 85, holds that where a taxpayer had elected to currently expense all research and experimental expenditures (with the exception of those on particular projects to which the deferred expense method was elected), it cannot in a later year elect the deferred expense method on new projects unless permission is granted by the Commissioner. Rev. Rul. 71-248, 1971-1 C.B. 55, adopts this requirement -- permission to change to a different method must be approved by the Commissioner -- to software development costs. Once permission is granted, such method must be used consistently unless permission is granted to change to another method with respect to part or all software development costs. Rev. Rul. 71-248 further requires that any change to a different method shall only be authorized by a letter ruling.1

Based on the facts presented here, consent is hereby granted the taxpayer to adopt the current expense method for software development costs pursuant to section 3.01-1 of Rev. Proc. 69-21 for costs paid or incurred on or after the first day of the year of adoption provided:

(1) the taxpayer keeps its books and records for the year of change and for subsequent taxable years on the method of accounting granted in this letter. This condition is considered satisfied if the taxpayer reconciles the results obtained under the method used in keeping its books and records and the method used for federal income tax purposes and maintains sufficient records to support such reconciliation;

(2) the taxpayer currently deducts all software development costs, whether incurred by the taxpayer or by third parties (where the taxpayer bears the risks incurred), as determined under section 3.01-1 of Rev. Proc. 69-21, paid or incurred during the year of adoption and later tax years unless permission is granted to change to another method with respect to part or all of the costs; and

(3) the taxpayer deducts the balance of the software development costs

1
Rev. Proc. 2000-50, 2000-52 I.R.B. 601 (Dec. 26, 2000), which permits changes in treatment of software development costs pursuant to the automatic change of accounting rules (and which supercedes Rev. Proc. 69-21) is not applicable to the year of change in this ruling. 3

capitalized prior to the first day of the year of change, in accordance with its present methods of amortizing such costs.

In connection with the consent granted in this letter, it is understood that the responsibility for making determinations as to whether costs paid or incurred by the taxpayer constitute software development as defined in section 2 of Rev. Proc. 69-21 is a matter to be considered upon examination of the taxpayer’s return.

The taxpayer should attach a copy of this letter to its tax return for the year of adoption as evidence of its authority for adopting the current expense method.

This ruling is directed only to the taxpayer who requested it. Section 6110(j)(3) of the Code provides that it may not be used or cited as precedent.

Sincerely yours,
Associate Chief Counsel
Income Tax and Accounting
By: _______
Clifford M. Harbourt
Senior Technician Reviewer, Branch 2

What does the Code say today, for your facts?

This determination bound one taxpayer and cannot be cited. Ezel checks the current Internal Revenue Code and IRS guidance against your situation, with citations.

Opens in Ezel Pro.

  • Checks the law as it stands today, not only this page
  • Cites every source it relies on, so you can verify it
  • Chat, drafting and research in one workspace