Business Central OnPrem vs Azure vs SaaS

A few last months constantly I see misunderstanding what Business Central SaaS offering is. To be honest I thought it is all well known, but often it is not a case. Because of that, I’ve readjusted standard IaaS vs PaaS vs SaaS chart and made it applicable to Business Central. I think this chart speaks for itself, but if someone needs additional info, you can send a question and I’ll add details.

Just to be clear, on the top level where we have Company Data, I think on using BC as a system through UI or API’s. That means you are master of your data. You need to be sure how you enter and post your documents. But if we talk about configuration of system, mostly it will be done by your partner, but again this is your decision (as customer) to find trusted partner to work with.

As this chart cannot offer completely picture, I’ve added one more. First one was all about technology, but the next one is about licensing and what is included in system.

*) One thing maybe not 100% clear from this chart is infrastructure subscription if you are using BC on Azure (IaaS model). If you want to use Business Central deployed on Azure infrastructure (no SaaS), you can use a few different models. First you (as customer) can have your own infrastructure (1 VM, 2 VM’2, or VM + Azure SQL). The second, you (as customer) can use partner infrastructure and in this case you can dedicated hardware or services to you (as if you use your own) or you can use shared resources (more cost effective). In this case, middle tier can be used for more clients, as well as Azure SQL database can be added to Azure Elastic Database Pool and to get better performances and better cost. You can find ideas how to make it here (and this is important especially if BC SaaS is not available in your country). And one more thing… if you are using model BC on Azure, cost for OS and SQL Server is included in HW Subscription.

I hope it is now far clearer, but again if you need any additional detail, just send a question.

Report Layouts per Customer in NAV 2016

Microsoft Dynamics NAV 2016 is released about one month and we could see a lot of different new features. One of the small but amazing news is possibility to add different report layouts per each customer. This was one of very often requirement in implementation process and finally we can use it.

We can choose different reports per customer and after that, different report layouts. We can also add an e-mail as default per each document. It is possible for Quote, Order Confirmation, Invoice, Credit Memo and Customer Statement.


We just need to open a customer card and find Document Layouts on Navigate tab. Than choose report IDs and layouts. Eventually, you can add an e-mail. You can use RDLC or Word layouts, as well. Now, if you print one of these documents, you will see that these report document layouts are configured as default.

If you want to make new document report Word layout, I already wrote about it here.

Posting Groups #14 – Payment Discounts

One of features in Microsoft Dynamics NAV is using of payment discount. You can configure conditions of using this functionality on General Ledger Setup. With this configuration, I mean on Appln. Rounding Precision and Payment Tolerance and types of Payment Accounts from Customer Posting Groups. More about this configuration, you can find using Help for these fields.

We can use payment tolerances and discounts in few different situations. You can see how it generally works on following flowchart:


In my first example, I have configured only payment tolerance without discounts. When we post payment some less from original amount on invoice (e.g. 2.395 instead 2.400), we will get following G/L entries:


If our payment is greater than Invoice Amount reduced by discount, we will get following entries. System will post full payment as original invoice amount plus tolerance and discount, as well:


If payment is less than Invoice Amount reduced by discount, we will get following entries. System will post full payment as original invoice amount, discount and tolerance:


Posting Groups #13 – Finance Charge and Reminders

When we have overdue sales invoices, we usually can use Reminders and/or Finance Charge Memos. Both of these documents increases debits of our customers. We don’t post these documents, but we issue them. But, these issued documents also can make G/L entries.

On the first flowchart, you can see how system uses posting groups on Finance Charge Memos.


Results of this issued document in G/L entries are as following:


Now, on the second flowchart, you can see how system uses posting groups on Reminder. It uses very similar as on Finance Charge Memos, but fees on Finance Charge Memos lines are based only on Terms, while fees on Reminders can be based on Terms and Levels.


Results of Issued Reminders in G/L entries are as following:


Posting Groups #12 – Payment Posting

When we post payments, we usually have payments for customers and from vendors. In the same time, we should have bank account posting as balance accounts. Bank account is not necessary, but it is the best practice.

When we post payments from bank statement, we will get the same G/L entries, regardless we have payment in local currency or in some other. These are entries as following:


If we use non-local currency in payment process, after running Adjust Exchange Rate batch job, we will get the following G/L entries:


In previous example, you could see result if used currency exchange rate was increased. But, if exchange rate was decreased, the posting results in G/L entries would be as following:


All previous results were unrealized exchange rates gains or losses, but when we apply these payments, we will get realized exchange rates as on following table:


All postings, based on difference currency code, use posting groups and accounts as on following flow chart:


Microsoft Dynamics NAV in statistic – 2015

Last year, I wrote about number of Microsoft Dynamics NAV implementation on my blog. On last Convergence we got information that NAV has 102.000 customers with 8.000 customer adds in this year.

Now, we have new information for the last year. Microsoft Dynamics NAV has 8.000 customer adds again. This mean, Microsoft Dynamics NAV is the most popular ERP solution on the world with 110.000 customers all around the world. NAV is also Microsoft Dynamics solution with the best growth in year.

Microsoft Dynamics NAV increases its participation in Microsoft Dynamics family from 46% to the 48%.


People still trust and like NAV globally. The last version was really excellent and we can expect more and more in following version.