Before You Automate, Document: A Practical Guide to SOPs for MSMEs

An SME manufacturer had everything going for him. Orders were steady, customers were happy, and the business was running smoothly. Then, one morning, a key team member resigned and simply did not turn up.

The problem was not the empty chair. It was what left with the person.

Which vendors to pay first, how an invoice was raised, what needed to be checked before dispatch: none of it was written down. It had all lived in one head.

So the owner stepped in. Instead of meeting customers and growing the business, he spent the following days figuring out how each job was done.

His business looked perfect on paper. In reality, it was only one resignation away from being stuck.

Is your business in a similar position?

When Business Processes Depend On People

For many MSMEs, day-to-day operations depend more on individual knowledge than on documented processes. The owner knows how things work, the accountant knows which payments are pending, and the purchase manager knows which suppliers need to be contacted. As long as these people are available, the business continues to run.

The difficulty begins when someone is unavailable, a new employee joins, or the business grows beyond what a few people can manage personally.

Most MSMEs do not struggle only because of a lack of customers. They also lose time and money through small, repeated operational gaps.

Consider a few common situations:

• Vendor payments: An invoice sits in a WhatsApp chat for 60 days because nobody has recorded its due date. If the supplier is a qualifying micro or small enterprise, delayed payment may also have statutory consequences.
• Delayed billing: Goods leave the factory, but the invoice is raised a week later by the accountant. The business has completed the dispatch but has delayed the start of its collection cycle.
• Unplanned purchases: Orders are placed over the phone, leaving the finance team unaware of commitments already made to suppliers. Cash planning becomes guesswork.

Each situation may appear manageable in isolation. The problem is that these gaps occur repeatedly, often across several departments.

What Do These Delays Mean Financially?

Consider a manufacturing business that dispatches goods worth ₹5 lakh every working day. If invoices are raised seven working days after dispatch, approximately ₹35 lakh of sales could be awaiting invoicing at any given time, assuming the dispatch value remains constant.

This does not mean the business has lost ₹35 lakh. It means a substantial amount of business activity is sitting between dispatch and billing, with the collection process yet to begin.

Now imagine that the delay is reduced through a clearly defined dispatch-to-invoice process. The business gains better visibility over unbilled dispatches, invoices can be raised promptly, and the collection cycle can start earlier.

The improvement does not necessarily require a new software system. It may begin with a simple rule: every dispatch must be communicated to the accounts team on the same day, and pending invoices must be reviewed regularly.

The problem is not always the absence of software. Often, it is the absence of a clear rule about who must do what, and by when.

The unwritten rule that only one person knows may be one of the most expensive weaknesses in a business.

What a written rule gives you

A Standard Operating Procedure (SOP) explains how a recurring task should be performed. It identifies what triggers the task, who performs each step, when it must happen, and who checks whether it has been completed.

For an MSME, an SOP need not be a lengthy manual. A single page may be sufficient for a straightforward process, provided another team member can follow it without depending entirely on the person who created it.

A well-written SOP helps in five ways:

1. Consistency: The task is performed in a consistent manner, irrespective of which team member handles it.
2. Control: Approvals and checks are built into the process. A maker-checker arrangement, where appropriate, helps identify errors before they become larger problems.
3. Compliance: Applicable tax and statutory requirements, along with their deadlines, can be incorporated into everyday processes rather than left to memory or year-end reminders.
4. Easier delegation and growth: A new employee has a reference to follow instead of having to learn everything through repeated instructions from the owner.
5. A foundation for automation: The SOP becomes the starting point for configuring software. It tells the business what the system needs to record, approve, remind, and report.

From SOP to Systems: The Order Matters

One common mistake business make is to purchase software first and then try to fit their processes into it. A system can make an existing process faster, but if the process itself is unclear, the system may simply help the business make the same mistakes more quickly.

A better approach is to follow a simple sequence:

1. Understand the current process. Identify how the task is performed today, where delays occur, and what frequently goes wrong.
2. Decide what needs to change. Remove unnecessary steps and clarify responsibilities, approvals, and timelines.
3. Write the SOP. Document the agreed process in simple language.
4. Identify what can be automated. Determine which steps can be supported through mandatory fields, approval workflows, reminders, and reports.
5. Configure and test the system. Check whether the software supports the SOP in practice before rolling it out across the business.

The first three steps establish the process. The next two help the business use technology to follow it more consistently.

For Example:

SOP line	What it becomes in software
“Every purchase needs a PO before the vendor ships”	A mandatory PO field before a bill can be booked
“Invoices above a set value need owner approval”	An approval workflow with limits
“Pay MSME vendors within the agreed days, never beyond 45”	A due-date alert and an ageing report filtered by vendor type
“Chase every customer invoice on day 30”	An automatic payment reminder
“Owner reviews open orders every Monday”	A pipeline report sent every Monday

An SOP kept in a Word file still needs an owner, a review routine and follow-through. A tool configured without an agreed process can leave gaps and weak controls.

The two need each other: the SOP says what should happen, and the tool supports the checks that can be built into the workflow.

Three everyday processes: what goes wrong, and how an SOP and tech fix it

Few SOPs examples below show how this works in reality.

1. Payment SOP: paying MSME vendors on time

• What used to happen: Supplier invoices arrive through email or WhatsApp. Someone forwards them to the accountant, but the invoice is not recorded immediately. When payment is due, the team may have to search through messages to establish the amount, terms, and due date. Payments become unplanned, and the business risks missing applicable statutory deadlines.
• What should the SOP say:
  • Record every supplier invoice in the designated system when it is received.
  • Capture the supplier’s details, invoice date, amount, agreed payment terms, and expected due date.
  • Identify qualifying micro and small enterprise suppliers so that the applicable payment requirements can be monitored.
  • Review invoices falling due during the coming week.
  • Obtain the required approval and maintain a record of payment.
• How the SOP fixes it: Payment no longer depends on someone remembering an invoice. Each invoice has a recorded status and due date, and a weekly review helps the business plan its payments in advance.
• How tech strengthens it: The accounting system can maintain due dates, generate ageing reports, and flag invoices approaching their deadlines. This gives the owner and finance team better visibility into upcoming cash requirements.

2. Purchases SOP: approving purchases before money is spent

• What used to happen: A manager phones a supplier and places the order on a verbal approval. The commitment is not recorded where the owner can see it. When the bill arrives, the owner discovers a payment that was missing from next month’s cash forecast.
• What should the SOP say:
  • Every purchase begins with a purchase requisition or an approved request.
  • The designated person approves the purchase within the applicable authority limits.
  • A purchase order is issued after approval.
  • Supplier bills are checked against the purchase order and supporting documents before being processed.
  • Exceptions are referred to the appropriate authority rather than being routinely accepted
• How the SOP fixes it: The business gains visibility over its commitments before the payment becomes due. The owner can make better decisions about purchases and working capital because the finance team has information about orders already placed.
• How tech strengthens it: A suitable system can record purchase requests, route them for approval, maintain purchase orders, and show open purchase commitments.

3. Sales SOP: never missing a WhatsApp or phone order

• What used to happen: A customer sends an order on WhatsApp or by phone. It is noted on a slip or remembered by one salesperson. If that person is busy or away, the order waits, dispatch is delayed, and the invoice goes out days late, so collection starts late too.
• What should the SOP say:
  • Record every enquiry or order on the day it is received, irrespective of the communication channel.
  • Assign a person responsible for the next action.
  • Confirm the order in writing and record the agreed delivery terms.
  • Coordinate dispatch with the relevant team and ensure that the invoice is raised promptly in accordance with the dispatch and billing process.
  • Follow up on pending orders, outstanding invoices, and customer payments according to a defined schedule.
• How the SOP fixes it: No order lives only in someone’s phone. Every order has a stage and an owner, and follow-up is a defined step. The business can identify which orders are awaiting confirmation, production, dispatch, or invoicing instead of relying on individual employees to remember what needs to happen.
• How tech strengthens it: A CRM or sales-order system can maintain enquiries and orders in one place, show their current status, identify items that have been pending for too long, and send reminders to the responsible employee. For a small business, even a well-maintained shared tracker may be a reasonable starting point. A more sophisticated system can be considered as the volume and complexity of operations increase.

These three examples demonstrate a common principle: the business first establishes a clear process, then uses technology to improve visibility and reduce dependence on memory.

How Chartered Accountants Can Help MSMEs

For many MSME owners, the Chartered Accountant is already a trusted adviser. The CA sees the financial consequences of operational gaps through the books of account, delayed collections, unapproved expenses, supplier balances, and year-end adjustments. This places the CA in a useful position to help the business identify where a simple change in process could prevent recurring problems.

