Utah Supreme Court
Can multiple writings establish accountant liability to third parties? Reynolds v. Bickel Explained
Summary
Scott Reynolds sued accountants Tanner L.C. and Jeffrey Bickel for professional negligence after they underestimated his tax liability from a business sale by $1.5 million. The district court granted summary judgment, finding no writing satisfied Utah Code section 58-26a-602(2)(b)’s requirement that accountants identify in writing to their client that services were intended to be relied upon by a third party.
Practice Areas & Topics
Analysis
In Reynolds v. Bickel, the Utah Supreme Court addressed a critical question for professional liability practitioners: whether Utah Code section 58-26a-602(2)(b)’s writing requirement can be satisfied through multiple related documents rather than a single explicit statement.
Background and Facts
Scott Reynolds retained Tanner L.C. to minimize his personal tax liability from selling three S corporations. The accounting firm’s partner, Jeffrey Bickel, provided ongoing tax advice through email exchanges and spreadsheet analyses. However, Bickel significantly underestimated Reynolds’ tax liability by $1,513,641. When Reynolds sued for professional negligence, defendants argued they were protected by Utah’s third-party liability statute because they never explicitly identified in writing that their services were intended for Reynolds’ reliance.
Key Legal Issues
The central issue was interpreting Utah Code section 58-26a-602(2)(b), which protects accountants from third-party liability unless they both knew the client intended the third party to rely on their services and “identified in writing to the client” that the services were intended for the third party’s reliance. The district court granted summary judgment for defendants, finding no single writing satisfied this requirement.
Court’s Analysis and Holding
The Utah Supreme Court reversed, applying statute of frauds principles by analogy. The court held that multiple writings can satisfy section 58-26a-602(2)(b) if there is a “nexus” between them, either through express or implied reference. Here, Bickel’s emails responding to spreadsheets about Reynolds’ tax liability, combined with the circumstances showing only Reynolds could benefit from the advice, collectively demonstrated the required written identification of intended reliance.
Practice Implications
This decision significantly expands potential accountant liability to third parties. Practitioners should advise accounting clients that informal communications discussing third-party tax consequences may collectively satisfy the writing requirement, even without explicit acknowledgment statements. The ruling also demonstrates how courts may apply contract law principles to interpret professional liability statutes, making comprehensive documentation strategies essential for risk management.
Case Details
Case Name
Reynolds v. Bickel
Citation
2013 UT 32
Court
Utah Supreme Court
Case Number
No. 20120396
Date Decided
June 4, 2013
Outcome
Reversed
Holding
An accountant’s liability to third parties under Utah Code section 58-26a-602(2)(b) can be established through multiple related writings that collectively identify the third party’s intended reliance on professional services, even without an explicit statement in a single document.
Standard of Review
Correctness for questions of law regarding summary judgment
Practice Tip
When representing accountants, ensure any communications regarding third-party beneficiaries are carefully drafted to avoid inadvertently satisfying the writing requirement of Utah Code section 58-26a-602(2)(b) through a series of related documents.
Need Appellate Counsel?
Lotus Appellate Law handles appeals before the Utah Court of Appeals, Utah Supreme Court, California Court of Appeal, and the United States Court of Appeals for the Tenth Circuit.
Related Court Opinions
About these Decision Summaries
Lotus Appellate Law publishes these summaries to keep practitioners informed — not as legal advice. Each case turns on its own facts. If a decision here is relevant to your matter, we’re happy to discuss it.