Dynamics 365 Finance

Our business is always facing problem when trying capture invoices with more that 15 to 20 pages via Invoice Capture AI model.

The reason for this is the attached invoices are having more than 1000+ lines, which can cause time outs from Ai builder.

Recommendation is to split and try with reduced number of lines.

We are suggesting an improvement in Microsoft Invoice Capture AI builder model to read and process invoices with more than 1000+ lines so that our customers can process invoices with more that 15 to 20 pages without splitting it.

Thanks.

We need Finance Insights available in the South African data centers, this is a highly sought after feature for our business but alas we are not able to use this, as its not available in our region.

According to MS doc,

when invoices are imported, the invoice lines are automatically generated, based on information on the corresponding purchase order, which means that product receipts must be processed before vendor invoice headers are imported into the system so the lines from product receipts can be automatically populated into the vendor invoices.

Since it's by design that there's no batch job running in the background for this process, it's not possible to import the invoice header first then wait for the lines to be created from product receipt which comes later, while this is a typical business scenario where invoices are sent electronically/via email – which will often get long before a delivery is made.

We request to have a process automation/ background batch job for this functionality to make it adapt with real business scenarios.

Able to mark items for posting of differences via ledger settlement function. These items should be moved to a journal and an offset account will be added to post the differences.

the requirement is to be able to have the Intrastat include both sales tax code in the same sales order knowing that the sales tax code in the sales order are linked to two different settlement period.

the current design is the Intrastat is reading from the customer invoice table or technically speaking the invoice journal table which have only one vat registration numbers, which lead to the problem that one sales tax code in the sales order can be used for the Intrastat when we have the above case.

Create an Import option for Billing rules to automatically populate fields for Projects Managements and Accounting -- Project -- Project Contracts.

The idea is to Import and Populate fields automatically.

Tax Journal is an essential function and is used to post the GST adjustments, having an approval workflow on the same is a normal business requirement as it affects the tax liability of the organization.

But as confirmed by MS the same is not available out of the box as of now.

Having a workflow on the same will enable to have a control over the transactions posted.

Hence, we would request to consider the same.

For the VAT reporting process customer used the Electronic Reporting (ER) module in Dynamics 365. Customers core process is rent of (units of) property, which requires by local (Norwegian) laws a proper and reliable VAT registration on (rental) contracts individually for the business operations. Because of customers core process, which requires a separate VAT number for each contract the number of generated VAT codes is very high in comparison with other branches and industries. Currently each VAT code has to be created and reported manually, which is very costly when taking into account the reservation of resources, vulnerable for errors and maintenance for this business process as this is mainly a manual process. In other words the administrative burden of the current, mainly manual process is unacceptable high for customer.

Therefore, customer ask us to develop a routine to automate the whole VAT reporting process, to automatically synchronize the generated VAT records with the Electronical report, so that customer can save costs, resources and maintenance and thus save money. We as Microsoft vendor, found out that we need made some extensions in the “Tax Reporting” module, however all of the objects (classes/tables) in the “Tax Reporting” module are blocked for extension, (because of the use of the "internal" attribute which makes extension not possible). We would like to raise a request to make at least the objects we need for this extension available for extension. In the list below you can see the objects we ask to release:

Table:

ERSolutionVersionAppSpecificParametersTable

methods: save & getXMLFromObject

-> opening this method give the opportunity to altering the standard XML format into customers requirement.

Classes:

ERAppSpecificParameters

ERAppSpecificParametersPresenterBase

ERComponentLookupRef

ERContract

ERLookupDataSource

ERLookupRootComponent

ERLookupRootComponentPropertyController

ERSolutionAppSpecificParametersPresenter

ERSolutionVersionAppSpecificParameters

ERSolutionVersionAppSpecificParametersApplier

ERSolutionVersionAppSpecificParametersRecordInAxRecord

ERXmlSerializerFactory