Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 296 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Consolidation and Translation Methods
quidamm
Member Posts: 12
I'm trying to import Consolidation files (XML format) from a separate database in a different currency. Ideally I'd like to use the exchange rates from the subsidiary companies (external DB). From my research, testing, and code deciphering it appears Navision only uses the subsidiary exchange rate if I choose 'Historical Rate' as the translation method for every GL Account. Unfortunately... I don't believe this is GAAP compliant. Not really clear why 'Historical Rate' is even an option. Really need to have 'Closing Rate' for all Balance Sheet accounts and 'Average Rate' for all Income Accounts.
Does this make sense to anyone? Am I missing something or is Navision just not working properly here? Any input would be helpful. Thanks in advance and hope to see you at Directions in Atlanta next month!
Does this make sense to anyone? Am I missing something or is Navision just not working properly here? Any input would be helpful. Thanks in advance and hope to see you at Directions in Atlanta next month!
The problem's usually between the chair and the keyboard!
0