Microsoft Dynamics NAV Financial Management

4 (1 reviews total)
By Cristina Nicolàs Lorente , Laura Nicolàs Lorente
  • Instant online access to over 7,500+ books and videos
  • Constantly updated with 100+ new titles each month
  • Breadth and depth in over 1,000+ technologies

About this book

Microsoft Dynamics NAV is an Enterprise Resource Planning (ERP) application used in all kinds of organizations around the world. An ERP helps to integrate internal and external management information across an entire organization. It provides a great variety of functionalities in different areas such as accounting, sales and purchases processing, logistics, and manufacturing.

Microsoft Dynamics NAV Financial Management explains all you need to know to successfully handle your daily financial management tasks. You will learn about functionalities such as the sales and purchase processes, payments, bank account management, reporting taxes, budgets, cash flow, fixed assets, inventory valuation, and business intelligence.

This book comprehensively walks you through all the financial management features inside Dynamics NAV following a logical schema. This book is focused on what’s most important to you, the functionalities of Dynamics NAV, and it covers all setup explanations in a single chapter.

You will gain in-depth knowledge about functionalities, including sales and purchase processes, pricing, document approval, payments, bank management, and accounting transactions. You will also learn about VAT reporting, fixed assets, inventory valuation, annual account closing, consolidation, reporting, and business intelligence.

By the end of this book, you will have also learned about budgets, cash flow management, currencies, intercompany postings, and accounting implications on areas such as jobs, services, warehousing, and manufacturing.

Publication date:
October 2013


Chapter 1. The Sales and Purchase Process

Sales and purchases are two essential business areas in all companies. In many organizations, the salesperson or the purchase department are the ones responsible for generating quotes and orders. People from the finance area are the ones in charge of finalizing the sales and purchase processes by issuing the documents that have an accountant reflection: invoices and credit memos.

In the past, most systems required someone to translate all the transactions to accountancy language, so they needed a financer to do the job. In Dynamics NAV, anyone can issue an invoice, with zero accountant knowledge needed. But a lot of companies keep their old division of labor between departments. This is why we have decided to explain the sales and purchase processes in this book. This chapter explains how their workflows are managed in Dynamics NAV. In this chapter you will learn:

  • What Dynamics NAV is and what it can offer to your company

  • To define the master data needed to sell and purchase

  • How to set up your pricing policies

  • What kind of documents you can issue

  • The workflows inside the sales and purchases area


Introducing Microsoft Dynamics NAV

Dynamics NAV is an Enterprise Resource Planning (ERP) system targeted at small and medium-sized companies.

An ERP is a system, a software, which integrates the internal and external management information across an entire organization. The purpose of an ERP is to facilitate the flow of information between all business functions inside the boundaries of the organizations. An ERP system is meant to handle all the organization areas on a single software system. This way the output of an area can be used as an input of another area.

Dynamics NAV 2013 covers the following functional areas:

  • Financial Management: This includes accounting, G/L budgets, account schedules, financial reporting, cash management, receivables and payables, fixed assets, VAT reporting, intercompany transactions, cost accounting, consolidation, multicurrency, and intrastat.

  • Sales & Marketing: This area covers customers, order processing, pricing, contacts, marketing campaigns, and so on.

  • Purchase: The purchase area includes vendors, order processing, approvals, planning, costing, and other such areas.

  • Warehouse: Under the warehouse area you will find inventory, shipping and receiving, locations, picking, assembly, and so on.

  • Manufacturing: This area includes product design, capacities, planning, execution, costing, subcontracting, and so on.

  • Job: Within the job area you can create projects, phases and tasks, planning, time sheets, work in process, and other such areas.

  • Resource Planning: Manage resources, capacity, and so on.

  • Service: Within this area you can manage service items, contracts, order processing, planning and dispatching, service tasks, and so on.

  • Human Resources: Manage employees, absences, and so on.

Some of these areas will be covered in detail in this book.

Dynamics NAV offers much more than robust financial and business management functionalities. It is also a perfect platform to customize the solution to truly fit your company needs. If you have studied different ERP solutions, you know by now customizations to fit your specific needs will always be necessary. Dynamics NAV has a reputation for being easy to customize, which is a distinct advantage.

