2024.05 | 3 May 2024

Legislative Updates

Content Enhancements

VAT return pdf form –
Added links for boxes 21A,B,C and 15A,B to populate values in the pdf form from the Return Summary. Previously there were no amounts populated for these boxes in the pdf form.
VAT return –
The calculation of the VAT credit amount in box 27 in the VAT return has been revised to not include it this box when box 0005 indicating VAT recovery on group level is ticked. Previously the credit amount was incorrectly included in box 27 instead of only being calculated in box AA reserved for group reporting.
Updated the box number mappings used in Box Number report to include tax codes that were missing in the report.

JPK_FA (on demand SAFT) –
• JPK_FA (on demand SAFT) – the logic for generating the report has been amended to address more use cases:
Exclude total values for Orders if there are no import of data made with import type DTR-JPKOrders. The orders are not mandatory and don’t have to be included to prepare the JPK_FA report. Previously the control amount with the count and sum of total values referring to the orders was incorrectly included in the output making the output inconsistent with the schema structure.
The element ZamowienieWiersz related to the orders details will be printed when JPK_Orders is imported only including mandatory fields in Zamowienie (P_2AZ and WartoscZamownienia) without any of the optional fields in ZamowienieWiersz
VAT return –
a new tax code has been added to allow reporting of partially recoverable VAT amounts under reverse charge related to Services purchased from EU suppliers included in boxes 29 and 30. Previously OIC only supported this tax code as fully recoverable and fully irrecoverable.

The logic has been amended to exclude foreign counterparty VAT registrations from the reporting and instead the aggregated values of transactions with suppliers and customers not registered in Portugal will be reported on a single line for each counterparty without the registration numbers.
Additionally, there is a mechanism added to exclude Debit Notes with negative sign from the listing by populating field InvoiceType5 with value ‘Debit Notes’. The field can be included in the import specification which requires an update to the configuration or can be populated in OIC via edit functionality (including bulk edit if the value will apply to multiple transactions).

VAT return pdf form:
Field including Email address has been revised to improve the display of this value in the pdf form. Previously the value was stretched and not fully visible in the form.
Fixed an inconsistency in printing of boxes populated as tick box which were previously not populated when the form was printed to pdf.
Intrastat –
revised logic applied to rounding of values in field Net Mass to allow capturing values less than 1 that should be rounded up to 1, previously they were reported as 0.

E-FILING UPDATES:

SAF-T:

The characters below will not be supported in SAF-T reports, due to XML file limitations:

Special Character	Name
&	Ampersand
<	Less Than
>	Greater Than
\	Backslash
'	Apostrophe
"	Quotation Mark

The below special characters should not be used for Entity names, as entity name is part of the standard naming conventions, and these characters are not supported in file names.

Special Character	Name
*	Asterisk
/	Forward Slash
:	Colon
?	Question Mark
"	Quotation Mark
<	Less Than
>	Greater Than
\	Backslash

API Updates

RETURNS:

Data from the Manual upload sheet (S) is not flowing to the S sheet of annual.
Data from the Adjustment summary sheet (S1) is not flowing to the S sheet of annual.

An intermittent issue was observed when multiple users accessed the same return in succession. Users would observe an unexpected error was displayed for the second user inconsistently. This was due to the incorrect handling of the multiple-user access logic. The issue has been addressed by updating the logic to properly handle scenarios of concurrent access, if the setting to allow multiple user access is enabled on database level.

An intermittent issue was reported on the closure of the returns i.e, when multiple users accessed a return and one user closed it from the Returns screen popup, it wasn’t disappearing from the Open Returns and this issue prevented promptly providing editing permission to the other users.
By updating the access control logic the returns are properly closed and editing permissions are accurately granted to other users. This enhancement ensures smoother workflow and resolves issues.

IMPORTS

As you begin to utilize the fully rolled-out Import Progress Tracking, please keep us informed about your experience. Your feedback is crucial for us to continue to refine and improve our features.

Categorized Error Grouping:
Allocation errors are now intelligently grouped by categories, allowing users to quickly identify and rectify issues without having to wade through a sea of unsorted error messages.
Detailed Error Descriptions:
Each error is presented in a structured format, providing clear details on the error type, the specific lines affected, and the occurrence frequency of each error.
Sequential Error Handling:
The system now processes multiple allocation errors in a predefined sequence, enhancing overall efficiency:
Entity code mapping is checked first.
Transaction type mapping is confirmed second.
Tax code and exchange rate mappings follow.
When reviewing allocation errors, certain missing data points mean it isn't possible to move to the next layer of checks eg. If entity code mapping is not present, the system is unable to identify the jurisdiction and therefore cannot verify whether the tax codes are mapped in the allocation specification selected for that jurisdiction.
Important Update on Importing Files:
The system now intelligently handles scenarios where a template license for an entity is missing. Instead of failing the import outright, an 'Entity Not Mapped' error will be shown first. This allows users to rectify the issue without losing the import progress. Once the license is added and other issues are resolved, the import and upload will proceed successfully.

REPORTS:

OTHER UPDATES

KNOWN ISSUES

Deletion of batch reports –
A user will have to delete all saved parameters before deleting a said batch report successfully. In the future, this flow will be enhanced to allow users to delete batch reports more directly.
Running a batch report by selecting a saved parameter –
In this release, we have identified that the batch report is not run unless users select the ‘output format’ in the ‘batch reports parameter’ screen after selecting one of the saved parameters. This will be streamlined in the upcoming release to ensure better user experience.

APPENDIX 1: LIST OF UPGRADED CONTENT TEMPLATES