Expert verified
| TL;DR Summary: |
| Process inefficiencies rarely show up as a single red flag; at ₹100 Cr+ enterprises running multiple plants or branches, they accumulate quietly across procurement, production, and collections until margins erode. PKC’s process audit combines walkthroughs, control testing, and cross-location benchmarking to surface these gaps and hand fast-scaling enterprises a prioritized, implementable fix list rather than a generic findings report. |
If you run a business with more than one plant or branch, you probably know this feeling. The numbers look fine on the surface, but something feels a little off. Margins are thinner than they should be. Working capital is stuck somewhere. And when you ask why, nobody has a clean answer. That is usually not a finance problem. It is a process problem that has been sitting there quietly for months before it shows up in the profit and loss statement.
This is exactly the gap a process audit is built to close. At PKC, we work with mid-to-large enterprises across manufacturing, retail, and services that have moved past the single-location stage and now run multiple plants or branches. The biggest leakages we find are rarely fraud or big mistakes. They are small, repeated inefficiencies in everyday processes – procurement, production, inventory, and order-to-cash – that nobody adds up until it is too late.
This blog looks at how a process audit works, where these leakages usually hide in a multi-plant setup, and how PKC turns findings into a roadmap your COO can act on.
Why Process Inefficiencies Stay Invisible Until They Hit the P&L Across Multiple Plants
Most businesses do not lack data. They lack a structured way of looking at their own processes end to end. A finance team can tell you what happened last month, but very few teams can tell you why a purchase order took eleven days to get approved at one plant and three days at another, for the same kind of purchase.
When a company runs out of a single location, small inefficiencies are visible because everyone works close together. Add a second plant or a regional warehouse, and the same inefficiency starts hiding behind distance. A delay in vendor approval at Plant B does not get flagged the way it would at head office, simply because nobody there sees it happen.
A few patterns we see often:
● Different plants following different versions of the “same” process, unstandardized since the second location opened
● Manual workarounds that started as a temporary fix during a system rollout and never went away
● Approvals that exist on paper but are rubber-stamped, so control is more illusion than fact
● Data entered differently at each location, making comparisons across plants misleading
None of this shows up as one big number. It shows up as margin that is a percentage point or two lower than it should be, or working capital tied up several extra days compared to industry peers. By the time the CFO notices it in the P&L, the inefficiency has usually been running for several quarters. A process audit is built to catch this earlier, at the process level, before it becomes a financial statement problem.
PKC’s Process Audit Methodology: Walkthrough, Testing, Benchmarking Across Locations
A process audit is not the same as ticking boxes against a checklist. At PKC, we follow a three-step approach built for multi-location businesses.
Walkthrough. We sit with the people actually doing the work – the purchase executive, the store keeper, the supervisor, the person raising invoices – and walk through the process exactly as it happens, not as it is written in the manual. This is where most of the real insight comes from, because documented processes and actual practice are rarely identical.
Testing. Once we understand how a process really works, we test a sample of real transactions against it, to see whether what we observed is a one-off or a pattern. If a plant’s rule says every large order needs two sign-offs, we pull actual purchase orders and check whether that is really happening.
Benchmarking across locations. This part is unique to multi-plant audits. We compare the same process – say, goods receipt or vendor payment – across every plant in the group. This shows which plant runs it well and which is lagging, and why. Sometimes the answer is a better system, sometimes just a more disciplined team. Either way, it turns a plant-level observation into a group-wide insight.
Throughout, we keep the evidence documented, so the discussion with your leadership stays about facts, not opinions. This three-step approach is the same one behind PKC’s process audit services, applied consistently whether we’re reviewing one process or five across your entire plant network.
Common Leakage Points in Procurement and Vendor Management at ₹100 Cr+ Scale
Once a business crosses roughly ₹100 crore in turnover and starts running multiple plants, procurement is often the first place control quietly slips:
● Vendor master duplication – the same vendor exists under two or three codes across plants, weakening negotiating power and raising fraud risk
● Rate variation across plants – the same material bought at different rates simply because buying was never consolidated
● “Urgent” purchases bypassing approvals – a genuine emergency exception that quietly becomes routine
● Weak three-way matching – purchase order, goods receipt, and invoice are meant to match before payment, but the check is often done loosely, letting short deliveries or rate mismatches slip through
Procurement is often where the largest single leakage sits, since it touches vendor negotiation, approvals, and cash outflow all at once – see PKC’s complete guide to a procurement-to-payment process audit for a deeper look at this specific process.
Each looks minor alone. Across four or five plants, they can add up to a meaningful share of annual procurement spend – a number that only becomes visible once you audit the process, not just the ledger.
Production Floor and Inventory Process Gaps Across Multi-Plant Operations
Procurement is only half the story. The rest plays out on the shop floor and in the warehouse:
● Inconsistent SOPs – one plant follows a documented process for material issue, another runs it informally, making it hard to compare efficiency fairly
● Slow-moving stock hiding in plain sight – carried forward year after year without proper review, tying up working capital
● Weak cycle counting – physical checks happen once a year at the statutory audit, so mismatches are discovered months after they occur
● Production planning disconnected from ground reality – plans made centrally without real-time visibility of downtime or manpower shortage
When we benchmark across plants, one or two are usually clearly more disciplined. That plant becomes the template for standardizing the group.
Order-to-Cash Cycle Breakdowns That Delay Collections Across Branches
The order-to-cash cycle is where inefficiency shows up directly as cash stuck outside the business. Small breakdowns at each branch add up to a large group-wide delay:
● Inconsistent credit terms – similar customers get different informal credit periods depending on the branch and the salesperson
● Invoicing delays – goods are dispatched but the invoice is raised a couple of days later due to a manual approval step, pushing back the collection clock
● Branch-to-head-office reconciliation gaps – branch sales do not always tie back cleanly to the receivables ledger
● Weak follow-up on overdue accounts – without a structured ageing review, collection often depends on how proactive one salesperson happens to be
Individually, each gap may cost only a few days. Repeated across five or six branches, the impact on collection days can be significant – money technically owed to the business but sitting outside its control.
Case Snapshot: What a Process Audit Uncovers in a Multi-Layered Organization
Here is an illustrative example based on the kind of pattern we typically see in a multi-plant manufacturing group (a composite for explanation, not a specific client engagement).
A group with three plants believed its procurement and inventory processes were reasonably well controlled, since each plant had its own SOP. A walkthrough across all three plants found that two plants were buying the same raw material category from overlapping vendors at noticeably different rates, simply because buying was never consolidated after the third plant opened. One plant caught stock discrepancies early through regular cycle counts, while the other two only found mismatches during the annual physical verification, by which time the root cause was hard to trace. Invoicing at two plants was delayed by a couple of days because of a manual sign-off step with little real control value, since the same person raising the invoice was also approving it.
None of this would have shown up from the financial statements alone. It became visible only by walking through the process, testing transactions, and comparing plants side by side – the value a process audit adds beyond a standard financial review.
Turning Findings Into an Implementation Roadmap the COO Can Standardize Group-Wide
An audit report full of observations is only useful if someone can act on it. This is where many process reviews fall short – they list problems but leave the “how do we fix this across every plant” question unanswered.
At PKC, every process audit closes with a roadmap built for the person who has to implement it, usually the COO or head of operations. It includes a prioritized list of findings sorted by financial impact and ease of fixing; a clear owner for each corrective action, not a vague team name but a named role; an SOP template for any process found inconsistent across plants, based on whichever plant was already doing it best; a realistic rollout timeline; and a simple set of metrics to track after implementation, so leadership can see whether the fix actually worked.
The goal is simple: once the audit is done, the COO should be able to pick up the roadmap and start driving change immediately, without needing another round of consulting to translate findings into action.
Frequently Asked Questions
Q1: What is a process audit and how is it different from an internal audit?
A process audit looks closely at how a specific process actually works day to day, such as procurement or order-to-cash, and compares it against what is efficient and well controlled. An internal audit has a broader scope, usually focused on compliance, risk, and financial controls across the organization. A process audit goes deeper into the “how” of one process; an internal audit takes a wider view. Many companies use both together.
Q2: How long does a process audit take for a ₹100 Cr+ enterprise running multiple plants?
This depends on the number of plants, the processes covered, and how well-documented current processes already are. A focused review of two to three core processes across three to four plants typically takes a few weeks, from walkthrough to final roadmap. A broader review covering procurement, production, inventory, and order-to-cash together will take longer. PKC scopes the timeline upfront based on the specific processes and plants involved.
Q3: Which departments does a process audit typically cover across locations?
The most common areas are procurement and vendor management, production and shop floor operations, inventory and warehouse management, and the order-to-cash cycle covering sales, dispatch, invoicing, and collections. It can also extend into HR and payroll or IT controls, especially ahead of an ERP rollout. Scope is agreed with the client before the audit begins.
Q4: What deliverables does PKC provide after a multi-plant process audit?
Clients get a detailed findings report with evidence from the walkthrough and testing stages, a plant-by-plant benchmarking summary, and a prioritized implementation roadmap with clear ownership and timelines. Where relevant, we also provide SOP templates for processes that need to be made consistent across plants. These are built to be used directly by the operations team, not filed away after a presentation.
Q5: How does a process audit help before a group-wide ERP implementation?
An ERP system is only as good as the processes it supports. If a company implements a new ERP on top of processes that are inconsistent across plants, the system ends up automating the inconsistency instead of fixing it. Running a process audit before the rollout gives the implementation team a clean, standardized process to configure around, which usually reduces rework and customization costs, and makes user adoption smoother once the system goes live.
Q6: Can a process audit be done alongside an ongoing statutory audit across entities?
Yes, and it often works well to run them together, since both involve reviewing transactions and controls, just from different angles. A statutory audit checks whether financial statements are fairly presented; a process audit looks at operational efficiency and control gaps in the underlying processes. Running them in parallel can also cut down the time your team spends explaining the same processes to two separate teams.