Since you will probably have customizations in your system, you might find some differences with what is explained in this book. Your customizations could imply that:

  • You have more functionality in your implementation

  • Some steps are automated, so some manual work can be avoided

  • Some features behave differently than explained here

  • There are new functional areas in your Dynamics NAV

In addition Dynamics NAV has around forty different country localizations that are meant to cover country-specific legal requirements or common practices.

Many people and companies have already developed solutions on top of Dynamics NAV to cover horizontal or industry-specific needs, and they have registered their solution as an add-on, such as:

  • Solutions for the retail industry or the food and beverages industry

  • Electronic Data Interchange (EDI)

  • Quality or maintenance management

  • Integration with third-party applications such as electronic shops, data warehouse solutions, or CRM systems

Those are just a few examples. You can find almost 2,000 registered third-party solutions that cover all kind of functional areas. If you feel that Dynamics NAV does not cover your needs and you will need too much customization, the best solution will probably be to look for an existing add-on and implement it along with your Dynamics NAV.

Anyway, with or without an add-on, we said that you will probably need customizations. How many customizations can you expect? This is hard to tell as each case is particular, but we'll try to give you some highlights.

If your ERP system covers 100 percent of your needs without any customization, you should worry. This means that your procedures are so standard that there is no difference between you and your competitors. You are not offering any special service to your customers, so they are only going to measure you by the price they are getting.

On the other hand if your Dynamics NAV only covers a low percentage of your needs it could just mean two things: this is not the product you need; or your organization is too chaotic and you should re-think your processes to standardize them a bit.

Some people agree that the ideal scenario would be to get about 70-80 percent of your needs covered out of the box, and about 20-30 percent customizations to cover those needs that make you different from your competitors.

Importance of Financial Management

In order to use Dynamics NAV, all organizations have to use the Financial Management area. It is the epicenter of the whole application. All other areas are optional and their usage depends on the organization's needs. The sales and the purchase areas are also used in almost any Dynamics NAV implementation.

Actually, accountancy is the epicenter, and the general ledger is included inside the Financial Management area. In Dynamics NAV everything leads to accounting. It makes sense as accountancy is the act of recording, classifying, and summarizing, in terms of money, the transactions and events that take place in the company.

Every time the warehouse guy ships an item, or the payment department orders a transfer, these actions can be written in terms of money using accounts, credit, and debit amounts.

An accountant could collect all the company transactions and translate them one-by-one to accountancy language. But this means manual duplicate work, a lot of chances of getting errors and inconsistencies, and no real-time data.

On the other hand, Dynamics NAV is capable to interpret such transactions and translate them to accountancy on the fly. In Dynamics NAV everything leads to accountancy, so all the company's employees are helping the financial department with their job. The financers can now focus on analyzing the data and taking decisions, and they don't have to bother on entering the data anymore.

Posted data cannot be modified (or deleted)

One of the first things you will face when working with Dynamics NAV is the inability to modify what has been posted, whether it's a sales invoice, a shipment document, a general ledger entry, or any other data. Any posted document or entry is unchangeable.

This might cause frustration, especially if you are used to working with other systems that allow you to modify data. However, this feature is a great advantage since it ensures data integrity. You will never find an unbalanced transaction.

If you need to correct any data, the Dynamics NAV approach is to post new entries to null the incorrect ones, and then post the good entries again. For instance, if you have posted an invoice and the prices were wrong, you will have to post a credit memo to nullify the original invoice and then issue a new invoice with the correct prices.

Document No.



Invoice 01



Credit Memo 01


This nulls the original invoice

Invoice 02



As you can see this method for correcting mistakes always leaves a track of what was wrong and how we solved it. Users get the feeling that they have to perform too many steps to correct the data, with the addition that everyone can see that there was a mistake at some point. Our experience tells us that users tend to pay more attention before they post anything in Dynamics NAV, which leads to make fewer mistakes in the first place.

So another great advantage of using Dynamics NAV as your ERP system is that the whole organization tends to improve their internal procedures, so no mistakes are done.

No save button

Dynamics NAV does not have any kind of save button anywhere in the application. Data is saved into the database while it is being introduced. When you enter data in one field, right after you leave the field, the data is already saved. There is no undo feature.

The major advantage is that you can create any card (for instance, Customer Card), any document (for instance, Sales Order), or any other kind of data without knowing all the information that is needed.

