1 17000077826 2016-12-08T15:44:53-07:00 17000122225 false Financials - General Ledger 3 2016-12-13T10:39:18-07:00 1 1 2016-12-02T11:48:23-07:00 0 2 Issue The user is trying to financially void a cheque, but receives the following error: Statement Status must be Open in Cheque Ledger Entry Entry No.='123456'. But the cheque is in open status, and has never been cleared through the bank reconciliation. Solution When someone starts a bank reconciliation, and does a Suggest Lines, the system cannot void that cheque while it appears in the open bank reconciliation. Two options: You can ask the user who is working on the bank rec to delete all their work so you can void that cheque. This is sometimes necessary, for example, if you need to immediately reissue the cheque, or if the bank rec user has just started and it's okay to delete their work. The other option is to wait until after the bank rec user has reconciled the bank account. <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> <table border="1" cellpadding="0" cellspacing="0" id="table21773" style="border-collapse:collapse; border:1px solid #afafaf;width:100%;"><tbody> <tr> <td><strong>Issue</strong></td> <td class="current">The user is trying to financially void a cheque, but receives the following error:<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"><br>Statement Status must be Open in Cheque Ledger Entry Entry No.='123456'.<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"><br>But the cheque is in open status, and has never been cleared through the bank reconciliation.<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"> </td> </tr> <tr> <td><strong>Solution</strong></td> <td>When someone starts a bank reconciliation, and does a Suggest Lines, the system cannot void that cheque while it appears in the open bank reconciliation.<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;">Two options:<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"><br>You can ask the user who is working on the bank rec to delete all their work so you can void that cheque. This is sometimes necessary, for example, if you need to immediately reissue the cheque, or if the bank rec user has just started and it's okay to delete their work.<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial; font-size: small;">The other option is to wait until after the bank rec user has reconciled the bank account.<br> </td> </tr> </tbody></table> </div> 17000122225 348 17000036686 2016-12-12T14:50:26-07:00 17002649915 1 Statement Status must be Open in Cheque Ledger Entry Statement Status must be Open in Cheque Ledger Entry Entry No.='123456' Microsoft,Dynamics,NAV,ODT,Edsuite,Financials,Cash,Management,Cash-management,Statement,Status,Open,Cheque,Check,Ledger,Entry,Bank 2 0 2 Statement Status must be Open in Cheque Ledger Entry Entry No.= 2016-12-13T10:12:29-07:00 17002649915 1 2016-12-02T14:37:06-07:00 0 0 Issue GST Rate Change Solution Go to Financial Management > Setup > Sales Tax > Details School Divisions have several Tax Jurisdiction Codes to manage the different ways they handle GST. In the Details window, insert a new line for each code, and set this new Tax Detail up the same as the other codes, except change the rates and the Effective Date to July 1, 2006.  The system will automatically know when to use the appropriate tax rate based on the effective date.  Remember to update all of your GST related tax codes! See attachment for further explanation and for handling credit memos. <div dir="ltr"><table border="1" cellpadding="0" cellspacing="0" id="table60009" style="border-collapse: collapse; border: 1px solid rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td>GST Rate Change<br> </td> </tr> <tr> <td><strong>Solution</strong></td> <td>Go to Financial Management &gt; Setup &gt; Sales Tax &gt; Details<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">School Divisions have several Tax Jurisdiction Codes to manage the different ways they handle GST.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">In the Details window, insert a new line for each code, and set this new Tax Detail up the same as the other codes, except change the rates and the Effective Date to July 1, 2006.  The system will automatically know when to use the appropriate tax rate based on the effective date.  <strong style="box-sizing: border-box;">Remember to update all of your GST related tax codes!</strong><br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><strong style="box-sizing: border-box;">See attachment for further explanation and for handling credit memos.</strong><br> </td> </tr> </tbody></table></div> 17000122225 98 17000036709 2016-12-12T14:52:21-07:00 17002649915 1 GST Rate Change GST Rate Change Microsoft,Dynamics,NAV,ODT,Edsuite,Financials,Payables,setup,GST,rate,change 2 0 0 GST Rate Change 2006 2016-12-13T10:15:07-07:00 17002649915 1 2016-12-07T10:33:12-07:00 0 0 Issue History: Microsoft Dynamics Incident Number: 8870672 Incident Type: Technical Support Subject: Error when attempting to Export to Excel Product Line: Microsoft Dynamics NAV Topic:  General Ledger Version: 4.0 Build/Detailed Version: SP3 Database: Microsoft SQL2000 Server OS: Windows Server 2003 When the client is using the Export to Excel functionality in the General Ledger, Analysis by Dimension they are getting the following error: Error message is This message is for C/Al Programmers: The Automation variable has not been instantiated. You can instantiate it by either creating or assigning it. Solution The Column/Row selection for the dimension was entered in lower case.  This causes an error because the dimension code is a code field and is upper case.  Ensure that when manually entering the dimension code for the row or coloumn layout prior to export that it is entered in uppercase. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><span id="history" style="box-sizing: border-box; font-weight: bold;">History:</span></p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Microsoft Dynamics Incident Number: 8870672<br style="box-sizing: border-box;">Incident Type: Technical Support<br style="box-sizing: border-box;">Subject: Error when attempting to Export to Excel<br style="box-sizing: border-box;">Product Line: Microsoft Dynamics NAV<br style="box-sizing: border-box;">Topic:  General Ledger<br style="box-sizing: border-box;">Version: 4.0<br style="box-sizing: border-box;">Build/Detailed Version: SP3<br style="box-sizing: border-box;">Database: Microsoft SQL2000<br style="box-sizing: border-box;">Server OS: Windows Server 2003<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">When the client is using the Export to Excel functionality in the General Ledger, Analysis by Dimension they are getting the following error:<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Error message is<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">This message is for C/Al Programmers:<br style="box-sizing: border-box;">The Automation variable has not been instantiated.<br style="box-sizing: border-box;">You can instantiate it by either creating or assigning it.</p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span class="current" style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">The Column/Row selection for the dimension was entered in lower case.  This causes an error because the dimension code is a code field and is upper case.  Ensure that when manually entering the dimension code for the row or coloumn layout prior to export that it is entered in uppercase.</span><br></p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 524 17000037279 2016-12-12T14:50:07-07:00 17002649915 1 C/AL Programmers Error message C/AL Programmers Error message when exporting the Analysis by Dimensions to Excel Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,account-schedules,CAL,programmer,error,export,analysis,dimension,excel 2 0 0 C/AL Programmers Error message when exporting the Analysis by Dimensions to Excel 2016-12-13T10:12:08-07:00 17002649915 1 2016-12-07T10:41:06-07:00 0 0 Issue An historical cheque needs to be voided. Solution Go to Financial Management > Cash Management > Bank Accounts.  Select the bank the cheque was written against, then click the Bank Acc Button > Check Ledger Entries. Browse and select the Cheque Ledger Entry that is to be voided.  Confirm the Entry Status is Posted and click the Check Button > Void Cheque. Update the Void Date to be the current Date and select the void type "Void Cheque Only".  This is only done for historic cheques transferred.  Normally you would use the Reverse Entry to re-open the invoice for payment, but for historical transactions there is no invoice in Navision to re-open. This process voids the Cheque.  Now the Bank transaction and the Vendor transaction must be entered. Go to Financial Management > Cash Management > Payment Journals. The Posting Date for this payment journal should be the same as the Void Check that was just processed; and the Document Date should be the Date of the original payment. Document Type should be "blank". The Document No should reference the original Cheque No and contain the word "VOID," so it will be easily discernible to other users that this was for a voided check. The External Document No should reference the original Invoice No. The first line should be a Debit to the Bank Account. The subsequent lines would Credit the Vendor to whom the payment was originally made. Balance Account No. should be left blank. Essentially, this is done like a GJ Entry via the payment journal.  It leaves a credit on the vendor's account, with each invoice outstanding and ready to pay.  If the invoices are to be removed, you must also enter a credit memo for this vendor to apply to these void documents.  Code the credit memo to the same invoice detail as was originally entered in the previous accounting system.  These invoices and payments would be processed in Navision in the new fiscal year only. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><span style="font-family: Arial;">An historical cheque needs to be voided.</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current"> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Go to Financial Management &gt; Cash Management &gt; Bank Accounts.  Select the bank the cheque was written against, then click the Bank Acc Button &gt; Check Ledger Entries.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Browse and select the Cheque Ledger Entry that is to be voided.  Confirm the Entry Status is Posted and click the Check Button &gt; Void Cheque.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Update the Void Date to be the current Date and select the void type "Void Cheque Only".  This is only done for historic cheques transferred.  Normally you would use the Reverse Entry to re-open the invoice for payment, but for historical transactions there is no invoice in Navision to re-open.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">This process voids the Cheque.  Now the Bank transaction and the Vendor transaction must be entered.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Go to Financial Management &gt; Cash Management &gt; Payment Journals.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">The Posting Date for this payment journal should be the same as the Void Check that was just processed; and the Document Date should be the Date of the original payment.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Document Type should be "blank".</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">The Document No should reference the original Cheque No and contain the word "VOID," so it will be easily discernible to other users that this was for a voided check.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">The External Document No should reference the original Invoice No.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">The first line should be a Debit to the Bank Account.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">The subsequent lines would Credit the Vendor to whom the payment was originally made.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Balance Account No. should be left blank.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Essentially, this is done like a GJ Entry via the payment journal.  It leaves a credit on the vendor's account, with each invoice outstanding and ready to pay.  If the invoices are to be removed, you must also enter a credit memo for this vendor to apply to these void documents.  Code the credit memo to the same invoice detail as was originally entered in the previous accounting system.  These invoices and payments would be processed in Navision in the new fiscal year only.</p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 108 17000037281 2016-12-12T14:50:17-07:00 17002649915 1 Voiding a Historical Cheque Voiding a Historical Cheque Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,bank-account,void,voiding,cheque,check,historical 2 0 0 Voiding a Historical Cheque 2016-12-13T10:12:29-07:00 17002649915 1 2016-12-07T10:43:43-07:00 0 0 Issue Multicurrency Bank Reconciliation Solution All bank rec users who perform reconciliations on banks held in foreign currency must enter an exchange rate for the adjustment period, preferably with the same date for the period's statement date. Then an adjust exchange rate must be performed for all transactions, posted on the statement/period end date. Once the adjust exchange rate program has finished, the bank rec worksheet should be started and a suggest lines on the bank reconciliation performed. If the bank rec is started prior to the adjustment entries posted via a journal or the exchange rate adjustment periodic utility is ran, the GL amount must be recalculated on the bank reconciliation worksheet card. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">Multicurrency Bank Reconciliation</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p style="box-sizing: border-box; line-height: 14px;"><span rel="tempredactor">All bank rec users who perform reconciliations on banks held in foreign currency must enter an exchange rate for the adjustment period, preferably with the same date for the period's statement date. Then an adjust exchange rate must be performed for all transactions, posted on the statement/period end date.</span><br></p> <br><br><span rel="tempredactor"><br></span><br><p class="current"><span rel="tempredactor">Once the adjust exchange rate program has finished, the bank rec worksheet should be started and a suggest lines on the bank reconciliation performed.</span><br></p> <span class="current" rel="tempredactor"><br></span><br><span class="current" rel="tempredactor" style='font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px;'>If the bank rec is started prior to the adjustment entries posted via a journal or the exchange rate adjustment periodic utility is ran, the GL amount must be recalculated on the bank reconciliation worksheet card.</span><br><p style="box-sizing: border-box; line-height: 14px;"><br></p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 217 17000037282 2016-12-12T14:50:33-07:00 17002649915 1 Multicurrency Bank Reconciliation Multicurrency Bank Reconciliation Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,reconciliation,multicurrency,bank 2 0 0 Multicurrency Bank Reconciliation 2016-12-13T10:12:53-07:00 17002649915 1 2016-12-07T10:47:37-07:00 0 0 Issue What are the requirements for using Navision Financials Consolidation functionality when dealing with foreign currency Company Consolidations? Note - How can I make sure that these Consolidations are done in accordance with FASB 52? Solution This Help Document is provided to give assistance for utilizing the Navision Financials Additional Reporting Currency functionality and processing Consolidations in Navision Financials Version 2.01.A and later. 1. Navision Financials Versions beginning with Version 2.01.A and all Navision Attain Versions provide functionality to use the additional foreign currency reporting functionality already in the the General Ledger Functional Area of the application. In using these options along with properly monitoring the currency Table in the Subsidiary Company, a Customer should be able to fully comply with FASB 52 requirements. The G/L Account Card has a 'Consolidation Currency Valuation Method' field that provides the flexibility to deal with the different currency requirements under FASB 52. This field has 4 options: Automatic, Current Rate, Historical Rate, and Manual Rate. The following is a brief explanation of each option. With the exception of consolidating using the Import Consolidation as noted in 4. below, these settings must only be dealt with in the Subsidiary Company's (ies') Chart of Accounts. Automatic: The Automatic option is provided for compatibility with versions of Navision Financials previous to 2.01.A. The system will automatically use conversion for Balance Sheet and Income Statement Accounts based on the Current Rate and Average Rate. This is the default configuration. On the Periodic Activities | Consolidation | Business Units screen, there is the Exchange Rate option button. This option button allows you to set up the Income Statement, Balance Sheet and Last Balance Sheet Exchange Rates. Current Rate: Conversion will force using the Current Rate for the Account. The Current Rate is utilized for all Assets and all Liabilities under the Current Method of Accounting for foreign currency transactions. The Temporal Method allows the utilization of the Historical Exchange Rate for Inventory. In addition, all Non-current assets and Equity Accounts, including Dividends, will utilize Historical Rates using the Temporal Method. Therefore, depending on the implemented method for handling foreign currency transactions under FASB 52 that is being utilized, you will use the Current Rate as discussed above. On the Periodic Activities | Consolidation | Business Units screen, there is the Exchange Rate option button. The Balance Sheet and Last Balance Sheet selections will allow you to set up the Current Rate for the current and the previous Consolidation periods. It is important for these to be set up properly so that the previously consolidated balances will be converted properly to the current Exchange Rate. Historical Rate: With the availability of the Additional Reporting Currency in the Navision G/L, all G/L transactions will be converted to this currency. With this functionality, an Exchange Rate that is in existence at the time of the transaction will be used for the translation calculation. Because of this, entries can be made and tracked using the currency at the Date of the original posting of the entry. Dividends, original Equity Investments, Inventory, and Fixed Asset Purchases would apply this Historical Rate for posting. The key factor in utilizing the Historical Rate Method is that the Foreign Subsidiary must have the Additional Reporting Currency under General Ledger | Setup | General Ledger Setup on the Reporting tab set to the Consolidation Company's currency. This allows all transactions entered through the system to be entered with a converted amount to the Consolidation Company's currency. Rather than converting the amount using a stated average Exchange Rate for these transactions, no conversion is required because the actual Historical Transaction Exchange Rate is used. FASB 52 allows this detailed conversion rather than using the average Rate. Manual Rate: This option will use the average Exchange Rate entered on the Business Unit Consolidation for all transactions entered during the Consolidation period. This average Rate is the one entered in the Income Statement selection under the Exchange Rate button on the Periodic Activities | Consolidation | Business Units screen. 2. Set-up on the G/L Account Card. Set up requirements on the Account Card includes setting up the Consolidated Debit and Credit fields on the Consolidation tab of the G/L Account Card in each Subsidiary Company. These Accounts must match the Consolidated Parent Company Chart of Accounts. 3. Set-up requirements also require Setup | General | Departments and Projects be set up with a Consolidation Department and Project Code in Navision Financials Version 2.01 through 2.60 if the Consolidation is going to include Department and Project detail. In Navision Attain, select Setup | Dimensions | Dimensions, select the Dimension button and select Dimension Values. In the Dimension Values Table, the Consolidation Codes must be established for all Dimension Values that will be included in the Consolidation process. 4. Additional set up requirements exist for the Consolidation if you are consolidating Companies outside of the Consolidation Company's database and using the Export Consolidation feature. If a Consolidation is using the Function | Import Consolidation from the Periodic Activities | Consolidation | Business Unit screen, then the Chart of Accounts in the Consolidation Parent must have a Chart of Accounts properly set up with the appropriate Consolidation Currency Valuation Method on each Account Card. This is required because the system will look to the Parent Company's Chart of Accounts for determining which Accounts were brought in using the appropriate Currency Valuation Method and making sure that those Accounts' Balances are properly converted to the new Current Exchange Rate during the import of the current data being consolidated. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><strong style="font-size: 12px; font-family: Verdana, Arial, sans-serif; color: rgb(0, 0, 0);">What are the requirements for using Navision Financials Consolidation functionality when dealing with foreign currency Company Consolidations?<br style="box-sizing: border-box;"></strong><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="font-size: 12px; font-family: Verdana, Arial, sans-serif; color: rgb(0, 0, 0);">Note - How can I make sure that these Consolidations are done in accordance with FASB 52?</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p class="current" style="box-sizing: border-box; line-height: 14px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">This Help Document is provided to give assistance for utilizing the Navision Financials Additional Reporting Currency functionality and processing Consolidations in Navision Financials Version 2.01.A and later.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span class="current" style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">1. Navision Financials Versions beginning with Version 2.01.A and all Navision Attain Versions provide functionality to use the additional foreign currency reporting functionality already in the the General Ledger Functional Area of the application.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">In using these options along with properly monitoring the currency Table in the Subsidiary Company, a Customer should be able to fully comply with FASB 52 requirements.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">The G/L Account Card has a 'Consolidation Currency Valuation Method' field that provides the flexibility to deal with the different currency requirements under FASB 52. This field has 4 options: Automatic, Current Rate, Historical Rate, and Manual Rate.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">The following is a brief explanation of each option. With the exception of consolidating using the Import Consolidation as noted in 4. below, these settings must only be dealt with in the Subsidiary Company's (ies') Chart of Accounts.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Automatic: The Automatic option is provided for compatibility with versions of Navision Financials previous to 2.01.A. The system will automatically use conversion for Balance Sheet and Income Statement Accounts based on the Current Rate and Average Rate. This is the default configuration. On the Periodic Activities | Consolidation | Business Units screen, there is the Exchange Rate option button. This option button allows you to set up the Income Statement, Balance Sheet and Last Balance Sheet Exchange Rates.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Current Rate: Conversion will force using the Current Rate for the Account. The Current Rate is utilized for all Assets and all Liabilities under the Current Method of Accounting for foreign currency transactions. The Temporal Method allows the utilization of the Historical Exchange Rate for Inventory. In addition, all Non-current assets and Equity Accounts, including Dividends, will utilize Historical Rates using the Temporal Method. Therefore, depending on the implemented method for handling foreign currency transactions under FASB 52 that is being utilized, you will use the Current Rate as discussed above. On the Periodic Activities | Consolidation | Business Units screen, there is the Exchange Rate option button. The Balance Sheet and Last Balance Sheet selections will allow you to set up the Current Rate for the current and the previous Consolidation periods. It is important for these to be set up properly so that the previously consolidated balances will be converted properly to the current Exchange Rate.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Historical Rate: With the availability of the Additional Reporting Currency in the Navision G/L, all G/L transactions will be converted to this currency. With this functionality, an Exchange Rate that is in existence at the time of the transaction will be used for the translation calculation. Because of this, entries can be made and tracked using the currency at the Date of the original posting of the entry. Dividends, original Equity Investments, Inventory, and Fixed Asset Purchases would apply this Historical Rate for posting.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">The key factor in utilizing the Historical Rate Method is that the Foreign Subsidiary must have the Additional Reporting Currency under General Ledger | Setup | General Ledger Setup on the Reporting tab set to the Consolidation Company's currency. This allows all transactions entered through the system to be entered with a converted amount to the Consolidation Company's currency. Rather than converting the amount using a stated average Exchange Rate for these transactions, no conversion is required because the actual Historical Transaction Exchange Rate is used. FASB 52 allows this detailed conversion rather than using the average Rate.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Manual Rate: This option will use the average Exchange Rate entered on the Business Unit Consolidation for all transactions entered during the Consolidation period. This average Rate is the one entered in the Income Statement selection under the Exchange Rate button on the Periodic Activities | Consolidation | Business Units screen.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">2. Set-up on the G/L Account Card. Set up requirements on the Account Card includes setting up the Consolidated Debit and Credit fields on the Consolidation tab of the G/L Account Card in each Subsidiary Company. These Accounts must match the Consolidated Parent Company Chart of Accounts.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">3. Set-up requirements also require Setup | General | Departments and Projects be set up with a Consolidation Department and Project Code in Navision Financials Version 2.01 through 2.60 if the Consolidation is going to include Department and Project detail. In Navision Attain, select Setup | Dimensions | Dimensions, select the Dimension button and select Dimension Values. In the Dimension Values Table, the Consolidation Codes must be established for all Dimension Values that will be included in the Consolidation process.</span><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">4. Additional set up requirements exist for the Consolidation if you are consolidating Companies outside of the Consolidation Company's database and using the Export Consolidation feature. If a Consolidation is using the Function | Import Consolidation from the Periodic Activities | Consolidation | Business Unit screen, then the Chart of Accounts in the Consolidation Parent must have a Chart of Accounts properly set up with the appropriate Consolidation Currency Valuation Method on each Account Card. This is required because the system will look to the Parent Company's Chart of Accounts for determining which Accounts were brought in using the appropriate Currency Valuation Method and making sure that those Accounts' Balances are properly converted to the new Current Exchange Rate during the import of the current data being consolidated.</span><br></p> <p style="box-sizing: border-box; line-height: 14px;"><br></p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 391 17000037283 2016-12-12T14:50:34-07:00 17002649915 1 Requirements for Using Navision Consolidation with Foreign Currency Company Consolidations Requirements for Using Navision Consolidation with Foreign Currency Company Consolidations Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,consolidation,requirements,use,navision,foreign,currency,company 2 0 0 Requirements for Using Navision Consolidation with Foreign Currency Company Consolidations 2016-12-13T10:13:12-07:00 17002649915 1 2016-12-07T10:52:18-07:00 0 0 Issue When one user does a post and print of a journal entry, it does not print. Solution If there is a filter on the G/L Register Report, the journals will not print when you click Post & Print. This report will save any filters that were used when it was printed. Go to General Ledger > Reports > G/L Register. Click through the tabs and remove any filters that are there. Most of the posting reports also appear on the report menu. For example, the General Ledger posting report appears in the general ledger report menu as G/L Register. If the user sets some filters when printing the report from the menu, those filters were not the ones that are overridden when the posting report is printed (i.e. not the register number). Therefore they are still kept. When combined with the register that was just posted, the previously set filter excluded all of the lines that were posted. Therefore, nothing printed. To resolve the problem for a particular instance, the user must go into the report and remove the filters that were set. Just preview the report and then hit cancel (you can cancel before it actually shows anything). If it happens often that the same user is printing the report from the menu and posts and prints using this same report, consider making a separate copy of the report; one for use during post and print and one to appear on the menu. For documents, one would appear in the Report Selection and the other would be used when printing documents. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">When one user does a post and print of a journal entry, it does not print.</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current">If there is a filter on the G/L Register Report, the journals will not print when you click Post &amp; Print. This report will save any filters that were used when it was printed.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Go to General Ledger &gt; Reports &gt; G/L Register. Click through the tabs and remove any filters that are there.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Most of the posting reports also appear on the report menu. For example, the General Ledger posting report appears in the general ledger report menu as G/L Register. If the user sets some filters when printing the report from the menu, those filters were not the ones that are overridden when the posting report is printed (i.e. not the register number). Therefore they are still kept. When combined with the register that was just posted, the previously set filter excluded all of the lines that were posted. Therefore, nothing printed.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">To resolve the problem for a particular instance, the user must go into the report and remove the filters that were set. Just preview the report and then hit cancel (you can cancel before it actually shows anything).<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">If it happens often that the same user is printing the report from the menu and posts and prints using this same report, consider making a separate copy of the report; one for use during post and print and one to appear on the menu. For documents, one would appear in the Report Selection and the other would be used when printing documents.<br> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 68 17000037285 2016-12-12T14:50:59-07:00 17002649915 1 Journal Entry Post and Print Journal Entry Post and Print Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,journal,entry,journal-entry,post,print 2 0 0 Journal Entry Post and Print 2016-12-13T10:13:34-07:00 17002649915 1 2016-12-07T10:59:39-07:00 0 0 Issue How to properly set up Navision Financials / Attain / MBS for multiple currency and reporting Solution Requirements The Multiple Currencies Granule must be purchased and have Navision Financials Version 2.00 or above. Background Information Related to Foreign Currency Reporting FASB 52 is the official pronouncement from the Financial Accounting Standards Board related to Foreign Currency Reporting. In FASB 52, the 'translation process' is defined as 'the process of expressing in the reporting currency of the enterprise those amounts that are denominated or measured in a different currency.' The translation from one currency (Company's functional currency) to another currency (reporting currency) can be handled through one of two methods defined by FASB 52. These two methods are the Current Method and the Temporal Method. The Current Method handles translation as follows: use the current Exchange Rate as of the Financial Statement Date for converting the Balance Sheet Accounts (except for the Equity Accounts, which use Historical Rate); use the average Exchange Rate for the year for converting the Income Statement Accounts (or the specific Rate for the Transaction Date); use the Historical Exchange Rate for Dividends (Rate on Date of Dividend Issuance); and records the difference as a gain/loss under the Equity Section of the Balance Sheet. The Temporal Method is more complex to implement. This method requires remeasurement as follows: use the current Rate for Cash, Receivables, and Liabilities; use the appropriate Historical Rates for Fixed Assets, Inventory, and Capital Stock; use the average Rates for Income Statement Accounts (except for Depreciation and Iinventory, which are at Historical Rates); and gain/loss on remeasurement reported on the Income Statement. The Current Method is the method used most often in reporting for foreign currency transactions. However, in cases where a country's functional currency is in a highly inflationary state (cumulative percentage of over 100% inflation over a 3 year period), use of the Temporal Method is required. Click on Attachments to view a table that summarizes the differences between the Current and Temporal Methods. Navision Financials 2.0 uses the Current Method for translating foreign currency transactions through the utilization of the Periodic Activities | Currency | Adjust Exchange Rates. Also, because Navision Financials allows for Multi-Currency reporting with the Additional Reporting Currency, all of the requirements for the Temporal Method will also be met. By updating the Currencies Exchange Rate Table to the latest Rates, all transactions will be posted using that correct Rate at the Transaction Date, thus applying the Temporal Method initially. If the user wants to update to the latest Exchange Rate, the Periodic Activity can be run to update those Accounts that require updating to the Current Exchange Rate. One additional issue deals with Budgeted Amounts using the Additional Reporting Currency. As a generally accepted practice, a Budget is established at the beginning of the year in the Additional Reporting Currency using a projected average Exchange Rate for the year, and will not get adjusted during the year for currency Exchange Rate changes. Therefore, when running the Periodic Activities to Adjust Exchange Rates, the Budget Amounts should not be adjusted. Therefore, a separate Budget will need to be established with amounts already converted to the Additional Reporting Currency. See attachments for additional detailed information. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">How to properly set up Navision Financials / Attain / MBS for multiple currency and reporting</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current"> <strong>Requirements</strong><br><br>The Multiple Currencies Granule must be purchased and have Navision Financials Version 2.00 or above.<br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">Background Information Related to Foreign Currency Reporting</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">FASB 52 is the official pronouncement from the Financial Accounting Standards Board related to Foreign Currency Reporting. In FASB 52, the 'translation process' is defined as 'the process of expressing in the reporting currency of the enterprise those amounts that are denominated or measured in a different currency.'</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">The translation from one currency (Company's functional currency) to another currency (reporting currency) can be handled through one of two methods defined by FASB 52. These two methods are the Current Method and the Temporal Method.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">The Current Method handles translation as follows: use the current Exchange Rate as of the Financial Statement Date for converting the Balance Sheet Accounts (except for the Equity Accounts, which use Historical Rate); use the average Exchange Rate for the year for converting the Income Statement Accounts (or the specific Rate for the Transaction Date); use the Historical Exchange Rate for Dividends (Rate on Date of Dividend Issuance); and records the difference as a gain/loss under the Equity Section of the Balance Sheet.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">The Temporal Method is more complex to implement. This method requires remeasurement as follows: use the current Rate for Cash, Receivables, and Liabilities; use the appropriate Historical Rates for Fixed Assets, Inventory, and Capital Stock; use the average Rates for Income Statement Accounts (except for Depreciation and Iinventory, which are at Historical Rates); and gain/loss on remeasurement reported on the Income Statement.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">The Current Method is the method used most often in reporting for foreign currency transactions. However, in cases where a country's functional currency is in a highly inflationary state (cumulative percentage of over 100% inflation over a 3 year period), use of the Temporal Method is required.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">Click on Attachments to view a table that summarizes the differences between the Current and Temporal Methods.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">Navision Financials 2.0 uses the Current Method for translating foreign currency transactions through the utilization of the Periodic Activities | Currency | Adjust Exchange Rates. Also, because Navision Financials allows for Multi-Currency reporting with the Additional Reporting Currency, all of the requirements for the Temporal Method will also be met. By updating the Currencies Exchange Rate Table to the latest Rates, all transactions will be posted using that correct Rate at the Transaction Date, thus applying the Temporal Method initially. If the user wants to update to the latest Exchange Rate, the Periodic Activity can be run to update those Accounts that require updating to the Current Exchange Rate.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">One additional issue deals with Budgeted Amounts using the Additional Reporting Currency. As a generally accepted practice, a Budget is established at the beginning of the year in the Additional Reporting Currency using a projected average Exchange Rate for the year, and will not get adjusted during the year for currency Exchange Rate changes. Therefore, when running the Periodic Activities to Adjust Exchange Rates, the Budget Amounts should not be adjusted. Therefore, a separate Budget will need to be established with amounts already converted to the Additional Reporting Currency.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Arial; font-size: 12px;">See attachments for additional detailed information.</span><br> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 98 17000037289 2016-12-12T14:51:12-07:00 17002649915 1 set up Navision Financials / Attain / MBS for multiple currency and reporting set up Navision Financials / Attain / MBS for multiple currency and reporting Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,multicurrency,setup,navision,financials,attain,MBS,reporting 2 0 0 How to properly set up Navision Financials / Attain / MBS for multiple currency and reporting 2016-12-13T10:13:51-07:00 17002649915 1 2016-12-07T11:11:03-07:00 0 0 Issue In the recurring journals, the user is able to post an entry, seemingly without a value in the Dept Code field.  But when you look at the Line Dimensions, there is a value there. And when you drill down on this transaction in the Chart of Accounts, the Dept Code field is blank. Yet when you filter on the dimension code that appeared in the line dimensions of the recurring journal, the transaction was posted to this dimension. Basically, when you look at the transaction in the general ledger, the dept code field appears blank, but when you drill down on the line dimension, there is a value.  So somewhere there is a 'disconnect' between these fields. I checked tables 17 & 355, and for the transactions I tested, a dept code appears in table 355, but not in table 17. Solution This issue is a result of the confusion in Navision between having dimension codes on the actual transaction entry line, in this case the recurring journal entry line, and the attached dimension table that includes all dimensions to be posted with the transaction.  The inconsistent structure between the treatment of the two global dimensions, which are always attached to all unposted and posted transaction lines, and the additional dimensions creates this problem.  The additional dimensions can be entered through shortcut codes available on unposted transaction lines but they are then posted only to the underlying dimension detail table attached to each posted transaction line.  The global dimensions will show on both the posted transaction line and the underlying dimension detail. The problem in this case was that the unposted recurring journal entry line did not have the global dimensions populated but the underlying dimension table did.  When the transaction was posted, the underlying dimensions were passed on to the posted general ledger detail line but the global dimensions on the posted line were left blank because they were blank on the unposted entry. Some confusion was created in using account schedules to analyze the transactions.  Using a filter on a department code displayed the transaction, which means the schedule must look at the underlying dimension table, but drilling down to the transaction showed a blank department field on the journal entry line itself. Recurring entries should have both appropriate global dimensions and all appropriate dimension shortcut fields populated before they are posted. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">In the recurring journals, the user is able to post an entry, seemingly without a value in the Dept Code field.  But when you look at the Line Dimensions, there is a value there.</span><br></p> <br><br><span rel="tempredactor" style='font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px;'>And when you drill down on this transaction in the Chart of Accounts, the Dept Code field is blank. Yet when you filter on the dimension code that appeared in the line dimensions of the recurring journal, the transaction was posted to this dimension.</span><br><br><span rel="tempredactor" style='font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px;'>Basically, when you look at the transaction in the general ledger, the dept code field appears blank, but when you drill down on the line dimension, there is a value.  So somewhere there is a 'disconnect' between these fields.</span><br><br><span rel="tempredactor" style='font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px;'>I checked tables 17 &amp; 355, and for the transactions I tested, a dept code appears in table 355, but not in table 17.</span><br><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td>This issue is a result of the confusion in Navision between having dimension codes on the actual transaction entry line, in this case the recurring journal entry line, and the attached dimension table that includes all dimensions to be posted with the transaction.<span style="box-sizing: border-box;">  </span>The inconsistent structure between the treatment of the two global dimensions, which are always attached to all unposted and posted transaction lines, and the additional dimensions creates this problem.<span style="box-sizing: border-box;">  </span>The additional dimensions can be entered through shortcut codes available on unposted transaction lines but they are then posted only to the underlying dimension detail table attached to each posted transaction line.<span style="box-sizing: border-box;">  </span>The global dimensions will show on both the posted transaction line and the underlying dimension detail.<br style="box-sizing: border-box;"><span class="current" style="box-sizing: border-box;"><br style="box-sizing: border-box;">The problem in this case was that the unposted recurring journal entry line did not have the global dimensions populated but the underlying dimension table did.  When the transaction was posted, the underlying dimensions were passed on to the posted general ledger detail line but the global dimensions on the posted line were left blank because they were blank on the unposted entry.<br></span><span class="current" style="box-sizing: border-box;"><br style="box-sizing: border-box;">Some confusion was created in using account schedules to analyze the transactions.<span>  </span>Using a filter on a department code displayed the transaction, which means the schedule must look at the underlying dimension table, but drilling down to the transaction showed a blank department field on the journal entry line itself.<br style="box-sizing: border-box;"></span><span style="box-sizing: border-box;"><br style="box-sizing: border-box;">Recurring entries should have both appropriate global dimensions and all appropriate dimension shortcut fields populated before they are posted.</span><br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 77 17000037293 2016-12-12T14:52:16-07:00 17002649915 1 Navision coding issue Navision coding issue Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,recurring-journal,navision,coding 2 0 0 Navision coding issue 2016-12-13T10:14:11-07:00 17002649915 1 2016-12-07T11:14:12-07:00 1 0 Issue GST Rate Change Solution Version 4:  Go to Financial Management > Setup > Sales Tax > Details Version 2.6 - 3.7:  Go to General Ledger > Setup > Sales Tax > Details Choose the code(s) that is(are) used for the GST. Insert a new line or go to the next available line, and set this new Tax Detail up the same as the old GST rate, except change the rate to 6% (14% for the HST in this example) and the Effective Date to July 1, 2006.  The system will automatically know when to use the appropriate tax rate based on the effective date.  Remember to update all of your GST related tax codes! See attachment for further explanation and for handling credit memos. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">GST Rate Change</span><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current">Version 4:  Go to Financial Management &gt; Setup &gt; Sales Tax &gt; Details<br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Arial;"><span class="current">Version 2.6 - 3.7:  Go to General Ledger &gt; Setup &gt; Sales Tax &gt; Details</span><br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Choose the code(s) that is(are) used for the GST.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Insert a new line or go to the next available line, and set this new Tax Detail up the same as the old GST rate, except change the rate to 6% (14% for the HST in this example) and the Effective Date to July 1, 2006.  The system will automatically know when to use the appropriate tax rate based on the effective date.  <span style="box-sizing: border-box;">Remember to update all of your GST related tax codes!</span><br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><span style="box-sizing: border-box;">See attachment for further explanation and for handling credit memos.</span><br style="box-sizing: border-box;"><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 60 17000037294 2016-12-12T14:52:45-07:00 17002649915 1 GST Rate Change GST Rate Change Microsoft,Dynamics,NAV,ODT,Edsuite,financials,setup,GST,rate,change,2007 2 1 0 GST Rate Change 2007 2016-12-13T10:15:07-07:00 17002649915 1 2016-12-07T11:20:20-07:00 0 0 Issue Closing Fiscal Year End Procedures Solution YEAR END CLOSING Closing the fiscal year in Navision Financials involves five steps: 1. Review all your accounts and make sure that all the accounts that should be closed out   to retained earnings are set to Income Statement. 2. Backup your data. 3. Close the fiscal year. On the General Ledger menu, click Periodic Activities, Fiscal Year, Accounting Periods. Click Close Year. 4. Close Income Statement. On the General Ledger menu, click Periodic Activities, Fiscal Year, Close Income Statement.  This routine will create the closing journal entry into a batch. 5. Review and then Post the year-end closing entry along with the offsetting equity account entries. Navision Financials does not require you to close a year, but doing so will make working in the system easier for you because you will be able to take advantage of the convenient filtering options provided by Navision Financials.  And you don't have to worry about losing details of transactions when you close. Navision Financials retains all details, even after you close the year. When you close at the end of the year, the system moves your earnings from calculated earnings, or the Current Earnings account, to a posted account, or the Retained Earnings account.  The system also marks the fiscal year as "closed", and marks all subsequent entries for the closed year as "prior year entries". The system then generates a closing entry, but it does not post the entry automatically. Navision Financials offers you a great deal of flexibility by letting you make the offsetting equity account entry or entries, which lets you decide how to allocate your closing entry.  For example, if your company has several divisions, you can let the system generate a single closing entry for all the divisions, and you can then make an offsetting entry for each division's equity account. After you close the fiscal year you can still make entries in the accounts in that year.  However, the system marks them as prior period adjustments. Closing the Fiscal Year The Accounting Periods option lets you close the fiscal year and the accounting periods within the year.  After you close these periods, you can generate the year-end closing entry.  Once you close the fiscal year you cannot open it again. From the General Ledger Menu, select Periodic Activities, Fiscal Year.  Select Accounting Periods, then click on the Close Year button.  The system displays a message explaining what will occur if you close the fiscal year.  It also verifies the dates and lets you confirm your choice before it closes the year. Generating the Year-End Closing Entry The Close Income Statement option lets you generate the year-end closing entry in the general journal.  From the General Ledger menu, select Periodic Activities, Fiscal Year.  Select Close Income Statement and a definition window appears.  Enter the information for the statement in the fields on the definition window.  These include: Ending Date - Enter the last date in the fiscal year you're closing. General Journal Template - Enter the name of the general journal for which you want the system to make the year-end closing entry.  Do a Lookup   (F6) for a list of journals to choose from. General Journal Batch - Enter the name of the batch in which you want the system to make the year-end closing entry.  Do a Lookup   (F6) for a list of batches to choose from. Document # - Enter a document number to be used of the year end closing entry i.e. YE-2000 for year end 2000. Posting Description - Enter the description for the year-end closing entry. Close Per Business Unit Code - Check box if you want the system to make separate entries for each business unit. Close Per Department Code - Check box if you want the system to make separate entries for each department. Close Per Project Code - Check box if you want the system to make separate entries for each project.  However, if you have a project spanning over two or more fiscal years, do not check this box. Click OK to confirm information and exit window. Completing and Posting the Year-End Closing Entry After you use the Close Income Statement option to generate the year-end closing entry or entries, you must then go into the journal you specified in the definition window and make the balancing entry. Then you can post the entry. Make an offsetting entry in the journal for the balancing amount using your Retained Earnings account.  You can enter this account number in the Balancing Account field in the closing entry for the same result.  However, using this field will cause detailed transactions to show up in the Retained Earning account. From the journal, on the Posting button pull-down menu, select Post and Print to post the entries and print a posting report or Post to post without printing a posting report. If the system detects an error, it displays a message describing the error.  If the posting is successful, the system removes the posted entries from the journal. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;">Closing Fiscal Year End Procedures</p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><strong style="box-sizing: border-box;">YEAR END CLOSING</strong><br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Closing the fiscal year in Navision Financials involves five steps:<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">1. Review all your accounts and make sure that all the accounts that should be closed out   to retained earnings are set to Income Statement.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">2. Backup your data.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">3. Close the fiscal year. On the General Ledger menu, click Periodic Activities, Fiscal Year, Accounting Periods. Click Close Year.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">4. Close Income Statement. On the General Ledger menu, click Periodic Activities, Fiscal Year, Close Income Statement.  This routine will create the closing journal entry into a batch.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">5. Review and then Post the year-end closing entry along with the offsetting equity account entries.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Navision Financials does not require you to close a year, but doing so will make working in the system easier for you because you will be able to take advantage of the convenient filtering options provided by Navision Financials.  And you don't have to worry about losing details of transactions when you close. Navision Financials retains all details, even after you close the year.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">When you close at the end of the year, the system moves your earnings from calculated earnings, or the Current Earnings account, to a posted account, or the Retained Earnings account.  The system also marks the fiscal year as "closed", and marks all subsequent entries for the closed year as "prior year entries".<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">The system then generates a closing entry, but it does not post the entry automatically. Navision Financials offers you a great deal of flexibility by letting you make the offsetting equity account entry or entries, which lets you decide how to allocate your closing entry.  For example, if your company has several divisions, you can let the system generate a single closing entry for all the divisions, and you can then make an offsetting entry for each division's equity account.<br style="box-sizing: border-box;">After you close the fiscal year you can still make entries in the accounts in that year.  However, the system marks them as prior period adjustments.</p> <br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><strong style="box-sizing: border-box;">Closing the Fiscal Year</strong><br style="box-sizing: border-box;">The Accounting Periods option lets you close the fiscal year and the accounting periods within the year.  After you close these periods, you can generate the year-end closing entry.  Once you close the fiscal year you cannot open it again.<br style="box-sizing: border-box;">From the General Ledger Menu, select Periodic Activities, Fiscal Year.  Select Accounting Periods, then click on the Close Year button.  The system displays a message explaining what will occur if you close the fiscal year.  It also verifies the dates and lets you confirm your choice before it closes the year.</p> <br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><strong style="box-sizing: border-box;">Generating the Year-End Closing Entry</strong><br style="box-sizing: border-box;">The Close Income Statement option lets you generate the year-end closing entry in the general journal.  From the General Ledger menu, select Periodic Activities, Fiscal Year.  Select Close Income Statement and a definition window appears.  Enter the information for the statement in the fields on the definition window.  These include:<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Ending Date</u> - Enter the last date in the fiscal year you're closing.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">General Journal Template</u> - Enter the name of the general journal for which you want the system to make the year-end closing entry.  Do a Lookup   (F6) for a list of journals to choose from.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">General Journal Batch</u> - Enter the name of the batch in which you want the system to make the year-end closing entry.  Do a Lookup   (F6) for a list of batches to choose from.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Document #</u> - Enter a document number to be used of the year end closing entry i.e. YE-2000 for year end 2000.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Posting Description</u> - Enter the description for the year-end closing entry.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Close Per Business Unit Code</u> - Check box if you want the system to make separate entries for each business unit.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Close Per Department Code</u> - Check box if you want the system to make separate entries for each department.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><u style="box-sizing: border-box;">Close Per Project Code</u> - Check box if you want the system to make separate entries for each project.  However, if you have a project spanning over two or more fiscal years, do not check this box.<br style="box-sizing: border-box;">Click OK to confirm information and exit window.</p> <br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><br style="box-sizing: border-box; color: rgb(80, 99, 135); font-family: Verdana;"><p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><strong style="box-sizing: border-box;">Completing and Posting the Year-End Closing Entry<br style="box-sizing: border-box;"></strong>After you use the Close Income Statement option to generate the year-end closing entry or entries, you must then go into the journal you specified in the definition window and make the balancing entry. Then you can post the entry.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Make an offsetting entry in the journal for the balancing amount using your Retained Earnings account.  You can enter this account number in the Balancing Account field in the closing entry for the same result.  However, using this field will cause detailed transactions to show up in the Retained Earning account.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">From the journal, on the Posting button pull-down menu, select Post and Print to post the entries and print a posting report or Post to post without printing a posting report.<br style="box-sizing: border-box;">If the system detects an error, it displays a message describing the error.  If the posting is successful, the system removes the posted entries from the journal.</p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 105 17000037296 2016-12-12T15:06:10-07:00 17002649915 1 Closing Fiscal Year End Procedures Closing Fiscal Year End Procedures Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,year-end,procedures,closing,fiscal 2 0 0 Closing Fiscal Year End Procedures 2016-12-13T10:15:27-07:00 17002649915 1 2016-12-08T15:48:10-07:00 0 0 Issue When selecting the post and print a GL Journal Entry the G/L Register report is run at the end of the post routine.  It is ran with whatever selections have been previously stored in the report the last time it was run. Solution To set the report to print dimensions you must: Go to the G/L Register report in the menu and select the report. Ensure there are no filters on the first 2 tabs.  Go to the options tab and ensure to select the include dimensions option and simply close or cancel the report to save the settings. If the G/L Register report is ran manually with a filter for a specific register or G/L Entry filter, and these filters are stored in the report the print and post will not print the report. To correct select the G/L Register report, clear the filter close the report and this should correct the issue. <table style="width: 100%;"><tbody> <tr> <td style="width: 11.4016%;"> <strong>Issue</strong><br> </td> <td style="width: 88.47%;">When selecting the post and print a GL Journal Entry the G/L Register report is run at the end of the post routine.  It is ran with whatever selections have been previously stored in the report the last time it was run.<br> </td> </tr> <tr> <td style="width: 11.4016%;"> <strong>Solution</strong><br> </td> <td style="width: 88.47%;">To set the report to print dimensions you must:<br><br>Go to the G/L Register report in the menu and select the report.<br><br>Ensure there are no filters on the first 2 tabs.  Go to the options tab and ensure to select the include dimensions option and simply close or cancel the report to save the settings.<br><br>If the G/L Register report is ran manually with a filter for a specific register or G/L Entry filter, and these filters are stored in the report the print and post will not print the report.<br><br>To correct select the G/L Register report, clear the filter close the report and this should correct the issue.<br> </td> </tr> </tbody></table> 17000122225 30 17000037558 2016-12-13T09:37:27-07:00 17002649915 1 G/L Register report not include dimensions when post and printing After switching machines the G/L Register report does not include dimensions when post and printing Microsoft,Dynamics,NAV,ODT,Edsuite,General,ledger,switch,machine,GL,register,report,include,dimensions,post,print 2 0 0 After switching machines the G/L Register report does not include dimensions when post and printing 2016-12-08T15:48:10-07:00 17002649915 1 2016-12-08T15:53:26-07:00 0 0 Issue Changing Company Logo (Picture) in Navision Solution Changing Company Logo: This is referred to in Navision as "Picture" in the company information form. Step 1: Select Company Information Form: Version 2.5-3.7 = General Ledger > Setup > General > Company Information Version 4.0 - outgoin = Administration > Application Setup > General > Company Information Step 2: To import a picture (logo) Click the "Picture" button and export existing picture (For records and backup in case) Click the "Picture" button and import new picture  Select picture to import - NOTE: must be in bmp format and have .bmp file extension Open > OK Close Company Information and picture is in company information. Example: Open any document or report with it added to preview new picture. <table style="width: 100%;"><tbody> <tr> <td style="width: 11.4016%;"> <strong>Issue</strong><br> </td> <td style="width: 88.47%;">Changing Company Logo (Picture) in Navision<br> </td> </tr> <tr> <td style="width: 11.4016%;"> <strong>Solution</strong><br> </td> <td style="width: 88.47%;"> <strong>Changing Company Logo:</strong><br>This is referred to in Navision as "Picture" in the company information form.<br><br><strong>Step 1: Select Company Information Form:</strong><br><br>Version 2.5-3.7 = General Ledger &gt; Setup &gt; General &gt; Company Information<br>Version 4.0 - outgoin = Administration &gt; Application Setup &gt; General &gt; Company Information<br><br><strong>Step 2: To import a picture (logo)</strong><br><br>Click the "Picture" button and export existing picture (For records and backup in case)<br><br>Click the "Picture" button and import new picture<span> </span><br><br>Select picture to import - NOTE: must be in bmp format and have .bmp file extension<br><br>Open &gt; OK<br><br>Close Company Information and picture is in company information. Example: Open any document or report with it added to preview new picture.<br> </td> </tr> </tbody></table> 17000122225 99 17000037560 2016-12-12T14:52:21-07:00 17002649915 1 Changing Company Logo (Picture) in Navision Changing Company Logo (Picture) in Navision Microsoft,Dynamics,NAV,ODT,Edsuite,General,ledger,setup,change,changing,company,logo,picture 2 0 0 Changing Company Logo (Picture) in Navision 2016-12-13T10:15:07-07:00 17002649915 1 2016-12-07T10:34:38-07:00 0 0 Issue When trying to go into Overview for any Account Schedule, receive the following message: There is no Accounting Period within the filter. Filters: Starting Date: '..10/31/06, New Fiscal Year: Yes This occurs when opening the overview for a newer company after viewing the overview in an older company. For example, Company A has accounting periods going back to 2000. Company B was just created and only has accounting periods for 2007. After looking at an overview for Co A, for the year 2005, then opening Co B, and you try to open the same overview, you receive the error message.  There is no place to change the date filter.  You need to go back to Co A, change the date filter there, then go back to Co B. Solution Based on the information presented, you are running into what amounts to an unfortunate side effect of the ZUP file functionality in Navision.  The ZUP file stores all of the filters, last record accessed in each area, last company information that was previously accessed by the user, and other settings on the client.  Because the date range entered on reports and in other system areas is carried to the Report the next time the Report is run, you have a situation where the retaining of a date filter isn't helpful.  I know of two workarounds for you in this situation: 1) Setup a different shortcut for each company access.  On the Target Line of the Shortcut Icon Properties, you could possibly use a different ID= Parameter to generate a unique zup file or have separate COMPANY= parameter on each shortcut icon to reference the specific company the user will access with each NAV icon.   You would have separate shortcuts for each company the user accesses.  The only negative with setup like this is that the user would need to exit out of Navision and use the different icon to access a different company. 2) The other option would be to set up the Accounting Periods to match in each company under Financial Management - Setup - Accounting Periods. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">When trying to go into Overview for any Account Schedule, receive the following message:</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">There is no Accounting Period within the filter.<br style="box-sizing: border-box;">Filters: Starting Date: '..10/31/06, New Fiscal Year: Yes</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">This occurs when opening the overview for a newer company after viewing the overview in an older company.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">For example, Company A has accounting periods going back to 2000.<br style="box-sizing: border-box;">Company B was just created and only has accounting periods for 2007.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">After looking at an overview for Co A, for the year 2005, then opening Co B, and you try to open the same overview, you receive the error message.  There is no place to change the date filter.  You need to go back to Co A, change the date filter there, then go back to Co B.</p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">Based on the information presented, you are running into what amounts to an unfortunate side effect of the ZUP file functionality in Navision.  The ZUP file stores all of the filters, last record accessed in each area, last company information that was previously accessed by the user, and other settings on the client.  Because the date range entered on reports and in other system areas is carried to the Report the next time the Report is run, you have a situation where the retaining of a date filter isn't helpful.  I know of two workarounds for you in this situation:</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">1) Setup a different shortcut for each company access.  On the Target Line of the Shortcut Icon Properties, you could possibly use a different ID= Parameter to generate a unique zup file or have separate COMPANY= parameter on each shortcut icon to reference the specific company the user will access with each NAV icon.   You would have separate shortcuts for each company the user accesses.  The only negative with setup like this is that the user would need to exit out of Navision and use the different icon to access a different company.</p> <p style="box-sizing: border-box; margin-bottom: 10px; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;">2) The other option would be to set up the Accounting Periods to match in each company under Financial Management - Setup - Accounting Periods.</p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 55 17000037280 2016-12-12T14:50:14-07:00 17002649915 2 Overview for Account Schedule error Overview for Account Schedule error Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,account-schedules,overview,error 2 0 0 Overview for Account Schedule error 2016-12-13T10:12:08-07:00 17002649915 1 2016-12-07T10:50:10-07:00 0 0 Issue When one user does a post and print of a journal entry, it does not print. Solution If a user is printing the G/L Register report from the General Ledger Reports, any filters (date filters, accounts, and others) put onto this report do not clear when the Report has been printed. The filters on the report cause this report not to print when using the Post and Print functionality. There must not be any filters set on this report otherwise nothing will print using the Post and Print functionality. To resolve this issue, you must: 1. Open the G/L Register report (General Ledger > Reports > G/L Register). 2. Click all tabs on the G/L Register report. Remove any filters that appear on any tab. 3. When all filters are removed, you can then use the Post and Print functionality with success. Note - Check the G/L Register report from the General Ledger menu before using the Post and Print functionality. The other option is when the user prints the G/L Register report from the General Ledger menu, go back into the window and remove any filters that they may have put on the report. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">When one user does a post and print of a journal entry, it does not print.</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td> <p class="current" style="box-sizing: border-box; line-height: 14px;">If a user is printing the G/L Register report from the General Ledger Reports, any filters (date filters, accounts, and others) put onto this report do not clear when the Report has been printed. The filters on the report cause this report not to print when using the Post and Print functionality. There must not be any filters set on this report otherwise nothing will print using the Post and Print functionality.<br><br>To resolve this issue, you must:<br><br>1. Open the G/L Register report (General Ledger &gt; Reports &gt; G/L Register).<br><br>2. Click all tabs on the G/L Register report. Remove any filters that appear on any tab.<br><br>3. When all filters are removed, you can then use the Post and Print functionality with success.<br><br>Note - Check the G/L Register report from the General Ledger menu before using the Post and Print functionality. The other option is when the user prints the G/L Register report from the General Ledger menu, go back into the window and remove any filters that they may have put on the report.<br></p> <p style="box-sizing: border-box; line-height: 14px;"><br></p> <p style="box-sizing: border-box; line-height: 14px;" class="current"><br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 96 17000037284 2016-12-12T14:51:04-07:00 17002649915 2 Post and Print issue Post and Print issue Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,journal,entry,journal-entry,post,print 2 0 0 Post and Print issue 2016-12-13T10:13:34-07:00 17002649915 1 2016-12-07T10:54:05-07:00 0 1 Issue After selecting Post & Print function for Journal, Invoice, Credit Memo, etc. the Post Report does not print. User is able to print reports not connected to posting function in Navision and printer connection is correct. This issue is happening at individual user clients. Solution Cause: Often when the Post & Print function doesn't work, it is because of a filter at the GL entry level. Solution: Check the following for filters: -Fin. Mgmt > General Ledger > Reports > Entries > G/L Register  -Clear any filters on G/L Register and G/L Entry tabs -Test Post & Print Also, if you want to print any reports after the fact that were missed because of above, go to: -Fin. Mgmt > General Ledger > History > Registers  -Search by entry number > Register button > select appropriate ledger  -Select entry > Navigate > Print <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">After selecting Post &amp; Print function for Journal, Invoice, Credit Memo, etc. the Post Report does not print. User is able to print reports not connected to posting function in Navision and printer connection is correct. This issue is happening at individual user clients.</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current"> <b style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Cause:<br style="box-sizing: border-box;"></b><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Often when the Post &amp; Print function doesn't work, it is because of a filter at the GL entry level.</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><b style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Solution:</b><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Check the following for filters:</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Fin. Mgmt &gt; General Ledger &gt; Reports &gt; Entries &gt; G/L Register </span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Clear any filters on G/L Register and G/L Entry tabs</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Test Post &amp; Print</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">Also, if you want to print any reports after the fact that were missed because of above, go to:</span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Fin. Mgmt &gt; General Ledger &gt; History &gt; Registers </span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Search by entry number &gt; Register button &gt; select appropriate ledger </span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><span style="color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">-Select entry &gt; Navigate &gt; Print</span><br> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 174 17000037286 2016-12-12T14:51:07-07:00 17002649915 2 Post and Print Function - Not printing report at posting Post and Print Function - Not printing report at posting Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,journal,entry,journal-entry,post,print, report 2 0 1 Post and Print Function - Not printing report at posting 2016-12-13T10:13:34-07:00 17002649915 1 2016-12-07T11:03:47-07:00 0 0 Issue I am having some what appears to be exchange issues.  What is happening is my National USD GL account is showing the opening balance for February is 254,537.88, this ties to the "Bank Acc-Detail Trial Bal".  However what has imported into my Bank Reconciliation worksheet is $258,506.28.  The difference between the two amounts is $3968.40.  This is the amount that is showing out of balance on my Feb Bank Reconciliation worksheet. Solution The Exchange rate the bank reconciliation for the NAT US bank rec is using was the updated/anticipated rate of 1.1353.  When you view the bank account ledger entries and the report Bank Account - Detail Trial Balance the rate between the displayed US amounts and the Canadian equivalent is a rate of 1.1530. The bank reconciliation uses the currency rate from the Currency Exchange Rate table for and calculates the US amount based from the known Canadian Balance ($) where as in the bank detail report and related GL entries uses the known US source transaction amount and converts to Canadian amount ($).  These are two different exchange rates in the rate table. There is a discrepancy in the Exchange rate table between the "Relational Exch. Rate Amount" and "Relational Adjmt Exch Rate Amt" fields for the february 28th record used.  The 'Relational Exch. Rate Amount' rate is used by the Bank Reconciliation and the "Relational Adjmt Exch Rate Amt" rate is used by the Adjust Exchange Rate program and calculates the GL Balance. Process: Please have update the table to ensure that both rates are the same. Then must do the following: -Run the Adjust the Exchange Rate program noted by Denise -Must Go to the Bank Reconciliation and use the Functions, Re-calculate G/L Balance -Possibly re-imput the statement date to refresh additional calculations if required. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">I am having some what appears to be exchange issues.  What is happening is my National USD GL account is showing the opening balance for February is 254,537.88, this ties to the "Bank Acc-Detail Trial Bal".  However what has imported into my Bank Reconciliation worksheet is $258,506.28.  The difference between the two amounts is $3968.40.  This is the amount that is showing out of balance on my Feb Bank Reconciliation worksheet.</span><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current">The Exchange rate the bank reconciliation for the NAT US bank rec is using was the updated/anticipated rate of 1.1353.  When you view the bank account ledger entries and the report Bank Account - Detail Trial Balance the rate between the displayed US amounts and the Canadian equivalent is a rate of 1.1530.<br><br>The bank reconciliation uses the currency rate from the Currency Exchange Rate table for and calculates the US amount based from the known Canadian Balance ($) where as in the bank detail report and related GL entries uses the known US source transaction amount and converts to Canadian amount ($).  These are two different exchange rates in the rate table.<br><br>There is a discrepancy in the Exchange rate table between the "Relational Exch. Rate Amount" and "Relational Adjmt Exch Rate Amt" fields for the february 28th record used.  The 'Relational Exch. Rate Amount' rate is used by the Bank Reconciliation and the "Relational Adjmt Exch Rate Amt" rate is used by the Adjust Exchange Rate program and calculates the GL Balance.<br><br><strong>Process:<br></strong><br>Please have update the table to ensure that both rates are the same. Then must do the following:<br><br>-Run the Adjust the Exchange Rate program noted by Denise<br>-Must Go to the Bank Reconciliation and use the Functions, Re-calculate G/L Balance<br>-Possibly re-imput the statement date to refresh additional calculations if required.<br> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 627 17000037290 2016-12-12T14:51:26-07:00 17002649915 2 Difference Between Currency Exch. Rate and Relational Exch. Rate Amount Difference Between Currency Exch. Rate and Relational Exch. Rate Amount Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,multicurrency,difference,currency,exchange-rate,relational,amount 2 0 0 Difference Between Currency Exch. Rate and Relational Exch. Rate Amount 2016-12-13T10:13:51-07:00 17002649915 1 2016-12-07T11:24:24-07:00 0 0 Issue User is running Consolidations for all companies and having issues. Sequence of events: 2000 - Ran consolidations for all companies - worked - correct amounts to Retained Earnings 2001 - Ran all companies again - didn't work - incorrect amounts for three of the companies. The 2001 amounts posted to Retained Earnings are incorrect.  Same amount for revenue as net income. Solution When the YE close was done in the Consolidation Company by default the entire Retained Earnings amount was calculated and entered as a lump sum to a blank Business Unit Code.  When processing the YE close in a consolidation company the following must take place: Show the Business Unit Code field on the General Journal Form using "Show Columns".  Ensure to run the import database and select "By Business Unit" and enter the retained earnings account and document no. Go to the Year End Batch the entry was generated in and go to the last line.  This line must be re-entered with the individual amounts per business unit similar to the lines generated for the specific Revenue and Expense lines by Business Unit Code. Example: Change the retained earnings line from - 12/31/06  3300  Retained Earnings    300.00 To- 12/31/06  3300  Retained Earnings  BUSUNIT1  50.00 12/31/06  3300  Retained Earnings  BUSUNIT2  150.00 12/31/06  3300  Retained Earnings  BUSUNIT3  100.00 <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span class="current">User is running Consolidations for all companies and having issues.</span><br><br>Sequence of events:<br><br>2000 - Ran consolidations for all companies - worked - correct amounts to Retained Earnings<br>2001 - Ran all companies again - didn't work - incorrect amounts for three of the companies.<br><br>The 2001 amounts posted to Retained Earnings are incorrect.  Same amount for revenue as net income.<br></p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td><p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span class="current">When the YE close was done in the Consolidation Company by default the entire Retained Earnings amount was calculated and entered as a lump sum to a blank Business Unit Code.  When processing the YE close in a consolidation company the following must take place:</span><br><br>Show the Business Unit Code field on the General Journal Form using "Show Columns".  Ensure to run the import database and select "By Business Unit" and enter the retained earnings account and document no.<br><br>Go to the Year End Batch the entry was generated in and go to the last line.  This line must be re-entered with the individual amounts per business unit similar to the lines generated for the specific Revenue and Expense lines by Business Unit Code.<br><br>Example:<br>Change the retained earnings line from -<br>12/31/06  3300  Retained Earnings    300.00<br><br>To-<br>12/31/06  3300  Retained Earnings  BUSUNIT1  50.00<br>12/31/06  3300  Retained Earnings  BUSUNIT2  150.00<br>12/31/06  3300  Retained Earnings  BUSUNIT3  100.00<br></p></td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 25 17000037297 2016-12-12T15:06:13-07:00 17002649915 2 Trouble running Consolidations Statements not balancing by Business unit after YE close in Consol. Company Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,year-end,procedures,run,consolidation,statement,balance,business,unit,company 2 0 0 Trouble running Consolidations-Statements not balancing by Business unit after YE close in Consol. Company 2016-12-13T10:15:27-07:00 17002649915 1 2016-12-08T15:50:45-07:00 0 0 Issue When you import a G/L budget from Excel, the amounts are imported into the wrong periods in the North American version of Microsoft Dynamics NAV 2013. For example, January amounts are imported into December, February amounts are imported into January, etc.  Solution Cause This problem is caused by the way the .net variable DateTimeHelper.FromOADate(Decimal) function handles time zones. Resolution Add the line of code in bold to the ParseCellValue  function in table 370 - Excel Buffer:     IF ((STRPOS(FormatString,'y') <> 0) OR   (STRPOS(FormatString,'m') <> 0) OR   (STRPOS(FormatString,'d') <> 0)) AND   (STRPOS(FormatString,'Red') = 0)   THEN BEGIN   // Excel Date is stored in OATime format   Decimal += 0.5; // Add time offset to help FromOADate select the correct date.   DateTime := DateTimeHelper.FromOADate(Decimal);   "Cell Type" := "Cell Type"::Date;   "Cell Value as Text" := FORMAT(DT2DATE(DateTime));   EXIT;   END; Refer to https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?WTNTZSMNWUKNTMMYVWQXNRNXTVKNSKYVSSYWTSMSMUQSNKWW <table style="width: 100%;"><tbody> <tr> <td style="width: 11.4016%;"> <strong>Issue</strong><br> </td> <td style="width: 88.47%;">When you import a G/L budget from Excel, the amounts are imported into the wrong periods in the North American version of Microsoft Dynamics NAV 2013. For example, January amounts are imported into December, February amounts are imported into January, etc.<span> </span><br> </td> </tr> <tr> <td style="width: 11.4016%;"> <strong>Solution</strong><br> </td> <td style="width: 88.47%;"> <strong>Cause</strong><br>This problem is caused by the way the .net variable DateTimeHelper.FromOADate(Decimal) function handles time zones.<br><br><strong>Resolution</strong><ol><li>Add the line of code in bold to the <strong>ParseCellValue </strong> function in table 370 - Excel Buffer:  <br> <br>IF ((STRPOS(FormatString,'y') &lt;&gt; 0) OR  <br>(STRPOS(FormatString,'m') &lt;&gt; 0) OR  <br>(STRPOS(FormatString,'d') &lt;&gt; 0)) AND  <br>(STRPOS(FormatString,'Red') = 0)  <br>THEN BEGIN  <br>// Excel Date is stored in OATime format  <br><strong>Decimal += 0.5; // Add time offset to help FromOADate select the correct date.  </strong><br>DateTime := DateTimeHelper.FromOADate(Decimal);  <br>"Cell Type" := "Cell Type"::Date;  <br>"Cell Value as Text" := FORMAT(DT2DATE(DateTime));  <br>EXIT;  <br>END;</li></ol>Refer to <a href="https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?WTNTZSMNWUKNTMMYVWQXNRNXTVKNSKYVSSYWTSMSMUQSNKWW" rel="noreferrer">https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?WTNTZSMNWUKNTMMYVWQXNRNXTVKNSKYVSSYWTSMSMUQSNKWW</a><br><br><br> </td> </tr> </tbody></table> 17000122225 66 17000037559 2016-12-13T09:37:04-07:00 17002649915 2 G/L budget amounts are imported into the wrong periods G/L budget amounts are imported into the wrong periods Microsoft,Dynamics,NAV,ODT,Edsuite,General,ledger,GL,budget,amount,import,wrong,periods 2 0 0 G/L budget amounts are imported into the wrong periods 2016-12-08T15:50:45-07:00 17002649915 1 2016-12-02T13:40:28-07:00 0 0 Issue We seem to have lost our budget numbers in the account schedules.  Prior to this week, we could go into the account schedule and select the annual budget - this column is no longer populating.  Solution  When new budget entries are imported from Excel, the analysis views must be updated as well.  Go to Financial Management > Periodic Activities > Update Analysis views.  For the Code filter choose or type ALL, then click OK.  You will then see the message: All selected Analysis Views were updated successfully. This will update the Analysis view Budget entries <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> <table border="1" cellpadding="0" cellspacing="0" class="current" id="table89962" style="border-collapse:collapse; border:1px solid #afafaf;width:100%;"><tbody class="current"> <tr> <td><strong>Issue</strong></td> <td class="current">We seem to have lost our budget numbers in the account schedules. <span style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: small;"> </span>Prior to this week, we could go into the account schedule and select the annual budget - this column is no longer populating.</td> </tr> <tr> <td> <strong>Solution</strong> </td> <td> When new budget entries are imported from Excel, the analysis views must be updated as well.  Go to Financial Management &gt; Periodic Activities &gt; Update Analysis views.  For the Code filter choose or type ALL, then click OK.<span style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: small;">  </span><span style="box-sizing: border-box;">You will then see the message: All selected Analysis Views were updated successfully.<br style="box-sizing: border-box;"></span><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Arial; font-size: small;">This will update the Analysis view Budget entries<br> </td> </tr> </tbody></table> </div> 17000122225 94 17000036698 2016-12-12T14:50:04-07:00 17002649915 3 Account Schedule Budget We seem to have lost our budget numbers in the account schedules. Prior to this week, we could go into the account schedule and select the annual budget - this column is no longer populating. Microsoft,Dynamics,NAV,ODT,Edsuite,Financials,Payables,Ledger,Account,Schedule,Budget,Analysis,View 2 0 0 Account Schedule Budget 2016-12-13T10:12:08-07:00 17002649915 1 2016-12-07T10:55:52-07:00 0 0 Issue Error Message Received when trying to post a general journal entry (in this example an Intercompany FX journal entry).  "Tax Calculation Type must be Sales Tax in Gen. Journal Line Journal Template Name='General', Journal Batch Name='INTERCOMP', Line No.='10000'." Solution CAUSE:This message occurs if the General Posting Type is incorrect or blank for any of the entries in the journal posting. SOLUTION:Enter the correct General Posting Type for the type of entry (i.e. Purchase) and post. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">Error Message Received when trying to post a general journal entry (in this example an Intercompany FX journal entry). </span><br></p> <br><br><span rel="tempredactor"><strong>"Tax Calculation Type must be Sales Tax in Gen. Journal Line Journal Template Name='General', Journal Batch Name='INTERCOMP', Line No.='10000'."</strong></span><br><table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current"> <strong>CAUSE</strong>:This message occurs if the General Posting Type is incorrect or blank for any of the entries in the journal posting.<br><br><strong>SOLUTION</strong>:Enter the correct General Posting Type for the type of entry (i.e. Purchase) and post.<br> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 43 17000037287 2016-12-12T14:50:42-07:00 17002649915 3 Tax Calculation Type Error Tax Calculation Type Error Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,journal,entry,journal-entry,tax,calculation,type,error 2 0 0 Tax Calculation Type Error 2016-12-13T10:13:34-07:00 17002649915 1 2016-12-07T11:06:24-07:00 0 0 Issue After running the month-end foreign exchange for October, half the automatically-generated entry got posted to October 31 (Ending Date Field) and half of it got posted on Nov. 15 and 29.(Nov. Cheque Run Dates)  Note: Each month, the fx activity is run more than once because out late invoices in. The one in October I am referring to was the third and final running of fx. Solution Cause: It appears that unrealized gains/losses are handled differently in v2.6 than in 4.0:   The same scenario in a 2.6 database is when both invoice and payment are posted prior to running the Adjust Exchange Rates batch job -- nothing is posted when running this job - ie. no postings at all to Unrealized Exchange Rate Losses acct.   Example 1 -- where the Adjust Exchange Rate batch job is run prior to the payment posting -- works the same in both versions.   V4.0 is handling unrealized gains/losses in a more accurate manner. Results of an extenstive review of GL entries created during the adjust exchange rate batch job: a.  that this is not occurring as a result of the upgrade to 4.00sp2 b.  that the Adjust exchange rates batch job is working as it should. The entries to later dates than specified in the ending date field for the batch job are posted because Adjust Exchange Rates Batch job is run after payments have been posted into the next period for invoices that were open at the end of the period that the Adjust Exchange Rates batch job is running for. As the Adjust Exchange Rates job is running everal times and users are continuing to post invoices back in time, the entries with later posting dates can be explained by the timing of posting invoices, payments and exchange rate adjustments. Attached is a document explaining the functionality with examples. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><span rel="tempredactor">After running the month-end foreign exchange for October, half the automatically-generated entry got posted to October 31 (Ending Date Field) and half of it got posted on Nov. 15 and 29.(Nov. Cheque Run Dates) </span><br></p> <br><br><span rel="tempredactor" style='font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px;'>Note: Each month, the fx activity is run more than once because out late invoices in. The one in October I am referring to was the third and final running of fx.</span><br><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td class="current"> <span style="box-sizing: border-box;">Cause:</span><br style="box-sizing: border-box;"><br style="box-sizing: border-box;">It appears that unrealized gains/losses are handled differently in v2.6 than in 4.0:  <br style="box-sizing: border-box;"><br style="box-sizing: border-box;">The same scenario in a 2.6 database is when both invoice and payment are posted prior to running the Adjust Exchange Rates batch job -- nothing is posted when running this job - ie. no postings at all to Unrealized Exchange Rate Losses acct.  <br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Example 1 -- where the Adjust Exchange Rate batch job is run prior to the payment posting -- works the same in both versions.  <br style="box-sizing: border-box;"><br style="box-sizing: border-box;">V4.0 is handling unrealized gains/losses in a more accurate manner.<br style="box-sizing: border-box;"><br>Results of an extenstive review of GL entries created during the adjust exchange rate batch job:<br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;">a.  that this is not occurring as a result of the upgrade to 4.00sp2<br style="box-sizing: border-box; color: rgb(0, 0, 0); font-family: Verdana, Arial, sans-serif; font-size: 12px;"><br style="box-sizing: border-box;">b.  that the Adjust exchange rates batch job is working as it should. <br style="box-sizing: border-box;"><br style="box-sizing: border-box;">The entries to later dates than specified in the ending date field for the batch job are posted because Adjust Exchange Rates Batch job is run after payments have been posted into the next period for invoices that were open at the end of the period that the Adjust Exchange Rates batch job is running for.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">As the Adjust Exchange Rates job is running everal times and users are continuing to post invoices back in time, the entries with later posting dates can be explained by the timing of posting invoices, payments and exchange rate adjustments.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;">Attached is a document explaining the functionality with examples.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 100 17000037291 2016-12-12T14:51:38-07:00 17002649915 3 Adjust Foreign Exchange Batch Job Adjust Foreign Exchange Batch Job Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,multicurrency,adjust,foreign,exchange,batch 2 0 0 Adjust Foreign Exchange Batch Job 2016-12-13T10:13:51-07:00 17002649915 1 2016-12-07T11:08:45-07:00 0 0 Issue G/L Account Setup and Exchange Rate Process Solution See attached document for instructions and examples. <div dir="ltr"> <table border="1" cellpadding="0" cellspacing="0" id="table60064" style="border-width: 1px; border-style: solid; border-color: rgb(175, 175, 175); width: 100%;"><tbody> <tr class="current"> <td><strong>Issue</strong></td> <td> <p class="current" style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;">G/L Account Setup and Exchange Rate Process</p> <p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> <table cellpadding="0" cellspacing="0" style="box-sizing: border-box; background-color: rgb(255, 255, 255); color: rgb(80, 99, 135); font-family: Verdana, Arial, sans-serif;" width="100%"><tbody style="box-sizing: border-box;"></tbody></table> </td> </tr> <tr class="current"> <td><strong>Solution</strong></td> <td>See attached document for instructions and examples.<br style="box-sizing: border-box;"><br style="box-sizing: border-box;"><p style="box-sizing: border-box; margin-bottom: 10px; line-height: 14px;"><br></p> </td> </tr> </tbody></table> <br><br><p><br></p> <div dir="ltr"> <p style="box-sizing: border-box; margin: 0in 0in 12pt; color: rgb(0, 0, 0); font-size: 12px; line-height: 14px; font-family: Verdana, Arial, sans-serif;"><br></p> <p><br></p> <p><br></p> <div dir="ltr"> <p><br></p> <p><br></p> <p><br></p> </div> </div> </div> 17000122225 65 17000037292 2016-12-12T14:51:48-07:00 17002649915 4 G/L Account Setup and Exchange Rate Process G/L Account Setup and Exchange Rate Process Microsoft,Dynamics,NAV,ODT,Edsuite,general,ledger,multicurrency,GL,account,setup,exchange-rate,process 2 0 0 G/L Account Setup and Exchange Rate Process 2016-12-13T10:13:51-07:00 17002649915