• 27

    CPI applied to usage items with tier pricing

    Suggested by Patricia Cervello New  0 Comments

    The CPI functionality for updating prices on billing schedules based on price indexes cannot be used for items of type Usage. This limitation makes the functionality unusable for companies that rely on this item type. We use the Subscription Billing module to invoice cloud subscriptions based on the number of users, which varies each month. Additionally, those users are billed using tiered pricing. We need the base prices for each tier—defined in the trade agreements—to be updated with CPI adjustments, just like other item prices.


  • 27

    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.


  • 27

    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.


  • 27

    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


  • 27

    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

  • 26

    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.


  • 26

    Extend "Require the calculated totals to equal the imported totals for workflow submission" to include tolerance amount

    Suggested by Tim Mark New  1 Comments

    Currently the parameter "Require the calculated totals to equal the imported totals for workflow submission" is a do or die decision. (accounts payable parameters-> invoice -> invoice workflow) Similar to other parameters like "price and quantity matching" or "charges matching" (accounts payable parameters -> invoice validation) it makes sense to extend the "Require the calculated totals to equal the imported totals for workflow submission" parameter to also incluce a toleranz amount. It means not all invoices should be blocked from workflow submission when the imported totals differs from the calculated totals. Only those out of a toleranz e.g. 0,10 USD/EUR/GBP should be blocked.




  • 26

    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.


  • 26

    Intent letters view - customer name should be visible as well as it's present in the vendor intent letters form

    Suggested by Camilla Gorini New  0 Comments

    Path: Accounts Receivable > Intent letters


    In the customer intent letters form the field "Name" is missing. There is only the customer account code.

    The name should be included in order to enhance the standard functionality and to align the behaviour to the form on the passive part (vendor intent letters)




  • 25

    Duplicate Invoice Check

    Suggested by Anna Davies New  0 Comments

    Currently Invoice Capture does not check for duplicate supplier invoice numbers. A duplicate invoice number check is only performed once the invoice is transferred into D365 F&O, this is too late in the process.


    The new requirement is for a duplicate supplier invoice check to be included as part of Invoice Capture.


    The validation logic should consider Vendor + Invoice Number + Legal entity to ensure the vendor invoice has not been duplicated in a single legal entity or across multiple legal entities.