Read summarized version with
My first finance hire quit four months in.
She was great. Sharp, organized, one of those rare people who genuinely liked reconciling bank accounts. When she walked out the door, our entire month-end close walked out with her. Nothing written down. Not a page.
Her replacement spent the first week of each month asking me questions I had no business answering. “How do we code Stripe payouts?” “Who approves wire transfers over 10K?” “Where’s the prepaid amortization schedule?” No clue.
I’m Yuval, founder of Glitter AI. We work with finance teams, accountants, controllers, AP managers, office managers running the books at small companies. The same pattern shows up again and again, and it’s the one I lived through: finance departments built on tribal knowledge, with one person holding the only working copy of how things actually get done.
This post is the fix. A role-by-role breakdown of the accounting SOPs your finance department actually needs in 2026. Not a generic SOP overview (that’s here), but the specific procedures each function inside finance should have documented before someone gives notice.
Teach your co-workers or customers how to get stuff done – in seconds.
How to Structure SOPs Around Your Finance Department (Not Just Tasks)
Most teams write SOPs the wrong way. They start with a long list of tasks, then try to cram those tasks into folders after the fact.
Better approach: structure SOPs around the functions inside your finance department. Each function gets an owner, a clear scope, and a set of repeatable procedures that need to keep running when the person doing them is on vacation, out sick, or gone for good.
For most finance teams, the functions split up roughly like this:
- Accounts Payable (AP) - money going out
- Accounts Receivable (AR) - money coming in
- General Ledger (GL) - the books themselves
- Payroll - paying the people
- Tax and Compliance - keeping you out of trouble
- Budgeting and Forecasting - looking forward
- Audit Preparation - proving it all worked
Each function needs three to five must-have SOPs. Below, I’ll walk through each one, what to document, who owns it, and the pitfalls teams keep falling into.
Accounts Payable SOPs
AP is where most finance teams start documenting, and for good reason. Mistakes here mean late payments, duplicate payments, missed discounts, or paying invoices that don’t even belong to you.
Who owns it: AP Manager, AP Clerk, or in smaller teams the Office Manager or Bookkeeper.
Must-have AP SOPs
-
Vendor onboarding - How to collect W-9s, set up new vendors in QuickBooks or NetSuite, verify banking details for ACH, and store remit-to addresses. Include a fraud check step (call a known phone number to verify wire instructions, never trust an emailed change).
-
Invoice intake and coding - Where invoices land (email inbox, Bill.com, Ramp), who reviews them, what GL accounts and cost centers they get coded to, and how they get matched to POs.
-
Approval workflow - Dollar thresholds and who signs off. Under 1K, AP Manager. 1K to 10K, Department Head. 10K to 50K, Controller. Above 50K, CFO. Document this in the SOP, not in someone’s head.
-
Payment runs - When checks or ACH batches go out (weekly is standard), who initiates, who approves the funding, and how exceptions are handled.
-
Vendor disputes and credits - How to log a dispute, who follows up, and how credit memos get applied.
Common pitfalls
The biggest one I see: no documented approval thresholds. Whoever happens to be in the office signs the check. That’s how duplicate payments slip through, and it’s how fraud quietly walks in the front door.
The second: vendor banking changes accepted by email. If your AP SOP doesn’t require a callback verification step using a previously-known phone number, you will eventually wire money to someone in another country. Not might. Will.
Teach your co-workers or customers how to get stuff done – in seconds.
Accounts Receivable SOPs
AR is the mirror image of AP. In my experience it gets documented less often, because the cash is coming toward you and people relax. That’s a mistake.
Who owns it: AR Specialist, Billing Coordinator, or Controller in smaller teams.
Must-have AR SOPs
-
Customer setup and credit terms - How a new customer gets created in your billing system, who approves credit terms, and what documentation is required (signed contract, MSA, PO).
-
Invoicing - When invoices go out (on signed contract, on milestone, monthly recurring), what they include, and who reviews before sending. For SaaS, this often runs through a billing platform like Stripe or Chargebee, but the SOP still needs to define the trigger.
-
Payment matching and cash application - How incoming payments (ACH, wire, check, Stripe payout) get matched to open invoices in QuickBooks, Xero, or NetSuite. This is where cash gets lost in suspense accounts when there’s no SOP.
-
Collections - The cadence of dunning emails, when an account goes to a phone call, and at what point you escalate to a collections agency or write off.
-
Bad debt write-offs - Who approves, what documentation is required, and how it hits the GL.
Common pitfalls
Cash sitting in suspense for months because nobody can figure out which customer sent it. A documented payment matching SOP, with explicit instructions for unclear remittances, mostly kills this problem.
The other pitfall: no defined collections cadence. Customers learn pretty quickly which vendors chase them and which ones don’t. If your collections SOP says “first reminder at day 5, second at day 15, phone call at day 30,” your DSO will drop.
General Ledger and Month-End Close SOPs
This is the heart of your finance department. The GL is your source of truth, and month-end close is the monthly ritual that produces the financial statements everyone else relies on.
Who owns it: Controller, Senior Accountant, or Staff Accountant.
Must-have GL SOPs
-
Journal entry preparation and approval - Who can post a JE, what supporting documentation is required, who reviews and approves, and how recurring entries (depreciation, prepaid amortization, accruals) get scheduled.
-
Bank and credit card reconciliations - Frequency (weekly for high-volume accounts, monthly for low), who performs them, who reviews, and how variances get researched.
-
Month-end close checklist - The full sequenced checklist with owners and deadlines. Day 1, AP cutoff. Day 2, AR cutoff. Day 3, accruals and prepaids. Day 4, reconciliations. Day 5, review. Day 6, close. This single document is often the most valuable SOP in the entire finance department.
-
Intercompany transactions - If you have multiple entities, document how intercompany invoices, eliminations, and transfers get handled.
-
Chart of accounts maintenance - Who can add or modify accounts, and the naming/numbering convention.
Common pitfalls
The “month-end close” SOP that’s really just a task list with no owners and no deadlines. Without owners and dates attached, the close drifts to whenever it happens to get done, which means investors, lenders, and your CEO get financials late.
The other one: no separation between preparer and reviewer on JEs. Whoever wrote the entry also approved it. That fails an audit every single time. For more on documenting these workflows in a repeatable format, see my SOP template guide.
Teach your co-workers or customers how to get stuff done – in seconds.
Payroll SOPs
Payroll is the function where mistakes hurt the most. Pay someone late, pay them wrong, or forget to cut off access for someone who left, and you have an immediate human problem on top of a financial one.
Who owns it: Payroll Manager, HR/Payroll Coordinator, or Controller. In smaller teams, often the Office Manager working with an outsourced provider like ADP, Gusto, or Rippling.
Must-have payroll SOPs
-
New hire setup - Collecting I-9, W-4 (or state equivalents), direct deposit, and benefits enrollment. Setting up the employee in ADP/Gusto with the correct pay rate, classification (exempt vs non-exempt), department, and start date.
-
Time approval - How hourly time gets submitted, who approves, and the deadline relative to the pay period close. Missing the cutoff causes off-cycle payroll runs that cost money.
-
Payroll run - The actual sequence: import time, review variances against last period, run preview, get approval, submit. Include who has the authority to release payroll.
-
Off-cycle adjustments - Bonuses, commissions, retro pay, and corrections. Who can request, who approves, and how they get processed.
-
Termination checklist - Final pay calculations (including PTO payout per state law), benefits termination, last paycheck delivery, and revocation of system access. This SOP saves you from the ex-employee who’s still on payroll three months later.
Common pitfalls
No second set of eyes on the payroll preview. The payroll runner is also the payroll approver. One typo on a salary change becomes a wire for ten times what it should have been.
Termination access not revoked because no SOP lists every system. Document every login the company controls, and make access revocation a checklist item, not a memory exercise.
Tax and Compliance SOPs
Tax doesn’t stop because your tax person is on vacation. Filings have hard deadlines, penalties are mechanical, and “we forgot” isn’t an acceptable answer to a state revenue department.
Who owns it: Controller, Tax Manager, or external CPA firm coordinating with internal finance.
Must-have tax and compliance SOPs
-
Sales tax filings - Which states you’re registered in, the filing frequency for each, the source data needed (often pulled from Stripe, Avalara, or your billing system), and who files. A simple calendar with owners prevents most missed filings.
-
1099 preparation - How vendors get flagged as 1099-eligible during onboarding, where W-9s are stored, and the year-end process for issuing 1099s by January 31.
-
VAT/GST filings - If you sell internationally, the per-jurisdiction filing process and the source data.
-
Annual report and franchise tax filings - Per state, the deadlines, fees, and who files.
-
Document retention - How long to keep what (invoices, receipts, payroll records, tax returns), and where they’re stored.
Common pitfalls
A sales tax registration in a state you forgot about. The SOP should include an annual review of nexus, both physical and economic, so new registrations get added before a state finds you first.
Budgeting and Forecasting SOPs
This function tends to get less attention because the work is project-based rather than transactional. But the budgeting cycle is one of the more painful annual events in any finance department, and an SOP makes it noticeably less painful the second time around.
Who owns it: FP&A Manager, Controller, or CFO in smaller teams.
Must-have budgeting SOPs
-
Annual budget process - The timeline (typically starting 90 days before fiscal year end), the templates each department head fills out, the consolidation process, and the approval cadence.
-
Monthly forecast updates - How actuals get loaded, who updates assumptions, and when the rolling forecast gets refreshed.
-
Variance analysis - The format of the budget vs actual report, what triggers a deeper investigation, and how variance commentary gets captured.
-
Headcount planning - How open reqs get tracked against approved headcount, and who approves new hires.
Common pitfalls
Department heads doing budget work in their own spreadsheets in their own format. The SOP should include the exact template every department uses, so consolidation doesn’t turn into three weeks of cleanup.
Audit Preparation SOPs
Whether you’re going through a financial statement audit, a SOC 2 audit, or a tax audit, the work is roughly the same: produce documentation, fast, that proves your controls operated as designed.
Who owns it: Controller, with input from every other function.
Must-have audit SOPs
-
PBC (prepared by client) request fulfillment - Where each common audit document lives, who pulls it, and the review step before it goes to the auditor.
-
Walkthrough preparation - The standing process narratives for AP, AR, payroll, and revenue recognition that get refreshed before each audit cycle. Your existing function-level SOPs feed directly into this.
-
Sample testing support - How to pull supporting documentation when the auditor selects a sample (invoice, payment, JE).
-
Management representation letter - The annual review of accounting policies and the sign-off process.
Common pitfalls
Scrambling to recreate process narratives during the audit because nobody updated them since last year. If your function-level SOPs are kept current throughout the year, audit prep shifts from a four-week fire drill to a two-day exercise of compiling what you already have.
Teach your co-workers or customers how to get stuff done – in seconds.
How to Get All of This Documented Without Burning Out Your Team
Reading this list, the natural reaction is: “Great, but who has time to write all these SOPs?”
That’s the real problem, and it’s the one we built Glitter AI to solve. Most finance teams I talk to already know they need documented procedures. They’ve been told for years. They have half-written Google Docs, an old Notion page, and a folder on someone’s desktop. None of it is current, none of it is complete.
The traditional approach (block off three days, sit down with each finance person, write everything from scratch) almost never happens. There’s always a close to run, a vendor to chase, a payroll to process.
What actually works in 2026 is recording the work as it’s being done. Have your AP Clerk run through a vendor onboarding once with a recorder going. Have the Controller walk through a bank rec. The Glitter SOP generator turns those screen recordings into step-by-step SOPs with screenshots automatically. No typing, no formatting, no separate writing project.
It’s the same idea as recording training videos for things like QuickBooks training or Sage 100 training, except instead of a video nobody re-watches, you get a text SOP that’s actually searchable, editable, and easy to update when the process changes.
Either way, manually written or auto-generated, the structure I laid out above is what your finance department needs. Pick the function with the highest single-person dependency risk, document the three to five must-have SOPs for it, then move to the next function.
The first time you have a finance person quit and the work keeps moving without them, the value of every hour you spent on this becomes pretty obvious.
Frequently Asked Questions
What SOPs does a finance department need?
Every finance department needs SOPs across seven functions: accounts payable (vendor onboarding, invoice processing, payment runs), accounts receivable (invoicing, collections, payment matching), general ledger (journal entries, reconciliations, month-end close), payroll (new hire setup, payroll run, terminations), tax and compliance (sales tax, 1099s, VAT/GST), budgeting and forecasting, and audit preparation. Most teams need 25 to 35 documented SOPs total.
What is an accounts payable SOP?
An accounts payable SOP is a documented procedure for how invoices get received, coded, approved, and paid. A complete AP SOP set covers vendor onboarding (including W-9 collection and bank verification), invoice intake and GL coding, the approval workflow with dollar thresholds, payment runs (checks and ACH), and vendor dispute handling.
Who owns accounting SOPs in a finance department?
Each function has its own owner: AP Managers own AP SOPs, AR Specialists own AR SOPs, Controllers typically own GL and audit SOPs, Payroll Managers own payroll SOPs, and FP&A leads own budgeting SOPs. The Controller usually serves as the overall owner who ensures the full library stays current.
How many SOPs should a finance department have?
A typical small to mid-size finance department needs 25 to 35 documented SOPs spread across AP, AR, GL, payroll, tax, budgeting, and audit prep. Larger departments with multiple entities, international operations, or complex revenue recognition often need 50 or more.
What is a month-end close SOP?
A month-end close SOP is a sequenced checklist of every task required to close the books each month, with owners and deadlines for each step. A typical month-end close SOP runs from day one (AP cutoff) through day six (close complete) and covers AP and AR cutoffs, accruals, prepaids, reconciliations, and final review.
What software is used for accounting SOPs?
Most finance teams build SOPs around their accounting platform - QuickBooks, Xero, Sage, or NetSuite for the books, ADP or Gusto for payroll, and Bill.com or Ramp for AP. The SOPs themselves are increasingly created with screen-recording tools like Glitter AI that auto-generate step-by-step documentation, and stored in a knowledge base like Notion or Confluence.
How often should finance department SOPs be updated?
Finance SOPs should be reviewed at least annually, with mandatory updates whenever a process changes - new software, new approval threshold, new tax registration, or new compliance requirement. The best practice is to update the SOP in the same workflow as the process change, not as a separate project.
What is the difference between a finance department SOP and an accounting SOP?
An accounting SOP typically refers to a single procedure (how to reconcile a bank account, how to post a journal entry), while a finance department SOP library is the full set of procedures across every function in the department. The finance department SOP library is structured around roles and functions; individual accounting SOPs are the building blocks.
What are the most common accounting SOP mistakes?
The three most common mistakes are: no documented approval thresholds (so anyone can sign anything), no separation of preparer and reviewer on journal entries (which fails audits), and no termination checklist for system access (which leaves ex-employees in payroll and accounting systems). All three are fixed with proper documented procedures.
How do you create accounting SOPs without a full-time documentation person?
The most efficient approach in 2026 is to record finance staff doing each process once with a screen recorder, then use an AI tool like Glitter AI to auto-generate the step-by-step SOP with screenshots. This eliminates the typing and formatting work that prevents most finance teams from ever finishing their SOP library.
