11 Wednesday Apr 2018
Posted in Cost accounting, Fixed Assets, Project
Tags
In this webcast, I show you how you can use MS-Flow for allocating depreciation costs from the fixed asset module to the projects that you operate in the project management and accounting module. Everything works out of the box without a system modification – something that was not possible in the past.
01 Thursday Mar 2018
Posted in Accounts Payable, Accounts Receivable, Fixed Assets
Tags
In this post I will show you how you can sell fixed assets in one company and automatically create and acquire a fixed asset in another company. With the help of MS-Flow I could solve a long-term mystery with out of the box functionalities.
17 Wednesday Aug 2016
Posted in Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger
The previous post dealt primarily with the question how the selection and posting of journals can be restricted. Within this post I would like to change the perspective and take a look at a function that allows a periodic posting of a number of journals that have been created.
The “post journals” functionality I refer to here can be found in the General Ledger module in the journal entries section. (In prior Dynamics AX versions it can be found in the periodic General Ledger module section).
As the information that has been provided e.g. on TechNet for the “post journals” functionality is a bit sparse and as several questions in regards to this function have been brought forward recently, I decided summarizing the different setup and processing options in this post.
Note: Please note that the following illustrations and explanations will only refer to posting General Ledger journals. The post journals function is, however, not limited to those kind of journals but can be applied to other journals as well. Please see the following summary.
In order to explain the different setup options of the post journals feature, I started setting up some daily General Ledger journals that included either no error (“OK”), some journal lines with errors (“Partly ok”) or only erroneous lines (“Error”). The next screenshot exemplifies the setup of some of those journals used.
Option 1: Select the journals, and post them
Once all demo journals have been prepared, I opened the post journals window and selected them through the identic button.
After all journals have been selected, the posting process was initiated by hitting OK button in the post journal form.
Result:
The result of this first posting test was that all journals except the ones that contained errors were posted.
Newly created journals that did not contain any error remained, however, unposted.
Option 2: Select the journals and post them by using a batch job
To get also those journals automatically posted that have been created later on, I deleted all unposted previously generated journals, setup some new ones and selected them as before in the post journals form.
This time I changed the posting process by making use of a batch process that runs every some minutes and that does the posting for me.
Result:
As before, all journals have been posted except the ones that contained errors.
My next step was setting up a new journal (No. 188) that did not contain any error.
Because of my posting setup I expected that the batch process will pick up the newly generated journal and post it. Yet, as nothing happened, I finally checked the batch job history window and noticed that the batch job stopped because it could not process the first two journals that contained erroneous lines. Please see the next screen-print.
Option 3: As option 2 & select the transfer errors checkbox
As processing newly created journals did not work with the previous approach, I repeated the earlier setup steps and created a number of new journals. This time I tried processing them by selecting the ‘transfer errors’ checkboxes (please see below).
Result:
As expected, all journals except the ones that contained errors were posted. After setting up a new journal that contained no error I expected that this time the newly created journal will be posted.
Yet, unfortunately nothing happened to the newly created journal as the batch job stopped as before after detecting errors.
Note: The difference between the 2nd and 3rd setup option is related to the journal that was partly ok. That is, this time all journal lines that did not include an error in the original (partly correct) journal No. 189 were posted and the journal lines that contained errors were transferred to a new journal No. 191 that contains only the erroneous lines.
Option 4: As option 3 but with the late selection and transfer errors checkbox activated
Since none of the prior setup options successfully posted the journals that I created subsequently, I changed the setup in the post journals form once again. This time – after selecting the journals that I want to post – the “late selection” and “transfer error” parameters were activated as shown in the next screen-print.
Result:
This time all erroneous journals/journal lines remained unposted as before but the journal that I created later on – in my case journal No. 196 – was finally picked up by the batch process and posted automatically as the following screen-prints prove.
Note: Despite the fact that the newly generated journal was successfully posted, the batch job still continued running (and ending) with errors because of the two journals that contained lines with errors.
Even though this issue in not directly related to the journal posting process itself, it can become quite cumbersome, as it might flood your mailbox with error messages / Emails if alerts and/or Email notifications have been setup that control the processing of batch jobs.
16 Saturday Jul 2016
C.6. Sale of goods
Within the last part of this series on the COS & NOE accounting method, the item that has been produced before will be sold for 1000 EUR / pcs through a standard customer sales order shown in the next screen-print.
The first sales order related voucher is created when the sales order packing slip is posted. In the example used, Dynamics AX created the following voucher:
As only Balance Sheet accounts are addressed, no influence on the company’s Income Statements can be identified and as a result, no difference between the COS and NOE method arises.
The next and final posting step in my example is related to the sales order invoice. The voucher created when posting the invoice is shown in the next screen-print.
For reasons of clarity and traceability, the vouchers created when posting the sales order packing slip and sales order invoice, have been summarized in the next illustration.
The following financial statements summarize the sales order related transactions resulting from the sales order invoice posting.
D. Summary
Within this series on the COS and NOE accounting method I demonstrated that Dynamics AX can be setup in a way to generate financial statements that follow both accounting methods in parallel. This also holds for situations where other inventory valuation principles, such as standard costs, moving average costs, etc. are used.
Irrespective of those valuation principles and differences thereof, the key to a successful parallel implementation of both principles is a “correct” setup of your chart of accounts and related account structures.
10 Sunday Jul 2016
C.5. Production of goods
Probably the most complex part when it comes to setting up the COS and NOE method in parallel is related to the production of goods. That is mainly because the production posting setup does not only require a setup of the inventory posting matrix but – depending on the parameter setup – also makes use of other accounts that are setup e.g. at the resource level, production category level and in the costing sheet.
Notes:
Irrespective of the specific ledger setup for production related postings, the basic production process in Dynamics AX follows a three step procedure that begins with the start of a production order, continues with reporting the production order as finished and finally ends with the closing or “costing” of the production order. Those basic production steps and the related postings executed are illustrated in the next diagram, which will be used as a guideline for the subsequent illustration of the production related postings for a production item.
The structure of the production item I referred to above can be identified in the next screen-print.
The cost price calculation screen shown above illustrates that the production item (FG2000) consists of two raw materials (RM300 and RM400) that have a cost price of 10 EUR / pcs each. For the production of this good one piece of the first raw material (RM300) and two pieces of the second raw material (RM400) are required. In addition, for the assembly of the product a worker has to work one hour on a machine that has a total cost price of 270 EUR / hour. Based on those data a total production cost price for the production item of 300 EUR / pcs arises.
C.5.1. Production step 1: Start
For reasons of simplicity, the production parameters used in this example have been setup in a way that the material consumption (BOM) and route consumption are immediately posted when the production is started. The next screen-print shows the vouchers that have been created through the posting of the BOM and route journals.
The effect that these vouchers have on the financial statements of the company can be identified in the next illustration.
From a Balance Sheet perspective, the production start related postings are reflected in changes that can be observed on the WIP accounts no. 13430 and 13440. For the raw material consumption another Balance Sheet account (no. 13150) has been used as the offset account and the offset account for the route consumption has been posted on an Income Statement account (no. 60110).
Given that the NOE accounting method typically uses stock variation accounts for each and every change recorded in the company’s stock level, the question arises how the raw material related postings that were executed with the start of the production order can be explained / justified?
I will try answering this question based on the following illustration that shows the recorded accounting transactions in the upper part and the missing “in between” stock variation accounts in pink color in the lower part.
What becomes obvious from this illustration is that the approach followed here is not fully correct in the sense that the pink transactions highlighted above are missing.
An important question at this point is whether those missing transactions result in a critically wrong illustration of a company’s financial position or not.
From the author’s perspective the “missing” pink transactions are not critically important as they do not distort the financial position of a company that follows the NOE accounting method. That is because the NOE Income Statement does on the one hand side summarize all stock variation transactions into a single line. On the other hand side, one has to remember that the pink highlighted lines add up to zero and do thus have no impact on the company’s financial position.
The second transaction I would like to discuss in more detail here is the route related voucher that credits an Income Statement account (no. 60110 “production wages clearing”) and thus affects the profit of the company.
From a NOE accounting perspective this account / transaction can be explained by stating that the clearing account used represents a part of the stock variation of the company. In other words, the increase in semi-finished products for the route consumption part on account no. 13440 is offset by the “stock variation” recorded on account no. 60110. For that reason, the production wage clearing account has been assigned to the stock variation section in the Income Statement that follows the NOE accounting method.
If you take a look at the Income Statement that follows the COS method, you can identify that the very same account no. 60110 has been included in the section that incorporates the production wages recorded before. Irrespective of the whether the name and the section where those accounts have been assigned to is correct, the question that arises how one can justify the assignment of the production wages clearing account there?
From the authors perspective this assignment can be justified by interpreting the transaction recorded on the production wages clearing account as a kind of allocation that shifts a part of the total production wages from the company’s Income Statement into its Balance Sheet.
Stated differently, the production salary / wages posting recorded before immediately reduces a company’s profit. The start of the production on the other hand side creates a tangible value for the company in form of a (semi-) finished product and thus increases its overall wealth. This wealth increase is reflected on account no. 60110 in the company’s Income Statement.
C.5.2. Production step 2: Report as Finished (RAF)
The next production step consists of reporting the production as finished. Executing this production step results in the following voucher that debits and credits a Balance Sheet account with the total production cost amount of the item.
As only Balance Sheet Accounts are used for recording the RAF transaction, no difference between the COS and NOE method arises.
C.5.3. Production step 3: End the production order
The last production step ends the production order and ensures that the realized production costs get posted. Dynamics AX realizes this by reversing and replacing all prior production postings that have been recorded based on planned cost values with postings that are based on realized ones, that is, actual cost values. In the example used, the following costing voucher results.
Note: The lines that have been selected in the prior screen-print reverse the prior postings that have been created during the first two production steps.
The outcome of the production postings generated can be identified in the financial statements illustrated next.
Interpretation of the production costing posting created
Lines highlighted in light green color
* The amount of 300 EUR recorded on ledger account 13470 represents the stock increase resulting from the production of the finished good.
* The negative amount of 30 EUR that Dynamics AX credits on ledger account no. 13160 represents the reduction in raw materials that have been used for producing the finished good.
Lines highlighted in yellow color
* The three ledger accounts no. 53420, 53410 and 53170 are Income Statement accounts that – from an overall perspective – offset each other. That is, the total amount posted on those accounts adds up to 0 EUR.
* A first reason why these accounts were setup this way is to get the production costs – of 270 EUR for the production worker and 30 EUR for the raw materials consumed – transferred into the cost accounting module for subsequent cost analysis.
* A second reason for using this specific production posting setup is related to the NOE method as the accounts highlighted in yellow color represent stock variation accounts. The next illustration exemplifies this in detail by showing that those accounts are used “in between” each and every stock transaction.
Lines highlighted in white resp. orange color
* The lines highlighted in white color in the first screen-print of this section – resp. the orange line in the illustration above – shows the production costing voucher which posts 270 EUR on ledger account 60120 that arose for the assembly of the production item.
* As explained further above, from a NOE perspective, this account represents a stock variation and is consequently included in the cost variation section of the company’s Income Statement following the NOE accounting method.
* For the COS method reference can also be made to the interpretations from production step 1. That is, the amount recorded on ledger account 60120 represents an amount that allocates costs from the company’s Income Statement into its Balance Sheet and offsets the value increase caused by the production of the finished good.
To be continued in part (5)
01 Friday Jul 2016
After analyzing purchase related transactions in the previous chapter we will now move on and take a look at the other business areas where differences between the COS and NOE accounting method can be identified.
C.2. Inventory adjustments
The next area where such differences can be recognized is related to adjustments of a company’s inventory. Whether or not the COS and NOE accounting method can also be applied in parallel for inventory related adjustment transactions will be investigated next based on the following sample transactions.
Note: Transfer orders within and between sites/warehouses and other item related transactions that do not generate ledger vouchers will not be analyzed in the following.
For reasons of brevity, no Dynamics AX screen-prints of the created inventory adjustment postings will be provided but rather a summarized overview of the ledger postings created when recording those transactions (please see the next illustration).
Note: The main accounts required to be setup for the inventory adjustment transactions recorded can be found in the inventory section of the inventory posting matrix shown in the next screenshot.
Once all four inventory adjustments are posted, the following result can be observed in the company’s financial statements:
In the prior illustration one can see that the Income Statement that follows the COS method incorporates the inventory profit and inventory loss accounts (no. 53150 & 53160) in the cost of sales section. Whether or not those accounts are better assigned to another Income Statement section – such as the other operating expense section – is not important for the general question whether or not the COS and NOE accounting method can be applied in parallel for inventory adjustment transactions.
What is important though is the question where to incorporate the inventory profit and inventory loss accounts according to the NOE method. Against the background of the explanations provided before, this question can be answered by stating that those accounts need to be incorporated into the stock variation section of the company’s Income Statement. That is because those inventory adjustments represent nothing else than “small” stock adjustment transactions that replace the “large” month-end stock variation transaction required for the NOE method.
C.3. Salary/wages & other operating expenses
Within this subchapter I will deal with the question how to record and disclose salary/wage & other operating expense related transactions in the financial statements that follow the COS and NOE accounting method.
The major difference to what has been shown previously is that the separation of the transactions according to their function of expense is now made through referencing the financial cost center dimension as exemplified in the next illustrations.
The financial statements resulting from the transactions recorded can be identified in the next screen-print.
An investigation of the Balance Sheet related transactions does not bring a specific notable outcome to light that deserves special attention. That is because the amounts shown on the other liabilities & accounts payable accounts (no. 22600 and 22500) increase due to the salary/wage & electricity expense transactions recorded.
What is notable though are the account balances shown in the Income Statements for the COS and NOE accounting method. In this respect it can be observed that the COS Income Statement shows the different amounts split up by functions (cost centers) whereas the NOE Income Statement shows those amounts on a summarized basis. Another disadvantage of the NOE method is thus that this method does not provide users with the same level of detailed information as the COS method.
C.4. Fixed asset acquisitions & depreciations
Recording and disclosing fixed asset related transactions does – in principle – not differ from the salary/wage & other operating expense transactions shown in the previous chapter. That is because also for fixed asset related transactions a separation of the different transactions through the use of a financial dimension is necessary in order to generate the Income Statement for the COS method.
Within the example used in this subchapter, several fixed assets have been setup and acquired first (please see the next screen-print) …
… before the related depreciation expense transactions were recorded.
The outcome of those transactions can be identified in the next Management Reporter report that shows the fixed asset acquisition and fixed asset accumulated depreciation accounts in the company’s Balance Sheet on the left-hand side.
In the middle part of the report one can identify the Income Statement that follows the COS method. From there it can be observed that the depreciation expense is split up by corporate functions by making use of the recorded financial (cost center) dimensions.
The Income Statement following the NOE method illustrated on the right-side does – on the other hand – summarize those transactions in a single line and does thus not allow an immediate analysis of the expenses recorded.
Intermediate result
In addition to the purchase related item transactions shown in the previous part, it can be summarized that also transactions related to inventory adjustments, salary/wages and other operating expeses as well as fixed asset related transactions can be posted in a way that allows the parallel generation of Income Statements that follow the COS and NOE method.
Please not that you can of course also use separate “function-related” ledger accounts – rather than financial dimensions – for separating the different corporate functions in the COS Income Statement report.
Yet, irrespective of what approach you chose for separating the different corporate functions (financial dimensions or separate ledger accounts), the most important thing that you have to take care of is that a consistent and integrated approach is followed in your company which ensures that the financial reports according to both accounting methods can be generated out of the box.
To be continued in part (4)
24 Friday Jun 2016
Posted in Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger, Inventory
Posting 01 January: Packing slip raw material 1
The packing slip transaction for the purchase of the first raw material results in the following voucher.
This voucher debits a product receipt account for the purchased material (account no. 13110) and credits the purchase accrual account (no. 22550). As both accounts are Balance Sheet accounts, no effect on the company’s Income Statement can be identified.
The following illustration summarizes the company’s Balance Sheet and its Income Statements according to the COS and NOE method and demonstrates that the packing slip transaction does not affect the company’s profit.
Outcome – after packing slip posting
Posting 02 January: Vendor invoice raw material 1
The next step in the purchase process is related to recording the vendor invoice. The invoice voucher created does first reverse the previous packing slip transactions. At the same time a stock increase (on account no. 13120) and an increase in vendor liabilities (on account no. 22500) is recorded.
Because of the automatic charge code that has been setup, an additional transaction equivalent to the item purchase amount is recorded on the raw material expense and stock variation accounts no. 53130 and 53140. The next two screen-prints summarize the voucher created and show its influence on the company’s financial statements according to the different accounting methods.
Outcome – after invoice posting
Note: As the raw material expense and stock variation account are both assigned to the cost of sales section of the company’s Income Statement that follows the COS method, no effect on the company’s profitability, KPI’s, etc. results.
Posting 03 January: Packing slip raw material 2
The voucher generated with the packing slip posting for the second raw materials purchase is identical to the one created for the first raw material. For that reason, everything that has been mentioned before for the first raw material purchase also applies here. The next screen-prints detail the resulting packing slip voucher and financial statements.
Outcome – after packing slip posting
Posting 04 January: Vendor invoice raw material 2
As also the invoice voucher for the second raw material debits and credits the same ledger accounts that have been used when the posting the vendor invoice for the first raw material, reference can be made to what has been mentioned above.
The only major difference between the first and second raw material purchase is reflected in the invoice voucher. That is, for the purchase of the second raw material the slightly higher purchase price of 12 EUR / pcs. results in a stock increase of 12000 EUR that is recorded on the respective ledger account no. 13120.
In line with this stock increase, an equivalent transaction on the raw material expense and stock variation accounts can be identified. For details, please see the postings on accounts no. 53130 and 53140 and the resulting financial statements shown next.
Outcome – after invoice posting
Posting 05 January: Packing slip vendor return raw material 1
The return of the first raw materials that did not pass our quality tests results in vouchers that are – except for the sign – identical to the one’s recorded before. For that reason, reference is made to the previous explanations.
Outcome – after packing slip posting
Posting 06 January: Vendor invoice vendor return raw material 1
What has been mentioned for the packing slip voucher generated also applies for the credit note “invoice” voucher. In this respect I would especially like to draw your attention on the parallel raw material and stock variation posting created for the vendor credit note shown in the following screen-print.
The overall result from all of the transactions recorded within this subsection can be identified in the next screen-print that summarizes the effects of the postings on the company’s financial statements according to the COS and NOE accounting method.
Outcome – after invoice posting
Note:
Dynamics AX uses the so-called running average cost price when issuing goods. With the recording of the vendor return transaction such an issuance occurs. As the running average cost price cannot directly be influenced by users and regularly differs from the price that our vendor credits for the item return, a temporary difference between the stock and stock variation accounts might result.
In the long-term this (temporary) variance will be offset through the transactions recorded when closing the company’s inventory. However, in the short-term an additional transaction on the “purchase expenditure, un-invoiced” resp. “purchase expenditure for product” accounts might occur.
The next screen-prints exemplify such a situation, where the amount credited by the vendor (10 EUR) differs from the running average cost price (11,83 EUR).
To ensure an always consistent and correct illustration of the company’s Income Statement according to the COS and NOE method it is thus recommendable to setup…
Please note that this setup is not obligatory but can make the analysis and interpretation of transactions recorded in Dynamics AX easier. The following screen-print shows the setup just described for the first two account sections mentioned.
Intermediate result
The following illustration summarizes all ledger postings created within this subsection.
Notes:
Based on the transaction summary shown in the previous illustration it can be concluded that the COS and NOE accounting methods can be applied in parallel in standard Dynamics AX. In this respect is has been shown that the shortcoming of the standard AP parameter “post to charge account in ledger” can be overcome by using an automatic charge code.
To be continued in part (3)
18 Saturday Jun 2016
Posted in Accounts Payable, Accounts Receivable, Fixed Assets, General Ledger, Inventory
International operating companies are often required to prepare financial statements that follow different accounting methods/regulations.
Especially local units of international business conglomerates that operate in a foreign country regularly have to prepare financial statement in one format for local accounting standard setters and in a different format for corporate headquarters.
In the European Union you will often face situations where companies have to prepare financial statements according to the so-called “Cost of Sales” (COS) Method for corporate headquarters and according to the “Nature of Expense Method” (NOE) for local accounting bodies / tax offices.
Within the following subsections I will illustrate how both methods – the COS and the NOE method – can be setup in parallel in Standard Dynamics AX.
Before digging into details, let’s have a look at the major differences between the COS and NOE accounting method.
A. Overview major differences between the COS and NOE accounting method
In the European Union (EU) different regulations are applicable when it comes to the use of COS and the NOE accounting method. As an example, the EU directive 2013/34 specifically describes both methods in detail by referring to the “Function of Expense” (COS) and “Nature of Expense” (NOE) method. Similar regulations can be found e.g. in Germany and Austria where legal regulations detail the differences and requirements of both methods. Irrespective of differences in the nomenclature, the major differences between the COS and NOE method can be recognized in the structure of a company’s Income Statement. The next screen-print compares those structures by showing the COS method on the left and the NOE method on the right.
Despite the summarized comparison of the different Income Statement formats, major differences can be identified in the inventory, human resource and fixed asset sections.
From a finance & controlling perspective, an important difference between the COS and NOE method is related to the data sources required for generating both financial statement formats. That is, while the NOE method does only require data from the accounting department, the COS method also requires cost / management accounting information in order to break down the costs by functions.
The next subsection details the sample data used for the illustrations shown in this post. This section is followed by a in depth specification of setups required in Dynamics AX and their effects on corporate financial statements.
B. Sample data
To illustrate you the differences between the COS and NOE method, a number of transactions have been recorded that are based on the following process flow:
The process flow that you can identify from above starts with the purchase of raw materials, which are later on partly returned to the vendor (due to quality problems). The next transactions are related to inventory adjustments in the warehouse. Thereafter, several transactions originating from the non-operating/administrative areas will be illustrated before the differences in the production process of finished goods will be explained in detail. The process flow finally ends with the investigation of the differences in regards to the sale of the produced goods.
C. Process illustrations
In the following, each of the different colored elements shown in the prior process flow diagram will be analyzed and explained in separate sub-chapters.
C.1. Purchase & return of materials
For purchase related material transactions, the major difference between the COS and NOE method is that the COS method does not affect a company’s Income Statement and thus its profit whereas the NOE method initially expenses the complete purchase of the materials. As a result, the company’s profit instantly decreases when the NOE method is applied.
If nothing else happens with the materials (that have been purchased) over the period, the profit reduction is subsequently offset by an adjustment (so-called “stock variation”) transaction. The next screen-print illustrates the differences between both methods just described in an accounting like format.
What can be identified from the COS method transactions shown on the left-hand side of the prior illustration is that the purchase of materials does only affect the company’s Balance Sheet (BS). The NOE method related transactions do on the other hand side – at least temporarily and depending on changes that occurred to stock levels over the month – also influence a company’s Income Statement (IS).
From what has been said so far, two major disadvantages of the NOE method can be identified.
Irrespective of the disadvantages mentioned and against the background of the accounting transactions illustrated in the prior screen-prints, the question arises how the COS and NOE method can be aligned with each other in a way to get both Income Statement formats out of Dynamics AX in parallel?
The following illustration tries answering this question by showing you that both accounting methods can be aligned with each other through an additional and parallel expense and stock variation transaction (highlighted in yellow color). Please see the lower part in the next illustration.
Given that our company creates two purchase orders – one for 2 TEUR and a second one for 3 TEUR – two additional “stock variation transactions” are recorded. The major difference to what has been explained before is thus the number of stock variations recorded. That is, rather than posting a single “large” stock variation transaction at the end of the month, several “small” stock variation transactions are recorded with each and every purchase.
A major advantage of this procedure is that there is no need for a (manual) analysis and recording of stock variations at the end of the month, which frees up some time for doing other things during the often busy month end closing period.
Note: The ledger accounts used for the additional material expense and stock variation postings debit and credit Income Statement accounts. As a result, no effect on a company’s profit arises. For the preparation of an Income Statement according to the COS method this result thus implies that assigning both accounts to the same Income Statement section will not influence a company’s profitability, KPI’s, etc.
After investigating how the COS and NOE method can be aligned with each other in a way to generate the transactions required for both accounting methods, the questions arises how to setup Dynamics AX in order to get those additional material expense and stock variation postings automatically recorded? From a “technical” Dynamics AX perspective, the following two options might help getting those additional postings recorded.
Option 1: Activate the “post to charge account in ledger” AP parameter
The first option makes use of the “post to charge account in ledger” parameter that can be found in the Accounts Payable parameters form. Activating this parameter results in an additional charge (expense) and stock variation posting on the ledger accounts specified in the respective sections of the inventory posting matrix illustrated below.
On first sight, this seems to be exactly what is needed for a parallel use of the COS and NOE method. Yet, a detailed investigation of this functionality shows that the additional posting triggered through the activation of this parameter only applies to ordinary purchase related transactions but not to vendor return transactions. Because of this shortcoming, this first setup option won’t be used in the following.
Option 2: Make use of automatic charge codes
Due to the limitations of the first option, an automatic charge code is used instead. The next screen-prints illustrates the setup of this charge code that debits an expense account and credits a stock variation account.
Once the charge code is setup, it is linked to an automatic charge in order to generate an additional posting equivalent to the one created for the materials purchased. This requires that an automatic charge percentage of 100% is applied, as illustrated in the next screen-print.
In order to enable you tracking what has been mentioned above, the following purchase order related transactions are recorded in a Dynamics AX demo environment:
The following illustration chronologically summarizes the transactions that will be illustrated and analyzed next.
To be continued in part (2)
16 Saturday Apr 2016
Posted in Fixed Assets
Within this and the following post I would like to show how one can setup budget control for fixed assets in AX2012 and AX7. Let’s start with the setup and configuration in AX2012 first by referring to the following example.
Setup
The first step in my setup process is specifying the main account that is used for posting fixed asset acquisitions in the fixed asset posting profile form. Please note that the main account setup here (account no. 180100) is a balance sheet account.
Because I am aware that the budget control configuration form does only allow setting up a single account structure, I setup my ledger with only one account structure that includes all of my balance sheet and income statement accounts.
My next step was selecting this account structure in the budget control configuration form and specifying that budget control shall be executed at the main account level only.
To let Dynamics AX check and ensure that I do not spent more money than the amount budgeted, I setup the following budget control rule, which defines that my main (balance sheet) accounts that start with “180” shall be subject to budget control.
Record budget amounts for the fixed assets
After setting up and activating budget control, I recorded fixed asset budgets for the different fixed assets that I setup for the years 2020 to 2024. For details, please see the next screen-print.
After transferring those budget values to the budgeting module, I double-checked the amounts transferred and updated the budget balances.
A first thing that I noticed in the budget register entry form was that the first column denominated “budget check results” did not include a green check mark for my transferred budget values.
As I wanted to compare this behavior with the one that can be identified for ordinary expense related budgets, I modified my budget control configuration and setup a second budget control rule for my travel expense accounts. Once that was done, I recorded a budget for one of those travel expense accounts and noticed that Dynamics AX automatically shows me a green check mark when entering the budget amount. Please see the next screen-print.
Post vendor invoice
Irrespective of the issue with the green check mark and after having done all the necessary setup, I finally tried recording and posting a vendor invoice. Please note that the invoice amount that I entered exceeds the budgeted amount. Details of my test are included in the next screen-print.
What you can identify from the screen-print above is that Dynamics AX allowed me posting the invoice for my fixed asset even though the invoice exceeds the budgeted amount by 25000 EUR.
This was not quite what I expected. For that reason, I changed the budget control configuration several times in order to execute the budget control at different levels and with different main account-financial dimension combinations. Yet, irrespective of the budget control configuration that I used, I was always able to post the vendor invoice even though the posted amount exceeded the budgeted one.
Solution: Code adjustment
After this disappointing result, I started having a look at the program code that is responsible for executing the budget control check and noticed that standard Dynamics AX runs the budget control check only for expense, profit&loss and total accounts. As balance sheet accounts – such as the one that I setup for my fixed asset acquisitions – are by default excluded from budget control, I slightly modified the code in the following two methods:
Second test run
Once the code adjustments were implemented, I setup a new fixed asset and entered a budget for it. The next screen-print shows you the process of entering the budget amount for the newly created fixed asset. The main difference that you can identify in the screen-print below compared to the earlier budget registration is the green check mark in the budget check column.
Please note that the previously recorded budgets for my „old“ fixed assets are not influenced by the code change, which induced me setting up a new fixed asset and fixed asset budget for the following tests.
With the new setup in place I tried once again recording a vendor invoice for the acquisition of my fixed asset. Interestingly and different from before, Dynamics AX did now prevent me from posting the invoice as the total invoice amount exceeded the budget amount. Please see the next screen-print.
After reducing my total invoice amount to one below the total budgeted amount I was finally able to get the invoice posted.
Summary
By doing some little code modifications you can let Dynamics AX check available budgets for balance sheet accounts. An important prerequisite for this budget control check is that the balance sheet accounts – for which you want to have the budget control enabled – are included in the account structure that is setup in the budget configuration form. In other words, if you want to have also balance sheet accounts checked for available budget funds, you might have to reconsider the setup of your account structures e.g. by including all accounts into a single account structure and by making use of advanced account structure rules.
Please do also note that additional code modifications are necessary in the budget control inquiry forms to get the balance sheet accounts included for subsequent comparisons.
Within the next post I will take a look at the same process and differences in the new Dynamics AX7. Till then.
13 Friday Nov 2015
Posted in Fixed Assets, Project
This blog post illustrates how you can use the Dynamics AX project module to track the costs of constructions in progress and transfer those costs later on to a fixed asset once the construction is finished.
Before you are able to track the costs of your construction in progress you have to ensure that an investment project group is setup that accumulates all costs on balance sheet accounts as illustrated in the next screen-print.
Once your investment project group is setup, you need to create an Investment project…
… that you use for recording all construction costs. In my case, I recorded hour, expense and item costs that add up to a total of 17300 EUR as shown in the next screenshot.
Once your construction project is finished and provided that all costs have been recorded on your project, you can transfer those costs to a fixed asset by using the estimate function.
The first step required in the estimate form is creating an estimate that accumulates all costs recorded. This can be done by selecting the “set cost to complete zero” cost to complete method.
After the estimate is created you can identify the total costs accumulated in the WIP tab of the estimate form. Example:
The next steps required are (a) specifying the fixed asset to which you want to transfer all costs and (b) posting the estimate.
Please note that posting the estimate does not create any ledger transaction and does not transfer any costs to the fixed asset selected. To do the actual transfer of the costs to the fixed asset, you need to eliminate the posted estimate by using the corresponding functionality.
After the elimination is done, you can identify the costs on the fixed asset selected before.
Note 1:
In the example used, the construction started and finished within a single month. If you are working on long-term construction projects and want to update your “construction in progress” fixed asset in the fixed asset module you need to:
Those steps need to be repeated every month as long as your project runs.
An alternative to reversing and repeating eliminations recorded before, you can separate your investment project into subprojects that are eliminated successively as the construction progresses.
Note 2:
If you are eliminating your construction projects on a regular basis, those costs are included in your fixed asset module and thus in your fixed asset statement.
If, on the other hand, you are not eliminating your project construction costs on a regular basis, all costs are accumulated in WIP (balance sheet) accounts only and are not included in the standard Dynamics AX fixed asset statement. In order to get your fixed asset statement right, you thus need to include the WIP accounts in your fixed asset statement which requires that you either use the Management Reporter for your fixed asset statement (see the previous post) or that implement a system adjustment.
Note 3:
If you are transferring all construction costs initially to a “in construction” fixed asset, you can move all costs from this “in construction” fixed asset to an ordinary fixed asset by using the standard AX fixed asset reclassification functionality. Example:
