Free Word download β’ Edit online β’ Save & share with Drive β’ Export to PDF
An Accounting Policies and Procedures manual is a formal reference document that defines how a company records, approves, and reports every category of financial transaction β from how invoices are coded and approved to how the books are closed each month. It combines two distinct layers: the policy layer (what the company does and why, such as using accrual-basis accounting or recognizing revenue at delivery) and the procedure layer (step-by-step workflows specifying who does what, when, and with what authorization). Together, they ensure that every person who touches the company's finances follows the same rules, regardless of staff turnover or business growth.
Without written accounting policies and procedures, financial errors compound silently, fraud risks go unaddressed, and lenders or auditors find gaps that stall financing rounds or trigger findings. A single bookkeeper who approves invoices, issues payments, and reconciles the bank account β with no documented controls or independent review β is one of the most common sources of small-business financial loss. When that bookkeeper leaves, institutional knowledge walks out the door with them. A documented manual protects against both risks: it creates the authorization trail and segregation of duties that auditors look for, and it transfers process knowledge into a durable company asset. Banks reviewing SBA loan applications, investors conducting due diligence, and grant-makers assessing nonprofit governance all treat a written financial controls document as evidence of a professionally managed organization. This template gives you the structure to build that document in a single working session rather than starting from a blank page.
| If your situation is⦠| Use this template |
|---|---|
| Small business with a single bookkeeper and basic reporting needs | Accounting Policies and Procedures (Small Business) |
| Nonprofit organization with grant-compliance and restricted-fund requirements | Nonprofit Accounting Policies Manual |
| Company needing a standalone expense reimbursement policy | Expense Reimbursement Policy |
| Business documenting only its accounts payable workflow | Accounts Payable Procedures Manual |
| Organization implementing a formal internal audit framework | Internal Audit Procedures Manual |
| Multi-entity business needing intercompany transaction rules | Intercompany Accounting Policy |
| Business preparing a standalone month-end close checklist | Month-End Close Checklist |
Why it matters: A procedure with no named role is a suggestion, not a control. Auditors and lenders look for clear ownership; without it, the manual fails its primary purpose.
Fix: Assign a specific job title β not a person's name β to every procedure step so accountability survives staff turnover.
Why it matters: A $500 approval threshold set when the company had five employees becomes meaningless when revenue is $10M and hundreds of invoices flow through monthly.
Fix: Schedule an annual review of all dollar thresholds and tie it to the fiscal year planning cycle so limits stay proportionate to business size.
Why it matters: A single person who can create a vendor, approve an invoice, and issue payment has unchecked ability to commit fraud β the most common source of small-business financial loss.
Fix: Document compensating controls where full segregation is not possible, such as owner review of the monthly bank statement and vendor master change log.
Why it matters: Without a version history, staff may follow outdated procedures and auditors cannot confirm which policies were in effect during a given period.
Fix: Add a revision history table to the cover page showing version number, change description, approver, and effective date for every update.
List every department, subsidiary, and transaction type the manual will govern. Identify the role responsible for owning and updating the manual annually.
π‘ Circulate the scope statement to department heads before finalizing β unexpected gaps (e.g., sales team expense cards) surface at this stage rather than after rollout.
Export your current account list from your accounting system, assign a logical numbering convention if one does not exist, and document the rules for creating or retiring accounts.
π‘ Clean up duplicate or unused accounts before documenting β embedding a messy chart of accounts into a formal policy locks in the mess.
Identify each revenue stream and specify the event that triggers recognition (delivery, subscription period, project milestone). Reference ASC 606 or IFRS 15 as applicable.
π‘ If you have more than one revenue stream, document each separately β a single blanket policy often fails to describe any of them accurately.
Decide on dollar thresholds for purchase approval, dual authorization, and purchase orders. Map the workflow from purchase request to payment posting and document each step with the responsible role.
π‘ Set thresholds based on your actual transaction volume β thresholds that are too low create bottlenecks; thresholds that are too high leave significant spend uncontrolled.
Identify every step in the expense reimbursement and payroll processes, then assign each step to a different person where possible. Document what happens when a small team cannot fully segregate duties.
π‘ For small teams where full segregation is impossible, compensating controls β such as owner review of the bank statement β should be documented explicitly.
List every task required to close a period in the order it should be performed. Assign a responsible person and a target completion date relative to month end (e.g., 'Day 3 β post all AP invoices').
π‘ Run the checklist for two consecutive months before embedding it in the policy β you will almost always discover missing steps.
List every regular financial report, its format, the basis of accounting (GAAP, cash, or tax), the delivery deadline, and the distribution list.
π‘ Add a variance commentary requirement for any line item that deviates more than 10% from budget or prior period β this forces proactive explanation rather than reactive guessing.
Have the controller or CFO review the final draft, obtain sign-off from the appropriate authority (owner, board, or audit committee), and distribute to all affected staff with a brief training session.
π‘ Version-control the document with an effective date and revision history table so staff always know which version is current.
Accounting policies are the specific rules a company applies when recording and reporting financial transactions β for example, using accrual rather than cash-basis accounting, or recognizing revenue at delivery rather than contract signing. Procedures are the step-by-step workflows that implement those policies β who approves an invoice, how it is coded, when it is paid, and how the transaction is documented. A combined manual brings both into a single reference document used by finance staff, auditors, and lenders.
Small businesses are disproportionately affected by bookkeeping errors and internal fraud because they often rely on a single person managing all financial tasks. Written procedures create checkpoints that catch errors before they compound, establish the documentation trail auditors and lenders require, and protect the business when key staff leave. Banks and investors routinely ask for evidence of financial controls during due diligence β a written manual provides that evidence directly.
Policies state what the company does and why β for example, "the company recognizes revenue when the performance obligation is satisfied." Procedures describe how that policy is executed step by step β who invoices the client, what system is used, when the entry is posted, and who reviews it. Policies set the standard; procedures operationalize it. Both are necessary: a policy without a procedure is aspirational; a procedure without a policy has no governing rationale.
At minimum, review the manual annually, tied to the fiscal year-end close. Trigger an immediate review whenever the company changes its accounting system, adds a new revenue stream, hires a new controller, undergoes an acquisition, or receives an audit finding. Approval thresholds and dollar limits should be reviewed at least annually to stay proportionate to business volume.
Core controls include segregation of duties for payment processing, payroll, and vendor management; dual authorization for payments above a defined threshold; independent review of bank reconciliations; a vendor master change log; expense receipt requirements; and a month-end close checklist with mandatory sign-off. Each control should name the responsible role, the frequency, and what happens when the control fails or is bypassed.
For most small businesses, owner or CFO approval is sufficient. Nonprofits are typically required by funders and best-practice governance standards to have their financial policies approved by the board or audit committee. Companies seeking institutional financing or preparing for an IPO should have the manual reviewed and approved at the board level to satisfy investor and auditor expectations.
US-based private companies typically follow GAAP, though many small businesses use simplified cash-basis or tax-basis accounting for internal purposes. Companies with operations in multiple countries or those preparing for a foreign public listing should reference IFRS. The manual should state the basis of accounting explicitly in the scope section and apply it consistently β mixing standards across sections creates confusion for auditors and financial statement users.
Yes β the template is system-agnostic and covers the policies and process logic that sit above any specific software. When completing the template, reference your accounting system by name in procedural steps (for example, "enter the invoice in [SYSTEM NAME] under Vendor > Enter Bills") so staff have a direct connection between the written procedure and the software workflow they follow daily.
A financial policies manual focuses on high-level governance β capital structure, investment authority, debt limits, and dividend policy. An accounting policies and procedures manual is more granular, covering the day-to-day transaction workflows, controls, and reporting cycles that implement those higher-level financial policies. Larger organizations typically maintain both; small businesses can combine them in a single document.
An internal controls checklist is a periodic assessment tool β used to verify that controls are operating as designed. An accounting policies and procedures manual is the governing document that defines what those controls are. The checklist tests the manual; the manual does not replace the checklist.
An expense reimbursement policy is a single-topic document covering employee spending, receipts, and reimbursement timelines. An accounting policies and procedures manual includes expense reimbursement as one section alongside revenue, AP, payroll, reconciliation, and reporting. Use the standalone policy when only expense controls need to be communicated to staff; use the full manual when building a comprehensive finance operations framework.
A chart of accounts template provides the numbered account structure for recording transactions. The accounting policies and procedures manual includes the chart of accounts as one component and adds the policies and workflows that govern how those accounts are used. The chart of accounts answers 'where does this entry go?'; the manual answers 'who approves it, when is it posted, and how is it reviewed?'
Time-and-materials billing cycles, WIP tracking, client trust accounts, and billable expense reimbursement policies.
Restricted and unrestricted fund accounting, grant draw-down procedures, board approval thresholds, and IRS Form 990 reporting requirements.
Inventory valuation method (FIFO, LIFO, or weighted average), point-of-sale reconciliation, sales tax collection and remittance, and returns and credits processing.
Percentage-of-completion revenue recognition, job-cost accounting by project, lien and retainage management, and subcontractor payment controls.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Small businesses, startups, and nonprofits formalizing procedures for the first time | Free | 4β8 hours to complete and review |
| Template + professional review | Companies preparing for an external audit, bank financing, or investor due diligence | $500β$1,500 for a CPA or controller review | 1β2 weeks |
| Custom drafted | Multi-entity businesses, regulated industries, or companies with complex revenue recognition and intercompany transactions | $2,000β$8,000 for a CPA firm or finance consultant | 3β6 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Start freeΒ Β·Β No credit card required
