Issues with posting description

bhwong
Member Posts: 13
Our Sales Invoices are mainly using Resource or G/L Account type rather than Item and has been heavily customized. This is because we have 3 Finance Departments with difference businesses and requirements sharing a common database and reports.
In our situation, if our invoice has 10 G/L Account items of the same G/L code, they will be posted into G/L as 10 separate entries using the line description but posted into Customer Ledger as 1 merged entry using the posting description. To me, this is inconsistency. Both G/L and Customer Ledger Table should be having the same entries, isn't it?
However, if our invoice has 10 Resource items of the same Resource code, they will be posted into G/L as 1 merged entry using posting description append with billing period, same as Customer Ledger Table behaviour.
The problem with using posting description that used the first line description append with period is that if the first line item is water bill and second line description is electricity bill, the G/L Code under electricity bill will also receive water bill description append with the billing period. Unless we switch to use line description and not merge the line items, which will make G/L ledger extremely lengthy.
I would like to know the default NAV behaviour and the common practice in your companies regarding how Sales Invoices with multiple sales line items get posted into the General Ledger and Customer Ledger.
In our situation, if our invoice has 10 G/L Account items of the same G/L code, they will be posted into G/L as 10 separate entries using the line description but posted into Customer Ledger as 1 merged entry using the posting description. To me, this is inconsistency. Both G/L and Customer Ledger Table should be having the same entries, isn't it?
However, if our invoice has 10 Resource items of the same Resource code, they will be posted into G/L as 1 merged entry using posting description append with billing period, same as Customer Ledger Table behaviour.
The problem with using posting description that used the first line description append with period is that if the first line item is water bill and second line description is electricity bill, the G/L Code under electricity bill will also receive water bill description append with the billing period. Unless we switch to use line description and not merge the line items, which will make G/L ledger extremely lengthy.
I would like to know the default NAV behaviour and the common practice in your companies regarding how Sales Invoices with multiple sales line items get posted into the General Ledger and Customer Ledger.
0
Comments
-
It is a standard behaviour: one entry per document in customer ledger and one or more entries i G/L, which are grouped by different values (posting groups, account no. etc.).0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions