Connect with us

Accounting

Navigating peer reviews and DOL inspections of 401(k) audits

Published

on

Peer reviews and Department of Labor inspections of 401(k) audits can be challenging for CPA firms, especially small and midsized firms. Auditors often find themselves facing questions about their methods, documentation, and procedures, with feedback ranging from legitimate findings to subjective preferences. 

Knowing how to distinguish between what is required by standards and what is opinion is crucial for auditors to confidently navigate these reviews and inspections.

Before diving into some real-world examples, it’s important to emphasize that understanding the standards governing 401(k) audits is non-negotiable. Compliance risks in auditing employee benefit plans can have serious consequences for CPA firms, including heavy fines, reputational damage, and, in extreme cases, the loss of a firm’s license to practice. 

Audit

BillionPhotos.com – stock.adobe.

These risks underscore why it’s vital for firms to fully understand the nature of any findings they face and the reasons behind them. To effectively defend against a reviewer’s findings, auditors must not only be familiar with the standards but also be able to reference them during reviews. Having a deep understanding of the standards empowers CPA firms to push back when necessary and confidently challenge findings that are based on subjective opinions rather than clear requirements.

The fine line between standards and opinion

A good example of this confusion is the issue of audit documentation for Form 5500 filings. As part of the audit procedures, the auditor must obtain and read the draft Form 5500 to identify material inconsistencies, if any, with the audited ERISA plan financial statements. However, nowhere in the codified standards does it say that a final copy must be maintained in the audit binder when management agrees to make the requested changes. 

Consider this real-world situation: As part of an audit, “Sam” reviewed the draft Form 5500, and identified material inconsistencies that needed to be corrected. Both management and the service provider agreed, and the changes were made to Form 5500 so no material inconsistencies remained. 

However, the changes were made on October 15, and Sam did not place the final draft in the audit binder, leaving only the original draft in the documentation. A peer reviewer dinged Sam’s firm, claiming that a final copy should have been in the binder.

What’s the standard? The standard is to review the draft Form 5500 to ensure that it is substantially complete and doesn’t contain material inconsistencies, which is exactly what they did. If Sam’s CPA firm had familiarized themselves with the standards — in this case, AU-C Section 703, “Considerations Relating to Form 5500 Filing” — they could have confidently pushed back against the peer reviewer. Instead, they accepted the penalty, not because of a legitimate issue, but because the auditor didn’t know the standard well enough to defend his position.

Key takeaway: If you’re facing findings, always refer to the specific standards. If the standards don’t explicitly require what the reviewer is claiming, it’s a subjective opinion, not a matter of compliance. Don’t be afraid to push back when necessary.

You don’t get points for extra credit

Confusion doesn’t always start at the peer review level. It can happen before the audit is submitted, among your own audit team. A good example of this involves whether auditors are required to verify the census data used for plan compliance tests, such as discrimination testing.

A compliance officer at a CPA firm wanted her audit team to verify the accuracy of the census data used in compliance testing. One of her auditors pushed back, pointing out that nowhere in the standards does it say auditors must reperform compliance tests or verify census data. 

Instead AU-C 703, Section .A31 only requires auditors to confirm that a plan’s TPA has performed the relevant IRC compliance tests, and whether any failures were identified and corrected. The auditor is only responsible for ensuring that the plan performed the required tests and passed, not for redoing the tests themselves.

What’s the lesson? Auditors are often pressured to perform steps that aren’t required by the standards. In this case, verifying the census data might seem like thorough auditing. How else would you know they passed correctly if you didn’t also know the census data was accurate? But it’s not required. As long as the compliance testing has been performed and reviewed by management, the standard is satisfied. Double-checking the compliance testing only adds unnecessary time to what is already a laborious audit process.

Key takeaway: Understand what is required by the standards and what is simply “nice to do.” Over-auditing isn’t necessary and can lead to inefficiencies. Know where to draw the line between what’s required and what’s not.

What you don’t know can hurt you

Another area of confusion arises when it comes to testing benefit payments and distributions in defined contribution plans. The AICPA Auditing and Accounting Guide for Employment Benefit Plans provides several acceptable methods for testing participant benefit distributions and withdrawals. Some methods make sense in today’s digital age — others, not so much. 

A DOL agent reviewing a 401(k) audit claimed the audit was deficient because the firm didn’t use cancelled checks to test benefit payments. However, the auditor had used an alternative method: comparing the payee’s name on electronic funds transfers to participant records, which is a satisfactory method explicitly mentioned in the AICPA Guide (Chapter 5, “Auditing Considerations for DC Plans”). The DOL agent argued that without the cancelled checks, the benefit payments couldn’t be fully tested.

What’s the lesson? The AICPA Guide lists several methods for testing benefit payments, including comparing EFT records. Cancelled checks, while still a valid testing approach, are no longer commonly returned by banks, making it an impractical method in today’s world. By pushing back with reference to the audit guide, the auditor successfully convinced the DOL agent that their approach was compliant, even though it wasn’t the method the agent preferred.

