Katarzyna Pyrka Senior Business Consultant

New data entity should be created to allow possibility to upload LE specific information like "allow to view all pools", add pools and default them on Credit and collection > Collection agents. Collection agents is a global table but setup inside is local per legal entity and today need to be maintained manually.

In Belgium localization package we can find BLWI report which should collect all sales and purchase non-domestic transactions connected to SERVICES.

Currently we can enable report and system will require BLWI code on all non-domestic transaction no matter if we use ITEM, procurement category which is linked to Item sales tax group - ITEM/SERVICE, or standard posting.

Idea is to expand this functionality and not only check Customer/Vendor country that is not BEL, but also ITEM SALES TAX GROUP and include only when Reporting Type is SERVICE. This way system will not ask for BLWI code when transaction is booked for ITEM Reporting type.

It will also allow easily using BLWI parameter - ERROR data validation, as todays it is useless, as all foregin transactions get error if no code is selected. My idea for ITEM SALES TAX GROUP usage is because BLWI report is part of foreign declarations like Intrastat and EU Sales list which both uses REPORTING TYPE to allocate and divide Services from Items and Investments.

Changing Number sequence of the Tags - Column Number in Financial Tags is not editable. 

It should be possible or rather it would be needed for the business to be able to change the Tag hierarchy and sequence. After Making an error when creating the Tags in Production environment it will be no possibility to fix it. 

As this feature is substitiution of having too many financial dimension, business should have possibility to update/change sequence of financial tags.

It would be beneficial for end users to have auto sorted values from A-Z point of view when they open the list to choose from. As per now when new values are added to custom list, they are at the end, so it is harder to scroll and find the proper value to use.

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'.