Automating Approvals Without Losing Control

Ask a GM how a discount gets approved and you will usually hear two answers. The first is the policy: anything above a set margin goes to the sales director, anything above that goes to the owner. The second is what actually happens. A salesperson sends a screenshot to a WhatsApp group, someone replies with a thumbs-up, and the deal moves on. The ERP finds out later, if it finds out at all.

Purchase orders and credit approvals follow the same pattern. A department head emails a quote to finance, finance forwards it to the CFO, and the CFO answers from his phone between meetings. The answer lands in a different thread from the question. Nobody is being careless. Each person is using the fastest tool available. But the approval, which is supposed to be the control, now lives in five places and none of them is the system of record.

This article covers why approvals get stuck in email and messaging, what that costs a business in practical terms, and how to automate them without burying every decision under forms nobody wants to fill in. The aim is not less oversight. It is more oversight with less chasing.

Where approvals actually live

Most dealer groups, distributors, developers and service-led businesses run a version of the same stack:

• An ERP (or a dealer management system on the automotive side) holding finance, inventory, purchasing, credit limits and invoicing.
• A CRM holding the customer, the opportunity and the quote.
• Email, where quotes, supplier documents and formal sign-offs travel.
• Messaging, mostly WhatsApp, where the real conversations happen, including the quick "can I give him this price?"
• Workflow tooling, either a module inside the ERP or a separate tool, usually configured for one department and ignored by the rest.

Each of these does its own job reasonably well. The trouble is the space between them. The ERP knows the customer's credit limit but not that a discount was promised in a chat. The CRM holds the quote, but the approval sits in a voice note. The email thread has the supplier's PDF, while the decision to proceed was made on a call and confirmed with an emoji.

So the approval matrix exists on paper, perhaps in the ERP, but the decision happens outside it. Anyone trying to audit, forecast or simply find out what was agreed has to reconstruct it by hand. This is also a RevOps problem. Pipeline, margin and revenue reports all assume that the price on the quote is the price that was approved, and that assumption quietly fails when the approval sits in a chat.

A Tuesday in a multi-branch dealer group

Consider a dealer group with branches in three countries. A corporate customer wants six vehicles and asks for a better price than the standard fleet terms. The salesperson prepares the quote in the CRM and sees that the discount exceeds his limit.

He sends a WhatsApp message to his sales manager, who is on the showroom floor with another customer. The manager replies later with a voice note: "Fine, but check with finance on the margin." The salesperson calls finance. The finance analyst needs the cost figures, which sit in the ERP, so she asks him to email the quote. He emails a PDF. She replies that the margin works if the customer takes the extended warranty.

Meanwhile the customer, who communicates entirely on WhatsApp, has asked twice for an answer. The salesperson tells him it is nearly approved. Then the customer asks to add accessories, so the quote changes. The "approval" the manager gave was for the earlier version. Nobody notices. The invoice is raised against the final quote at the discount from the first, and the difference surfaces at month-end as a credit note and an awkward conversation.

Every individual step was reasonable. The result was a slow answer for the customer, a day of back-and-forth for four staff members, and a margin decision that nobody can trace to a specific version of a specific quote. Multiply that by every branch in the group, each with its own habits, and head office has no single view of how discounting really works.

The purchase order that waited for the approver

Now take the aftersales side, which in most dealer groups drives the bulk of revenue and is the most manual part of the operation. A workshop needs a part that is not in stock. The parts coordinator raises a purchase request and emails it to the aftersales manager, who must approve above a certain value, and then to finance.

It is the middle of a public-holiday period. Working hours are shorter, the aftersales manager is covering two branches, and the finance approver is on leave ahead of a long weekend. The email sits in an inbox. There is no formal delegate in the system, only an understanding that "someone will cover." The coordinator chases on WhatsApp. The customer's car occupies a bay for another day, and the customer, who prefers to be served in their own language, receives a vague update from a service advisor who cannot see where the request is.

When the part finally arrives, the supplier's invoice does not match the PO: the price changed, and a line was added by phone. In markets where e-invoicing mandates, including Peppol-based schemes, expect invoices to be structured and traceable, and anywhere VAT or sales tax treatment must be right on every document, a mismatch like this is not trivial. Someone has to reconcile the approved PO, the amended price and the final invoice by hand, and the trail that explains the change is scattered across email and chat.

What fragmentation costs

The costs of approvals scattered across tools are rarely visible on one line of the P&L, which is why they persist. They do show up in everyday operations:

