Management Reporter now supports your global business in 36 languages

Management Reporter now supports your global business in 36 languages

Your financial reporting in AX 2012 is now even better with Management Reporter supporting 36 languages and several new capabilities.

ManagementReporterglobalmap

Few of the highlights of the enhancements are,

1. Now directly integrated with the General Ledger module of AX 2012.

2. Flexible consolidation options.

3. Transaction drill down even better.

4. Build custom reports with more data visibility options.

5. Schedule the automatic report delivery to those who need it.

6. Even available on the Web.

Read the complete post here to explore more.

Microsoft Dynamics AX 2012 R2 is available now

Microsoft Dynamics AX 2012 R2 is available now

Hello Everyone,

Microsoft Dynamics AX 2012 R2 has been launched now.

More to come ! New exciting capabilities within Microsoft Dynamics AX 2012 in R2 release. Stay tuned.

Here are a few highlights of the capabilities in R2 release.

1. Manage you global operations through a single deployment there by trimming overall deployment costs and still manage operations in several countries with shared infrastructure.

2. More localization which includes , China, Japan, India, Brazil, Russia, Poland, Czech Republic, Hungary, Latvia, Lithuania and Estonia.

3. Data partitioning capabilities which allows effective sharing of data between business units.

4. More powerful business intelligence. New KPIs, integration with Power view and data visualization technology of MS SQL Server 2012.

5. Improved workforce management, talent and central resource skills repository management process.

6. Enhancements to compensation and benefits management which allows organizations in the US, to manage Payroll in-house, where data is completely under your control. (US Payroll included in R2)

7. Introduced enhancements for ALL – Manufacturing, Retail, Public Sector and Professional services firms.

Learn more by clicking the below links.

http://www.microsoft.com/en-us/dynamics/erp-ax-2012-r2.aspx

http://blogs.msdn.com/b/dax/archive/2012/10/23/a-sneak-peak-tour-4-business-benefits-of-microsoft-dynamics-ax-2012-r2.aspx

#Switch to Microsoft Dynamics AX 2012.

Thanks

Sandeep

Preparing Financial Statements with financial dimensions getting printed in different Columns in the report in Microsoft Dynamics AX 2012

Sometimes companies may want to generate their financial statements with one or more of their financial dimensions getting printed in different columns of the financial statement report for comparison and review purpose. For example, a company may want to generate the income statement with the data for each of its “Business Units” getting printed in separate columns in the report.

Take a look at the dummy screenshot of such a report below.

Sample Income Statement

Here are the quick guide lines how to achieve this in Microsoft Dynamics AX.

1. First of all, configure the financial statement by navigating to General Ledger > Setup > Financial Statement > Financial statement.

2. Define the financial statement column structure as shown in sample screen below.

Financial Statement Column Structure

3. Now assuming that your row definition for the financial statement is ready, let us go and generate the financial statement.

4. Navigate to General Ledger > Reports > Transactions > Financial Statement. Key in the values for financial statement, Row definition(If not already defaulted from financial statement) and click the Columns tab.

Generate Financial Statement

5. You will notice the 3 columns(Current) which we configured in the financial statement.

6. Select the first record and click Select button.

Select Business units/Financial dimensions during report generation

7. Click Add button and select the business unit financial dimension in the “Field” and provide the criteria value(For example BU-001)

Select the financial dimensions

8. Repeat steps 6 and 7 to complete this for business unit 2 and 3.

9. Click Ok button and we are done. This will print the financial statement as depicted in the sample screenshot above in this post.

Companies may also have different financial dimensions like Territory/Region, Product Line etc. They may also report based on these financial dimensions with having these printed in separate columns in the report.

Complex Reporting !!! Made Powerfully simple. Smile

Microsoft Dynamics AX 2012 - Powerfully Simple

Intercompany accounting setup and process in Microsoft dynamics AX 2012

Friends,

In this post, I will take you through a very simple functionality called  the intercompany accounting in dynamics AX 2012. This is a simple walk through of the setup required to be able to do intercompany transactions and also we will post and verify the ledger updates for an actual intercompany transaction in both the source and destination legal entities.

We will do this in the CONTOSO dataset. Let us say that the CEU is the source company and CEE in the destination legal entity and CEE ordered some stationary for promotional events, for which the finance controller of CEU received the invoice. Now the controller needs to post and intercompany entry to record the transaction in CEE.