Imagine you need to create a new customer. You have all their fiscal data except their VAT Number. You could create the card, fill in all the information except the VAT Registration No. field, and leave the card without losing the rest of the information. When you have figured out the VAT Number of your customer, you can come back and fill it in. The not-losing-the-rest-of-the-information part is important.

Imagine that there actually was a Save button; you spend a few minutes filling in all the information and, at the end, click on Save. At that moment, the system carries out some checks and finds out that one field is missing. It throws you a message saying that the customer card cannot be saved. So you basically have two options:

  • To lose the information introduced, find out the VAT number for the customer, and start all over again.

  • To cheat. Fill the field with some wrong value so that the system actually lets you save the data. Of course, you can come back to the card and change the data once you've found out the right one. But nothing will prevent any other user from posting a transaction with the customer in the meantime.


Understanding master data

Master data is all the key information to the operation of a business. Third-party companies, such as customers and vendors, are part of the master data. The items a company manufactures or sells are also part of the master data.

Many other things can be considered master data, such as the warehouses or locations, the resources, or the employees.

The first thing you have to do when you start using Dynamics NAV is load your master data into the system. Later on, you will keep growing your master data by adding new customers, for instance. To do so, you need to know which kind of information you have to provide.


We will open a customer card to see which kind of information is stored in Dynamics NAV about customers. To open a customer card, follow these steps:

  1. Navigate to Departments/Sales & Marketing/Sales/Customers.

  2. You will see a list of customers, find No. 10000 The Cannon Group PLC.

  3. Double-click on it to open its card, or select it and click on the View icon found on the Home tab of the ribbon.

The following screenshot shows the customer card for The Cannon Group PLC:

Customers are always referred to by their No., which is a code that identifies them. We can also provide the following information:

  • Name, Address, and Contact information. A Search Name can also be provided if you refer to your customer by its commercial name rather than by its fiscal name.

  • Invoicing information: It includes posting groups, price and discount rates, and so on. You may still not know what a posting group is, since this is the first time those words are mentioned in this book. At this moment, we can only tell you that posting groups are important. But it's not time to go through them yet. We will talk about posting groups in Chapter 6, Financial Management Setup.

  • Payments information: It includes when and how will we receive payments from the customer.

  • Shipping information: It explains how do we ship items to the customer.

Besides the information you see on the card, there is much other information we can introduce about customers. Take a look at the Navigate tab found on the ribbon.

Other information that can be entered is as follows:

  • Information about bank accounts so that we can know where can we request the payments. Multiple bank accounts can be set up for each customer.

  • Credit card information, in case customers pay using this procedure.

  • Prepayment information, in case you require your customers to pay in advance, either totally or partially.

  • Additional addresses where goods can be shipped (Ship-to Addresses).

  • Contacts: You may deal with different departments or individuals from your customers.

  • Relation between our items and the customer's items (Cross References).

  • Prices and discounts, which will be discussed in the Pricing section.

But customers, just as any other master data record, do not only have information that users inform manually. They have a bunch of other information that is filled in automatically by the system as actions are performed:

  • History: You can see it on the right side of the card and it holds information such as how many quotes or orders are currently being processed or how many invoices and credit memos have been issued.

  • Entries: You can access the ledger entries of a customer through the Navigate tab. They hold the details of every single monetary transaction done (invoices, credit memos, payments, and so on).

  • Statistics: You can see them on the right side and they hold monetary information such as the amount in orders or what is the amount of goods or services that have been shipped but not yet invoiced.

  • The Balance: This is a sum of all invoices issued to the customer minus all payments received from the customer.

Not all the information we have seen on the customer card is mandatory. Actually, the only information that is required if you want to create a transaction is to give it a No. (its identification) and to fill in the posting group's fields (Gen. Bus. Posting Group and Customer Posting Group). All other information can be understood as default information and setup that will be used in transactions so that you don't have to write it down every single time. You don't want to write the customer's address in every single order or invoice, do you?


Let's take a look now at an item card to see which kind of information is stored in Dynamics NAV about items. To open an item card, follow these steps:

  1. Navigate to Departments/Sales & Marketing/Inventory & Pricing/Items.

  2. You will see a list of items, find item 1000 Bicycle.

  3. Double-click on it to open its card.

The following screenshot shows the item card for item 1000 Bicycle:

