Anaconda Co. v. Department of Revenue

565 P.2d 1084, 278 Or. 723, 1977 Ore. LEXIS 1022
CourtOregon Supreme Court
DecidedJune 28, 1977
DocketTC 991, SC 24690
StatusPublished
Cited by31 cases

This text of 565 P.2d 1084 (Anaconda Co. v. Department of Revenue) is published on Counsel Stack Legal Research, covering Oregon Supreme Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Anaconda Co. v. Department of Revenue, 565 P.2d 1084, 278 Or. 723, 1977 Ore. LEXIS 1022 (Or. 1977).

Opinions

[725]*725LINDE, J.

Plaintiff appeals from a decision of the Tax Court sustaining a tax deficiency assessment ordered by the Department of Revenue. Anaconda Co. v. Dept. of Revenue, 6 OTR 475 (1976). The main issue presented is the effect of the department’s noncompliance with the statute entitling the taxpayer upon request to confer with the department before a final assessment is made.

The department began an audit of an Anaconda subsidiary, the Anaconda Wire and Cable Company, in 1969 to determine whether the subsidiary’s taxes should have been reported in combined, unitary returns with those of the parent company. In December 1970 the department sent Wire a deficiency notice proposing to assess $133,526.11 in additional taxes for the years 1965-1968. After a 60-day extension allowed by the department, taxpayer in March 1971 filed a protest and requested a conference. The department replied in April that before scheduling a conference it would have the file reviewed by a Mr. Tepper, who would call the taxpayer.

During the next seven months, however, Mr. Tep-per apparently did not get around to this file, and no conference was held or scheduled. In November 1971 the department proceeded to send notices of deficiency assessments to taxpayer, with an explanation that the case was approaching the one-year statutory deadline, ORS 314.410(4), and that Mr. Tepper would contact taxpayer when he could find time to review the file. In reply taxpayer requested withdrawal of the deficiency assessment and offered to extend the deadline for six months pursuant to ORS 314.410(6). It received no response.

Orders assessing a much reduced deficiency and involving both Wire and another subsidiary, the Anaconda American Brass Company, were finally issued in September 1974 and August 1975 after a [726]*726belated hearing and other proceedings during 1973-1975. While these proceedings gave rise to a second issue in the Tax Court and on appeal here, we do not reach it if the department’s failure to follow the statute invalidated the original assessment.

The assessment of deficiencies in income tax returns is governed by ORS 314.405. Subsection (2) allows the taxpayer 30 days after notice is mailed to pay the deficiency or to protest. The subsection continues:

If requested by the taxpayer in his written objection to the proposed deficiency, the taxpayer shall have an opportunity to confer with the department or its delegate as to the proposed assessment at any time prior to the date such assessment is made.

Subsection (8) of the same section provides that "deficiency assessments ... shall be made pursuant to this section, and not otherwise,” within specified time limits.

The department concedes that it made the assessment before according taxpayer the requested opportunity to confer, and thus "otherwise” than provided in ORS 314.405. Indeed, the department’s own rules recognized that a taxpayer "is entitled to a conference” before the assessment, but after assessment a conference is no longer "a matter of right.” OAR 150-314.405(3) (1971). The department argues, however, that it granted taxpayer a post-assessment conference which served the "intent and purpose” of the statute and that its violation of the rule and the statute should not invalidate the assessment. The Tax Court agreed with the department’s conclusion on this issue. We reverse.

The Tax Court stated the question to be whether the statutory directive is "mandatory” or "directory,” and that this question, in turn, was to be determined as a "general mile” by whether plaintiff can show abridgment of some substantial right by the failure to follow the statute. This approach tends to confuse two [727]*727distinct issues. The first concerns the intended effect of a particular statutory requirement. The second is whether failure to follow a required procedure may nevertheless be excused if it did no harm in the individual case.

First, it should be clear that the catchwords "mandatory” or "directory” do not serve as premises for deciding whether noncompliance with a prescribed procedure voids administrative action; they are labels for the conclusion. Action is not invalidated because a statutory requirement is "mandatory” or permitted to stand because the requirement is "directory;” rather, the requirement will be called one or the other according to the effect sought to be attached to noncompliance. Such an issue cannot be decided by examining whether the legislature "directed” that the procedure be followed or "mandated” it, for the issue arises only when the legislative words make compliance obligatory. So understood, the conventional usage of "mandatory” or "directory” may be harmless, but for the risk of encouraging an agency to misconstrue a decision that a procedural failure is not fatal into a holding that compliance is not legally required.