Let us now look at the setup we need to do in CEU  and CEE for these to be able to intercompany transactions with each other.

In CEU company, navigate to GL > Setup > Posting > Intercompany accounting and see that its required IC setups.

image

Credit account: The ledger account that contain the intercompany credit transactions.

Debit account: The ledger account that contain the intercompany debit transactions.

Journal : It is the name of the journal to which the transactions are transferred.

Now, in the CEE company, navigate to GL > Setup > Posting > Intercompany accounting and see that its required IC setups.

image

We have now done/verified the necessary setups for the intercompany transactions. Let us now go and post and actual transaction and verify the impacts.

Say that the CEU and CEE ordered some stationaries for which CEU finance controller of CEU received the invoice. Now the controller needs to post and intercompany entry

For this do the following.

  1. In CEU go to GL >  General Journal and create a new intercompany journal.

image

2. Click lines and enter account type = ledger , Main account = 110180(Petty cash account) and credit amount of $1000.

image

3. Click General tab and select offset account company  = CEE, account type = Ledger and account = 6300

image

4. Click post and notice the info log. (One in CEE and another in CEU)

image

5. Let us now verify the voucher postings. In CEU, navigate to GL > Inquiries > Voucher transactions and fetch the required voucher. Please see the screen below and verify that the petty cash account is credited and the Inter unit receivable – CEE account is debited. ( This is the debit account which we did set in the inter company accounting setup form earlier).

image

