Skip the Materiality Worksheet: A Practical Audit Compliance Walkthrough

This is for the staff accountant or first-year senior who inherited an audit binder and a deadline. Not for partners. Not for the person who already has a PCAOB inspection letter framed on the wall.

Here's the contrarian claim: stop treating the materiality worksheet as the centerpiece of your audit file. Most teams spend hours benchmarking, re-benchmarking, and screenshotting a number that the standard never asked them to defend to three decimal places. PCAOB AS 2105 requires you to establish a materiality level for the financial statements as a whole and plan procedures to catch misstatements that would matter to a reasonable investor — the same "total mix of information" language the U.S. Supreme Court used. That's a judgment standard, not a precision exercise. What inspectors actually read is whether your judgment holds together across the file.

We've run enough of these to know the difference between a binder that survives review and one that gets reworked in May. Here's the walkthrough we use.

1. Start with the entity, not the spreadsheet

Before you touch a tickmark legend, answer three questions about the client: what do they sell, who owns them, and what keeps the controller up at night? The answers determine almost everything downstream.

If it's a C corporation, profit gets taxed at the entity and again when distributed as dividends — the classic double taxation problem — and the client files Form 1120 (IRS). If it's an S corporation, income passes through to shareholders and the entity files Form 1120-S instead. A partnership files Form 1065 and passes profits or losses to partners. Those structural facts change which accounts carry risk. A pass-through with three owners fighting over distributions has a different equity risk profile than a C corp with a single institutional shareholder.

The entity question also tells you whether SOX Section 404 applies. If the client is public, management has to assess internal controls over financial reporting, and the PCAOB — created under Section 101 of the Sarbanes-Oxley Act of 2002 — oversees your work. That's not a compliance checkbox; it's the reason your documentation standard is higher than it would be for a private engagement.

2. Build materiality from a benchmark you can defend, then leave it alone

Pick a benchmark, pick a percentage, document why. That's it. The failure mode we see most often is a team that sets materiality at, say, 5% of pre-tax income, then quietly adjusts it twice during fieldwork because a misstatement came in just under the line. That's not judgment. That's reverse-engineering, and a reviewer will spot it in the revision history.

Set performance materiality lower than overall materiality so you have room for undetected misstatements, and set a clearly trivial threshold so you're not documenting every $40 variance. Then stop. The standard asks for a level, not a negotiation.

3. Map risk to accounts, then map accounts to procedures

This is where most binders fall apart. Teams write a beautiful risk assessment and then run the same substantive tests they ran last year, because the prior-year file is open in another tab.

Do it in the other direction. For each significant account, write one sentence: what could go wrong here? Then write the procedure that addresses it. If you can't write the sentence, the account probably isn't significant, and you can cut the procedure.

A quick example. A distributor with $4.2 million in inventory and thin margins has a real risk around net realizable value — the estimated selling price less costs to complete and sell. Under IFRS (IAS 2 Inventories), inventory is measured at the lower of cost and net realizable value, and cost is assigned using FIFO or weighted average for interchangeable items. If the client is on IFRS, your procedure needs to test the NRV write-down, not just recalculate the roll-forward. Different framework, different procedure, same account balance.

4. Write the going concern conclusion like you mean it

Under U.S. GAAP (ASU 2014-15, codified in ASC 205-40), management must evaluate whether there's substantial doubt about the entity's ability to continue as a going concern. Substantial doubt exists when conditions indicate it's probable the entity won't meet its obligations within one year after the financial statements are issued (CAQ Going Concern).

We see two failure modes. One: the team copies last year's paragraph and changes the date. Two: the team flags every client with a working capital deficit as a going concern problem. Neither is right.

Do the math. If the client has a $600,000 revolver maturing in eight months and projected operating cash flow of $450,000, you have a gap. That gap is the conversation. Document management's plan — refinancing, equity injection, cost cuts — and then test whether the plan is probable, not just plausible. "Probable" is doing real work in that sentence.

5. Close the file with a reviewer's eyes, not an author's

Before you sign off, read your own work as if you're the inspection team. Ask three questions:

• Does every significant risk have a linked procedure, and does every procedure have a conclusion?
• Are the estimates and judgments documented with the alternative you considered and rejected?
• Would a reviewer who has never met this client understand why you did what you did?

If the answer to any of those is no, you have work to do. And do it before the partner review, not after.

What can go wrong: the most common audit failure we see isn't a missed misstatement. It's a file that documents what the team did but not why. When a reviewer or inspector can't reconstruct the reasoning, they assume there wasn't any. A well-reasoned file with a small miss is survivable. A poorly reasoned file with a clean number is not.

What I'd actually do

I'd cut the materiality worksheet in half and spend the recovered time on the risk-to-procedure map. That's the part of the file that actually demonstrates professional judgment, and it's the part that most teams treat as boilerplate. The standard doesn't reward precision on materiality. It rewards a coherent story about what could go wrong and what you did about it. Build the story first. The numbers will follow, and the file will hold up.

Sources

• PCAOB AS 2105 - https://pcaobus.org/oversight/standards/auditing-standards/details/AS2105
• CAQ Going Concern - https://www.thecaq.org/going-concern-management-and-auditor-responsibilities
• IFRS IAS 2 - https://www.ifrs.org/issued-standards/list-of-standards/ias-2-inventories/
• SOX (Public Law 107-204) - https://www.govinfo.gov/content/pkg/PLAW-107publ204/html/PLAW-107publ204.htm
• IRS Corporations - https://www.irs.gov/businesses/small-businesses-self-employed/corporations