Writing the Procedures Manual Your Accounting Firm Never Had Time For

How to build a procedures manual for a small accounting firm, using the document types you already handle as its backbone, with a one-page template and example.

Written by Miriad with AI assistance and checked against the sources at the end. A method for small accounting and bookkeeping firms, not legal or compliance advice: your security plan and professional rules decide.

TL;DR: A small accounting firm's procedures manual is easier to write if you organise it by document type rather than by department. List the documents the office receives and produces, then write one page per type: trigger, steps, checks, storage, retention and whether AI may touch it. Write one or two pages a week in the quiet months, from staff notes, with no client data.

Every small firm has a manual. It is in the senior bookkeeper's head, in a partner's old emails, and in a spreadsheet called "how we do things v3" that nobody has opened since the last person who understood it left. When that bookkeeper is off for two weeks in February, the office finds out how much of the firm runs on memory.

This article shows how to build the written version without stopping client work. It sits within our guide to accounting firm marketing strategies, because written procedures are what make consistent service, and safe AI use, possible.

Why do small accounting firms never write the manual?

Because the work that needs a manual is the same work that leaves no time to write one, and because a manual organised by "departments" does not match how a small office actually works. Staff think in documents: a payroll report arrived, a tax authority letter came in. A manual organised the same way gets used.

The gap is visible in AI as well. In a 2026 vendor survey of about 600 accounting professionals, 98% said their firms use AI, but only 21% had an AI policy or strategy, and fewer than half invested in AI training (Karbon, 2026). That is a vendor's survey, but it describes a familiar pattern: the tools arrive before the written rules. A procedures manual is where those rules go.

It also matters for continuity. Partners in a firm of five or fifteen often hold knowledge that no one else has written down. A manual is low-cost insurance against that knowledge leaving with one person.

How do document types give the manual its structure?

List every document type the office receives or produces, and give each one a page. An accounting office handles a long but finite list: engagement letters, bank statements, invoices, payroll reports, tax returns, year-end accounts, letters from the tax authority. Each type has a natural procedure, so the list becomes the table of contents.

A starting list for a small firm, grouped by where the document comes from:

Group Document types Typical procedure
From the client Bank and card statements, sales and purchase invoices, receipts, payroll changes, tax organizer answers Receive, check completeness, file, process
Produced for the client Bank reconciliation, month-end close pack, payroll reports, VAT or sales tax returns, year-end accounts, tax returns Prepare, review, approve, send, file
From authorities Tax authority letters, penalty notices, registration confirmations Log, assign, deadline, reply, file
Firm documents Engagement letter, notice of outside tools, invoices for fees, due diligence records Template, fill, sign, store
Internal Security plan, AI rule sheet, training records, continuing professional development logs Owner, review date

Written down, the list may run to a few dozen types, and so to a few dozen pages. That sounds like a lot until you notice that many share a procedure. All "from the client" documents, for example, can share one receiving page with a short table of differences.

What goes on one procedure page?

One page per document type, always in the same eight fields: trigger, inputs, steps, checks, output, storage, retention, and whether AI may be used and in which tool. The fixed fields make the page quick to write, quick to read in a rush, and easy to check for gaps later.

Example (illustrative, not a real case): The bank reconciliation page of a seven-person bookkeeping firm.

Field Content
Trigger Bank feed or statement received for the month; at the latest by working day 5
Inputs Bank feed or statements, the previous month's reconciliation, open items list
Steps 1. Match feed to ledger. 2. Investigate unmatched items over the firm's threshold. 3. List open items. 4. Ask the client about anything older than 30 days, in one email.
Checks Closing balance agrees to the statement; open items list reviewed by a second person once a quarter
Output Reconciliation report in the client folder; open items email to the client
Storage Client folder in the practice management software, never on a personal drive
Retention Per the firm's record policy
AI use Approved tool only (named in the security plan) for matching suggestions; never a public tool; the bookkeeper checks every suggested match

A page like this takes about 45 minutes to write from a staff member's notes. The hardest part is the "checks" field, because it forces the question: how would we know this was done right?

Where do the security plan and the AI rules belong?

Inside the manual, as its first chapter, and referenced from every page's "AI use" and "storage" fields. In the US, tax and accounting firms of every size must keep a Written Information Security Plan; the manual is where that plan becomes daily practice rather than a file nobody reads.