6. Now go to entity CEE and notice the voucher. The Due to CEU account(3360 is the credit account which set in the intercompany accounting setup parameters of CEE entity.

image

7. You may also wish the see the IC journal which got created in the CEE company as shown below.

image

Simple !!!!!!! That’s it for today.

Thanks

Keep DAXING Smile

The “Pay when paid” functionality in Microsoft dynamics AX 2009 PSA

Friends,

I will explain the pay when paid functionality available in Microsoft dynamics AX 2009 PSA module in this post. As the name implies , payment to vendors is made only when payment is received from customers and this process is automated in PSA.

This functionality of PSA gains more attention in the AEC and advertising industry as huge amount of money is paid to sub contractors / vendors with very low contract margin. The implementation of the this functionality not only ensures a positive cash flow in the organization but also verifies that the customers/clients are also satisfied with the performance of the vendors.

In order to ensure that the pay when paid works as intended, make sure the below setups.

  • Ensure the PSA parameters are setup properly. This includes the flags for pay when paid section.
  • Ensure that the pay when paid check boxes are marked properly in vendor group and vendor level.
  • Ensure the flags for pay when paid are setup correctly in Project contract and project.
  • The flags at the PO header and line level will inherit from vendor master.
  • Check the PwP flag at the AP voucher record.

How the Pay when paid works – Information flow in pay when paid functionality:

The pay when paid works using the logic depicted below.

  1. PwP looks at the threshold amount or percentage which are setup in the PSA parameters. If the amount is set up , system subtracts this value from the total customer invoice amount and the calculated difference is compared to the customer payments till date.If the total payments till date is greater than the difference , the customer invoice is said to be “Fully” paid.
  2. If the threshold percentage is set up , then percent value is subtracted from 100 and the difference is multiplied with the total customer invoice. If customer payments till date exceeds this value, then customer invoice is assumed to be fully paid.
  3. The addition of two new fields, “Customer payment status” and “Customer invoice number” in vendor transactions form forms a relationship between the Vendor invoice and the Customer payment.
  4. When a new AP voucher is initiated for the vendor payment/invoice, the value for the customer payment status will be Blank and customer invoice number will be null in the related vendor transaction record.
  5. Once the customer/client invoice is processed, the invoice number for this  will be updated for the related vendor transaction.
  6. Once a full payment is received from customer , the customer transaction will be updated as settled and system will cause the “Customer payment status” field to be set to Paid and if a partial payment is received , it is updated to Partial.
  7. When the vendor payment is initiated by using payment proposal option , then only those vendor transactions are filtered where customer payment status is Paid.
  8. When the vendor payment is initiated through manual settlement (Functions > Settlement option), then only those vendor open transaction which pass the PwP criteria are listed to be chosen for payment.

Let us understand the example below to get a better idea on the pay when paid functionality of PSA.

Let’s say your company sells speakers and you enter into an agreement with your customer to provide 200 speakers for them . As you dont have the manufacturing facility for the speakers, you engage a vendor/sub contractor to manufacture those for you. Let us assume that the price that the customer agreed on for each speaker is $100.

Your customer also makes an agreement like they will approve the quality of the speakers before the they pay you . Therefore, your organization can have an option of not paying the third-party vendor until you have been paid by the customer.

Now you can set up the project with a PWP threshold  percentage of 100%. This means that you will withhold all payments to the vendor until you receive full payment for the customer invoice.

When vendor sends the speakers , say they charge $60 for each speaker, so along with the goods they will send an invoice of amount 200*60 = $12000. But you will not pay now them as you have the PWP setup.

When you send the speakers to the customer, you will send the customer an invoice of 200*100 = $20000. The customer will inspect all the speakers and then if approves the quality of the product , they will pay the amount for your invoice.

After you receive the full payment from the customer, you will pay $12,000 to the vendor for the full amount of their vendor invoice. This will ensure satisfactory service from the third party vendors.

Hope this post will help understanding the base concept of PwP and  troubleshooting issues if any. Will be glad to answer more on this.

Thanks, Keep DAXING 🙂

Controller profitability analysis Role center/KPI in Dynamics AX 2009 – Formulas for calculation of the Actaul and Goal values

Hi There,

In this post, i am going to explain the business logic and the setup behind the controller profitability role center/KPI in Microsoft Dynamics AX 2009.

The Controller Profitability Analysis KPI report/role center displays management’s effectiveness in generating profits. The values displayed under the Actual column on the role center are always for the current month and the values for the GOAL, Trend and Status are calculated based on conditions in business logic.  These setups are done in the General ledger cubes.

The screenshot below depicts how a standard controller profitability KPI looks like.

Now, let us discuss these indicators and columns one by one.

1. Revenue:

Actual: It shows the sum of balances for all revenue accounts.

Calculation: Sales (33) + Other Income (48) +Sales credits (34) + Gain/Loss on asset disposal (51). (33, 34, 48 and 51 above refers to the Ledger account categories which are setup at GL > Setup > Ledger Accnt. Categories.)

Goal: The Goal is always set as a % of the Actual value. For e.g. if the total actual revenue is 100% in a month, then Goal can be set to 105%. The expression for the Goal value is set in the KPI for the role center. Once the user decided the Goal for a month, it can be setup in the KPI expression back in the cube which is accessible by opening visual studio.

Default value for the Goal in KPI = Actual Value * 1.05(If the Goal % assumed is 105%).

Trend: Upwards arrow if the actual revenue in current period (month) is greater than or equal to equal to the actual revenue in the previous period (month) else downwards.

Status: Green (If Actual > Goal), Yellow (If Actual > 90% of Goal) and Red (Otherwise).

2. Expenses:

Actual: It shows the sum of balances for all expense accounts.

Calculation: Cost of goods sold (35) +Selling expense (ref id = 36) + Admin exp (37) + Manu exp (38) +Travel and enter exp (39) + Project expenses (40) + Salaries exp (41) + Other Emp exp (42) + Interest exp (43) + Tax exp () + Depr exp (45) + Income tax exp (46) +Other expenses (= 47) + Amortization of intangible assets (ref id = 52) + Gain/loss on asset disposal (ref id = 51) .

The numbers in brackets above refers to the ledger account categories .

Goal: Default value for the Goal = Actual Value * 1.20

Trend: Upwards arrow if the actual expenses in current period (month) are less the actual expenses in the previous period (month) else downwards.

Status: Green (If Actual <= Goal), Yellow (If Actual <= 90% of Goal) and Red (Otherwise).

3. Cost of Goods sold :

Actual: It shows the total cost of goods sold.

Calculation: The value from the Ledger account category 35 which represents COGS.

Goal: Value for the goal of the COGS is set to 99% of the Actual COGS in previous period (Previous Month).

Trend: Upwards arrow if the actual COGS in current period (month) are less the actual expenses in the previous period (month) else downwards.

Status: Green (If Actual <= Goal), Yellow (If Actual <= 90% of Goal) and Red (Otherwise).

4. Gross profit :

Actual: It shows the value of the gross profit.

Calculation: It is the value obtained by Sales (33) – Sales credits (34) – Cost of goods sold (35).(33,34 and 35 are the ledger account categories.)

Goal: Value for the goal of the gross profit is set to 105% of the Actual Gross profit in previous period (Month).

Trend: Upwards arrow if the actual gross profit in current period (month) are greater than or equal to the actual expenses in the previous period (month) else downwards.

Status: Green (If Actual >= Goal), Yellow (If Actual >= 90% of Goal) and Red (Otherwise).

5. Gross profit margin:

Actual: It is the (Net Sales (33-34) – Cost of goods sold (35)) / Net sales (33-34). (Net Sales = Sales – Sales credits)(33, 34 and 35 refers to the ledger account categories.)

Goal:  Value for the goal of the gross profit margin is set to 105% of the Actual Gross profit margin in previous period (Month).

Trend: Upwards arrow if the actual gross profit margin in current period (month) are greater than or equal to the actual gross profit margin in the previous period (month) else downwards.

Status: Green (If Actual >= Goal), Yellow (If Actual >= 90% of Goal) and Red (Otherwise).

6. Net Income :

Actual: It is the (Revenue – Cost of goods sold – sales credits – Expenses).

Goal: Value for the goal of the net income is set to 105% of the Actual Gross profit in previous period (Month).

Trend: Upwards arrow if the actual net income in current period (month) are greater than or equal to the actual net income in the previous period (month) else downwards.

Status: Green (If Actual >= Goal), Yellow (If Actual >= 90% of Goal) and Red (Otherwise).

Thanks , Keep DAXING. 🙂

List pages and their benefits in Dynamics AX 2009

Hello everyone,In this post of mine, I will summarize a basic introduction to Microsoft Dynamics AX 2009 list pages and their benefits for the users on their daily business operations.

Introduction:

Dynamics AX list page is a navigation page that displays a list of related data records. They represent a primary means of displaying data, performing actions on specified records, and opening their other related forms. There are two types of list pages supported by Dynamics AX 2009 which are described as below.

Primary list page : Displays all the records for a specific document type(for e.g. Customers/Vendors). These may also have a filter option in them which can be used to display more meaningful data.

Secondary List page : Displays a subset of records from an existing primary list page. It appends filters to the list page  that restrict the records getting displayed.(For e.g. Display a list of vendors on Hold). The secondary list pages comes very helpful for users in their daily business needs.

Below are descriptions for few of the list pages under the Accounts Payable and Accounts Receivable ares fo AX 2009 which the users will find extremely useful in daily business operations.

Accounts Payable :

Below image is an indication of all the out of box list pages available under Accounts payable area for a user with permissions of Admin group. However Dynamics AX security framework restricts the list pages to be out of box when the user belongs to limited user groups. Now when i say out of box , it means the list pages which are defaulted on the area page irrespective of user permissions.

Each of these list pages are useful for different user profiles. For example , the Controller or the Accounts payable clerk can open the Vendor Invoices Due today(Secondary list page) to view all the invoices of vendors which are due on the current date and can process payments or take suitable actions for them right here from the list page.

Another example of these is the Purchase Orders not Sent secondary list page. The Purchasing manager of the organization can take a look at all the POs that are not sent yet and can take necessary actions on them in the list page itself.

Similarly users can get to know the  other information such as the vendors past due, sent RFQs , Open RFQs, RFQ replies, delayed purchases, delayed receipts pending PO invoices etc and can take suitable actions for them.

Accounts Receivable:

Below image is an indication of all the out of box list pages available under Accounts receivable area for a user with permissions of Admin group. However Dynamics AX security framework restricts the list pages to be out of box when the user belongs to limited user groups.

List pages under Accounts Receivable – AX 2009

Each of these list pages are useful for different user profiles in the AR team. For example , the Controller or the Accounts receivable clerk can open the customer Invoices Due today(Secondary list page) to view all the invoices of customers which are due on the current date and can process payments or take suitable actions for them right here from the list page.

Another example of these is the Shipped but not invoiced Sales orders secondary list page. The Accounts receivable clerk of the organization can take a look at all the SOs that are not invoiced yet but are already shipped and can take necessary actions on them in the list page itself.

similarly users can get to know the  other information such as the customers past due, customers on hold ,sent and open sales quotations, delayed shipments, open return orders etc and can take suitable actions for them.

similarly AX 2009 has other list pages under almost all the modules of it which the users in various departments of the organization can find helpful in their daily operations.

This post holds a very basic information which most of us already know. I just tried putting them together as i got chance to work on them on a great deal in one of my assignments.

Thanks ,Keep DAXING. 🙂