In many small and medium-sized businesses, things work like this: the warehouse clerk ships goods, the accountant issues the invoice, and the owner finds out when he gets back. Or a sales rep offers a steep discount to close a deal, nobody notices, and at month-end nobody can explain why the numbers are off. This picture is familiar to anyone who has worked in a Turkish SME. The problem usually is not bad intent — it is the absence of rules. When operations depend on individuals, everything falls apart the moment that person goes on leave or walks out the door.
ERP (enterprise resource planning) software offers a concrete answer to this problem. Inside these programs, business workflows can be defined. A workflow is a set of steps that determines in what order a transaction moves forward, who must approve it, and what rules govern it. When a purchase request is created, for example, the program automatically routes it to the next approval step. The order cannot be placed until the warehouse manager approves it; the payment instruction cannot be issued until the finance manager signs off. Every step is recorded.
Authority limits work the same way. The maximum discount a sales rep is allowed to offer is entered into the program. If a quote exceeds that limit, the program either warns the user or stops the transaction entirely. The same logic applies to purchasing: orders above a certain value automatically go to a senior manager for approval. None of this requires a phone call or a fax. The program already knows the rules and routes accordingly.
The most tangible benefit of this structure is a reduction in errors. In handwritten ledgers or separate spreadsheet files, a line can be skipped and a figure can be typed wrong. In an ERP program, every transaction is linked to the one before it. If goods cannot leave the warehouse without a stock movement record, and an invoice cannot be created without that movement, and a delivery note cannot be issued without the invoice — then any gap in the chain stops the process from moving forward. This is a simple but powerful mechanism. Instead of spending hours at month-end trying to figure out why the books do not balance, transactions flow in the correct sequence and without missing steps.
A reduction in misuse risk follows naturally from the same structure. Every action a user takes leaves a trace in the program. Who changed which invoice, who cancelled which order, who applied which discount rate — all of it is recorded. No extra effort is needed for auditing. The owner or the finance manager can look at these records at any time. For firms that found themselves under serious cash and inventory pressure during the economic difficulties of 2001, this kind of visibility is a real safeguard.
Setting this up, however, is not a simple task. The company first needs to put its own workflows down on paper. Who approves what, in what order does each transaction move, above what amount is senior approval required — none of this can be entered into the program until it is clearly defined. Many SMEs stumble at this stage because written rules never existed; everything ran on habit and memory. The authorised reseller installing the software can guide the process, but the real work has to be done inside the company. Staff adjustment also takes time. Encountering someone who says ‘why do I have to enter everything into the program, a note used to be enough’ is unavoidable.
For an SME owner considering a move to ERP software, one question can serve as a useful starting point: in my business today, whose approval does a transaction go through, who has authority over what, and is any of this written down? If the answer is ‘nothing is written down, we have always done it this way,’ then the rules need to be clarified before the program is even installed. The software is not magic; it is a tool that makes an existing order run faster and more reliably. If there is no order, the program does not create one on its own. But once the rules are entered into the system, operations from that point forward run according to the system rather than the individual. That shift — from person-dependent to rule-dependent — is one of the most valuable things a growing SME can build.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 2, 2001 and has been automatically translated into English and other languages using machine translation.