Since the question always arises from a particular enactment, there can be no "general rule” for concluding when failure to follow an obligatory procedure nevertheless does not invalidate an action. It is a matter of interpretation, not much helped by general formulas in opinions construing different statutes in this or other states. Statutes are not fungible, and their interpretation is not a form of common law. It is, of course, possible for a legislature to mandate certain procedures while limiting the legal effects of noncompliance, as for instance in the Public Meetings Law,1 but draftsmen commonly give no attention to the [728]*728matter and leave courts to attribute the more probable intention to the lawmaker. Thus procedures designed to protect individuals dealing with an agency more likely are meant to be "mandatoiy” than provisions, equally obligatory, that are designed to assure legally and fiscally correct public administration in general, though the text or background of a particular enactment may show otherwise. Similarly the nature and extent of the disadvantage sought to be avoided by the procedure can bear on the probable intent with respect to noncompliance. See Childs v. Marion County, 163 Or 411, 97 P2d 955 (1940). Thus a holding setting aside action for failure to comply with one protective requirement of a statute does not necessarily mean that failure to comply with other directives in the same or a similar statute will necessarily lead to the same result. See, for instance, Childs v. Marion County, supra; Equitable Savings & Loan Association v. State Tax Commission, 3 OTR 1, aff'd 251 Or 70, 444 P2d 916 (1967).

Moreover, in the present case the text and its prior interpretation by the agency charged following it are not silent on the question. ORS 314.405(2) states that "the taxpayer shall have an opportunity to confer” before the assessment is made. This requirement dates from 1933. Oregon Laws 1933, ch 388, § 4. The department’s rule recognized it as obligatory.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Scott v. Department of Revenue
370 P.3d 844 (Oregon Supreme Court, 2016)
Nicolynn Properties LLC v. Dept. of Rev.
21 Or. Tax 320 (Oregon Tax Court, 2013)
Public Utility District No. 1 v. Department of Revenue
17 Or. Tax 290 (Oregon Tax Court, 2005)
Keil v. Department of Revenue
16 Or. Tax 1 (Oregon Tax Court, 2001)
ONRC Action v. Columbia Plywood, Inc.
26 P.3d 142 (Oregon Supreme Court, 2001)
Eby v. Department of Revenue
15 Or. Tax 247 (Oregon Tax Court, 2000)
Preble v. Department of Revenue
14 Or. Tax 276 (Oregon Tax Court, 1998)
Robblee v. Department of Revenue
942 P.2d 765 (Oregon Supreme Court, 1997)
Johnson & Johnson v. Taxation & Revenue Department
1997 NMCA 030 (New Mexico Court of Appeals, 1997)
Pacheco-Gonzalez v. SAIF Corp.
860 P.2d 822 (Court of Appeals of Oregon, 1993)
Benzinger v. Oregon Department of Insurance & Finance
812 P.2d 36 (Court of Appeals of Oregon, 1991)
Salem Police Employees Union v. City of Salem
781 P.2d 335 (Oregon Supreme Court, 1989)
Kent v. Department of Revenue
9 Or. Tax 356 (Oregon Tax Court, 1983)
Hoffman v. City of Portland
654 P.2d 1106 (Oregon Supreme Court, 1982)
City of Yakutat v. Ryman
654 P.2d 785 (Alaska Supreme Court, 1982)
State v. Stroup
620 P.2d 1359 (Oregon Supreme Court, 1980)
Suwol v. Department of Commerce
597 P.2d 1274 (Court of Appeals of Oregon, 1979)
Cooley v. Roman
596 P.2d 565 (Oregon Supreme Court, 1979)
Matter of Sawyer
594 P.2d 805 (Oregon Supreme Court, 1979)

Cite This Page — Counsel Stack

Bluebook (online)
565 P.2d 1084, 278 Or. 723, 1977 Ore. LEXIS 1022, Counsel Stack Legal Research, https://law.counselstack.com/opinion/anaconda-co-v-department-of-revenue-or-1977.