Since we nowadays almost every project migrate data from one instance to another via data management or we copy data from one legal entity to another legal entity via copy to legal entity function in data management. It would be great if newly added fields were also mapped in data entities, for example field "GLStatementByMainAccountFormat", which is prerequisite for smooth data migration.

The problem is not once upon a time manually migrate this field, the problem is when you need to migrate 200+ legal entities, and you have to do it 200 times manually. I do not have to write about not existing time efficiency + space for mistakes the problem produces, right?

To calculate a planned cost, we need to override the the exchange rate or choose another type of exchange rate. By default the last exchange rate of the company is used in the calculation but we need to use the exchange rate of our budget.

Can we be alerted when the Financial Reporting  MRDB and AXDB gets out of sync?

Business Justification:

We are continuing to experience issues with the FR - accounting is having to check data in FR every time FR reports are refreshed before certifying the report for consumption. We reported this in case 2312040040006743 - we know that there is a known issue that can occur when MRDB and AXDB get out of sync. We also know how to fix it - by resetting the datamart

How can we trust the data in the FR due to this issue? Checking FR report every time they are generated is not practical.

Per an Idea suggested in April 2022 - the Product team was focusing on "eliminating the need for data mart resets".

Does not look like this has made any progress. Hence the need for system help .This issue with FR is eroding confidence in FR reporting & has raised the risk of inaccurate financial reporting for our organization.

There is no detailed reporting for procurement categories.

Business process/setup

Company is based in UK but this might occur in different entities location

Company use Date of VAT register global feature: Tax point date (Date of VAT register) - Finance | Dynamics 365 | Microsoft Learn

Company run ‘settle and post” based on Date of VAT register

Company post vendor invoices with the automatic fill of Date of VAT register as document date

Due to the delay in receiving invoices there might be documents that are posted in current month but with date of vat register in one of previous periods, example, Posting date: 10/30/2023, Date of VAT register (document date) 15/07/2023

Till the document is posted in the system ‘settle and post sales taxes” has been run for all previous periods – original and as well correction. 

User do not want to run ‘settle and post’ for each month, but identify all transactions that has not been included in settlement, change the Date of VAT register to current period and include in last declaration. 

NOTE: Running ‘settle and post” for each previous month is time consuming, not efficient and require to submit corrections for all periods to Tax Office.

Issues

Issue 1: Not easy to find what transactions have not been included in any of previous ‘settle and post sales taxes and find all that has not been included. 

Issue 2: Not able to find out from where the difference is coming on VAT account if we check Trial Balance, Accounting source explorer. 

Current way of control

Right now, user must run 2/3 (sales tax list, sales tax transactions) reports and filter transactions on “Maintain VAT register transactions” to identify the transactions and discrepancies.

Go voucher by voucher to check if it was included in ‘settle and post”

Note, that we can only count on the “version” on the sales tax transactions/Maintain VAT register transactions which is not sufficient, because in each previous period ‘settle and post’ could be run several time (original and latest corrections), so the version for each month will be different and we cannot use this for filtering. 

There is no other information about if and where the sales tax transaction ahs been included in ‘settle and post” periodic task. 

Possible improvements: 

Possible improvements that will help to reconcile ledger and sales tx sub ledger and also identify transactions that has been posted after the ‘settle and post”

1. Create 2 new columns in table — VAT Settlement Voucher and VAT Settlement Date. 

2. Populate data to 2 new columns When using Settle and post sales tax process into TaxTrans. 

3. Add these 2 new columns to posted Sales Tax, Maintain VAT Register Transactions and Voucher Transactions. 

4. Add Date of VAT Register to Accounting Source Explorer, Ledger Settlements and Voucher transactions. 

5. Add Document Date to Maintain VAT Register Transactions 

6. Block functionality to change Date Of VAT Register after Settle and post sales tax was done 

(VAT Settlement Voucher column is filled) in Maintain VAT Register transactions. 

To Microsoft Team,

I am seeking your assistance in the development of a structured process for the creation of an API database import mechanism from Tier 1 Environment to Tier 2 Environment. The establishment of this database migration procedure is deemed imperative and promises to be advantageous not only for our customers but also for the testing engineers involved.

Your guidance and expertise in this matter would be greatly appreciated.

When

1. utlizing Dual Write, map Customers V3 (accounts)
2. Tax Exempt Number is set mandatory by configuration in F&O

Creation of accounts cannot be performed in CE, i e Dual Write's integrated customer master scenario is thus broken. In order to walk the talk, this issue needs resolution.

Above is due to the fact that Tax Exempt Number is a supported table that needs to be referenced in F&O, whilst it is a single field in CE. There is no ability to insert the record in the supporting table in F&O from a synchronised text field in CE

According to the Dual Write product team, above issue belongs the Accounts Receivable product team. Thus this entry.

When we use the ledger settlement functionality, it should be possible to configure an automatic account ledger that will post automatically the penny difference when we try to settle ledger account. This business process is very critical for our customers and it will be extremely helpful the Ledger settlement Module.

Today is out of scope the record 1601 for the generation of the fiscal SPED.

This record 1601 (OPERATIONS WITH ELECTRONIC PAYMENT INSTRUMENTS (VALID FROM 01/01/2022) depending on each federative unit, its generation may be mandatory from 2023.

See the page 301

Link:  http://sped.rfb.gov.br/estatico/83/641EFB2FC0E317FFF8A5A5D09E3C874F3CDB04/Guia%20Pr%c3%a1tico%20EFD%20-%20Vers%c3%a3o%203.1.3.pdf

WIth the "Reject duplicate" invoice number setup in the accounts payable parameters, we expected to forbide the creation of two pending invoices with the same number.

But it is not the current behaviour while one of this two invoices is not posted but on going into the workflow

So I suggested to extend the feature "Prohibit submission to workflow when the invoice number already exists on a posted invoice", to un-posted invoice also,

Thank you for taking into account this idea and voting for it,

Bests regards