When the customer has more than one CT-e for different Vendors within the month and for each situation, a different Credit base source is used.

Due to this scenario, when records D101 and D105 are generated, in the 5th field called NAT_BC_CRED, only the first information in the Credit base source field is generated.

e.g Vendor BRMF-000003

|D100|0|1|2_BRMF-000003_58871657000104|57|00|057||572110001|35231058871657000104570575721100017533544564 |21102023|2110202 3|0||3300,00|0,00|0 |3300,00|3300,00|594,00|||5.1.1.3.08|

|D101|2|3300,00|56|13|3300,00|1,6500|54,45|5.1.1.3.08|

|D105|2|3300,00|56|13|3300,00|7,6000|250,80|5.1.1.3.08|

e.g Vendor BRMF-000002

|D100|0|1|2_BRMF-000002_11613525000119 |57|00|057||231002357|35231011613525000119570572310023570283340309|21102023|21102023|0||2150,00|0,00 |0 |2150,00|2150,00|387,00|||5.1.1.3.08|

|D101|9|2150,00|56|13|2150,00|1,6500|35,48|5.1.1.3.08|

|D105|9|2150,00|56|13|2150,00|7,6000|163,40|5.1.1.3.08|

1. Parameter "Require manual matching with advance bank reconciliation find multiple documents that match on amount" is set to yes. The bank statement has transaction code 195 and two lines for the same amount of 2500 dated 01-Jul-23, but the D365 bank transaction has one line for of 2500 dated 01-Jul-23. A bank reconciliation rule is created where the bank statement line transaction code is 195 and in bank transactions, it will match with amount and date. Here, D365 is randomly matching one statement line amount of 2500 with a bank transaction line amount of 2500. D365 should stop matching if statement find two/more lines with same amount, as it could match the wrong statement line with the wrong transaction line.
2. Many customers use BAI2 statements or other statements as provided by their bank which does not mention its a reversal transaction. For the reversed transactions in the bank statement, the imported statement from BAI2 format in D365 does not enable the Reversal field. It is not possible to clear the statement reversal transaction with the statement positive transaction manually and also by the reconciliation rules in the reconciliation worksheet. Solution is required for this issue as first step in reconciliation to clear the reversed transaction.
3. Bank transaction types should allow selecting account type (Ledger, Bank etc.) and Account. A new parameter which override the 'Allow multiple transactions within one voucher' will be applicable for this. This will allow auto creation of transaction from bank for bank to bank transfer.
4. Default description for offset account. Bank account generally entered as offset account (vendor payment journal, customer payment journal). D365 should allowed auto defualt description to be created for offset accounts as well.

Other related idea for advance bank reconciliation - https://experience.dynamics.com/ideas/idea/?ideaid=09763ae3-de7e-ee11-a81c-6045bd8043.

Quando criamos um produto, ao exportar no arquivo texto o registro 0200 está considerando o campo SEARCH NAME ou INVÉS do campo PRODUCT NAME.

Exemplo:

Item number = BRMF010

Search name = BRMF010

Product name = Caixa acústica padrão 100W

Arquivo texto gerado registro 0200

|0200|BRMF010|BRMF010|||pcs|04|85182200||85||12,00||

Deveria carregar na 3 coluna = Caixa acustica padrão 100W.

Title

Support for Vendor-Related Entries in Malaysian E-Invoicing System for D365 F&O

Description

Background

Currently, the Malaysian e-invoicing implementation in Dynamics 365 Finance and Operations provides limited functionality for linking invoices to their source documents. As confirmed by Microsoft Support, the system does not support linking e-invoices to employee or vendor-related entries.

Requested Enhancement

We request Microsoft to extend the Malaysian e-invoicing globalization features in D365 F&O to include:

1. Full traceability between e-invoices and vendor-related transactions
2. Support for linking vendor entries to e-invoices generated in the system
3. Comprehensive audit trail functionality for vendor transactions in the e-invoicing workflow

Business Impact

This enhancement would:

• Improve compliance with Malaysian tax regulations
• Streamline audit processes for finance teams
• Reduce manual reconciliation work
• Enhance reporting capabilities for vendor-related transactions

Urgency

