Our first spending approval process lasted six weeks
The list that replaced it is still running, and it changed how I ask my team about odd costs on the account.
By Jens Hagel, Co-Founder at Yupana · Edited by Jenn Moon, Editor at Featured News · Nov 16, 2026
I ran an IT service company in Hamburg, Germany. When we first tried to keep track of spend, we had a multilevel approval workflow. A purchase request was entered at the bottom and exited, signed, at the top.
It worked for about six weeks. After that, half of all purchases were made without using it. Nobody was being sneaky about it. When you need to buy something, you want it done quickly. A request that needs to be signed by someone takes longer. If you have a process that can be avoided, people may avoid it.
Where the workflow failed
The levels were probably not the biggest problem. By putting the workflow in front of the purchase, you miss information you only have after the purchase is made. Do you still use this tool? Does anyone know who is using it? Is it more expensive than it used to be? None of these questions can be answered before a purchase is requested.
Small recurring spend is a good example. We looked at our list of small recurring spend and found 11 items. Each cost between €4 and €38 per month, totaling €214 per month. For seven of these items, we could not say why we had purchased them. I don't believe we would have caught any of them if we had an approval workflow in place. Each item probably seemed like a good idea when we first bought it.
List on a Friday
We created a list we would look at on a Friday. This is what we do today.
I believe it has lasted because it allows the person making the purchase to do what they need to do. Then on a Friday, we go through our list and compare it to our account statement. We are now asking questions about purchases a week later instead of not at all.
If I was setting this up today, I would have all purchases from last Friday to current on the list. Include any that you don't recognize. Keep it small enough to get through in one sitting. I would ask who is responsible for the purchase. We have learned this the hard way. We had a contract that renewed for a year. There was a reminder to cancel the contract, but it was in someone's calendar who no longer worked for us.
Unusual is a question
When I look at something unusual on my account statement, I ask a question. Usually, there is a simple explanation. Billing changed to a different day of the month or a trial we forgot to cancel. If you start to look at every unusual item as suspicious, you might never find out what is really going on.
When you do find something that isn't simple, you want to know. According to the Association of Certified Fraud Examiners (ACFE) in their 2026 Report to the Nations, 43% of the occupational fraud cases studied were detected through tips. That is almost three times the next highest method. More than half of those tips came from employees. I think that if you have a company culture where you ask questions about money, your employees will be more comfortable reporting.
We took this into Yupana when we created our software. We ran our checks on unusual bookings against our own data. Before we allowed anyone to be alerted, we looked at all 548 results. You don't want to create a check that alerts on too many things. People will learn to ignore it, and you are back where you started.
Where this method fails
This is my opinion based on my experience running one company. It may not work for you. A list on a Friday may not catch big one-time purchases. Or maybe a contract you should have known about before you signed it. You should have an approval workflow for those types of purchases. There are also companies that require you to separate purchasing from paying.
I think it takes about an hour to go through the list. If you have 10 employees, that is an hour of someone's time. I would still do it. Those 11 recurring expenses totaled €214 a month, or €2,568 a year.
The same ACFE study found that over half of the fraud they studied occurred because of missing internal controls or someone bypassing them. Having a list that your team goes through with good intent is not going to prevent that. You also need someone to remember to look at it.
The expert featured here is a member of Connectively or HARO, Featured’s expert networks.
About the author
Jens Hagel is co-founder of Yupana, software for mid-sized companies that brings bank transactions, contracts, software licenses and the monthly management report together in one view. In 2004 he founded an IT services company in Hamburg, Germany, and ran it for more than 20 years. He writes about spending and controls in small firms.