Key takeaway: Know the multiple methods allowed by the audit guide for testing benefit payments. If a peer reviewer or inspector prefers a method that’s not required by the guide, don’t hesitate to defend your choice of an alternative method.

Practical tips for navigating peer reviews and DOL inspections

While peer reviews and DOL inspections can seem intimidating, you can protect yourself and your firm by taking a few simple steps:
1. Know the standards: This can’t be emphasized enough. If you’re uncertain about a finding, look it up. Knowing the codified standards allows you to differentiate between subjective opinion and objective requirements.
2. Be ready to push back: Not all findings are grounded in standards. Some reflect personal preferences or common practices that aren’t required. Always ask for clarification on where the requirement is codified before accepting a finding.
3. Document, document, document: Proper documentation is key. Whether it’s the Form 5500 review or compliance testing, maintain thorough records. This doesn’t mean you need to over-audit, but it does mean you need clear evidence of compliance with the required steps.
4. Use the AICPA Audit Guide: This resource is invaluable for addressing many of the grey areas in 401(k) audits. Refer to the guide when determining which procedures to follow, especially in areas like benefit distributions where there are multiple testing methods.
5. Seek clarification on ambiguities: When faced with a finding that you’re unsure about, consult with the AICPA’s audit guide or the standards. Engage in a constructive dialogue with peer reviewers or DOL inspectors to clarify what’s required versus what’s a matter of personal preference.
Navigating a peer review or DOL inspection of your 401(k) audit can be complex, but it doesn’t have to be daunting. The key to success lies in your understanding of the standards, knowing when to push back against subjective opinions, and using the right resources to support your audit process. 

As demonstrated in the examples above, a strong grasp of the ASC and the AICPA’s audit guide can be the determining factor between a successful audit review and one that results in costly penalties or even a failed inspection. Stay informed, stay prepared, and always ensure your practices align with the written standards — not subjective opinions.

Continue Reading

Accounting

PwC AI agent acts proactively to preserve value

Published

on

Big Four firm PwC announced new agentic AI capacities, including a model that proactively identifies areas of value leakage and acts inside the tools teams already use to fix them itself. 

The new solution, Agent Powered Performance, combines continuous AI-driven insight with embedded execution to address the problem of businesses only finding problems when they have already hurt performance. By actively monitoring and working inside the client’s existing systems, though, PwC’s agents can actively and autonomously address such issues. 

The software, which is supported by PwC’s recently released Agent OS coordination platform, is  embedded in enterprise systems to sense where value is leaking, think through the most effective performance strategies using predictive models and industry benchmarks, and act directly in tools like ERP or CRM software to make improvements stick. 

The system connects directly into ERP environments, continuously monitors key metrics, and acts inside the tools teams already use. For example, a supply chain agent might detect rising shipping costs and automatically reroute deliveries to reduce spend. Finance agents can spot and correct billing errors before they reach the customer. Clients typically see measurable efficiency gains in the first quarter, with continued improvements over time as the system learns and adapts.

“Too many transformations still rely on one-off pilots and stale data, stretching the gap from insight to impact and suffocating ROI,” said Saurabh Sarbaliya, PwC’s principal for enterprise strategy and value. “Agent Powered Performance flips the economics by distilling PwC’s industry transformation playbooks into AI agents that turn static insights into compounding gains, without rebooting each time.”

Agent Powered Performance is platform-agnostic and built on an open architecture so it can work across different LLMs based on client preferences and task-specific needs. It works with major enterprise platforms including Oracle, SAP, Workday and Guidewire.

Agent OS Model Context Protocol

PwC also announced that its Agent OS AI coordination platform now supports the Model Context Protocol, an open standard from Amazon-backed AI company Anthropic. 

By integrating this standard, agent systems registered as MCP servers can be used by any authorized AI agent. This reduces redundant integration work and the overhead of writing custom logic for each new use case. By standardizing how agents invoke tools and handle responses, MCP also simplifies the interface between agents and enterprise systems, which will serve to reduce development time, lower testing complexity, and cut deployment risk. Finally, any interaction between an agent and an MCP server is authenticated, authorized and logged, and access policies are enforced at the protocol level, which means that compliance and control are native to the system—not layered on after the fact. 

This means that agents are no longer siloed. Instead, they can operate as part of a coordinated, governed system that can grow as needs evolve, as MCP support provides the interface to external tools and systems. This enables organizations to move beyond isolated pilots toward integrated systems where agents don’t just reason, but act inside real business workflows. It marks a shift from experimentation to adoption, from isolated tools to scalable, governed intelligence.

Research Composer

Finally, a PwC spokesperson said the firm has also launched a new internal tool for its professionals called Research Composer, a patent-pending AI research agent embedded in the firm’s ChatPwC suite, designed to accelerate insight generation by combining web data with PwC-uploaded content. 

