A purchase request is posted in the management group at ten in the morning. By noon it sits under forty other messages. The owner replies with a thumbs-up at night, to which message nobody is sure. The accountant enters the bill the following week and asks who approved it. Most growing businesses approve things this way, and most of them reach a point where it stops being safe. Approval workflow software is the usual answer, though not always the right first one.
We are a product engineering team at Infopark in Kochi. We build business software for companies in India, the UAE and Australia, and approvals are part of the systems we build, from custom ERP software to sales and HR tools. This guide covers what to look for and when to leave things as they are.
The short answer
WhatsApp is a good way to tell someone that an approval is waiting. It is a poor place to hold the approval itself, because a chat does not know what is pending, who must decide or what was agreed. Move sign-offs into software when approvals have more than one step, involve money, or need to be proved later. If one person approves everything and the amounts are small, stay on WhatsApp.
Why approvals end up on WhatsApp
Approvals end up on WhatsApp because it is on every phone, it needs no training and the approver can answer from anywhere. Those are real advantages. An owner who is travelling can release an order in ten seconds. A formal system that makes the same owner log in on a laptop will be ignored.
Stay on WhatsApp and stop reading if these are true. One person approves everything. Requests are few enough that none gets buried. The amounts are small, or the approver would notice a wrong one anyway. Nobody outside the business, such as an auditor, a bank or a head office, asks you to show who approved what. A system would add steps and remove nothing.
Where chat approvals break down
Chat approvals break down because a message is not a record. It has no status, no owner and no link to the transaction it concerns. The problems below follow from that one fact.
Nobody can see what is pending
A chat shows messages in the order they arrived. It has no list of requests still waiting for a decision. The person who asked has to remember to chase, and the person who approves has to scroll. Requests are missed because they sank under newer messages, not because anyone refused them.
The approval is separate from the thing approved
The request says a quantity and a price. The purchase order raised afterwards may say something different. Nothing ties the thumbs-up to the document, so nobody can tell whether what was bought is what was approved.
The rules live in people's heads
Purchases above a certain value need the director. Discounts beyond a certain level need the sales head. Everyone knows the rules roughly, and new staff do not know them at all. A chat group cannot stop a request from skipping a step.
The record sits on personal phones
The history of who approved what is spread across the phones of the people in the group. When someone leaves the company, changes phone or clears a chat, their part of that history may go with them. Finding one approval from eight months ago means scrolling or guessing at search words.
There is nothing to hand to an auditor
An auditor, a lender or a group head office may ask for evidence that a payment or a write-off was authorised. Screenshots of a chat are weak evidence, and collecting them is slow.
One absent approver stops the queue
When the approver is on a flight or on leave, requests wait. A chat has no way to pass the decision to a deputy after a set time, or to tell the requester that it has been passed on.
What approval workflow software does
Approval workflow software turns each request into a record with a status, sends it to the right people in the right order, and keeps a history of every decision. The parts are simple.
A request form. The same fields every time, with the quotation, bill or drawing attached to the request.
Routing rules. Who approves is decided by amount, department, branch or type, and the system applies the rule without being asked.
Steps in order or side by side. One approver after another, or several at once, as the policy requires.
A pending list for each approver. Everything waiting for a decision, oldest first, on a phone.
Approve, reject or send back. A rejection carries a reason, and a request sent back returns to the requester to be corrected.
Reminders, escalation and delegation. An unanswered request is chased, passed upwards after a set time, or handed to a deputy while the approver is away.
An audit trail. Who decided, when, and what the request said at that moment.
A link to the transaction. The approved request becomes the purchase order, the payment or the leave entry, so what is done matches what was approved.
WhatsApp approvals vs approval workflow software
WhatsApp is faster to start and easier for the approver. Workflow software is stronger on everything that happens after the approver taps a button.
| Approvals on WhatsApp | Approval workflow software | |
|---|---|---|
| Setting up | Nothing to set up. | Rules, roles and forms have to be agreed and configured or built. |
| Making a request | A free-text message, different every time. | A form with the same fields and the documents attached. |
| Who approves | Whoever replies in the group. | The people named by the rule, in the order the policy sets. |
| What is pending | Known only by scrolling and remembering. | A list for each approver and each requester. |
| Absent approver | The request waits. | Reminder, escalation or a named deputy. |
| Record | Chat history on personal phones. | A history on each request, kept by the company. |
| Link to the transaction | None. The order or payment is entered separately. | The approved request creates or releases the transaction. |
| Reporting | None. | How many requests, how long they waited and where they waited. |
| Main risk | Missed requests and approvals nobody can prove. | A flow with too many steps that people work around. |
Keep WhatsApp for the notification
Moving approvals out of WhatsApp does not mean taking WhatsApp away from approvers. A system can send the approver a message on WhatsApp, by SMS or by email saying that a request is waiting, with a link that opens it. The convenience stays. The decision and its record move into the system. Messages sent by software go through the WhatsApp Business Platform, which is the route WhatsApp provides for businesses, not through a personal account or a group.
Which approvals to move first
Move first the approvals that involve money, repeat often and pass through more than one person. In most businesses these are the candidates.
Purchase requests and purchase orders, routed by value and department.
Vendor payments, where the bill, the order and the goods received should agree before money leaves.
Discounts and credit beyond a limit, where a salesperson needs a release before confirming an order.
Expense claims and advances.
Leave and overtime, where the approved result has to reach payroll.
Our guide to what to automate first gives the tests for ranking them. Approvals that are rare, or that are a discussion more than a decision, can stay in conversation.
Buy, configure or build
Look at what you already own before buying anything, and buy before you build. There are three routes.
Use the approval feature in a tool you already have
Many accounting, CRM and HR products include approval steps for their own documents. If the approvals you need are for leave, expense claims or sales discounts, and the product you use already handles them, switch the feature on. This costs the least and is often enough.
Use a general workflow or form tool
No-code workflow tools let you build a request form and a chain of approvers without a developer. They suit a small number of simple flows. Their limit is the link to the transaction. The approval is recorded in one place and the purchase order or payment is still entered in another.
Build approvals into the system that runs the operation
When approvals depend on live data, such as stock on hand, a customer's outstanding balance, a project budget or a vendor's past prices, they belong inside the system that holds that data. This is where a custom build earns its cost. In a custom ERP the approval is a state of the purchase order itself. In a custom CRM a discount approval is routed from the quotation. Our post on Tally vs ERP explains why multi-step approvals are often the first sign that operations have outgrown accounting software.
How to design an approval flow people will use
An approval flow fails when it is slower than the chat it replaced. Design it to be quicker for the approver than scrolling a group.
Write the policy first. Who approves what, up to which value. If the directors cannot agree this on one page, no software will settle it for them.
Use as few steps as the risk requires. Every extra approver adds waiting. Small amounts can be approved by one person or by rule.
Put everything the approver needs on one screen: the amount, the reason, the attachment and the budget or balance it draws on.
Make it work on a phone, with one tap to approve and a required reason to reject.
Name a deputy for every approver, and decide what happens when a request has waited too long.
Pilot one flow with one department before adding the rest.
When we build this, the policy is agreed during discovery and the first flow is in front of real approvers early, as part of the process we follow on every build.
Frequently asked questions
What is approval workflow software?
It is software that turns a request into a record, sends it to the right approvers in the right order, reminds them, and keeps a history of each decision. It may be a feature of a larger system or a separate tool.
Is it wrong to approve things on WhatsApp?
No. For a small team with one approver and modest amounts it works well. It becomes a risk when requests are missed, when approvals have several steps, or when you need to prove later who authorised a payment.
Can approvers still be notified on WhatsApp?
Yes. A system can notify the approver on WhatsApp, by SMS or by email with a link to the request. The decision is made and recorded in the system, and the chat is only the alert.
Do we need an ERP to get approval workflows?
Not necessarily. If the approvals are for leave, expenses or discounts, the HR or CRM product you already use may cover them. An ERP or a custom system makes sense when approvals depend on stock, budgets or credit limits held in that system.
How many approval levels should a business have?
As few as the risk justifies. Tie the number of approvers to the value and type of the request, so that routine small items pass quickly and only large or unusual ones reach the owner.
Conclusion
Approving on WhatsApp is quick, and for a small business with one approver it should stay as it is. Once approvals have several steps, involve payments or need to be proved later, a chat group is the wrong place to hold them. Approval workflow software keeps a list of what is pending, applies the rules for who decides, and records the decision against the transaction. Start with the feature in a tool you already own, and build only when the approval depends on data that lives in your own operations.
We are happy to look at how sign-offs move through your business today and say which route fits, including when the answer is to leave them on WhatsApp. Tell us how your approvals work and we will start from there.
Human. Digital. Future.



