Sten Baumgarten CGI Danmark Functional Architect

Companies with fixed assets that generate financial statements based on IFRS must revalue their fixed assets, e.g. aircraft and shipping companies. This may result in separate fixed assets that must be depreciated with a different service life than the fixed asset the new fixed asset is related to. 

The revaluation might end up with a negative amount, that must be stated as a liability in the financial statement and depreciated as a normal fixed asset with a positive amount.

The functionality requested is the same as for a “traditional” fixed asset with a positive acquisition value:

1. Creating depreciation proposal in a fixed asset journal
2. Create depreciation proposal across companies

In platform update 6 it is possible to import lines into a general journal, but it is only possible to import main account and not financial dimension values that must be included before the journal can be posted. 

Customization are described by Microsoft, but instead of making the customization, I will prefer that the functionality are included in the standard solution. 

Currency rates can be imported from a currency rate provider, e.g. ECB. The currency rates imported are all against EUR (EUR-USD, EUR-GBP, EUR-CAD).

When a legal entity use another accounting currency than EUR e.g. GBP and post transactions with a transaction currency different from EUR e.g. CAD, D365 need a currency rate for GBP-CAD before the transaction can be posted. 

The currency pair and currency rates can be created and maintained manually. Often the customer want to automate the ECB import and update of the additional currency pair rates and a customization are made. 

I prefer that the calculation of the additional currency pair rates can be configured and run automatic based on the currency rates imported from ECB.

I don't know if that update can be done by exporting the ECB rates as a recurring job from the Data management workspace, have the calculation of additional currency pairs done automatic outside D365 and have a recurrent job import and update the exchange rate type selected on Ledger automatic, but this solution are less user friendly. 

Working with Pending vendor invoices can be more efficient if the user have the ledger account available on the Pending vendor invoice line instead of the user have to select Financials > Distribute amount on the invoice line.

Often the same vendor invoice contain both items and the related charges (freight, duty, insurance). When posting the vendor invoice against the related voyage in Landed cost module the charges must be allocated againts the Auto cost for the voyage.

Today it is not possible to allocate the charges against the Auto cost. This means that it is timeconsuming in inefficient to post these vendor invoices.

The currenct proces to invoice charges related to a voyage is to create an vendor invoice journal, select the voyage and allocate the invoice against the Auto cost for the voyage. Often transpost invoices (charges) contain transports for multiple voyages. It is not possible with the current standardfunctionality in D365FO to allocate transport invoices against several voyages. The invoice must be split into several invoices and interim vendor and main accounts must be used to post one invoice. This is timeconsuming and inefficient and increase the risk for errors.

When you select posting type for e.g. posting validation on a main account you cannot filter on the available posting types, but you have to find the correct type manually scrolling down and find it between the aproximately 200 available types.

The idea is the create the same filter functionality as we have around in D365FO (Begin with, Contains etc.).

Posting type is not only selected on a main account but also in other parts of D365FO e.g. auto charges.

When a company within EU sell to a customer who does not have a valid VAT registration, the transactions cannot use intracommunity VAT calculation. Domestic VAT must be calculated instead.

In principle a company must validate that the VAT registration is valid every time the company sell to an EU customer to avoid calculating domestic VAT.

Since this is a manual procedure, this is often not done. Instead we need this to be automated,

The European Commission have create a website where it is possible manually to validate if a VAT registration is valid or not.

Wen site is called "VIES VAT number validation"

Idea: a functionality in D365FO that can be set up to on a daily basis to make that check for all VAT registrations in the Tax exempt number table.