-
Posting layer for inventory transaction
It would be useful to set a specific posting layer for each specific posting type defined in the inventposting rules. In this way, it would be possible to exclude from the “current” posting layer, which is the one used for official fiscal book, the transactions that typically are not mandatory for fiscal purposes (i.e. monthly accruals for depreciation in Italy or other periodic managerial transactions) or simply do not belong to the fiscal book (i.e. the transactions for cost of good sold accounting system in Italy, since in Italy the accounting system is stock variation). For these posting rules, the most appropriate posting layer is “operation” and not “current”. -
Different company's bank account in the customer Invoice
In the customer invoice (free text invoice, from sale order and project invoice) it would be helpful to manage different company's bank accounts for a specific customer or customer group instead of having just a default one for all the customer invoices. A solution could be the creation of a specific field in the “Payment” section of the invoice such as “our bank” where you can select the desired company bank account. -
Massive update sales item group in pending vendor invoice
It would be usefull to have a procedure that allows the massive update of the Item sales tax group or the sales tax group in the pending vendor invoice line instead of update every single line. -
Enable Financial Tag Field for "Generate Voucher" Action in Advanced Bank Reconciliation Matching Rules
Idea Summary:
In Microsoft Dynamics 365 Finance and Operations, within the Advanced Bank Reconciliation functionality, the matching rules allow users to perform automatic actions such as "Generate Voucher." However, when using this action type, it is currently not possible to input or assign a financial tag (also known as a financial dimension tag).
Proposed Enhancement:
Extend the capabilities of the "Generate Voucher" action in reconciliation matching rules to allow users to specify a financial tag. This would ensure that vouchers generated during reconciliation are properly classified and aligned with financial reporting requirements.
Business Value:
- Improved accuracy in financial reporting through better tagging and classification of generated vouchers.
- Enhanced automation by reducing the need for manual voucher adjustments post-reconciliation.
- Consistency in financial tagging across all types of transactions, including those created automatically via reconciliation rules.
Use Case:
A company that uses financial tags extensively for internal reporting needs to ensure that all transactions, including automatically generated vouchers during bank reconciliation, carry the correct tag.
Suggested Implementation:
- Add the Financial Tag field as an editable input option when configuring the “Generate Voucher” action within the reconciliation matching rule setup.
- Ensure this tag is applied to the resulting voucher transactions.
You’re offline. This is a read only version of the page.
