-
BRA Return order
Suggested by Priscila Sozigam – New – 0 Comments
We need a solution to create a cancelation to purchase/salles return order and recreated it.
-
Improve Invoice Attachment Naming and Duplication Handling
Suggested by Alireza Eshaghzadeh – New – 0 Comments
Scenario
When posting an invoice (Free Text Invoice, Sales Invoice, or Project Invoice), and if the following conditions are met:
- e-Invoice attachment is activated on the customer card.
- “Print invoice” is activated on the posting form.
Then the following actions occur automatically:
- The invoice is printed.
- The invoice is posted.
- A PDF copy of the printed invoice is attached to the respective journal (CustInvoiceJour or ProjInvoiceJour).
- The e-invoice file is generated and stored under Electronic Reporting jobs.
Current Behavior
The attached PDF file uses a generic file name regardless of whether users apply standard SSRS reports or CBD formats.
The default names are as follows:
- SalesInvoice.Report.pdf – Sales Invoice
- FreeTextInvoice.Report.pdf – Free Text Invoice
- ProjInvoice.Report.pdf – Project Invoice
- CustCollectionJour.Report.pdf – Collection Letter
This causes two main issues:
- User Experience – Users can't easily identify the document before opening it due to the generic naming convention.
- System Conflict – When used in e-invoice XML files or exposed via access points, these non-unique names can result in duplicates issues.
Proposed Solution
To resolve this, we recommend:
- Updating the logic to follow the file name format defined in CBD or SSRS reports so that attachments have unique and descriptive names.
- Implementing a check to prevent duplicate attachments: if an attachment already exists for an invoice, the system should not recreate the same file when users reprint.
This enhancement would greatly improve document management, streamline user interaction, and avoid issues in systems that consume these attachments.
-
Pending vendor invoice cannot be posted - unhelpful error message
Suggested by Martin Winkler – New – 0 Comments
In case a pending vendor invoice (without purchase order, without item, with procurement category) has a fixed assent number in the line and the deprecation profile of the book related to the fixed asset has method manual, the error message when posting the invoice simply is "exception has been thrown by the target of an invocation". This is not helpful and requires debugging.
-
Adding Factur-x format in standard for electronic reporting
Suggested by Jean-Benoît Simonutti – New – 0 Comments
HI all
It would be great to have the format Factur-x (pdf with xml data) in standard for e-invoice.
Customers are using it more and more.
Would be great to have this format in the roadmap for d365 f&O
Best regards
-
PO header workflow should also evaluate the 'Budget check not performed’ condition for auto rejection action.
Suggested by Hemant Sohoni – New – 0 Comments
The customer is using the PO approval workflow. They have a scenario where the PO should be routed to the approver only if the budget check result for all the PO lines is passed.
We have tried catering to this scenario by using automatic action on PO header workflow as follows:
If any of the PO line has either of the following statues, the work item should be automatically rejected:
Budget check not performed for any of the PO lines; or
Budget check passed but with warning for any of the PO lines; or
Budget check failed for any of the PO lines.
We have tried using the ‘Purchase orders. Budget check results for document’ condition to achieve the desired result.
However, we have noted that the condition ‘Purchase orders. Budget check results for document is value Budget check not performed’ is not evaluated by the system and the PO is routed to the approver/s for approval even though the budget check is not yet performed on PO line/s.
The ask is that the system should analyze the ‘Purchase orders. Budget check results for document is value Budget check not performed’ condition and should take the automatic action (of auto rejecting the workflow) as setup in Automatic actions section of the Approve PO workflow.
-
Slowness in Reset all distribution
Suggested by Chee Meng Chan – New – 0 Comments
Pending Vendor Invoice > View distributions > Reset all distribution
Experiencing significant delays when "Reset all distribution" with large datasets (over 1,000 lines). In certain instances, the system took more than 1 hour to complete the process when the invoice contained more than 4,000 lines.
-
Slowness in Pending Vendor Invoices
Suggested by Chee Meng Chan – New – 0 Comments
Facing slowness in editing the Pending Vendor Invoices with large records (More than 1000 lines). In some event, system took more than 30 mins to open the form to edit pending vendor invoices when records more than 4000 lines. Looking for the team to improve the performance of this functionality
-
SAF-t Lithuania (LT) - all description elements should be truncated to 256 characters
Suggested by Katarzyna Pyrka – New – 0 Comments
As per below regulations all description elements in SAF-t (LT) should be automatically truncated to 256 characteds (purchase/sales invoice, invoice lines description, GL and FA desctiptions and Payment descritpions):
SAF-T legislation in Lithuania
- Article 16 of the Law on Accounting;
- Resolution No 699 of 01 July 2015 of the Government of the Republic of Lithuania;
- Order No VA-49 of 21 July 2015 of the Head of the State Tax Inspectorate under the Ministry of Finance;
- Specification of XSD description of the XML scheme of SAF-T, as prepared by the State Tax Inspectorate under the Ministry of Finance.
Schema in english:
https://www.vmi.lt/evmi/documents/20142/725548/SAF-T_XSD_specifikacija_v2.1_F+en.pdf/23775a8a-0ba7-6b9c-1fc9-cfceb4ba8bd0?t=1606462594737
Reg ticket number 2502051420001009.
Becasue of missing limitations such errors appears and XML for SAF-t (LT) is not accepted:
ERROR: Element '{https://www.vmi.lt/cms/saf-t}Description': [facet 'maxLength'] The value has a length of '267'; this exceeds the allowed maximum length of '256'.
-
[BRAZIL-FB] - SPED ECD - I010 -
Suggested by Elisabete de Souza Padula – New – 0 Comments
Today Dynamics F&O only supports Type G - Daily Ledger and we need it to serve other Indicators = R, A, B and Z.
R - Journal with Summary Bookkeeping (with auxiliary bookkeeping).
A - Journal Book Auxiliary to the Journal with Summary Bookkeeping.
B - Balance Sheet Book Daily and Balance Sheets.
Z - Auxiliary General Ledger (Accounting Book Auxiliary according to layout defined in records I500 to I555
Follow the link to the SPED ECD manual, check page 101 - record I010
http://sped.rfb.gov.br/estatico/A8/AA5DF23EBFCB8A669E3EA36904E0719A5DAD42/Manual_de_Orienta%c3%a7%c3%a3o_da_ECD_Leiaute_9_Atualiza%c3%a7%c3%a3o_Nov_2024.pdf
-
VAT Nummbers check on Non-VAT Customers or Vendors
Suggested by Kristyna Petruzelova – New – 0 Comments
There are business cases, where we can sell to or buy from a customer/vendor, who has no VAT ID at all, but is in EU country. In this case, if the check on VAT IDs is set to validate EU countries, we won´t be able to post the invoice for such partners.
There should be a possibility to set a parameters, which put an additional criteria to this check.
I can imagine to have it on Cust/Vend groups or directly on customers/vendors.
For now, you would need to use Dummy IDs, what´s wrong.