As Malaysian e-invoicing requirements continue to evolve, this functionality is becoming increasingly critical for businesses operating in the region.

Enhancement to the feature Awareness between ledger settlement and year-end close

Issue: If we are using ledger settlement and above feature retrospectively we are facing an issue related to same. Since the ledger settlement page does not allow to post the cross year settlements in the system and it throws an error that we need to select the same fiscal year. This type of the cross year settled transactions are generated and are related to AP or AR transactions which is a standard process followed in the business.

Solution:

To identify whether the settled transactions are done through the ledger settlement functionality when reviewing the cross year settlement page, we can add a flag indicating if the customers has generated this transactions using the ledger settlement functionality or not. This will allow customers to implement ledger settlement functionality retrospectively by not reversing the cross year settled transactions.

Additionally to the above process we can have a field indicating date when the ledger settlement functionality and advanced awareness options parameters was turned on and also history related to when the toggles were set to No.(As provided in the budget control configuration change history. Path: Budgeting > Setup > Budget control > Budget control configuration)

Ability to define the settlement ID number sequence to be used in the ledger settlement functionality and advanced awareness option.

Example: We are currently using 10.0.41 version and wanted to use the ledger settlement functionality and advanced awareness option retrospectively. For example for the year 2020 we wanted to use both the features and there were cross year settled transactions which we did not want to reverse the transactions as those transactions were related to AP or AR module. Hence, we were not able to use the functionality in the system.

Conclusion:

By implementing these changes, customers will be able to effectively leverage the ledger settlement functionality without disrupting their historical transactions or requiring reversals, even for cross-year settled AP/AR transactions. This solution will improve operational efficiency and ensure that the system supports both new and legacy business processes.

Ability to Import and automate the inbound XML(Invoice) in Dynamics 365 Invoice Capture solution.

Necessity for this?

1. It is recommended that business users monitor inbound e-invoices in D365 Finance

2. While the information in the XML (Invoice) is sufficient for approval by business users, it should be presented in a more visually appealing format, such as a PDF

3. The majority of European Union customers need above mentioned points as Out-of-the-Box feature in Invoice capture

4. A country like Italy considers Inbound XML (invoice) as "legal" invoice

These are few missing components in the out-of-the-box solution:

The current invoice capture solution lacks this functionality

1. A custom solution is needed to import and view the inbound invoices

2. Customer need OOB feature instead of relying on ISV solutions such as Exflow, for an invoice approval process

We request this functionality to be available in Invoice capture solution, to make it easier for business users to view the inbound invoices and carry out their day-to-day activities.

Regards,

Rakesh Darge

Cash and Bank management > bank statement reconciliation > Bank transaction form

Here there is an option for reconcile, but no option for un-reconcile.

It is really helpful if the option can be added.

Belgian companies need to annually file a VAT list with all Belgian tax dutiful customers listed by enterprise number, their turnover and the total VAT amount charged. The report is to be generated as an xml file and has to uploaded to the Intervat website.

A report is available for this in D365FO (menu Tax, report 'invoice turnover report - Belgium') and an ER format (Invoice turnover report (BE)). This works fine in legal entities with just one VAT number.

When using multiple VAT registrations there is no option to link the report to just one of the company's registration ID's as you can do with the VAT declaration, the EU sales list and the Intrastat declaration.

The result is that in the annual listing all turnover to Belgian customers is included, not limited to the sales done from the company's Belgian VAT number.

The Belgian annual VAT listing is a legally required declaration, just like the monthly declaration, EU sales list and Intrastat, therefor it should be supported by multi VAT as well.

Could we release a new report which like AP ageing report or Accrued purchases excluding GST where there is a cut-off date. such as the AP invoice registered in March, then approved in May. but the user needs to print it in April, that's mean they need to print "Invoices not approved" report with backed date.

The detailed from end user required. as below. Customer uses AP register and approval for AP invoices.

There is GL code that that holds the balance for invoices that are registered but not approved but requires to reconcile with the AP submodule. There is an existing report under the AP module "Invoices not approved". this report prints only the current invoices not approved. Auditor is requesting one report to match the March TB as at 31st march but the existing report cannot print back dated. 

We need something like the AP ageing report or Accrued purchases excluding GST where there is a cut-off date.