By Vincent Howard, CPA | Managing Partner, Howard, Howard and Hodges | SkillAbility for Accounting Firms
Last updated: July 16, 2026 | 25-minute read
- What an accounting firm SOP is
- SOP vs. policy, checklist, workpaper, and training
- Why procedure manuals become outdated
- Which workflows to document first
- The 14 parts of a useful accounting SOP
- Copy-and-use accounting firm SOP template
- How to map the workflow before writing
- How to document judgment without oversimplifying it
- How to capture exceptions and escalation
- Ownership, version control, and retirement rules
- How to test whether the SOP works
- 100-point SOP quality scorecard
- Completed CPA firm SOP example
- 90-day SOP implementation plan
- AI, confidentiality, and security controls
- What CPA firms should measure
Most accounting firms already have procedures.
They may be stored in a shared drive, intranet, workflow system, Word file, spreadsheet, training portal, checklist library, or a collection of emails that everyone knows not to delete.
The problem is not always the absence of documentation.
The problem is that the documentation is difficult to find, too long to use, too vague to follow, too specific to one employee, disconnected from the live workflow, or outdated enough that experienced staff ignore it.
That creates a familiar cycle.
A manager asks someone to document a process. The employee writes every step they can remember. The firm places the document inside a master procedure manual. Leadership checks the project off the list.
Six months later:
- The software screen changed
- The client portal changed
- The reviewer added a new requirement
- The employee found a faster method
- A recurring exception appeared
- The responsibility moved to another role
- No one updated the document
The SOP still exists.
The actual process moved on.
A dead manual is not created because the firm documented too little. It is usually created because the firm documented the workflow as a static file instead of managing it as a living operating system.
This article provides a practical accounting firm SOP template, a workflow-mapping process, validation standards, version-control rules, and a maintenance system designed to keep procedures connected to real work.
Who I Am and Why This Matters
I have practiced public accounting since 1990. I founded my accounting firm in 1993, merged it in 2001 to form Howard, Howard and Hodges, and helped grow the organization from three people to approximately 50 staff across four locations and multiple states. Our firm was named PASBA Firm of the Year in 2015.
When a firm is small, operating knowledge often moves through proximity.
Someone asks the person sitting nearby. A manager sees the issue and explains what to do. The partner remembers why the client’s work is handled differently. An experienced administrator catches a deadline before the system does.
As the firm grows, that method becomes expensive and unreliable.
Managers become the search engine for every undocumented exception. New employees learn different versions of the process depending on who is available. Staff may complete the same workflow several ways. Review notes correct problems after the work reaches the manager instead of defining the standard before the work begins.
Writing procedures helps—but only when the procedure is connected to:
- The actual workflow
- The role performing it
- The quality standard
- The client or engagement context
- The exceptions that experienced people recognize
- The training required to use it
- The evidence that proves the process worked
Since 2020, I have built and run the SkillAbility accounting workforce development platform used by more than 1,000 accounting professionals across dozens of PASBA firms. That experience has reinforced an important distinction:
An SOP can explain the work. People still need practice, feedback, and judgment before the firm can rely on them to perform it.
Why SOP Quality Matters for CPA Firms Now
CPA firms must absorb workforce movement, changing technology, and increasing expectations for analysis, advisory work, data security, and quality.
The U.S. Bureau of Labor Statistics reports approximately 1.58 million accountant and auditor jobs in 2024 and projects about 124,200 openings per year from 2024 through 2034. BLS expects many openings to result from workers changing occupations or leaving the labor force, and it expects automation and AI to increase productivity while making analytical and advisory responsibilities more prominent.
Repeatable Workflows Matter While Talent and Technology Keep Moving
Source: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
The AICPA PCPS CPA Firm Competency Model, updated in October 2025, identifies six firmwide competencies:
- Productivity
- Technical knowledge
- Client service
- People development and teamwork
- Business development
- Culture and inclusion
A useful SOP supports more than productivity. It shows how technical work should be completed, how clients should be served, how work moves between people, how quality is protected, and how firm standards appear in daily behavior.
Documentation should make work understandable to another qualified professional
PCAOB AS 1215 applies specifically to PCAOB engagements, not every CPA firm workflow. Its documentation principle is still useful: documentation should clearly show its purpose, source, procedures, evidence, results, and conclusions in enough detail for an experienced auditor with no previous connection to understand the work.
The same operating principle improves tax, bookkeeping, payroll, client accounting services, advisory, and internal administrative workflows:
A qualified person who did not create the process should be able to understand what must happen, why it matters, what evidence proves completion, and where judgment or escalation is required.
Knowledge management requires maintenance
ISO 30401:2018 remains the current published knowledge-management systems standard as of July 2026, although a replacement draft is under development. It establishes requirements and guidance for implementing, maintaining, reviewing, and improving a knowledge-management system.
A CPA firm does not need ISO certification to apply the central lesson:
Creating the document is not the end of the process. The firm must maintain, review, improve, and retire knowledge as circumstances change.
What Is an Accounting Firm SOP?
An accounting firm standard operating procedure is a controlled, role-specific instruction that explains how to complete a recurring workflow consistently, securely, and to the firm’s defined quality standard.
A useful SOP answers:
- Why does this workflow exist?
- What starts it?
- Who owns it?
- What information and systems are required?
- What sequence should be followed?
- Where are decisions made?
- What commonly goes wrong?
- What must be escalated?
- What proves the process is complete?
- Who keeps the SOP current?
An SOP should be detailed enough to guide performance and concise enough to use during performance.
That balance is important.
A two-line instruction may be too vague to protect quality. A 40-page document may be too difficult to use during a live deadline.
SOP vs. Policy vs. Checklist vs. Workpaper vs. Training
| Tool | Primary Purpose | Example | What It Does Not Prove |
|---|---|---|---|
| Policy | Defines a rule, principle, or required boundary | Client data may be stored only in approved systems | How a specific workflow is performed |
| SOP | Explains how a recurring process should operate | How to complete and route a monthly close | That the employee can apply it independently |
| Checklist | Confirms that critical items were considered or completed | Pre-submission workpaper checklist | Why or how each item should be performed |
| Workpaper or record | Documents what happened in a specific engagement or period | Bank reconciliation and conclusion | The complete standard process for future work |
| Template | Provides a consistent starting structure | Client open-item request form | That the content entered is accurate or complete |
| Training and practice | Builds the capability to apply the process | Guided close, planted exception, and reviewer feedback | That the written process will remain current |
Use these tools together.
The policy defines the boundary. The SOP explains the workflow. The checklist supports execution. The workpaper records what happened. The training develops capability. The manager validates the result.
For a staff-facing submission standard, use the Workpaper Review Checklist for CPA Firms.
Why Accounting Procedure Manuals Become Dead
1. The document is organized around departments instead of work
Employees think in terms of the task they need to complete.
They search for:
- Create a new engagement
- Process a rejected return
- Close a monthly client file
- Request missing information
- Prepare a payroll adjustment
They do not necessarily know that the answer is stored on page 86 of the “Operations and Administrative Controls Manual.”
2. The SOP describes the software instead of the outcome
Software screens change.
The purpose, risks, quality standard, and required evidence often remain more stable.
A screenshot-only SOP becomes obsolete as soon as the interface changes.
3. The normal process is documented, but the exceptions are not
Experienced staff are most valuable when:
- The client sends incomplete information
- The numbers do not make sense
- The prior-year treatment no longer applies
- The workflow produces an error
- The deadline and quality requirements conflict
Those situations need decision rules and escalation—not another screenshot.
4. No one owns the SOP
“The tax department” is not an owner.
Assign one role or person responsible for accuracy, access, updates, testing, and retirement.
5. The SOP is not used during training
When managers teach a separate version verbally, employees learn that the written procedure is optional.
6. Employees cannot report a gap easily
The person using the SOP is often the first to discover that a link is broken, an exception is missing, or a step changed.
Make reporting a correction simple.
7. Every process is documented at the same level
A high-risk tax review process and a low-risk office-supply request do not need the same depth, controls, or validation.
8. Outdated content is never retired
Two procedures for the same workflow can be more dangerous than no procedure because employees may choose the wrong version with confidence.
Which Accounting Workflows Should Be Documented First?
Do not begin by asking every employee to document everything they do.
Prioritize workflows using four factors:
- Business or client impact
- Frequency or deadline sensitivity
- Knowledge concentration
- Current documentation gap
Impact + Timing + Concentration + Documentation Gap
| Factor | 1 Point | 3 Points | 5 Points |
|---|---|---|---|
| Impact | Minor internal inconvenience | Meaningful rework or service delay | Major client, filing, quality, security, revenue, or reputation risk |
| Timing | Infrequent and flexible | Recurring deadline with some flexibility | High-volume, closely sequenced, or immovable deadline |
| Concentration | Several people perform it consistently | One owner and one partial backup | Only one person understands the workflow |
| Documentation gap | Current SOP is tested and owned | Partial or outdated documentation | Knowledge exists mainly in memory or scattered files |
- 17–20: Critical—document, test, and assign backup ownership immediately.
- 13–16: High—complete the SOP and validation within 60 to 90 days.
- 9–12: Moderate—schedule documentation and review.
- 4–8: Routine—use a lighter instruction or checklist where appropriate.
Start with a small set of workflows the firm cannot afford to reconstruct under pressure.
For a broader diagnosis of skill and process problems, read CPA Firm Training Needs Assessment: How to Find Skill Gaps Before Buying More Courses.
The 14 Parts of a Useful Accounting Firm SOP
1. Clear title
Name the workflow in the language employees use when searching.
Better: Process a Rejected Individual Tax Return
Weaker: Tax Department Procedure 4.7.2
2. Purpose and business result
Explain why the process exists and what it protects.
3. Trigger and completion point
State what starts the workflow and what must be true when it is complete.
4. Scope
Identify which clients, entities, service lines, work types, and exceptions are included or excluded.
5. Owner and roles
Identify the process owner, performer, reviewer, approver, backup, and escalation contact.
6. Required inputs
List source documents, client information, prior work, technical guidance, approvals, and system access.
7. Systems and security requirements
Name approved systems, required permissions, secure transfer methods, and prohibited practices.
8. Workflow steps
State the sequence, responsible role, output, and evidence for each step.
9. Quality standard
Define what accurate, complete, supported, secure, and review-ready mean for this workflow.
10. Decision points
Explain where the employee must evaluate facts rather than follow a fixed action.
11. Exceptions and warning signs
Capture common failures, unusual facts, conflicting information, and signs that the normal process should stop.
12. Escalation rules
Specify who must be contacted, when, and what information must be provided.
13. Evidence and records
Identify what proves completion, where it is stored, who reviews it, and how long it should be retained under applicable policy and requirements.
14. Control information
Show the owner, version, effective date, last tested date, next review date, change summary, and retirement status.
Copy-and-Use Accounting Firm SOP Template
Accounting Firm Standard Operating Procedure
| SOP title | |
| Process owner | |
| Primary performer / backup | |
| Reviewer / approver | |
| Version and effective date | |
| Last tested / next review |
1. Purpose and business result
2. Trigger and completion definition
| Process Starts When | Process Is Complete When |
|---|---|
3. Scope and exclusions
4. Required inputs, access, and source materials
5. Roles and decision rights
| Role | Responsibility | May Decide | Must Escalate |
|---|---|---|---|
6. Standard workflow
| Step | Action | Owner | System / Source | Output / Evidence |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 |
7. Quality and review-ready standard
8. Decision points
| Decision or Question | Information to Evaluate | Approved Responses |
|---|---|---|
9. Common exceptions and warning signs
| Exception / Warning Sign | Required Response | Escalation |
|---|---|---|
10. Security, confidentiality, and prohibited actions
11. Supporting resources
☐ Completed example
☐ Technical guidance or policy
☐ Screen recording or system guide
☐ Client or engagement profile
☐ Communication template
☐ Training scenario
☐ Related SOPs
12. Validation and training
| Validation Activity | Success Evidence | Date / Reviewer |
|---|---|---|
13. Revision history
| Version | Date | Change | Approved By |
|---|---|---|---|
14. Review and retirement controls
☐ Links and access tested
☐ SOP used by a person who did not write it
☐ Exceptions reviewed
☐ Related training updated
☐ Superseded version archived or removed
☐ Next review date assigned
Map the Workflow Before Writing the SOP
Do not begin with a blank Word document.
Begin with the work.
1. Define the trigger and result
What starts the process? What outcome must exist at the end?
2. Observe the workflow
Watch the person perform it. Ask the person to explain decisions aloud. Capture handoffs, waiting, rework, duplicate entry, and unofficial shortcuts.
3. Identify each role
Show who:
- Provides the information
- Performs the task
- Reviews the result
- Approves the decision
- Communicates with the client
- Owns the deadline
4. Mark decision points
A process map should show where the next step depends on facts.
5. Mark evidence and controls
Show where support, approval, reconciliation, security, review, or acknowledgment must exist.
6. Remove avoidable complexity before documenting it
Do not memorialize a broken process merely because it is familiar.
Map → Simplify → Document → Train → Validate → Improve
Observe the real workflow, roles, handoffs, decisions, and evidence.
Remove duplicate steps, unclear ownership, and avoidable rework.
Create the searchable SOP, checklist, examples, and controls.
Explain, demonstrate, and let the employee perform the workflow.
Test normal work, exceptions, access, and escalation.
Use errors, feedback, and changes to update or retire the SOP.
How to Document Professional Judgment Without Pretending It Is a Checklist
Some accounting workflows cannot be reduced to fixed steps.
Examples include:
- Evaluating whether a client explanation is reasonable
- Determining whether an unusual fluctuation requires more support
- Deciding whether a matter is within the preparer’s authority
- Evaluating contradictory information
- Determining when a technical specialist should be involved
Do not write false certainty into the SOP.
Use a judgment framework
For each decision, capture:
- The question to be answered
- The facts and sources to evaluate
- Common alternatives
- Risk indicators
- Required documentation
- Authority and escalation limits
Use examples and non-examples
Show one routine case, one borderline case, and one case that requires escalation.
Use questions rather than unsupported rules
For example:
- Does the explanation agree with the source documents?
- Is the change consistent with the client’s operations?
- Is the prior-period treatment still appropriate?
- Is the matter within the role’s approved authority?
- What evidence would another reviewer expect?
Connect the SOP to competency
A procedure may be available to everyone while the decision remains limited to a senior, manager, partner, or specialist.
The Accounting Firm Knowledge Transfer Template provides a deeper framework for transferring tacit judgment, client context, and expert decision logic.
Document Exceptions, Failure Points, and Escalation
The exception section may be more valuable than the standard steps.
Capture the most common failure patterns
- Missing or incomplete client information
- Conflicting source documents
- Broken system integrations
- Prior-period balances that do not roll forward
- Rejected filings
- Unauthorized changes
- Unusual transactions
- Deadline risk
- Client requests outside scope
State what the employee should do next
“Contact a manager” is often too vague.
Specify:
- Which manager or role
- How quickly
- What facts to provide
- What work may continue
- What work must stop
- How the escalation should be documented
Separate technical, client, security, and employee escalation
Different issues require different authority.
A technical question may go to a tax partner. A suspected security incident may require immediate escalation under the firm’s written information security plan. An employee-relations matter may require HR or legal guidance.
Ownership, Version Control, and Retirement Rules
Assign one accountable owner
The owner does not have to perform every step. The owner is accountable for:
- Accuracy
- Access
- Testing
- Updates
- Related training
- Retirement of superseded content
Use an effective date and version number
Employees should be able to determine quickly whether they are using the current procedure.
Summarize material changes
Do not force users to compare two long documents to discover what changed.
Create event-based review triggers
Review when:
- Software changes
- A professional standard or law changes
- A client requirement changes
- A recurring error appears
- The process owner or role changes
- A security incident reveals a gap
- The workflow is redesigned
Use calendar reviews as a backup—not the primary trigger
An annual review may be appropriate for stable procedures. A tax filing or security process may require more frequent testing.
Retire old versions visibly
Archive for required records where appropriate, but remove superseded instructions from the active search path.
How to Test Whether the SOP Actually Works
Use a person who did not write it
The author may fill gaps automatically because they already know the process.
Test findability
Ask the employee to locate the correct SOP without being given the direct link.
Test a routine case
Can the employee complete the normal workflow accurately?
Test one exception
Can the employee recognize that the normal process should stop, change, or escalate?
Test the evidence
Can the manager determine what happened, who performed it, what remains open, and whether the result met the standard?
Measure procedural rescue
Record how often the owner must explain a missing step, find a resource, correct the sequence, or make a routine decision.
Update the SOP from the test
A failed test may reveal:
- An unclear SOP
- A missing example
- A training gap
- An access problem
- A process-design problem
- A capability gap
Do not assume every failure means the employee did not read carefully enough.
100-Point Accounting Firm SOP Quality Scorecard
| SOP Quality Area | Points | Strong Evidence |
|---|---|---|
| Purpose, trigger, and scope | 10 | User understands why, when, and where the process applies |
| Roles and decision rights | 10 | Ownership, review, approval, backup, and authority are clear |
| Workflow clarity | 15 | Steps, sequence, systems, handoffs, and outputs are usable |
| Quality and completion evidence | 15 | The SOP defines review-ready completion and required records |
| Judgment and decision support | 10 | Decision questions, sources, alternatives, and authority are visible |
| Exceptions and escalation | 15 | Common failures, warning signs, stop points, and escalation are actionable |
| Security and access | 10 | Approved systems, permissions, data handling, and prohibited actions are clear |
| Findability and supporting resources | 5 | Users can find the current SOP, examples, checklists, and related guidance quickly |
| Independent usability test | 5 | A qualified user who did not write it successfully completed a test |
| Ownership and maintenance | 5 | Owner, version, update triggers, review date, and retirement controls exist |
Suggested interpretation
- 85–100: Strong, controlled, and usable SOP.
- 75–84: Operationally useful with targeted gaps to correct.
- 60–74: Partial procedure; significant reliance on manager knowledge remains.
- Below 60: The document should not be treated as a reliable operating standard.
A high score should not override a material security, authorization, technical, or professional-standard failure.
Completed Example: Monthly Close Client Information and Reconciliation Workflow
Recurring Client Accounting Services Monthly Close
| Purpose | Produce complete, supported, review-ready monthly financial information by the agreed internal review date. |
| Trigger | Month-end occurs and required system feeds and client documents become available. |
| Completion | Material balance-sheet accounts are reconciled, unusual activity is evaluated, adjustments are supported, open items are assigned, and the reviewer summary is complete. |
| Scope | Routine monthly close for assigned CAS clients. Excludes technical matters reserved for the manager or partner. |
| Primary roles | Staff prepares; senior reviews routine work and open items; manager resolves judgment, scope, and client-risk matters. |
| Workflow | Confirm inputs, update bank feeds, reconcile cash and credit cards, post approved recurring entries, reconcile material balance-sheet accounts, compare results with prior periods and expectations, investigate unusual items, prepare consolidated client questions, complete reviewer summary, and submit. |
| Quality standard | Sources are linked, reconciliations explain differences, adjustments are supported, conclusions are stated, unusual changes are addressed, and unresolved items show owner and next action. |
| Decision point | Determine whether an unusual transaction can be resolved from available support or requires client clarification, technical research, or manager review. |
| Warning signs | Unexplained cash difference, stale reconciling item, payroll liability that does not clear, large repair expense, unusual deposit, personal activity, duplicate transaction, or material variance without support. |
| Escalation | Stop finalization and notify the manager when a material difference cannot be explained, evidence conflicts, potential fraud or misuse appears, the requested treatment is outside authority, or the deadline is at risk. |
| Security | Use only approved systems and individual credentials. Send client information through approved secure channels. Do not place client data into unapproved AI tools. |
| Validation | A staff accountant who did not write the SOP completes a prior-period close with one missing document and one planted unusual transaction, produces a consolidated question list, and submits review-ready work. |
| Update triggers | Software change, client scope change, new recurring error, review-standard change, security change, or annual post–busy season review. |
This SOP does not attempt to include every possible accounting answer.
It defines the process, quality standard, decision framework, warning signs, authority, and proof of successful completion.
A 90-Day Accounting Firm SOP Implementation Plan
| Period | Primary Focus | Evidence |
|---|---|---|
| Days 1–30 | Inventory workflows, score priorities, select five to ten critical SOPs, assign owners, map current processes, and remove obvious waste | Priority register, owners, workflow maps, source inventory, and documentation schedule |
| Days 31–60 | Draft SOPs, attach examples and checklists, capture judgment and exceptions, review security, and conduct user testing | Controlled drafts, test results, correction log, training assignments, and approved version records |
| Days 61–90 | Train performers and backups, run normal and exception cases, publish current versions, remove superseded content, and establish maintenance reviews | Independent validation, access tests, readiness scores, active links, revision history, and next review dates |
Do not measure success by the number of pages produced
Measure whether the firm has fewer undocumented decisions, fewer repeated process errors, less manager reconstruction, stronger backup coverage, and faster onboarding into live workflows.
For a person-specific development structure, use the Accounting Employee Development Plan Template for CPA Firms.
Using AI to Build SOPs Without Creating New Risk
Approved AI can help:
- Turn an expert interview into a first draft
- Organize a screen-recording transcript
- Convert a workflow map into step language
- Identify missing sections
- Create sanitized practice scenarios
- Compare two versions and summarize changes
- Generate questions for a user test
AI should not be the final owner or authority.
Verify every technical statement
Compare the procedure with current authoritative guidance, firm policy, system behavior, and approved professional judgment.
Protect confidential information
IRS Publication 4557 explains that professional tax preparers must protect client data, maintain a written information security plan, implement safeguards such as multi-factor authentication, limit access to people with a business need, and provide security-awareness training.
Do not place client or employee data into an unapproved AI system to make procedure writing faster.
Label verified knowledge clearly
Distinguish:
- Approved firm procedure
- Authoritative external guidance
- Draft language
- AI-generated suggestions awaiting review
Keep human accountability
The process owner remains responsible for accuracy, access, version control, and testing.
What Should CPA Firms Measure?
Coverage
Critical workflows identified, SOPs owned, backups trained, and superseded versions retired.
Usability
Find time, successful user tests, broken links, procedural rescue, and reported gaps.
Quality
Repeated process errors, missing evidence, review notes, exceptions identified, and escalation timing.
Capacity and Continuity
Manager interruptions, onboarding time, backup readiness, deadline disruption, and key-person dependence.
Useful measures include:
- Percentage of critical workflows with a current owner
- Percentage with an independently tested SOP
- Average time required to locate the correct procedure
- Procedural questions per workflow
- Repeated errors caused by unclear or outdated instructions
- SOP corrections reported by users
- Time from reported change to approved update
- Superseded SOPs still accessible in active folders
- Backups who can perform the workflow independently
- Manager rescue time
Do not reward teams for producing a large manual.
Reward them for making critical work easier to perform, review, teach, transfer, and improve.
How SkillAbility Helps Firms Turn SOPs Into Capability
SkillAbility helps CPA firms connect documented workflows with structured practice, feedback, judgment development, and evidence of performance.
It is an accounting workforce development and knowledge-transfer platform built around a pathway from new hire to future partner.
The SkillAbility Development Pathway
Builds technical execution, software workflow fluency, source recognition, documentation, self-review, and review-ready performance through realistic practice.
Builds client communication, financial interpretation, business acumen, advisory thinking, professional presence, and judgment when a procedure alone is not enough.
Builds review leadership, coaching, delegation, quality ownership, workflow improvement, succession, firm economics, and future-partner thinking.
An SOP tells people what the firm expects.
Structured practice shows whether they can perform it.
For the broader strategy, read Accounting Workforce Development: How CPA Firms Build Capacity From Within.
A strong SOP reduces avoidable variation. A strong development system ensures employees can use the SOP, recognize when it no longer applies, and improve the workflow without weakening quality.
Frequently Asked Questions
What should an accounting firm SOP include?
It should include the purpose, trigger, scope, owner, roles, required inputs, systems, workflow steps, quality standard, decision points, common exceptions, escalation rules, security requirements, evidence of completion, version history, and review schedule.
What is the difference between an SOP and a checklist?
An SOP explains how and why a workflow operates. A checklist helps the user confirm that critical items were completed or considered. A checklist usually supports the SOP rather than replacing it.
How long should an accounting SOP be?
It should be as short as possible while still covering the process, quality standard, decisions, exceptions, escalation, and evidence. A routine workflow may need one or two pages plus a checklist. A complex process may need a short core SOP linked to technical guidance, examples, and training.
How do you stop an SOP manual from becoming outdated?
Assign one owner, use version control, connect review to workflow-change events, make user corrections easy, test the SOP during real work, update related training, and remove superseded versions from active search locations.
Who should write accounting firm SOPs?
The process expert should help capture the workflow, but the owner should involve performers, reviewers, security or technology specialists where relevant, and a user who did not create the document. One person writing from memory is not enough.
Should SOPs include screenshots?
Use screenshots when they make a difficult system step clearer, but do not build the entire SOP around screenshots. Explain the purpose, result, decision points, and evidence so the document remains useful when the interface changes.
How do you document professional judgment in an SOP?
Document the question, facts and sources to evaluate, common alternatives, risk indicators, required evidence, authority limits, and escalation rules. Use routine, borderline, and escalation examples instead of pretending judgment is a fixed checklist.
How often should accounting SOPs be reviewed?
Review when software, clients, professional guidance, roles, security requirements, or recurring errors change. Use scheduled reviews as a backup. High-risk and high-volume workflows should be tested more frequently than stable low-risk processes.
How should SOPs be organized?
Organize them around searchable workflow names and user tasks rather than one long departmental manual. Connect each SOP to the relevant role, checklist, completed example, technical guidance, and training assignment.
How can a firm prove an SOP works?
Have a qualified person who did not write it locate the SOP and complete a normal case plus an exception. Measure accuracy, quality, security, escalation, evidence, completion time, and procedural rescue.
Can AI write accounting firm SOPs?
Approved AI can create a useful draft from interviews, recordings, maps, and existing materials. A qualified human must verify technical accuracy, security, client context, decision rights, current system behavior, and the final workflow.
Should confidential client information appear in an SOP?
Use only the information necessary for the procedure and follow firm confidentiality, access, retention, and security requirements. Use sanitized examples where possible and store client-specific history in the appropriate protected client or engagement record.
How do SOPs support onboarding?
SOPs make workflow expectations visible, but onboarding should also include completed examples, explanation, guided practice, feedback, exception scenarios, and independent validation before the employee is relied on for live work.
What workflows should a CPA firm document first?
Start with workflows that have high client, filing, quality, security, revenue, or deadline impact; depend on one person; occur frequently; or currently rely on outdated or scattered documentation.
External Research and Authority Sources
The Bottom Line
An accounting firm does not need a larger procedure manual.
It needs a smaller number of useful, owned, searchable, tested, and current operating procedures connected to the real work.
Start with critical workflows. Map the process before writing it. Simplify unnecessary steps. Define purpose, trigger, roles, inputs, workflow, quality, decisions, exceptions, security, escalation, and evidence. Attach completed examples and short checklists. Train people through realistic work. Test the SOP with someone who did not write it. Update it when the process changes. Retire the old version.
The procedure should reduce avoidable questions.
It should make quality visible before review.
It should preserve knowledge without pretending that a document replaces professional judgment.
Do not write an SOP to prove the process was documented. Write it so another qualified person can perform, review, teach, and improve the workflow without rebuilding the firm’s knowledge from scratch.
Protect Knowledge. Develop People. Scale the Firm.
Does your firm have living workflows—or a manual employees ignore until something goes wrong?
SkillAbility helps CPA firms connect technical workflows, review standards, client judgment, knowledge transfer, and leadership development with realistic practice and measurable evidence.
Book Your Free 10-Minute Structural Alignment Review →
Includes our 45-Day Out-of-Pocket Performance Guarantee.
To building procedures people can actually use,
Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
SkillAbility for Accounting Firms
About the Author
Vincent Howard, CPA has practiced public accounting since 1990. He holds a Master’s degree in Taxation from the University of Central Florida, founded his accounting firm in 1993, and helped grow Howard, Howard and Hodges from three people to approximately 50 staff across four locations and multiple states. He has participated in PASBA since 1997, and the firm was named PASBA Firm of the Year in 2015. Since 2020, he has built and run the SkillAbility accounting workforce development platform, used by more than 1,000 accounting professionals across dozens of PASBA firms.
© 2026 SkillAbility for Accounting Firms. This article provides general educational information and does not replace legal, employment, human-resources, accounting, tax, auditing, data-security, records-management, or regulatory advice.