Professionals will use the Research Composer to produce in-depth, citation-backed reports for either the firm or its clients. The solution is intended to enhance the quality of client work by equipping teams with research and strategic analysis capabilities. 

The AI agent prompts users through a step-by-step research workflow, allowing them to shape how reports are packaged—tailoring the output to meet strategic needs. For example, a manager in advisory services might use Research Composer to evaluate white space opportunities across industries or geographies, drawing from internal reports and up-to-date market data.

Continue Reading

Accounting

Eide Bailly merges in Traner Smith

Published

on

Eide Bailly, a Top 25 Firm based in Fargo, North Dakota, is growing its presence in the Pacific Northwest by adding Traner Smith, based in Edmonds, Washington, effective June 2, 2025. 

Traner Smith’s team includes two partners and 16 staff members and specializes in tax compliance and advisory services. Financial terms of the deal were not disclosed. Eide Bailly ranked No. 19 on Accounting Today‘s 2025 list of the Top 100 Firms, with $704.98 million in annual revenue, approximately 387 partners and over 3,500 employees. 

Eide Bailly already has offices in Seattle, but hopes to grow further in the Pacific Northwest. “We’re pleased to welcome the talented team at Traner Smith to Eide Bailly,” said Eide Bailly managing partner and CEO Jeremy Hauk in a statement Monday. “Their expertise with high-net-worth individuals, real estate and privately held businesses aligns well with our strengths, and their client-centric approach is a perfect cultural fit. Having an office in Edmonds, Washington, is a great complement to our existing presence in Seattle. Together, we’re poised to deliver even greater value to families and businesses in the Seattle metro area.” 

“Joining Eide Bailly is a natural next step for us — it provides access to deeper technical resources in areas like state and local tax, national tax, succession planning and international tax while allowing us to continue the personalized service our clients value,” said Kevin Smith, a partner at Traner Smith, in a statement. 

“With this expanded support and platform, we’re excited to grow our reach, elevate what we do best, and help more clients than ever before,” said Shane Summer, another partner at Traner Smith, in a statement.

Eide Bailly has announced several other mergers in recent weeks. Earlier this month, it added Hamilton Tharp, a firm based in Solana Beach, California, and Roycon, a Salesforce consulting firm in Austin, Texas. In late April, it merged in Volpe Brown & Co., in North Canton, Ohio. Eide Bailly expanded to Ohio last year by merging in Apple Growth Partners. Last year, Eide Bailly also sold its wealth management practice to Sequoia Financial Group. The deal with Sequoia appears to be fueling the recent M&A activity. As part of the deal, Eide Bailly Advisors became part of Sequoia Financial, while Eide Bailly received an equity investment in Sequoia.

In 2023, Eide Bailly added Secore & Niedzialek PC in Phoenix, Raimondo Pettit Group in Southern California, Bessolo Haworth in California and Washington State, Spectrum Health Partners in Franklin, Tennessee, and King & Oliason in Seattle. In 2022, it merged in Seim Johnson in Omaha, Nebraska, and in 2021, PWB CPAs & Advisors in Minnesota. In 2020, it added Mukai, Greenlee & Co. in Phoenix, HMWC CPAs in Tustin, California, and Platinum Consulting in Fullerton.

Continue Reading

Accounting

BMSS announces investment, collaboration with Knuula

Published

on

Top 100 firm BMSS announced an investment in Knuula, an engagement letter and client documents software provider. The investment from BMSS came after successfully implementing Knuula over the past year to streamline its engagement letter process. It was after doing so that the firm’s leadership came to believe that Knuula could create complex client documents at an enormous scale, which was a huge need for the broader accounting industry. BMSS thought this presented a great opportunity to guide Knuula and help facilitate its growth. 

“We began working with Knuula in Spring 2024 to streamline our engagement letter process,” said Don Murphy, Managing Member of BMSS. “It quickly became clear that Knuula was not only a strong solution for us, but also an ideal partner in advancing industry-wide automation.”

While the specific terms of the deal were not disclosed, a spokesperson with Knuula said that, after this investment, BMSS and a collection of 21 of their partners now own 13% of the company. The investment represents not some passive revenue deal but an active collaboration between the two companies, with the spokesperson saying they will be working closely together on things like product development, new features, improvements, and networking.

The deal comes about a year after Knuula integrated with QuickFee, a receivables management platform for professional service providers, which allowed users to have engagement letters directly connecting to their QuickFee billing platform, tying the execution of the letter directly to the billing process. 

“We’ve long sought to partner with a firm focused on strategic innovation in the accounting space,” said Jamie Peebles, founder of Knuula. “To develop a perfect solution for large firms, it is ideal to have a partner that is willing to work closely together and iterate quickly. This requires constant feedback between our two teams. The IT team from BMSS worked with our development team constantly and helped us iterate rapidly. We also had consistent input from partners, manager, and administrative staff to help us make valuable changes to Knuula. BMSS was a perfect partner for us.”

Continue Reading

Trending