As you can see in the screenshot, items first have a No., which is a code that identifies them. For an item, we can enter the following information:

  • Description: It's the item's description. A Search Description can also be provided if you better identify an item using a different name.

  • Base Unit of Measure: This is the unit of measure in which most quantities and other information such as Unit Cost or Unit Price for the item will be expressed. We will see later that other units of measure can be used as well, but the Base is the most important one and should be the smallest measure in which the item can be referred.

  • Classification: Item Category Code and Product Group Code fields offer a hierarchical classification to group items. The classification can fill in the invoicing information we will see in the next point.

  • Invoicing information: This includes posting groups, costing method used for the item, and so on. Posting groups are explained in Chapter 6, Financial Management Setup, and costing methods are explained in Chapter 3, Accounting Processes.

  • Pricing information: This is the item's unit price and other pricing configuration, which we will cover in more detail in the Pricing section.

  • Foreign trade information: This is needed if you have to do Instrastat reporting.

  • Replenishment, planning, item tracking, and warehouse information: These fast-tabs are not explained in detail because they are out of the scope of this book. They are used to determine how to store the stock and how to replenish it.

Besides the information you see on the item card, there is much other information we can introduce about items through the Navigate tab found on the ribbon.

As you can see, other information that can be entered is as follows:

  • Units of Measure: These is useful when you can sell your item either in units, boxes, or other units of measure at the same time.

  • Variants: These is useful when you have multiple items that are actually the same one (thus, they share most of the information) but with some slight differences. You can use variants to differentiate colors, sizes, or any other small difference you can think of.

  • Extended Texts: These is useful when you need long descriptions or technical info to be shown on documents.

  • Translations: These is used so that you can show an item's descriptions in other languages, depending on the language used by your customers.

  • Prices and discounts: These will be discussed in the Pricing section.

As with customers, not all the information in the item card is mandatory.

Vendors, resources, and locations

We will start with third-parties: customers and vendors. They work exactly the same way. We will just look at customers, but everything we will explain about them can be applied to vendors as well. Then, we will look at items, and finally we will take a brief look at locations and resources.

You can apply to vendors the same concepts learned with customers, as they work exactly the same way. You can also apply to resources the concepts learned with items.

We have seen in detail how customers and items work as master data. You can apply the same concepts to other master data. For instance, vendors work exactly the same way as customers. The concepts learned can be used in resources and locations, and also to other master data such as G/L accounts, Fixed Assets, Employees, Service Items, and so on.



Pricing is the combination of prices for items and resources, and the discounts that can be applied to individual document lines or to the whole document.

Prices can be defined for items and resources and can be assigned to customers. Discounts can be defined for items and documents and can also be assigned to customers.

Both prices and discounts can be defined at different levels and can cover multiple pricing policies. The following diagram illustrates different pricing policies that can be established in Dynamics NAV:

Defining sales prices

Sales prices can be defined at different levels to target different pricing policies.

The easiest scenario is when we have a single price per item or resource, that is, the One single price for everyone policy. In that case, the sales price can be specified on the Item card or on the Resource card, in a field called Unit Price.

In a more complex scenario, where prices depend on different conditions, we will have to define the possible combinations and the resulting prices.

We will explain how prices can be configured for items. Prices for resources can be defined in a similar way, although they offer fewer possibilities.

To define sales prices for an Item, follow these steps:

  1. Navigate to Departments/Sales & Marketing/Inventory & Pricing/Items.

  2. You will see a list of items, find item 1936-S BERLIN Guest Chair, yellow.

  3. Double-click on it to open its card.

  4. On the Navigate tab, click on the Prices icon found under the Sales group.

  5. The Edit – Sales Prices page will open.

As you can see in the screenshot, multiple prices have been defined for the same item. A specific price will only be used when all the conditions are met. For example, a Unit Price of 131 will be used for any customer that buys item 1936-S after 17/01/2014 but only if the customer buys a minimum of 11 units.

Different fields can be used to address each of the pricing policies:

  • The combination of Sales Type and Sales Code fields enable the different prices for different customers policy

  • Fields Unit of Measure Code and Minimum Quantity are used for the different prices per volume policy

  • Fields Starting Date, Ending Date, and Currency Code are used for the different prices per period or currency policy

They can all be used at the same time to enable mixed policies.


When multiple pricing conditions are met, the price that is used is the one that is most favorable to the customer (the cheapest one).

