Comments
Dear Johan,I understand your comment, but this won't work when you run a batch to bring the production order status from reported as finished to ended. After the batch someone still has to proces these production orders as you mentioned.For me STD cost items are super simple.If there is no good output quantity reported then all the reported cost (WIP) are going to the variance accounts.Please reconsider your decision so that we can make the ending of production orders fully automated.Thanks,Niels
Hello,However, the link they provided doesn't specify whether the functionality will be available for the on-premise version in October 2026.I've seen that the Verifactu module is already included in version 27 of the SaaS version, which was released in the spring.But I haven't seen any news from Microsoft indicating that it will be available for the on-premise version without needing third-party tools like b2brouter—that is, that it will be natively integrated, like the SII (Spanish Tax Agency).Regards,
In a multilingual ERP system, Item Charges should support translations instead of forcing customers to create separate Item Charges for each language.Creating duplicate Item Charges only to maintain different descriptions leads to unnecessary master data growth, increased maintenance effort, and a higher risk of inconsistent configurations.An Item Charge is a business object, not a language-specific object. The description shown on documents should be determined by the document language, while the Item Charge itself should exist only once.Translation support would improve data quality, simplify administration, and align Item Charges with other Business Central entities that already support multilingual descriptions.This is a small enhancement with significant benefits for every international Business Central customer.