Blogs: All posts
Multiple subsidiaries or divisions tend to conduct many transactions between each other. At some point, the parent company performs a consolidation of all general ledgers and faces the need to eliminate the intercompany flows in order to avoid inflation of the receivables and payables accounts. This is the point at which it may turn out that tracking intercompany document mismatches down is way too time-consuming.
Quite often performance is the key element that makes customers either very happy with a solution or very unhappy. We, at Xpand, have seen millions of lines of code and I must admit that NAV developers too seldom think about the speed of execution of what they write. Even though it is a rather compelling topic, we are not going to explore it within this article. Instead, let us concentrate on how to rewrite your code using queries and increase the speed of a solution a thousand fold!
Like we are all waiting for the end of a year when the Christmas and New Year spirit is present wherever you go, so is the accounting world anticipating their winter season pastime. In many companies, the financial year matches the calendar year, which makes a year end not only a time of jingle bells and mistletoes but a time of hard work, especially for companies that go through annual consolidation process.
At the end of a reporting period, an accountant of a company must perform the income statement closure procedure. With respect to this need, Microsoft Dynamics NAV provides “two-click” functionality that makes this process quick, accurate and easy. However, do we understand why this procedure is required and what exactly is behind it? Let us examine the logic behind this process.