Table of Contents

Share this Article

Share |


Deficiencies in Auditing Related-Party Transactions: Insights from AAERs

Timothy J. Louwers, Elaine Henry, Brad J. Reed, Elizabeth A. Gordon

SUMMARY: After several high-profile frauds involving related-party transactions, regulators have raised questions as to whether current auditing standards remain appropriate. In this study, we examine 43 SEC enforcement actions against auditors related to the examination of related-party transactions. We conclude that the audit failures in these fraud cases were more the result of a lack of auditor professional skepticism and due professional care than any deficiency in current auditing standards. In other words, revised auditing standards would likely not have prevented these auditing failures, raising questions about the need for auditing standard revision for related-party transactions at this time. Despite this finding, we conclude with some suggestions to improve the auditing of related-party transactions, such as including the discussion of related-party transaction abuse during SAS No. 99 mandated fraud awareness “brainstorming” sessions.

Received: March 2008; Accepted: April 2008

Announcements

Welcome to the online journal website for AAA Journals.

Visitors to the site will be able to:
  • save favorite articles
  • more search options
  • save searches
  • much, much more!

Register for a Profile

Not Yet Registered?

Welcome to our new, improved website!

AAA Members

You received an email with a link to register on this site.

If you followed that link, then you're already registered, and you can log in with your email address (NOT your AAA login) and the password you created for this site.

If you don't have that email, you still need to register.


Not an AAA Member?

Please register on this site when you first use it by clicking the link above.

After you complete this process once, you will be able to log in with your email address and the password of your choice.

Library access?

Institutional subscribers' access via IP ranges is unchanged.


For more information, please click here.