web
You’re offline. This is a read only version of the page.
close
  • Take over invoice financial dimensions in AR Payment

    The financial dimensions of the invoice header (Customer financial dimensions) are not retrieved in the AR settlement process and get lost. For clients that want their customers tracked with financial dimensions, this is a major downside as they have to manually add these informations in the customer payment form, thus slowing their process to an unacceptable level. The invoice header financial dimensions should be taken over in the AR settlement process.

  • Allow mass publish of WBS

    Currently each WBS has to be published individually. For customers with a large number of project, this can be quite cumbersome, especially in case of data migration. It would be great to have a functionnality that allows to publish more than one WBS at a time.
  • Cost accounting: Allocate/Distribute cost to a combination of cost objects

    Maybe very close to the idea: https://experience.dynamics.com/ideas/idea/?ideaid=22431cfb-e1a4-e711-80c0-00155d7cb38d It should be possible to allocate or distribute costs on a combination of cost objects. With the dimension hierarchies linked to only one cost object, this is not possible currently. Consider the following GL Transactions (for the same period) 1) Account 6000 - BU A - CC X 10'000$ 2) Account 6000 - BU B - CC X 8'000$ Since each Cost object hierarchy can only be associated with one dimension, how - with the above transactions - allocate or distribute only the 10'000$ from the CC X (BU A) and not the 18'000$ ?
  • Link collection status with collection letter flag

    On the collection screen, when changing the status of a voucher, there should be an option to directly change the status of the collection letter flag (yes/no). So when, f.eg. the customer sets a position to "disputed", he could choose to automatically also change the collection letter state from yes to no. This way, as the position is disputed, it would not appear on the collection letter.
  • Sales tax inquiry by voucher

    On the accounts payable invoice entry (before the posting of the journal) we have either a tax inquiry on the line level or a total tax inquiry for the whole journal. The level in the middle - inquiry by voucher - is missing. Let's assume the customer enters 3 invoices in one journal and the 3rd invoice/voucher has multiple VAT rates. There is no way for the customer to check if the VAT entered on these multiple lines matches what is on that 3rd invoice. Idea: add a tax inquiry at the voucher level in the accounts payable invoice journal.
  • Cash on delivery to work also on invoice register/approval

    The cash on delivery (COD) function in the terms of payment doesn't work anymore on the invoice register - invoice approval flow (it still does for invoice journal) (see issue 756614).

    There are customers that were using this functionality and would still need it.

    We ask this functionality to be working as it was in the past.

  • Allow multiple fixed asset statement rows

    It is a frequent request from customers to be able to see the fixed asset statement in a grouped manner (f.eg. by FA group) but also to have a detailled view (f.eg. by individual fixed asset).

    Either we should have the possibility to use various row definitions in parallel or we should be able to drill-down to the fixed assets when we are on a line defined as a fixed asset group.

  • Vendor settlement currency should be the same as with payment proposal

    Currently when we use the payment proposal, the currency of the invoice is retrieved. If we use the settlement function, the system uses the vendor currency instead; we should be able to define with which currency we want to do the settlement.

  • EU Sales List Germany: generate csv file

    The german tax portal (Elster) provides the ability to upload a csv-file for the EU sales list.

    See link: https://www.elster.de/eportal/helpGlobal?themaGlobal=zmdo_import_eop#csvBeispiel


    Unfortunately, neither the Excel nor the txt file generated by the electronic reporting format is suitable.


    We should have a new ER format to export the data in the expected csv-file format.