Imagine Customer 10000 belongs to the RETAIL price group. On 20/01/2014 he buys 20 units of item 1936-S. There are three different prices that could be used: the one defined for him, the one defined for its price group and the one defined to all customers when they buy at least 11 units. Among the three prices, 130.20 is the cheapest one, so this is the one that will be used.


Prices can be defined including or excluding VAT

Defining sales discounts

Sales Discounts can be defined in different levels to target different pricing policies.

We can also define item discounts based on conditions. This addresses the Discounts based on items policy and also the Discounts per volume, period, or currency policy, depending on which fields are used to establish the conditions.

In the following screenshot, we can see some examples of item discounts based on conditions, which are called Line Discounts because they will be applied to individual document lines.


In some cases, items or customers may already have a very low profit for the company and we may want to prevent the use of line discounts, even if the conditions are met.

A field called Allow Line Disc, can be found on the customer card and on sales prices. By unchecking it, we will prevent line discounts from being applied to a certain customer or when a specific sales price is used.

Besides the line discounts, invoice discounts can be defined to use the General discounts per customer policy. Invoice discounts apply to the whole document and they depend only on the customer.

Follow these steps to see and define invoice discounts for a specific customer:

  1. Open the customer card for customer 10000, The Cannon Group PLC.

  2. On the Navigate tab, click on Invoice Discounts.

The following screenshot shows that customer 10000 has an invoice discount of 5 percent.


Just as with line discounts, invoice discounts can also be disabled, using a field called Allow Invoice disc. that can be found on the item card and on sales prices.

There is a third kind of discount, payment discount, which can be defined to use the Financial discounts per early payments policy. This kind of discount applies to the whole document and depends on when the payment is done. Payment discounts are bound to a Payment Term and are to be applied if the payment is received within a specific number of days.

The following screenshot shows the Payment Terms that can be found by navigating to Departments/Sales & Marketing/Administration/Payment Terms:

As you can see, a 2 percent payment discount has been established when the 1M(8D) Payment Term is used and the payment is received within the first eight days.

Purchase pricing

Purchase prices and discounts can also be defined in Dynamics NAV. The way they are defined is exactly the same as defining sales prices and discounts. There are some slight differences:

  • When defining single purchase pricing on the item card, instead of using the Unit Price field, we will use the Last Direct Cost field. This field gets automatically updated as purchase invoices are posted.

  • Purchase prices and discounts can only be defined per single vendors and not per group of vendors as we could do in sales prices and discounts.

  • Purchase discounts can only be defined per single items and not per group of items as we could do in sales discounts.

  • We cannot prevent purchase discounts from being applied.

  • Purchase prices can only be defined excluding VAT.



Dynamics NAV is not an accountancy system, but an Enterprise Management system. Invoices are not the general ledger entries that resume them, but the document that you ship to your customer. The ledger entries are just a result of posting the document.

Documents are used to create transactions bound to one customer (or vendor) and to one or many items or resources.

Let's see how documents work by creating a sales invoice. There are other types of documents. They will be explained in the next section.