IRS Publication 5708 explains that under the FTC Safeguards Rule, tax and accounting professionals are financial institutions "regardless of size", and lists what the plan must cover: designating a qualified individual, assessing risks, testing safeguards, and choosing service providers whose contracts require them to keep safeguards (IRS Publication 5708, 2024). Each of those has a natural home in the manual: the qualified individual owns chapter one, the risk assessment sits beside the document list, and each tool appears in the storage field of the pages that use it.

The AI rule sheet belongs in the same chapter. ICAEW's ethics guidance sets the two principles to build it on: confidential information stays out of public generative AI tools, and those tools "do not make up for a lack" of professional knowledge (ICAEW, accessed 2026). The first decides which tool each page allows. The second is why every page with AI use also has a human check. The detailed rules are in using AI without exposing client data.

How do you write the manual without stopping client work?

Write one or two pages a week, in the quiet months, from notes the person doing the work already has. A staff member describes the procedure in their own words or records a short walk-through; AI turns the notes into the eight-field page; the senior person checks it. No client data is needed, only the steps.

There is no published benchmark for how long a small firm's manual takes, so use a frame:

Total hours = number of document types × (notes time + drafting time + review time)

Example (illustrative, not a real case): A firm counts 32 document types. Notes take 20 minutes, AI-assisted drafting 15 minutes and review 20 minutes per page: 55 minutes, call it 1 hour. That is 32 hours. At two pages a week from May to August, about 17 weeks, the manual is done before the extension deadline season, with no week needing more than 2 hours.

A few practical rules make this work:

  • Use dummy examples. Where a page needs an example, invent one with obviously fake names and round figures. Never copy a real client's file into the manual.
  • Start with the risky pages. Tax authority letters, payroll changes and anything with a deadline come first.
  • One owner per page. The person who does the work owns the page and updates it.

The client onboarding checklist is a ready-made chapter: its eight items are eight pages of the "firm documents" group.

How do you keep the manual current?

Give each page an owner and a review date, and review the whole manual once a year after the main filing season. Rule changes trigger an update of the affected pages, and training records live in the internal chapter. A manual nobody updates slowly turns back into the "how we do things v3" spreadsheet.

Training and continuing professional development records belong here too. In Hungary, registered bookkeepers must earn at least 16 credit points in each training year, at least 8 of them in accounting, with no carry-over of extra points (93/2002. Korm. rendelet, Jogtár). In the EU, Article 4 of the AI Act requires deployers of AI systems, from 2 February 2025, to take measures for sufficient AI literacy of their staff (AI Act Article 4, 2024). A dated log of who walked through the AI rule sheet, and when, is a simple start on the second.

If you want the manual's facts, the services, document types, tools and rules, written down once in plain files your AI tools and new staff can both read, the Business Brain Starter Kit is built for that. Get notified when it launches.

FAQ

How do I start a procedures manual for a small accounting firm?

List every document type the office receives or produces, such as bank statements, payroll reports, tax authority letters and engagement letters, and make that list the table of contents. Then write one page per type in fixed fields: trigger, inputs, steps, checks, output, storage, retention and AI use. Start with the pages that carry deadlines or risk.

How long does it take to write an accounting firm procedures manual?

It depends on how many document types the firm handles. Multiply the number of types by the time per page for notes, drafting and review. In the illustrative example in this article, 32 pages at about one hour each come to 32 hours, spread over the quiet months at two pages a week, so no week needs more than two hours.

Can AI help write our office procedures?

Yes, if the input is a staff member's description of the steps rather than client files. AI can turn rough notes or a transcribed walk-through into a structured page, and a senior person then checks it. Use invented examples with obviously fake names, and keep the AI rules themselves in the manual's first chapter.

Does the procedures manual replace our Written Information Security Plan?

No, it puts the plan into practice. In the US, tax and accounting firms of every size must keep a written security plan under the FTC Safeguards Rule. Put the plan in the manual's first chapter, and refer to it from each page's storage and AI use fields, so staff apply it every time they handle a document.

Sources

Related articles

Products from Miriad

Business brainBusiness Brain Starter Kit

Stop explaining your business from scratch. Write it down once, with a source next to every line.

49 USD

Get notified

See all prompt packs