• 62

    The Subscription Billing-Revenue Allocation needs to support combining Non-Revenue Allocation Sales Orders (SO) and Revenue Allocation Sales Orders into a single SO Invoice.

    Suggested by Rui Zhong Needs Votes  16 Comments

    The Subscription Billing-Revenue Allocation needs to support combining Non-Revenue Allocation Sales Orders (SO) and Revenue Allocation Sales Orders into a single SO Invoice.


    Currently, the Subscription Billing-Revenue Allocation does not support this functionality. The system will display an error message in the following scenario:

    1. Create two sales orders, one with Revenue Allocation and the other without.
    2. Create a single invoice that includes both sales orders and set the Summary update for the Invoice Account.



  • 48

    Late selection on price update of billing schedule

    Suggested by Paul Princen Needs Votes  0 Comments

    In the subscription billing module you can use trade agreements as billing price.

    When the trade agreement price changes, the price update function can be used to adjust the price on the billing schedules.

    On this price update function, we also have the option to make a selection of billing schedules, and make it a recurring task.


    Here the idea comes in play:

    We want to be able to use the price update function on a recurring basis, while using late selection (making sure the query evaluated each time the batch job runs).


    Example

    • Existing billing schedule:

    BS001 (billing schedule) for cust001 with itemA for price 10€

    • Existing recurring batch job price update for billing schdules of cust001 without end date.
    • Create new billing schedule:

    BS002 (billing schedule) for cust001 with itemA for price 10€

    • Update price of itemA to 11€ (trade agreement)
    • Result without idea: BS001 price itemA 11€, BS002 price itemA: 10€ (odd, right?)
    • Result with after idea: BS001 price itemA 11€, BS002 price itemA: 11€



  • 32

    Provide data entity for externcodes on units

    Suggested by Martin RĂĽckebeil Needs Votes  0 Comments

    External codes on units are mandatory setup to issue electronic invoices. In D365 you can have a lot of units in different instances. Setup of these codes will be a time consuming task.


    Please provide an data entities to import external codes for units!


    These kind of entities are already in place in a lot of other areas like on VAT codes.:

    • External code classes for tax code (TaxCodeExternalCodeClassEntity)
    • External codes for tax code (TaxCodeExternalCodeEntity)



  • 23

    Deferred Revenue Recognition batch job improvements

    Suggested by Paban Sharma Needs Votes  2 Comments

    At the moment it is not possible to perform Revenue Recognition in batch for a large number of revenue deferral schedules (approx 1 million schedules increasing at 30k schedules per month). The user has to go through the 'View preview' option and can only process around 40k deferral schedules per batch to avoid timeout issues.


    It should be be possible to

    1. Submit one job per month, not multiple jobs.
    2. Auto split into smaller batch jobs
    3. Allow data selection by financial dimension, deferral end date.
    4. Not have to go through 'View preview'.
    5. Retain the selection by as-of date.
    6. 1 million+ deferral schedules to be processed in less than 24 hours.

  • 16

    GL Journals postings only possible when there is an attachment

    Suggested by Jose Azevedo Needs Votes  0 Comments

    Requirement:

    All GL Journals should have an attachment to be possible to be posted. Without attachment, a pop-up should prevent the post.


    Proposed Solution:

    New Configuration to activate/de-activate this option

    When activated, the control should be in place. The solution should also allow to use at the same time Workflow for Approval

    When inactivated, it should work as the out-of-box solution now.


    Before raising this idea, several options were assessed and all of them require a customisation.


  • 15

    Extend Electronic Reporting Jobs with new fields

    Suggested by Alireza Eshaghzadeh Needs Votes  0 Comments

    Electronic Reporting (ER) Jobs form could be improved in its UI by adding fields to better track document status, such as invoice or order IDs, destination types, and ER configurations. These updates would make it easier for users to retrieve and manage Business Documents files and streamline reporting processes. To better display business document status, the following fields should be added:

    1. Account Number: Invoice account number.
    2. Document ID: ID for the document (e.g., invoice, packing slip, or confirmation ID).
    3. Order ID: Order ID or project contract ID.
    4. Form: Form source (e.g., Project Invoice or Customer Invoice).
    5. Destinations: ER destination type (Screen, Archive, Email) to indicate the document distribution method.
    6. ER Config: Name of the ER configuration used.


    These new fields will be be filterable and searchable, enabling users to find specific documents more efficiently. Additionally, they can be marked for quick and straightforward deletion.


    Additionally, a new “Archive” functionality can be added to each required form (e.g. Invoice journal and Project invoices), redirecting users to Electronic Reporting Archived Jobs if the document has already been archived via ER destinations (i.e., Archived = Yes). This enhancement allows users to quickly access already archived documents without needing to open extra forms to locate the business document.


  • 13

    No parameter found to calculate the exchange rate as per the document date in the Intrastat.

    Suggested by Sarah Azmy Needs Votes  0 Comments

    We are suggesting here a parameter which is possible to calculate the exchange rate in Intrastat using the document date.



  • 9

    Display exchange rate from journal/source document instead of a reverse-calculated one from transaction currency amount and accounting currency amount on printed ledger voucher

    Suggested by ダニエル リー Needs Votes  0 Comments

    Currently, the exchange rate that is displayed on a printed ledger voucher (and Chinese ledger voucher) is reverse-calculated using the following formula: Accounting currency amount/Transaction currency amount.


    Although this may appear correct, it may actually differ from the exchange rate in the exchange rate master and the one that was initially used in the journal or source document eg. free text invoice.


    Due to the currency rounding settings in D365, the accounting currency amount will change slightly after multiplying by the exchange rate.

    Hence, if you reverse calculate the rate using the formula above, it may not be equal.

    This is apparently visible when there are auto-posted sales tax entries too. The exchange rate in the journal voucher lines differ for each line due to the rounding settings even though they should actually be the same.


    Our users would like to see the original exchange rate that was used in the master and in the journal/source document for reporting purposes and for consistency of the exchange rate values in the journal voucher lines.


    Previously, Microsoft agreed to a fix where the exchange rate factor was wrong. However, they did not agree to displaying a rate from the journal. We would like to suggest this improvement.


  • 8

    Access level for ledger calendar periods

    Suggested by Ariadna Guiberra Needs Votes  1 Comments

    We cannot select more than one user's group to access to a specific module in the GL calendars access level form.


    Since we can only select one user group to access to one specific module, we have to edit this user's group to add or remove users frequently. It would be convenient to be able to select more than one user's group to access the module.




  • 8

    The unit price in line details is not updated for billing schedule of usage item until the next line is updated

    Suggested by Alfie Ta (Tek Experts) Needs Votes  0 Comments

    When updating the unit price and quantity in the Billing details lines, only the quantity on Price details tab gets updated, but not the unit price and net amount. Save and refresh don’t work either. Only when the unit price and quantity of the next line are updated, the price details of the previous line get updated correctly. And it keeps moving forward like that.


    Actual result: The price details in line details tab is not updated unless the next line is updated.


    Expected result: The price details in details tab is updated correctly when completing filling in the consumed quantity and unit price.