Read summarized version with
The most expensive document my first company never had was an accounting manual.
I’m Yuval, founder of Glitter AI. Years ago I ran a startup where the entire accounting process lived in one person’s head. She left, and the knowledge walked out with her. How we coded expenses. When we accrued. Which accounts mapped to what. The order of our close. All gone.
We ended up rebuilding it from bank statements and guesswork. That took months, and it cost us real money in restatements and a pretty painful audit.
If you’re a controller or finance leader, you already know an accounting manual matters, so I won’t try to sell you on the idea. The hard part isn’t being convinced. It’s building one that people actually open, and keeping it from rotting the moment your processes change. That’s what this post is about.
Teach your co-workers or customers how to get stuff done – in seconds.
What an accounting manual actually is
An accounting manual is the single source of truth for how your finance function operates. It pulls together two things people tend to mix up:
- Policies - the rules and the why. Our revenue recognition policy. Our capitalization threshold. Who can approve what, and up to what dollar amount.
- Procedures - the step-by-step how. How to run the AP batch. How to reconcile the bank. How to close the month.
If you’ve ever argued about the difference in a meeting, this breakdown of policy versus procedure is worth a read. Short version: a policy says “all invoices over $5,000 require dual approval.” A procedure shows you exactly which buttons to click to route that invoice for the second approval.
A good accounting manual answers three questions for anyone on your team. What are the rules? How do I do this task? And who’s on the hook when it goes wrong?
Why most accounting manuals fail
I’ve seen plenty of finance teams that have an accounting manual. Most of them are useless. Here’s why.
They’re written for auditors, not staff. The manual reads like a controls narrative because it was built to survive an audit in the first place. Nobody on the team reaches for it during daily work, so it quietly drifts out of sync with reality. This matters more than teams realize: a Gartner survey of controllership professionals found that roughly 59% of accountants make several errors per month, and the most common cause isn’t carelessness - it’s not having clear procedures within reach when the work gets hectic.
They’re walls of text with no screenshots. Your AP clerk doesn’t want a paragraph describing the three-way match. They want to see the actual screen in your ERP, with the right fields highlighted.
They’re a one-time project. Someone spent a quarter writing a beautiful 80-page PDF. It was accurate the day it shipped, and wrong six months later when you migrated systems.
The fix for all three is the same. Make the manual cheap to create and cheap to update. If documenting a procedure eats an entire afternoon, it never gets done and it never gets fixed. I’ll come back to that problem.
How to structure your accounting manual
Don’t start with a blank page. Start with a skeleton. Here’s a structure that holds up for most finance teams, whether you’re a 3-person department or a full controllership.
1. Introduction and governance
- Purpose and scope of the manual
- Who owns it (name a documentation owner - usually the controller)
- Review cadence (quarterly is realistic; annually is too slow)
- Org chart and roles in the finance function
2. Accounting policies
This is the rules section. Keep each policy short and decisive:
- Chart of accounts and account mapping
- Revenue recognition
- Expense and capitalization policy
- Accruals and prepaid expenses
- Fixed assets and depreciation
- Intercompany transactions (if relevant)
- Period-end and adjusting entries
3. Core procedures
This is the heart of the manual, and it’s where most of your maintenance time will go. Each procedure should be its own standalone guide, so you can update one without touching the rest. The essentials:
- Accounts payable - invoice intake, coding, approval workflow, payment runs
- Accounts receivable - invoicing, collections, cash application
- Bank and account reconciliations
- Payroll posting and reconciliation
- Journal entries and the audit trail standard
- Month-end close - the full sequence, with owners and deadlines
4. Internal controls
Document the financial controls that protect the numbers: segregation of duties, approval thresholds, reconciliation sign-offs. If you want to go deeper on this layer, I wrote a full guide on internal controls in accounting that pairs well with the manual.
5. Systems and access
Which systems you use, what each one is for, and who has access to what. This section earns its keep during onboarding and audits alike.
Teach your co-workers or customers how to get stuff done – in seconds.
The “record once” approach to procedures
This is the part I care about most, because it’s the part almost everyone gets wrong.
The policies section of your accounting manual is stable. You write it once, you review it quarterly, and it barely moves. Writing that in a doc is totally fine.
The procedures section is the opposite. It changes constantly, because your software changes, your team changes, and your process keeps improving. And procedures happen to be the part that’s miserable to write by hand. Screenshotting every step of a month-end close, annotating it, pasting it into a doc, then redoing all of it when your ERP ships a new UI? That’s why manuals rot.
So I stopped writing procedures. I record them instead.
The idea behind Glitter is simple. You do the task once while narrating it, and you get a clean step-by-step guide with screenshots, generated for you. Reconcile the bank account once, talk through what you’re doing, and the bank reconciliation procedure is documented. Run the AP batch once, and the AP procedure exists.
When your ERP changes, you don’t rewrite anything. You do the task one more time and re-record. Documenting the how stops being a project and becomes a side effect of doing the work. That’s the only approach I’ve seen keep the procedures half of an accounting manual alive.
The policies live in your manual as written rules. Each procedure is a recorded guide you link from the manual. The manual becomes the index, and the guides stay current because they’re cheap to refresh.
A practical build sequence
If you’re starting from nothing, don’t try to do everything at once. Here’s the order I’d go in.
- Build the skeleton. Use the structure above. Just headings and owners. One afternoon.
- Write the policies. These are decisions, not documentation. Get them on paper and get them approved.
- Record your highest-risk procedures first. Start with whatever breaks if the person who runs it is out, which is usually the close, then bank rec, then AP. Capture each one the next time you actually do it.
- Document your internal controls alongside the procedures they protect.
- Link it together. The manual points to each recorded procedure. One home, always current.
- Set a review cadence. Put a recurring quarterly task on the controller’s calendar. The manual is either a living document or a dead one.
For the bigger picture of how these pieces fit into your day-to-day finance operations, my accounting workflow guide walks through the end-to-end flow that your manual should mirror.
What a good accounting procedure looks like
Whether you write it or record it, every procedure in your manual should share the same anatomy. This holds for any solid standard operating procedure, not just finance ones:
- A clear title and purpose - “Month-End Bank Reconciliation,” not “Banking.”
- Owner and frequency - who does this and when.
- Prerequisites - what must be true before you start (statement received, sub-ledger closed).
- Numbered steps with visuals - the actual screens, not prose.
- Controls and sign-offs - who reviews, who approves, where the audit trail lives.
- Exceptions - what to do when it doesn’t reconcile.
If you’re formalizing this across the whole department, a finance SOP framework and a clear accounting SOP standard give you the kind of consistency that makes a manual trustworthy.
Keeping it alive
The single biggest predictor of whether an accounting manual survives is how expensive it is to update. Everything else comes second.
Name an owner. Put a quarterly review on the calendar. Then cut the cost of refreshing a procedure down to near zero, so that when your AP system changes on a Tuesday, the new procedure exists by Friday instead of next year.
A manual that’s 90% accurate and current beats a beautiful 100%-accurate one that’s 18 months stale. Your team trusts the one they can actually rely on. And the cost of not having one compounds faster than most finance leaders expect - per a 2025 month-end close benchmark, only 18% of finance teams close the books in three days or less, and the ones that close faster almost always have the procedures written down. Build for that.
Teach your co-workers or customers how to get stuff done – in seconds.
Frequently Asked Questions
What is an accounting manual?
An accounting manual is a single source of truth for how a finance function operates. It combines accounting policies (the rules and the why) with procedures (the step-by-step how) and the internal controls that protect the numbers.
What is the difference between an accounting policies and procedures manual?
Policies define the rules, such as your capitalization threshold or approval limits. Procedures define the exact steps to perform a task, like running the AP batch. A complete accounting manual includes both, with policies as written rules and procedures as step-by-step guides.
What should an accounting manual include?
At minimum: governance and ownership, accounting policies, core procedures (AP, AR, reconciliations, payroll, journal entries, month-end close), internal controls, and a systems and access section. Each procedure should be its own standalone guide so it can be updated independently.
How do I create an accounting manual from scratch?
Start with a skeleton of headings and owners, write your policies, then document your highest-risk procedures first (usually the close, bank reconciliation, and AP). Link everything from the manual and set a quarterly review cadence.
Who owns the accounting manual?
Typically the controller or finance leader owns the accounting manual. One named owner is responsible for the review cadence and for ensuring procedures stay accurate as systems and processes change.
How often should an accounting manual be updated?
Quarterly review is realistic for most finance teams. Annual review is usually too slow because accounting software and processes change frequently. Individual procedures should be refreshed whenever the underlying system or workflow changes.
Why do most accounting manuals fail?
They are written for auditors instead of staff, they lack screenshots, and they are treated as a one-time project. The fix is making the manual cheap to create and cheap to update so it stays in sync with reality.
Should an accounting manual have screenshots?
Yes. Procedures with annotated screenshots of the actual system screens are far easier to follow than text descriptions. Recording a task while doing it is the fastest way to produce screenshot-based procedures.
How is an accounting manual different from an accounting SOP?
An accounting SOP is a single documented procedure for one task. An accounting manual is the broader document that contains your policies, all of your SOPs and procedures, and your internal controls in one organized place.
How do you keep an accounting manual from becoming outdated?
Assign a single owner, schedule a recurring quarterly review, and reduce the cost of updating procedures to near zero. The biggest predictor of whether a manual survives is how cheap it is to refresh when processes change.
