Navision ve Microsoft Dynamics 4 dk okuma

How Navision Financials Cuts Errors Caused by Entering the Same Data Twice

A warehouse clerk writes down a delivery on paper. The accountant copies the same figures into the ledger. Someone else types it all into a spreadsheet that evening. Three people, three locations, the same information entered three times. If any one of them makes a single typo, the stock count is off, the invoice does not balance, and the end-of-month reconciliation (the process of checking that all records match) turns into a half-day investigation. This is a routine scene in many small and medium-sized businesses across Turkey.

Navision Financials addresses this problem at its root. The program links purchasing, inventory, and accounting records inside a single system. When a purchase order is created, when goods arrive, and when the supplier invoice comes in, all three steps move forward inside the same structure. There is no second screen to retype the same numbers into. The data goes in once, and the program handles the rest.

In practice this works as follows. When goods arrive, the accountant enters a goods receipt (the record confirming delivery) into the system. The program immediately reflects this movement in the inventory count. When the supplier invoice arrives, the accountant matches it against the receipt already in the system. The program compares the two and flags any difference. There is no need to lay two pieces of paper side by side. If everything matches, the payment step opens. If there is a discrepancy, the record stays on hold and nothing gets overwritten until someone resolves it.

The inventory side makes this even clearer. Under the old approach, the stock card lives in one place and the accounting ledger in another. When they disagree at month end, hours go into finding out who made the mistake and where. In Navision, a stock movement and its accounting entry are created at the same moment. When goods come in, the quantity goes up and the cost account updates simultaneously. When a sale goes through, the stock drops and the revenue entry appears at the same time. There is no second ledger to maintain; one record produces both results.

The cost of invoice errors is easy to overlook until it accumulates. A single invoice posted with the wrong amount can mean an overpayment to a supplier or a shortfall that strains a business relationship. A wrong stock deduction means a salesperson promises delivery on goods that are not actually there. Reconciliation gaps eat hours every month, and when those hours are converted into salary costs, the total often exceeds the licence fee of a decent accounting program. Navision makes this calculation visible: as errors fall, the time saved becomes concrete rather than abstract.

The most common difficulty in practice is the setup and learning period. The program comes with a Turkish-language interface, but the initial installation does not get done without support from an authorised reseller. The database (the structure where all records are stored) requires technical knowledge to configure correctly. Migrating old records from a previous system is a separate task, and any errors already sitting in those old files travel across with them. Staff need a few weeks to get comfortable with the new screens. An accountant who has worked the same way for years does not always welcome a change in routine. These are real obstacles. Businesses that install the program properly and train their staff patiently tend to see invoice discrepancies drop within the first month.

A small business owner evaluating Navision Financials should start with one question: how many people in this company currently write the same information into different places? How many hours a month go into re-entering data and correcting mistakes? If the answer is more than one person and more than a few hours a week, an integrated program can return real savings in time and money. But the software alone is not enough. The company also needs to decide in advance which document gets entered by whom and at which step. If those rules are not set before the system goes live, the program cannot fix the confusion on its own. Buying the technology is the starting point; using it correctly is the actual work.

This article was originally written in Turkish by Gökhan MERCANOĞLU on March 20, 2000 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 →