Øyvind Berg-Olsen Solutions architect

The OData entity BusinessDocumentTaxTransactions only includes the basis amount in transaction currency.

D365FO allows to report tax in a currency different from the transaction and accounting currency and to make this entity complete it should include all three currency amount groups:

ACCOUNTING CURRENCY

• Amount Origin
• Actual sales tax amount
• Actual nondeductible sales tax

SALES TAX - CURRENCY

• Amount origin
• Actual sales tax amount
• Actual nondeductible sales tax

TRANSACTION CURRENCY

• Amount origin
• Actual sales tax amount
• Actual nondeductible sales tax

The bank file i.e. ISO20022 camt053 files reside in Sharepoint but the import bank statement does not support Sharepoint, only browsing for files.

It is possible to set up an electronic reporting source entry which connects to document types defined with Sharepoint addresses.The import of bank statement should also have the functionality to automatically move files based on the setup below as already exists for ISO20022 Camt054 and ISO20022 Pain.002 files:

Source settings / Sharepoint in Electronic reporting source

• Document type for input sources
• Document type for imported files
• Document type for files with warnings
• Document type for failed files

Autogiro is used for direct debet payment and we would like to update the payment journal lines with a confirmation of bank payments executed, based on the ISO20022 Camt.054C format. By matching the paymentID to existing payment lines it should be possible to distinguish between existing Autogiro lines and new customer payments.This should be done by importing the Camt.054C file into the Payment transfers page similar to this Swedish functionality:

"Bankgirot Autogiro returns format for the direct debit payment format of the same name. These messages can be imported as a response to direct debit messages that were previously exported. Currently, these payments are represented in Operations as payment journal lines with a Sent status. To import a file, complete the following steps.

Go to the Payment transfers page.

Click Return file-customer.

In the dialog box, select corresponding method of payment, and then browse to the location of the file to import.

After you import the return file, the payments should be updated to the status Approved."

Description:

Currently, the ability to define bank accounts based on currency using the BankVendPaymModeBankAccounts and BankCustPaymModeBankAccounts tables is restricted to legal entities with the country code NOR (Norway). This functionality is extremely valuable for multinational organizations that operate in multiple currencies and need to automate bank account selection during payment proposal generation.

Business Impact:

Manual bank account selection increases the risk of errors and inefficiencies.

Organizations outside Norway must implement customizations to replicate this functionality.

Lack of global support for this feature limits the scalability and usability of D365 Finance in multi-country deployments.

Requested Enhancement:

Make the currency-dependent bank account selection feature available for all country codes, not just NOR.

Allow configuration of bank accounts per currency in the payment method setup for vendors and customers.

Ensure compatibility with payment proposals and journal generation processes.

Benefits:

Reduces manual intervention and errors in payment processing.

Enhances automation and compliance with banking requirements.

Improves user experience and consistency across legal entities.