Systems and Process Audit: Finding the Money Your Business Loses Every Day

Most owners feel it before they can name it: the company is busy, orders keep coming, everyone is working — yet profit does not grow at the same pace as turnover. Money rarely disappears in one big loss. It leaks in a thin, steady stream: an extra hour here, the same data typed in twice there, a subscription nobody opens, a report someone assembles by hand every Friday that nobody reads.

A systems and process audit is a way to see those leaks and close them. Not tidying up for the sake of tidiness, but finding the specific places where the business pays for something that gives it nothing back.

Three kinds of audit that people often confuse

The word “audit” means something different to everyone. Let us separate them.

• A financial audit answers the question “did we count correctly, and will the tax office be happy”. It is about numbers and compliance with rules. It is necessary — but it will tell you almost nothing about why a manager spends two hours a day moving data from an inbox into a spreadsheet.
• A technical audit is about the state of what has already been built: whether the site holds up under load, whether backups exist, whether something is sitting in the open that should not be, whether everything stops the day the one person who knows the passwords leaves.
• An IT audit — or a systems and process audit — is the broadest one, and the most useful for an owner. It looks at the company as a living mechanism: where the data flows, who types what by hand, how many times the same piece of information is copied from one place to another, which decisions sit waiting for approval, and what that waiting costs.

The rest of this article is about the third one.

We look at how the process actually works

The main trap of any audit is reading the procedure instead of watching the work. The procedure says a request goes through four steps. In real life the manager skips two of them because it is faster. The accountant keeps her “own” spreadsheet in parallel with the accounting system because that is more convenient for her. The warehouse worker photographs a delivery note and sends it over Telegram because the system takes too long to load.

A procedure is how somebody once wanted things to be. The real process is what people actually do at ten in the morning on a Monday. The losses live precisely in the gap between those two pictures.

So the work looks like this:

• Conversations with the people who do the work by hand. Not only with department heads, but with the people who press the buttons. The question is simple: “Show me how you do this. What annoys you most about it?” People usually know exactly where it hurts — nobody has ever asked them.
• Following a real request or order from the first contact to the money in the account. We travel with it through every pair of hands, every inbox, spreadsheet and chat.
• A review of what has already been bought. Which systems are paid for every month, and which of them anyone has actually opened in the last quarter.
• The arithmetic. Every leak we find is converted into hours per month and into money. Without that, an audit is just a list of remarks.

We do not arrive with a ready-made answer of “you need to automate everything”. Sometimes the right recommendation is to cancel a subscription and remove one unnecessary approval step. That costs nothing and returns the time immediately.

Where the money usually leaks

The same stories repeat year after year. Here are the most common ones — check yourself against them.

• Double, sometimes triple data entry. An order arrives by email, the manager copies it into a spreadsheet, then types the same thing into the accounting system, then creates the shipping label by hand as well. One piece of information, four rounds of typing, four chances to make a mistake.
• Unnecessary approvals. A step that appeared once after an unpleasant incident, and ever since then every small expense waits for the signature of a person who signs everything without reading it. Often this is not control — it is ritual.
• Software that is paid for and unused. Licences for people who no longer work here. A service bought for a project that closed. Two systems doing the same job because two departments each chose their own.
• Manual reports. Someone spends an hour every week assembling numbers into a spreadsheet. Two questions are worth asking: can this be collected automatically, and — more importantly — does anyone actually read that report and make a decision based on it. Sometimes the best way to automate a report is to stop producing it.
• Waiting. A request sits for two days not because it is difficult, but because it is waiting for someone to pass it along. Your money is standing in a queue.
• Knowledge in one head. One employee is the only person who knows how to start or fix a certain thing. That is not a saving — it is a risk with a price tag.

Imagine a small shop where three people move the same orders between an inbox, a spreadsheet and an accounting system every day. Even at one hour each, that adds up to a full working week every month — paid for, and sold to nobody. You can calculate that in half a day, and it is exactly that calculation that turns a conversation about automation into a business decision.

What you get at the end

An audit should end with a document you can work from, not with impressions. For us it is three things.

• A map of the process “as it really is”. A clear diagram of how a request, an order or a document moves through the company — including every real workaround, chat and spreadsheet. Very often the picture alone makes management say: “Do we honestly work like this?”
• A list of losses with a price on each. Every bottleneck comes with an estimate: hours per month, money, risk. The estimates are conservative and built on your data, not on market averages.
• An action plan sorted by effect against cost. First what can be removed tomorrow for free. Then the cheap automations. And only at the end the things that require serious development. You see the whole list and decide for yourself where to stop.

The plan stays yours whether or not we are the ones who implement it. An audit that only makes sense as the sales pitch for a big project is not an audit.

In short

• A financial audit is about numbers, a technical audit is about the state of your systems, a process audit is about how the company actually works and where it loses.
• Losses live in the gap between the written procedure and reality, so you have to watch the work, not read the documents.
• The usual leaks: double data entry, unnecessary approvals, paid-for software nobody uses, manual reports, waiting, and knowledge locked in one head.
• Every finding must be converted into hours and money — otherwise it is just an opinion.
• The output is a process map, a list of losses with a price on each, and a plan sorted by effect against cost.

If you recognised your company in at least two of those points, there is probably something worth counting. Try the AI assistant on this site: a few questions about your business and you will see where it makes sense to start. Or simply write to us, and we will calmly work out whether there is anything here worth doing at all. If there is not, we will say so honestly.