—Guide
How to Write SOPs for Finance and Operations That People Actually Use
A practical guide to writing standard operating procedures for finance and operations — structure, level of detail, controls, and how to keep SOPs from gathering dust.
Many businesses have SOPs that nobody reads: long documents written once for an audit and never updated. A useful SOP is short, specific, and written for the person doing the work. This guide explains how to write them.
Start With the Right Processes
Document first the processes that are high-risk, done by only one person, or about to change. In finance, that usually means vendor payments, payroll, month-end close, GST and TDS compliance, and customer billing.
A Simple SOP Structure
- Purpose — what the process achieves, in one or two lines.
- Scope — what's included and what isn't.
- Roles — who performs, reviews and approves.
- Frequency and deadlines — when it happens, and statutory due dates where relevant.
- Steps — numbered, in order, with the system screens used.
- Controls — the checks built in, and the evidence kept.
- Exceptions — what to do when something doesn't fit.
- Version and owner — who maintains it and when it was last updated.
Tips for Writing
- Write in the imperative: 'Download GSTR-2B', not 'GSTR-2B should be downloaded'.
- One action per step.
- Include screenshots for system steps.
- Use worked examples for judgement calls.
- Test the SOP by having someone unfamiliar follow it.
Build Controls In
An SOP is where controls come to life. If vendor bank changes must be verified by phone, that step belongs in the vendor master SOP, along with where the call record is kept. Auditors reviewing internal financial controls will look for exactly this.
Keeping SOPs Alive
- Give each SOP a named owner.
- Review it at least annually.
- Update it whenever the system, the law or the team changes.
- Use it to train new joiners.
Getting Help
Think Filing documents finance and operations processes for growing businesses, with controls built in.