Dynamics 365 Finance

It would be nice to extend the Invoice Id to at least 30 length. It's not country specific, but world wide need. Unfortunately, Shorter number (what means wrong number of the invoice) will be reflected in bookings and in SAF-T file (XML files required by the Authority in Poland). Manual workaround exists, to manually correct the SAF-T file before sending to government, but this is not a good approach because still the wrong number is in the system and is not the same like on reports send to tax authority which can effect on penalties as well. From July 2019 there is an addition to the regulations of the information reported in SAF-T files, stating that if information is incorrect there is a charge of 500 PLN for each mistake.

It would be useful if you could replicate the PO prepayment functionality and apply similar functionality on the sales order side.  We frequently have requests from clients to be able to create payments in advance from customers and link them to a SO.  I know it is possible to create a prepayment journal and link that to the sales order using existing functionality but the problem is there are limitations.  These are as follows:- 

1) You can't generate an invoice off the back of the prepayment 

2) It is not easy to see what prepayments you have generated in the system with remaining balances.

3).  It would be a simpler process if you could generate the prepayment directly from the SO, similar to the PO prepayment function.

In the pending invoices screen is should be possible, as it is in the invoice approval screen, to select an accruals scheme that allows an invoice to be distributed across a number of periods. Ideally, it should be possible to select the scheme on line level.

In Dynamics 365 for Finance and Operations, Trial Balance (General Journal > Inquiries and reports > Trial balance) is displayed with Main accounts and Dimension segments in separate columns. This is enabled by the parameter "Display segments in separate columns". Hence, when the Trial Balance is exported to excel, all segments are exported into separate columns in Excel too.

Similar functionality is also required in all other places where we view financial transactions viz. Voucher transactions (General Journal > Inquiries and reports > Voucher transactions).

Currently, when Voucher transactions (posted data) are exported into excel, segments and main account is combined into a single column, and hence not understandable which segment value belongs to which Segment.

Hi, Running the collection letter process allows generating a collection letter document that can be send out to the customer for example by email. This is a great functionality. What is missing though is that one wants to attach the invoices included in the collection letter to this email that goes out to the customer. That is because many customers call once they receive their collection letters and ask for a copy of the invoice(s). Sending them directly with the collection letter alleviates and speeds up this process. Would be great if this could be implemented with one of the next releases. Many thanks, Ludwig

Transaction-based financial dimension:

There was an easy-to-implement possibility to largely improve GL reporting and analysis capabilities by extending the ledger integration by financial dimensions.

In several setups, a posting integration is defined by ledger account defined in the posting profiles and some additional set-up tables (i.e. item postings, resources postings, fixed asset postings, indirect cost postings, project postings, bank postings, customer/vendor postings, automatic postings, etc.).

The idea is to add financial dimensions to the main account entries. The filled dimension depends on the posting type / transaction type and brings all types of transactions together (cross-module) and hence makes it easier to run reports on GL postings on general level.

Advantages:

1. Quite easy to implement since the framework is already there.

2. Separation of quantity values from transaction values in the GL - more transparancy

3. Enables cash-flow statement according to the direct method as required in financial reporting of many groups of companies

4. Enables standard reports (tax development, provision development, cash development, fixed asset balances, inventory changes) or makes it easier to create from GL (using financial reporting)

5. Reduces number of required GL accounts

This kind of "movement" or "flow" analysis is almost always required by customers but so far hardly supported by D365. The extension brings big improvements by low effort.

When the asset is terminated at the end of lease period, the accumulated depreciation value left in the account is not being reversed. And the value is being carry word to every year.

Hence user is manually posting an adjustment entry to Knock off the value present under the accumulated depreciation account.