Request

• Microsoft Dynamics for Finance & Operations is per design summarizing voucher transactions which have the same accounting string.
• Current Batch transfer rules indicates that the general ledger transactions should NOT be summarized

• The product is currently grouping the voucher transactions based on the following entities;
o Voucher Number
o Posting date
o Ledger account
o Main account

Business justification

To easily manage general ledger transactions, we need to make sure that the voucher transactions with the same accounting string are not summarized.
The business would need to be able to manage and analyze postings in General ledger in an accurate and efficient way.
The split is required for traceability and reporting purposes.

Example
 Free text invoice posted
 Two lines added with the same accounting string


Outcome

The general ledger transactions are summarized per accounting string.
Description is only captured for the first line item. Related to the following idea:
https://experience.dynamics.com/ideas/idea/?ideaid=35387ade-35b1-ea11-8b71-0003ff68c1c4

The same logic is recognized in different levels of the system. The same can be found when transferring 2 or more subledger journal entries with the same accounting string.
One other example is easily visualized when the system recognizes 2 new transactions in the stage of importing the bank statement for reconciliation purposes.
- Both transactions are mapped towards the same bank transaction type + Main account
- The system will in the stage of posting the bank statement – summarize the accounting entries