The role need not begin with a large technology project. It can begin with a discussion about why a particular problem keeps recurring.

A CA can support an MSME in five practical ways:

1. Process mapping and SOP drafting. Walking through how the business actually runs, then turning it into one-page SOPs the owner can approve.
2. Compliance built into the process. Building statutory requirements and deadlines into everyday steps, so reporting comes from data and not year-end scrambling.
3. Tool selection and set-up. Choosing the accounting, CRM or reporting tool that fits the business, configuring approvals, reminders and reports, and training the staff.
4. Prototypes for gaps. Using an AI builder tool to mockup a simple tracker, so the owner can react to something real before paying for a build.
5. Regular review. A short monthly report that shows whether the processes are being followed and where money is leaking, which turns SOPs into a habit.

The SOPs decide what should happen. The tools decide how reliably it happens. That is why the next section looks at the tools an MSME can actually use to enforce them.

Tools an MSME can actually use

Tools do not create good processes. They enforce them. Whichever process you write down, whether it is buying, selling, paying, hiring or reporting, a good tool does four things: it records each step, applies the rule, reminds the right person and reports the result.

There is no single right tool, so the better question is which process needs help and how much. The following are examples of tools used for common business needs. They are illustrative options, not a ranking or an endorsement.

Business Requirement	Examples of Tools / Softwares
Accounting, GST billing, inventory	TallyPrime, Zoho Books, Vyapar, Marg ERP
Sales, enquiries and customer follow-up (CRM)	Zoho CRM, HubSpot CRM
Payroll and attendance	Zoho Payroll
Reporting and dashboards	Excel, Google Sheets
Documents and SOP library	Google Drive
Niche requirement using AI Builder*	Lovable, Bolt, Replit, Claude code

Features, pricing, integrations, and suitability vary by product and may change over time. A business should verify the current capabilities and commercial terms before making a decision.

A few principles apply regardless of the tool selected:

• Map the process first. Choose the tool after the SOP is documented, not before.
• Start with what you already use. The existing accounting system may already support approvals, reminders, and ageing reports that have not been configured.
• Avoid unnecessary complexity. Every additional tool requires time, training, and maintenance. Prefer systems that work together and avoid duplicate data entry.
• Keep control of your data. Understand who can access business information and whether the records can be exported when required.
• Train the people who will use the system. A well-configured tool is of little value if employees do not understand how to use it or continue maintaining parallel records outside the system.

Where AI builder tools fit

AI-powered application builders, such as Lovable, Bolt, Replit, and Claude Code, can help create a prototype or a simple internal application from a written description.

For an MSME, these tools may be useful when a process requires a basic tracker or workflow that the existing software does not adequately support. For example, a business may want a tracker for pending customer approvals, delayed dispatches, or maintenance requests.

Where to begin

The biggest mistake an MSME can make is to treat process documentation as a large project that must cover the entire business.

It does not have to. A simple step works better:

1. Start with one process that regularly causes a problem.
2. Write down the steps on one page. Identify who performs each step, when it must happen, what approval is required, and who checks whether it has been completed.
3. Discuss the process with the employees who perform the work. Test whether the instructions are practical, make the necessary changes, and agree on how compliance with the SOP will be reviewed.
4. Then look at the available tools. If the existing system can support the process, configure it. If it cannot, evaluate whether a simple tracker or another application is justified.
5. Review the results after 30 days. Look for missed steps, avoidable delays, and improvements in visibility.

For a CA working with an MSME client, the same approach provides a manageable starting point: select one client and one recurring problem, document the process, help configure the appropriate controls, and review the results together.

The first successful implementation can become a practical example for addressing other processes.

The Best Time to Write It Down

Go back to the manufacturer at the beginning of this article.

On the day his key employee left, he did not necessarily need a bigger team or an expensive system. He needed the important processes to be documented while the business was running smoothly.

The SOP records what the business knows. The right tool helps the team follow the process. And a trusted adviser can help the owner put both in place.

An MSME does not need to automate everything at once. It needs to identify where the business is most dependent on individual memory, establish a clear process, and gradually build the discipline to follow it.

The best time to write the first page is before anyone resigns.

[The author can be reached at kunjesh.90@gmail.com]