• Delays. Requests wait because the approver did not see them, was not the right approver, or answered in a different channel from the one the requester was watching.
• Exhausted teams. Skilled people spend their day forwarding, chasing, re-attaching and re-explaining. Peak seasons, such as holiday sales campaigns, year-end pushes and summer service rushes, multiply the volume while capacity stays the same.
• Mistakes. Approvals given against outdated quotes, limits overridden without a record, and POs that no longer match invoices all come from the same cause: the decision and the document are not connected.
• Frustrated customers. A customer waiting on a WhatsApp reply, in whatever language they use, does not care which internal approval is outstanding. They see slowness, and slowness invites a competitor.
• Leaked money. Discounts that exceed policy, credit extended without a recorded decision, duplicate or unmatched supplier invoices, and credit notes issued to repair mistakes all cost money. No single instance looks large. Together they are a steady drain.

There is also a control cost. If an approval cannot be proved, it is a risk, whether the question comes from an internal auditor, a group finance head or a tax authority. Where customer details travel through personal phones and chat groups, data protection laws such as GDPR add a further question about where that information ends up.

Control is not the same as friction

When leaders hear "automate approvals," some picture rigid software that slows the sales floor. That fear is well founded, because many workflow projects fail by forcing people into a portal they will never open. A good design starts from the opposite principle: people keep working where they already are, but the decision is captured properly.

In practice that means a few things:

1. The approval matrix is data, not folklore. Thresholds by branch, country, product line, customer type and value are held in one place and applied automatically. When policy changes, it changes once.
2. The request is created from the source. A discount request starts from the quote in the CRM or DMS. A PO request starts from the purchase record in the ERP. Nobody retypes or screenshots anything.
3. The approver gets full context. Margin, customer history, credit position and the exact quote version are in front of them, not in another tab.
4. The decision happens in the channel people use. An approver can be notified on WhatsApp or email and respond there, in their own language, while the decision is written back to the system of record with a timestamp and a version.
5. Delegation and escalation are built in. If the approver is on leave or silent, the request moves to a named delegate or the next level, without anyone chasing.
6. Exceptions are allowed but visible. A manager can still approve something unusual. The difference is that it is recorded, and anyone with the right access can see it.

Done this way, automation removes the chasing, not the judgement. Managers still decide. They simply decide with better information and leave a trail.

There is a second benefit for leadership. Once every decision is written back to the same place, you can build a command-center view on top of it: what is waiting, for how long, in which branch or country, and where exceptions are piling up. That turns approvals from a blind spot into something the centre of the business can actually see and manage, without adding another layer of reporting work for the people on the floor.

How The Ninjaz Group approaches it

We are a managed-services partner, and we sell the outcome rather than software. For approvals, that outcome is simple: the right person decides quickly, with the right information, and the decision lands in the right system. We get there in phases, and you can stop after any one of them.

Blueprint. We map the operation end to end, following discounts, purchase orders and credit requests as they actually travel, including the WhatsApp detours. The aim is to find every gap where work is done twice, data goes stale or money leaks. You keep the map whether or not you continue with us. For some businesses, that map alone settles the argument about what to fix first.

Build & Link. We build what is missing and wire your existing systems into one backbone: DMS or ERP, CRM, finance, messaging and email. This is not rip-and-replace. Software you have already paid for stays, including any workflow capability your ERP already has but nobody configured. The approval then runs across those systems as one process, and the same backbone can feed a central operating center that gives leadership one view across every location. This is the work of our Managed Link layer, the operating layer between systems, built, owned and maintained by us so they behave like one system.

Operate. Approval rules do not stay still. Branches open, thresholds change, people move roles and new regulations arrive. Through Managed Business Operations, we provide the support, monitoring and continuous improvement that keep the flows working, in effect your operations and IT team without the headcount. If the change itself needs design and development, Managed Transformation Services covers that.

You can take any one of these layers on its own. On delivery, regional strategy and account leadership sit close to your market, while engineering, AI development and support come from our dedicated delivery operation in India, working across your business hours. That matters for approvals, which tend to go wrong at the edges of the day, and for groups whose sites span several time zones.

What we would not automate first

Automation is not a goal in itself. Not every approval deserves a workflow, and some should stay as a quick conversation. The sensible starting point is the approvals where delay or error is most expensive: the discounts that touch margin, the purchase orders that hold up a workshop bay or a project, and the credit decisions that expose cash. A single well-built flow in one of those areas will teach you more than a company-wide programme launched in one go, and it gives your teams something concrete to trust.

Start with one approval

If you want to know where your approvals really live, the quickest test costs nothing. Pick one discount, one purchase order and one credit extension from last month, and try to trace each from request to decision to record. If the trail takes more than a few minutes to piece together, you have found your starting point.

If you would like help with that, we are happy to talk it through. Book a consultation and we will look at how approvals move through your business today and where a Blueprint, a build or ongoing operation would make the biggest difference.