Dynamics 365 Finance

When adding a Ledger accruals to a vendor invoice, the description of the accrual line vouchers is taken from the accrual scheme. There is no concrete link between the vendor invoice number and the related accrual transactions. For (year-end) audits and month end closing it can be important to have a link between the accrual lines in the ledger and the original invoice where they are based on.

Therefore my idea would be to be able to add a direct link between the vendor invoice number and the related created accrual lines in the ledger. For example via:

• A parameter in AP where you can decide that the vendor invoice number is automatically added in the field ‘Description’ on each related accrual line instead of using the description from the accrual scheme or in addition to the description from the accrual scheme.
• And / or being able to create a Default description for this accrual postings to add information like vendor invoice number.
• And / or being able to find the link between all postings via the option ‘Related vouchers’ in the created voucher transactions. 

My Client receives a high volume of zero valued invoices relating to the scenario where faulty/damaged stock is replaced by a supplier and they issue zero value invoices for the replacement of the stock that is faulty or damaged instead of issuing a credit note and re-invoicing for the new stock at the normal cost. 

When a PO is created for the zero value stock, It is possible to process an invoice directly against the PO, however it is not possible to post the invoice to the invoice register to be matched later to the PO 

When attempting to add the invoice to the invoice register, and then match the invoice to the PO, it is not possible to post the invoice on the invoice register, you receive the error message "Posting without amount cannot be made"

My client needs to be able to raise these invoices on the invoice register so that they have a consistent process for their staff for processing purchase invoices.

If it is possible to post the invoice against the PO it should be possible to post the invoice on the invoice register as well.

Please can this be fixed so that these invoices can be processed via the Invoice register?

It can take months of effort to train the custom invoice model. This must first be done in a UAT/test environment so that we can ensure proper functionality before bringing to production. However, when our testing is completed there isn't a way to move the model and it's training to our production environment. This significantly limits our ability to implement custom models due to the time needed to invest in the training. The model and it's training should be able to be promoted to production and also copied to other environments.

Starting from 01.01.2025 it is mandatory to be able to receive electronic invoices in B2B Business context in Germany. The legal requirement will be implemented in steps depending on company size etc.

However Microsoft released the ability to send Electronic invoices via xml in the ubl syntax. So far so good.

This is meeting legal requirements.

When receiving invoices however customers are dependent on what format the vendor sends and are not allowed to deny a transmitted invoice. There are 2 main formats used: Zugpferd and XRechnung. While MS decided to go for a standard solution with the XRechnung the vendor can still choose between the syntaxes UBL or CII. So far MS does not cover the import of CII which is a legal requirement as described.

This functionality should be added since it is a must!

As per below regulations all description elements in SAF-t (LT) should be automatically truncated to 256 characteds (purchase/sales invoice, invoice lines description, GL and FA desctiptions and Payment descritpions):

SAF-T legislation in Lithuania

• Article 16 of the Law on Accounting;
• Resolution No 699 of 01 July 2015 of the Government of the Republic of Lithuania;
• Order No VA-49 of 21 July 2015 of the Head of the State Tax Inspectorate under the Ministry of Finance;
• Specification of XSD description of the XML scheme of SAF-T, as prepared by the State Tax Inspectorate under the Ministry of Finance.

Schema in english:

https://www.vmi.lt/evmi/documents/20142/725548/SAF-T_XSD_specifikacija_v2.1_F+en.pdf/23775a8a-0ba7-6b9c-1fc9-cfceb4ba8bd0?t=1606462594737

Reg ticket number 2502051420001009.

Becasue of missing limitations such errors appears and XML for SAF-t (LT) is not accepted:

ERROR: Element '{https://www.vmi.lt/cms/saf-t}Description': [facet 'maxLength'] The value has a length of '267'; this exceeds the allowed maximum length of '256'.

Within Accounts receivable parameters > Update > Invoice there is a parameter called "Default language for sales invoices". This parameter can be set to "Order account" or "Invoice account".

When selecting "Order account" the invoice will always be printed in the language that is stored at the customer account that is currently selected within the sales order - that's fine.

When selecting "Invoice account" in the parameter then the invoice will always be printed in the language of the invoice account that is stored at the customer account at the time when the customer is selected. Though, it can occur that the invoice account will get changed on purpose within the sales order. The new invoice account might have a different language stored. But the invoice is not printed in the deviating language.

This leads to the fact that in these cases the invoice will be printed in a language that the invoice account doesn't speak, neither maybe does the customer account. So, none of them would understand the invoice properly.

The idea is that by setting this parameter to "Invoice account" the system will always consider the invoice account, that is currently selected in the sales order, and not the default invoice account language of the customer account.

Current situation

It is not possible to change the parent amount on the billing schedule line entity. In case an update is processed on the billing schedule line entity for the parent amount for example via Excel add in or dual write, the parent amount is not allocated to the revenue split child lines.

With 10.0.42 it is possible to change the parent amount directly in the billing schedule form and the amount is correctly allocated to all child lines.

Suggested solution

Similar to the behavior in the billing schedule form, it should be possible to change the parent amount via the billing schedule line entity and the parent amount is allocated to all child lines, so that the same process can also be used via interfaces such as in the standard via dual write.

Currently in Budget Control Parameters, we are only able to select one Account Structure. This limits our ability to use budget control on accounts if they are across multiple Account structures.

Navigation: Budgeting > Setup > Budget Control > Budget Control Configuration > Define Parameters (tab)

Field: Account Structure 

Only selection of one Account Structure is Possible.

Often it does not make sense to have all financial Dimensions in one account structure for all ledger accounts. It should be possible to use Budget control on more than one account structure.

When posting an hour journal via Project management and accounting > Journals > Hour AND Project management and accounting > Journals > Dynamics 365 for Project Service Automation integration journal, the data displayed in the existing columns available in Accounting Source Explorer is insufficient for performing a detailed ledger/subledger analysis.

The columns Document, Document date, Account entry description, Destination company, Party number, Party name, Activity number, Category name, and Line property are all available in the ASE, but they do not contain data when the transaction is originating from an hour or PSA journal entry.

For instance, while the originating document (the hour journal) contains key columns such as Document, Document date, Account entry description, Destination company, Party number, Party name, Activity number, Category name, and Line property, the data from these fields is not carried over into the Accounting Source Explorer, resulting in a lack of traceability and detail.

This creates challenges when posting standard hour journals in F&O and also shows the limitations of the Project Operations non/stocked product. As an out-of-the-box integration between CE and F&O, its maturity is brought into question, as all transactions flowing from CE to F&O are processed as journals which would actually mean that all hour transactions would lack the necessary detail for analysis from a subledger perspective through the Accounting Source Explorer.

With this idea, we want to retrieve the data from the columns mentioned above into the Accounting Source Explorer, no matter what the originating document is.

Suggestion for improvement and time saving of vendor invoice payments: We as a company pay vendor invoices in several different currencies. In our bank we have different bank accounts for each currency for the outgoing payments. Now we need to make one payment file for each currency (outgoing bank account). It would be more time efficient if it was possible to create one payment file including all the vendor invoices and currencies, meaning the possibility to have several outgoing bank accounts in one vendor payment file.