To create an invoice such as the one in the previous screenshot, perform the following steps:

  1. Navigate to Sales & Marketing/Order Processing/Sales Invoices.

  2. Click on the New button found on the ribbon bar.

  3. A new blank invoice opens. Press the Enter key to get a Number.


    This is just a temporary number. You will get a definitive number for the invoice once you post it.

  4. On the Sell-to Customer No. field, start typing the code 20. As you type, a drop-down list shows all the results that match the No. typed so far.


    You can change the default field used as a filter. To do so, check the heading of the column you want to set as default. The little funnel icon will move to the new column. Now, click on the Set as default filter column option.

  5. A message will tell us that the customer has an overdue balance and will ask us for confirmation to proceed. Click on Yes.

  6. On the Lines tab, create lines by filling in the fields of the following table.




    Unit Price Excl. VAT





    Charge (Item)








    G/L Account




    Let's explain the different type of lines that can be used:

    • Item: This is used when you need to sell an inventory item. When the invoice is posted, it will create an item entry to reduce its stock.

    • Charge (Item): This is used to adjust the costs of items. In our example, the freight charges will count as sales amount for the items, and therefore it might adjust the benefit of this particular sale. Charges can be used either in the sales and purchase area, on the same document, or in a different document. You have charged your customer for the freight; your carrier will charge you. When you get your vendor's invoice you will need to use charges, to adjust the cost of the sale.

    • Resource: This can be employees, machinery, or other company resources.

    • G/L Account: Yes, you can also use G/L accounts in documents. In an ideal scenario you will try to avoid them for two reasons: you need accountant knowledge to select the correct account, and you cannot define prices and other commercial info.

    • Fixed Asset: This is used to buy or sell fixed assets.


    A blank type is used for comments. You can enter text in the Description field.

    Item Charges require one extra step to be performed before the invoice is ready to post:

  7. Select the freight charge line, and click on the Line icon and then choose the Item Charge Assignment option. Write 1 in the Qty. to Assign field and close the page.


    The Get Shipment Lines and Get Return Receipt Lines process are used to select lines from other documents to be charged.

  8. To get an overview of the invoice before it is posted, use the Statistics option found on the ribbon bar. You can also press F7 to access this option.

    On this page you can change the two fields shown in the previous screenshot

  9. Go back to the Invoice. Choose Post from the ribbon bar or press F9.

  10. The invoice is already posted. It has been moved from the Sales Invoices list to the Posted Sales Invoice list. You can access it writing Posted Documents/Posted Sales Invoices on the navigation bar.

  11. The posted invoice has created multiple entries on the different areas of the application. Let's see them:

    • General ledger entries: The system has translated the invoice to accounting language. We selected the customer, so it knew what account from group 23 to use. We sold an Item, so the system knew which income account to use, and so on. Dynamics NAV is capable to choose the right accounts, thanks to some setup tables called Posting Groups. They are covered in detail in Chapter 6, Financial Management Setup.


      For this book we used a demonstration company called CRONUS International Ltd. that uses the British chart of accounts. You can use the general chart of accounts of your country, or you can define a customized one.

    • VAT entries: These are created when invoices are posted. They will be used later on, to post the VAT Settlement and to report VAT to the authorities.

    • Customer ledger entries: These are used to keep track of all the transactions posted to one customer. Customer ledger entries are also used to manage receivables. The Remaining Amount field tells us how much money the customer owes us for this invoice. It will be zero when the invoice is completely paid.

    • Item ledger entries: Since we sold 50 units, we need to decrease the item stock. Item ledger entries help us keep track of the company stock. They also keep track of the Sales and Cost Amount of this particular entry.

    • Value entries: The Sales and Cost Amounts shown in each item ledger entry are the sum of their value entries. In future, the cost of this particular item entry might change if we post new item charges or the item gets revaluated. If any of this happens, new value entries will be created.


      Values entries will be used later on to know the changes in inventory in a period and post it in the General Ledger Entry.

    • Resource ledger entries: The resource called MARK worked 8 hours to assemble the item we sold. We keep track of resources, thanks to their ledger entries. We also know the cost and total price for each entry.

As you can see, one single invoice has generated eighteen different entries in different ledgers. A financer will mainly focus on general ledger and VAT entries, while the warehouse guy will focus on item ledger entries, and the resource manager will focus on resource entries. One single invoice impacts all areas of the company. So we have demonstrated what was told in the introduction: "An ERP system is meant to handle all the organization areas on a single software system. This way the output of an area can be used as input of another area."


Document workflows

In the previous section we have seen what a document is. In this section, we will see how many documents exist in Dynamics NAV, how they are related to each other, and which are the commonly used workflows to create them. We will see sales documents, but the exact same purchase documents exist in Dynamics NAV.

There are two kinds of documents in Dynamics NAV:

  • Open documents: These hold the information that we will use to start an action or a transaction. An order, for instance, is the beginning of the action of shipping items to our customers. Open documents can be modified.

  • Posted documents: These hold the result of a transaction that has been posted. They can be understood as historical documents and they cannot be modified. A shipment, for instance, is the result of shipping items to our customers.

The following diagram shows the available documents that exist in Dynamics NAV. There are other warehouse specific documents that could be used on the sales and purchase processes, but we have skipped them because they are out of the scope of this book.

Documents in white are open documents, while those in grey are posted documents.

Not all documents have to be used. Some can be skipped and some may appear multiple times. For example, you could not use quotes, orders, shipments, return orders, and return receipts, and thus only use invoices, posted invoices, credit memos, and posted cr.memos. You can also use orders, which may lead to multiple shipments (when the order is shipped partially) and then use a single invoice to group all shipments and end up having a single posted invoice. This scenario is shown in the following diagram:

Actually, in an invoice we can group multiple shipments, no matter if they are shipments from the same order or from different orders. There is still another possible workflow, not using invoices and generating the posted invoice from the order.

There are many other possible combinations, since all the workflows we have seen could start with a quote document, for instance. We have not seen different workflows for the sales return path, but the same workflows can be used.

Document approval

Dynamics NAV has a document approval functionality that can be applied over open documents to prevent users from posting them (and thus reaching the next document, a posted document) while they have not been approved.

Document approval can be set up in different ways so that not all documents have to go through an approval process. Only the documents that meet certain conditions will actually require someone to approve them. We can decide:

  • Which kind of open documents will require approval.

  • The hierarchy of approvers. The hierarchy is based on the maximum amount each approver can approve.

  • The conditions that should be met to require approval for a specific document. All possible conditions are based on document amounts.



In this chapter, we have learned that Dynamics NAV is an ERP system meant to handle all the organization areas on a single software system.

The sales and purchases processes can be used by anyone without the need of having accountancy knowledge, because the system is capable of translating all the transactions to accountant language on the fly.

Customers, Vendors, and Items are the master data of these areas. Its information is used in documents to post transactions. There are multiple options to define your pricing policy: from one single price for everyone to different prices and discounts per groups of customers, per volumes, or per period or currency. You can also define financial discounts per early payment.

In the next chapter, we will learn how to manage cash by showing how to handle receivables, payables, and bank accounts.

About the Authors

  • Cristina Nicolàs Lorente

    Cristina Nicolàs Lorente has been working with Dynamics NAV since 2005. She started in the ERP world as a developer, but soon evolved into a complete Dynamics NAV professional, doing all the tasks involved in Dynamics NAV implementation: consultancy, analysis, development, implementation, training, and support to end users.

    When Cristina started developing solutions for Dynamics NAV she had no idea about accounting or any kind of business workflows. They don't teach those topics for a technical university career. Soon, she discovered that it is important to know the set of tools used, but even more important to understand the meaning of whatever you develop. Without knowing accounting rules, practices, and legal requirements, it is impossible to develop useful accounting functionalities even if you are the best developer. Only when you fully understand a company's processes, will you be able to do the appropriate developments. Having that in mind, she has taken courses in accounting, warehouse management, and operations management. She is also willing to take courses on any other company-related topics.

    She thinks that the best way to learn is to teach what you are learning to someone else. She has actually learned almost everything she knows about Dynamics NAV by responding to user questions on Internet forums, by writing a blog about Dynamics NAV, and of course by writing the book you have in your hands. When you have to write about something, you have to experiment, try, investigate, and read. It is definitely the best way to learn. Cristina is also a coauthor of the book Implementing Microsoft Dynamics NAV 2013, which had really good comments coming from different Dynamics NAV experts.

    Browse publications by this author
  • Laura Nicolàs Lorente

    Laura Nicolàs Lorente started working with Dynamics NAV back in 2005, first in the support department, mostly solving functional issues and doubts. She soon jumped to full deployment: consulting, analysis, development, implementation, migration, training, and support.

    Right at the beginning, she realized that it was very important for a Dynamics NAV consultant to have a deep knowledge of business workflows. Technical skills are just not enough. So she started training herself in accounting, taxation, supply chain, logistics, and so on. She discovered a whole new world and found it very interesting.

    After having enough consultancy experience, she got to manage the first project on her own. And then, she realized that even tech and business knowledge is not enough; she also needed management skills. So, after reading different management books and trying different approaches on the projects she worked on, she decided to deepen her knowledge by taking a master's degree in project management. She is now transitioning to agile management and agile development for better project success. She continues her training in the three areas (tech, business workflows, and management) whenever she gets a chance to. The Web is a huge source of inspiration for her: groups, forums, blogs, books, and so on. She also contributes by sharing her knowledge and experience with the Spanish Dynamics NAV community. Laura is also a coauthor of the book Implementing Microsoft Dynamics NAV 2013, which had really good comments coming from different Dynamics NAV experts.

    Browse publications by this author

Latest Reviews

(1 reviews total)
Good product. It is what I was looking for.
Book Title
Access this book, plus 7,500 other titles for FREE
Start FREE trial