-
Customer and Vendor settlement issue when multiple employee execute the same daily tasks
Suggested by Peter Jacobsen – New – 0 Comments
Hey Guys
Issue we are facing is multiple finance people are settling vendor or customer transactions at the same time.
Employee A open vendor settlement from the Vendor form and select multiple transactions
Employee B open vendor settlement on the same Vendor.
No indications that user A already has marked transactions, these is just marked as as normal.
Employee B start to select transactions, and employee A select settle. The transactions employee B has done and not finalized in the process is getting settled by employee A, so many partially settled. An now updated that Employee A has settled all transactions, but is Employee B which had marked the transaction and is not finalized in the process.
An indication like marked transactions from a General journal or other journal will help so employees not settle unexpected transactions.
-
Invoice capture - Allow multi-PO recognization in the same invoice
Suggested by Claire Chambrier – New – 1 Comments
Currently, it is not possible to recognize multiple Purchase Orders within the same invoice that is read by Invoice capture.
Within a business, it can often happen that suppliers can send one invoice combining multiple Purchase Orders.
Hence, instead of having an automated way to capture the vendor invoices, the business has to manually review the invoices and assign the right PO on each line of the PO invoice before transferring to F&O.
This has a big impact on the purpose of Invoice capture and the automation of the process to facilitate the business processes of the Finance team.
The recognization of multi PO within one invoice would be then very appreciated.
-
Malaysia electronic invoicing - Electronic document submission log does not reflect latest related submission status
Suggested by Katie Nguyen – New – 0 Comments
When an initial e-invoice submission fails, the status in the Electronic Document Submission Log remains “Failed”. Even after a successful related submission, the original log entry does not update. Users must manually navigate to Inquiries > Related submissions to find the latest status. This makes Submission status unreliable and time-consuming to use for tracking submission outcomes.
We would like to propose a design change request that involves either:
- A status override or chaining mechanism in the submission log to reflect the latest related submission.
- A visual indicator or link in the original failed submission pointing to successful related submissions.
- A consolidated view that merges submission history for the same document.
-
Subscription billing - Add "Billing frequency" to the trade agreement journals for better pricing
Suggested by Melissa Mähnert – New – 3 Comments
On the trade agreement journals it should be possible to enter prices per period for the Billing schedules.
For that, the "Billing frequencies" should be added, so it is possible to enter prices for Onetime, Daily, Monthly, Quarterly, Semiannually and Annually.
Currently, there is no possibility to enter the prices per period, neither does the Billing schedules automatically calculate the correct price when changing the period. It would be a huge enhancement having the Billing frequency in the trade agreements to avoid errors due to the need of manual calculations.
This concept would not effect existing trade agreements or the pricing methods in general for billing schedules when you simply add the possibility to select "All" in the added Billing frequency field in the trade agreements.
-
Import LC settlement with vendor invoice on vendor transactions
Suggested by Stephanie Roosen – New – 1 Comments
We have often the case that the vendor invoice is not yet posted and the vendor payment (linked to an LC) is already posted via the bank statement import. This is especially the case for LC Sight payment terms.
If we settle the invoice and the payment on the vendor transactions, the LC remains in status Invoiced and not Paid and the bank utilization is still open.
We would need that the LC is paid and that the bank utilization is updated when settlement on vendor transactions is done without needing to create general journals as a correction for each case.
-
Support integration between D365 Commerce and Tax Calculation service
Suggested by Eric Wang – New – 1 Comments
Hi,
This idea is created by Tax Calculation service product team to understand the market requirements to support the integration between D365 Commerce and Tax Calculation service. Please vote for this idea if you need this integration in your project.
Thanks
Eric
-
ITALY - CHECK OF DATE OF VAT REGISTER WITH DOCUMENT DATE AND POSTING DATE
Suggested by Gian Luca Santicioli – New – 9 Comments
On October 23, 2018, Law Decree 119 (L.D.119/2018) in Italy introduced a change in Italian value-added tax (VAT) management. This change went into effect on July 1, 2019. Here is a summary of the change: 1) For the supply of goods and services, the invoice can be issued by the fifteenth day of the month after the month when the VAT point was triggered. Invoices that are issued and booked before the fifteenth day of the month after the month when the VAT point was triggered must be included in the VAT settlement of the previous month. 2) Invoices that are booked before the fifteenth day of the next month but have a reference to the previous VAT settlement should not interrupt the sequential posting. If invoices have a VAT point date in the previous month but an invoice date in the current month, they should be booked in chronological order with the invoices in the current month that have a reference that indicates that these invoices are related to the previous VAT settlement. Thus, the system should allow the posting of the VAT register date in the previous month respect to the posting date, only if the document date is referred to the previous month and the posting date is booked before the fifteenth day of the month. While the invoices posted after the fifteenth day of the month the system must check that the date of VAT register is included in the same month. At the moment such control is not available and this can cause mistakes in VAT declaration. Such control should be activated at taxbooksection level in order to decide which tax book section should maintain this check or not. Not all tax book sections require this control. Many thanks Regards Gian Luca -
Transaction Currency Issue in Consolidated Invoices for Japan
Suggested by Yuji Imaoka – New – 0 Comments
Issue Description:
When creating a new Consolidated invoice for Japan, the runtime parameter for currency is fixed to JPY. As a result, consolidated invoices cannot be created for customers with foreign currency transactions (e.g., USD).
This issue occurs when the Japan Invoice support feature is enabled.
Request:
Please make the following improvements:
a. Enable the creation of Consolidated invoices for Japan regardless of the transaction currency.
b. Ensure that when a consumption tax discrepancy occurs, the adjustment entry (consumption tax transaction) is correctly created even for foreign currencies.
-
Invoice number is not populated in the Document field on the Accounting source explorer form when registration journal is approved in another period
Suggested by Basavaraj Kammar – New – 1 Comments
Currently after posting invoice approval journal is approved in another period then system is not showing the "Invoice number" for the new voucher id lines (Accounting source explorer report), this is creating issue while referring the report of "Accounting source explorer" it needs to be added manually.
-
Tax options Special report failing to include all Settled and posted VAT Payments
Suggested by Monika Upadhyay – New – 0 Comments
Current Scenario: The generated report achieved by running the Report VAT for a settlement period process in combination with the SPECIAL REPORT is displaying VAT from 'Original’ settled and posted VAT Payment only not from the ‘Total list’. (Total List : Original + Latest Corrections)
Expected Scenario: The generated report achieved by running the Report VAT for a settlement period process in combination with the SPECIAL REPORT should display VAT from all the Settled and posted VAT Payments i.e. the ‘Total list’, not just from the ‘Original’ settled and posted VAT Payment.