For 24 years, the Public Company Accounting Oversight Board has decided which auditing standards to write, in what order, and on whose priorities—largely behind closed doors. On June 23, 2026, that changed. The PCAOB opened its first-ever public comment period asking anyone—audit firms, investors, academics, and yes, ordinary business owners who rely on audited financial statements—to weigh in on what should be on its standard-setting and research agenda before the agenda is set, not after.
The comment window closes August 7, 2026. If you run a small audit practice, sit on the finance side of a company that expects an audit in the next few years, or just want to understand how the rules that govern "can I trust this financial statement" actually get made, this is worth five minutes of your attention.
What the PCAOB Actually Does
The PCAOB is the regulator created after the Enron and WorldCom collapses to oversee audits of U.S. public companies and broker-dealers. When a public company's 10-K carries an auditor's signature, that auditor answered to PCAOB standards while doing the work, and the audit firm itself is subject to PCAOB inspection. If you've never dealt with a PCAOB-audited entity, the standards still touch you indirectly—they're the backstop that lets banks, investors, and acquirers treat a set of financial statements as trustworthy without redoing the work themselves.
Historically, the PCAOB decided which standards to write next through internal strategic planning, informed by inspection findings, enforcement trends, and informal outreach. Formal public comment happened only after a specific rule was drafted and proposed—the standard "notice and comment" process required for any rule that actually takes effect. What never had a formal public comment step was the earlier question: what should the Board be working on at all?
What's Actually Being Requested
The June 23 release asks for input on three distinct things:
- Potential future focus areas for standard setting and research. What's missing from the current agenda that stakeholders think should be there?
- The Board's general approach to standard setting. Is the current process—timelines, sequencing, how projects get prioritized—working, or does it need structural change?
- The impact of the SEC's pending semiannual reporting proposal on the PCAOB's existing suite of standards. The SEC has floated letting certain smaller reporting companies file semiannually instead of quarterly; if that goes through, several PCAOB standards written around a quarterly review cadence would need to be revisited.
This builds directly on a broader Strategic Priorities Request for Comment the PCAOB issued in March 2026, which asked open-ended questions about the Board's overall direction. The June request is the more targeted follow-up, aimed specifically at the standard-setting and research pipeline. PCAOB Chair Demetrios Logothetis framed it this way: "This open comment period will allow us to hear directly from stakeholders as we refine our priorities, ensuring that our efforts remain focused, practical, and aligned with the needs of today's investors and capital markets."
What's Currently on the Agenda—and What Might Get Added Back
Understanding this request means understanding what the PCAOB is already working on, since the comment period is effectively asking "what are we missing" against that baseline:
- Quality Control (QC 1000) targeted changes. The Board is weighing narrower amendments to QC 1000 after a supplemental comment period closed in June 2026. This is a live, separate track from the December 2026 implementation deadline firms are already working toward.
- Conforming amendments tied to SEC reporting changes. If the SEC finalizes revisions to Exchange Act Rules 13a-13 and 15d-13 (the quarterly reporting rules), PCAOB interim auditing standards will need matching updates.
- Data and Technology research. An active research project examining whether auditors' and preparers' growing use of technology tools—including AI—requires new guidance or standard changes. This is a research phase, not yet a proposed rule, but it's the project most likely to eventually touch how audits of tech-forward companies get performed.
- The Broker-Dealer Inspection Program. A rulemaking project finalizing the PCAOB's permanent inspection program for broker-dealer audits, still at the proposal stage.
Two older, more contentious projects are also implicitly in play as the Board decides what to prioritize: noncompliance with laws and regulations (NOCLAR), which would expand auditors' responsibility to detect and report client legal violations, and firm and engagement performance metrics, which would require standardized quality metrics to be disclosed. Both had support from investor-protection advocates in earlier rounds and pushback from audit firms concerned about scope and cost. Whether either resurfaces depends heavily on what this comment period turns up.
Why This Matters If You Run a Small Audit Practice
If your firm audits smaller public companies or broker-dealers, you're usually on the receiving end of PCAOB rules, not part of the conversation that shapes them. Formal proposals get a comment period, but by the time a rule is proposed, the scope and direction are largely locked. This is a rare window where the sequencing itself is still open.
Two things are worth doing with this window:
- Flag the compliance load you're already carrying. If the Board is deciding what to add to the agenda, a comment letter explaining what a small-firm QC 1000 implementation actually costs in partner hours is directly relevant data the Board doesn't otherwise see in volume.
- Weigh in on NOCLAR and performance metrics specifically, if either would materially change your engagement scope. Silence here reads as "no objection" when the Board tallies input; audit firm trade groups will comment, but the Board explicitly wants direct practitioner voices, not just organized submissions.
Why This Matters Even If You've Never Filed with the SEC
Most readers of a small-business finance blog aren't PCAOB-regulated. But the standards this Board writes still shape your world in a few concrete ways:
- If you're raising capital or planning an exit, the acquirer or the underwriter's due-diligence team will eventually care whether your books can survive an audit built to these standards. Understanding what "audit quality" means to a regulator—not just to your bookkeeper—is useful before you're in a data room.
- If you bank with, invoice, or process payments through a fintech or crypto platform, there's a decent chance that platform's broker-dealer subsidiary is PCAOB-inspected. The Broker-Dealer Inspection Program directly affects the audit rigor behind the custody and settlement infrastructure you're trusting with client funds.
- The Data and Technology research project is the one to watch longer-term. As auditors formalize how they evaluate AI-assisted bookkeeping and AI-generated transaction records, the standards that come out of it will influence what "auditable" means for any business using automated tools to manage its books—plain-text or otherwise.
How to Actually Submit a Comment
Unlike a formal rule proposal, there's no prescribed comment letter format here—the PCAOB is explicitly fishing for open-ended input, which means a short, specific letter carries real weight.
- Deadline: August 7, 2026
- Email: comments@pcaobus.org — reference "Request for Public Comment on PCAOB Standard Setting" in the subject line
- Mail: Office of the Secretary, PCAOB, 1666 K Street, NW, Washington, DC 20006-2803
A useful letter answers one or two of these directly rather than trying to cover everything: What specific standard-setting gap have you personally run into? Does the current pace and sequencing of PCAOB projects work for a firm or company your size? Does the SEC's semiannual reporting proposal, if finalized, create a mismatch with any PCAOB standard you rely on?
Transparent Records Make Every Version of This Conversation Easier
Whether you're a small audit firm sizing up a comment letter or a business owner thinking ahead to your first audit, the underlying ask from every one of these standards is the same: can someone outside your organization verify what your books say happened? Beancount.io's plain-text, git-versioned accounting keeps every transaction in a format that's inherently auditable—no black-box database, no proprietary export format standing between your ledger and whoever needs to check it. Get started for free and see why developers and finance professionals are switching to plain-text accounting.