Zmiany w module Handel enova365 wersja 2512.10.12: KSeF

Are your correction invoices being rejected by the KSeF gateway due to a misinterpretation of the P_10 field, and your sales department wasting hours manually deleting items that haven't changed? In enova365 version 2512.10.12, this is a thing of the past – we're showcasing the complete KSeF changes in the Trade module. 🎯 WHAT YOU WILL FIND IN THIS VIDEO: ✅ Two-line export of sales corrections (StanPrzed and StanPo) with the new "Corrected Only" option. ✅ Full automation of Podmiotu3 data configuration at the payment method level. ✅ Defining the account description and payment due date directly in the XML file. ✅ New order of selecting items from the KSeF file when importing purchase invoices. ✅ Support for long feature values ​​and descriptions exceeding 256 characters – without data truncation. ✅ A key change in the interpretation of the P_10 field as a unit discount. ✅ Accounting for deposit and packaging refunds with separate fields in the KSeF structure. ✅ Individual "Zoom" field in the visualization preview for each operator. 👥 FOR WHOM THIS MATERIAL IS FOR: • Chief accountant responsible for the error-free validation of XML files sent to KSeF. • Sales manager looking for ways to issue and process corrections faster. • Business owner who wants to avoid the risk of downtime due to KSeF document rejections. • ERP system administrator responsible for the configuration and flexibility of document templates. 🔧 KEY CHANGES AND BENEFITS: New standard for correction reporting. A single value difference has been replaced by a clear, two-line layout: before and after the change for each corrected item. The "Corrected Only" parameter ensures that, for an invoice with 100 items, only the one that has been changed is sent to KSeF – smaller files, faster transfer, and drastically fewer validation errors. Automation of Entity3 and payments. You set KSeF internal identifiers, entity roles, and data formats once in the payment method, and the system transfers them to the commercial document. The account description and payment due date are also transferred to XML – the customer immediately knows when and to which account to pay, without additional emails. Intelligent product import. A modified search order (first the customer's EAN, then custom codes, and finally indexes from the file) ensures that items from KSeF purchase invoices are always correctly recognized – even if the supplier uses a different nomenclature. No more 256-character limit. Long features and descriptions are automatically divided into sections in XML, so the full technical specifications are delivered to the file without missing elements, and the new element sorting improves readability. A revolution in the P_10 field. The field is now interpreted as a unit discount (per item), not an entire item. With the "Price and Discount" setting, the system correctly displays the price before the discount and the discount value—no more mathematical errors blocking shipments. Precise deposits and packaging. Deposit refunds can be linked to the issue document directly on the sales invoice, and positive values ​​and refunds are transferred to separate KSeF fields—clear settlements with deposit systems. Neosmart is a trusted enova365 implementation partner—we support companies in optimizing their sales processes and fully integrating with the National e-Invoice System. #enova365 #KSeF #Trade #ERP #books #invoice #invoicecorrection #einvoice #ERPsystem #Neosmart #Podmiot3 #KrajowySystemeFaktur #automatyzacja #finanse #enova