Navision ve Microsoft Dynamics 4 dk okuma

Financial Control with Navision: Budgets, Spending Authorization and Debtor Risk

Picture a wholesale textile company. The purchasing manager places a material order. The accounting department finds out weeks later. To ask how much of the budget has been spent, someone has to walk into the owner’s office. Meanwhile, several customers have overdue invoices that nobody has noticed. When month-end arrives, the numbers are a mess and arguments follow. Keeping financial control in this kind of environment, working with paper records and telephone calls, is genuinely hard.

Navision is an ERP (enterprise resource planning) system — a software program that brings all business processes into one place. Its financial control side focuses on three things: spending authorization, budget comparison, and credit limit tracking. When these three work together, visibility over the company’s money improves considerably.

Spending authorization works like this: when a purchase order or payment request is entered into the program, the system automatically links it to the relevant budget line. If the amount exceeds the defined approval threshold, the program routes it to a senior person for sign-off. That person approves or rejects it from their own screen. No fax, no waiting in the corridor. Every approval step is recorded inside the program — who approved what, and when. Nothing gets lost.

Budget comparison works in a similar way. At the start of the year, budget figures are entered for each department. As spending happens, the program automatically measures actual costs against the budget. The purchasing manager can look at the screen and immediately see how much of the raw materials budget has been used this month. The owner does not need to ask; the information is already there. Think of it as a much faster version of checking the ledger and doing the arithmetic by hand.

Credit limits — the maximum balance allowed for a given customer or supplier — are where many small businesses feel the most pain. A customer with overdue invoices keeps placing new orders because the relationship feels important, and the total receivable quietly grows. In Navision, a credit limit can be set for every account. When a customer’s balance crosses that limit, the program raises a warning. It can even be configured to block new orders entirely until the balance comes down. It works like a safety lock: the alarm sounds before the door opens.

In practice, the biggest benefit of these mechanisms is catching problems when they happen, not at month-end. The program produces a list of receivables overdue by more than thirty days. The manager looks at that list and knows exactly which customers to call. The same applies on the payables side: which supplier needs to be paid, and when, is visible from the program. Managing cash flow — the balance between money coming in and money going out — becomes something you can actually see and plan around, rather than guess at.

None of this is effortless to set up. Before these features can work, budget figures need to be entered correctly, credit limits need to be defined for every account, and the approval hierarchy needs to be configured. This setup takes time and is difficult to complete without support from an authorised local reseller. Beyond setup, the system depends entirely on staff entering data accurately and consistently. If entries are incomplete or wrong, the program cannot give reliable warnings. The value of the software is only as good as the data going into it.

For a small business owner thinking about tightening financial control, three questions are worth asking before making any decision. Are spending approvals currently tracked on paper, or is there a proper record? How often do you review overdue receivables — and how long does it take to pull that information together? How much time does it take each month to compare actual spending against the budget? The answers to those three questions will tell you fairly quickly whether a program like Navision would make a real difference in your day-to-day operations.

This article was originally written in Turkish by Gökhan MERCANOĞLU on April 16, 2001 and has been automatically translated into English and other languages using machine translation.

Gökhan MERCANOĞLU

Gökhan MERCANOĞLU

Teknoloji Danışmanı & Yazar

ERP, CRM, otomasyon, yapay zekâ ve kurumsal teknoloji stratejisi üzerine yazan bağımsız teknoloji danışmanı.

Navision ve Microsoft Dynamics — Tüm Yazılar Navision ve Microsoft Dynamics kategorisindeki yazıları gör →