R2023.01 | 6 January 2023
Content Legislative Updates
Slovakia Control Statement: New fields have been added to the form in sections C.1 and C.2 dedicated to invoice corrections:
- C1 - § 25a: Correction of tax base if consideration for supplied goods or services is fully or partly unpaid.
- C2 - § 53b: Correction of tax deducted for an uncollectible receivable.
The fields are optional and are populated manually in the listing’s sheets in ONESOURCE Indirect Tax Compliance by checking a box if the correction applies to a transaction.
note
There will be an additional content release in mid-January (Friday, 20 January) to accommodate further legislative updates and finalized annual returns.
Content Enhancements
Invoice Type (Invoice & Credit Note) presentation in a return: Invoice type (Invoice & Credit Note) lines now appear in two different rows in the return, instead of being aggregated into one row. This is to provide greater visibility of adjustments to INV/CN amounts. If invoice type overrides are used in the import specification, for example to treat negative amounts as INV, data is aggregated into a maximum of four rows per tax code, as defined below:
- Positive value, INV
- Negative value, INV (Adj flag ticked)
- Negative value, CN
- Positive value, CN (Adj flag ticked)
This has been introduced to the following jurisdictions:
- Czech Republic: Datasets with start dates from December 2022
E-Filing
- Germany Periodic VAT Return direct e-filing:2021 and 2022 e-filing schemas were updated to comply with the latest instructions
- Slovakia Control Statement (XML output):E-filing schemas were updated to comply with the latest changes.
Content Updates
Annual return information added to box number report: A new column was added to the box number report to show the box in the annual return that transactions are flowing to. This release includes the following jurisdictions:
- Austria, Germany, Ireland – all reporting dates
- Luxembourg and Spain – reporting dates from January 2023
Slovakia Control Statement: Corrected an issue in the e-filing schema that caused validation errors due to empty values in non-mandatory fields
Poland VAT groups – impact on OIC: Starting from January 2023 taxpayers will be able to form VAT groups and submit a single JPK VAT declaration on behalf of all group members. There are no changes in the technical requirements at this stage, therefore the reports in Indirect Tax Compliance are not being updated. The group filing will be an aggregation of the underlying data imported to each of the group members.
To populate a return created in Indirect Tax Compliance and a JPK VAT report to file for a VAT group, you should create a dataset with the Poland VAT Single template. The various entity codes that may appear in source data specific to each member of the group, should be mapped in the Entity Map to one group entity that you create using the Entity Manager (
Configuration
> Entity Manager
).Users should not make summary adjustments at the group member level and expect them to roll up a group structure. Any changes to source data should be made as transactional edits. This return, which consolidates data from all group members, should be filed as per usual process for Poland using JPK VAT report. The .xml output will consolidate the transactional details and returns data for the group entity.
Intra-group transactions should be excluded from the group reporting and in ONESOURCE Indirect Tax Compliance . This needs to be managed within the source data. We suggest mapping the transactions to Disregarded or Outside of Scope tax codes.
Additionally, intra-group transactions need to be reported as a separate submission, which will come into force on July 1, 2023. Until then, the reporting is on-demand and there is no published logical structure yet.
We recommend those interested in updating their existing configuration to allow group consolidation to contact a member of the ONESOURCE team or their implementation partner.
SAF-T
Opening and closing balances: The logic was updated to show the opening and closing balances based on the first and the last transaction in a given period.
When a report is run for more than one reporting period, the opening and closing balances should consider values from the first accounting period for the opening balance and last accounting period for the closing balance.
The dates are tied to the start and end dates used in the report parameter. The logic has been revised for populating
Opening Balance
and Closing Balance
fields in the .xml output in the following import types and jurisdictions:Lithuania:
- DTR_GeneralLedgerAccounts
- DTR_Customers
- DTR_Suppliers
- DTR_PhysicalStock
Austria:
- DTR_GLAccounts
- DTR_PhysicalStock
Luxembourg:
- DTR_GeneralLedgerAccounts
- DTR_Customers
- DTR_Suppliers
- DTR_PhysicalStock
Poland – JPK_KR:
- Trial Balance
Other Updates
APIs
Workbook Adjustments: Ability to bulk import adjustments directly into return using API. Documentation will be added to the developer portal. Using this API will allow users to populate manual entry cells in the workbook programmatically without needing to access multiple returns through the UI. This includes for example the ability to import W3(WHT) amounts to Australia returns by importing figures with client facing external API. Users can make multiple adjustments into a single return with one API call, however due to performance considerations, we are currently limiting the number of returns that can be updated in a single call to 1. For more information on how to utilize the OIC APIs, please contact TR Customer Support, your relationship manager, or your professional services consultant.
Custom Exchange Rates: An API has been developed that will allow customers to automatically populate the Exchange Rate tables which can be used as custom sources to drive FX conversions within OIC. Users will be able to create new exchange rate source and set up process to automatically populate the exchange rate tables with relevant currency pairings and rates, as per local requirements. Some configuration will be required within the UI to ensure the correct exchange rate source is used for each registration / entity. The documentation will be added to the developer portal for reference.
User Interface
- Resolved an issue with saving calculations to Excel from the return interface.
- Made improvements to UI to the edit preview panel to ensure the specific transactions which are due to be edited (those related to draft returns) are shown.
- The label for custom fields, configured in Transactional Fields screen, will now be shown in UI when adding transactions.
- Modified entity information (name) to be updated in the returns screen, calculations and prints. Clients should edit the dataset after amending the entity name in entity manager screen to see the new entity name in entity selection screen of dataset wizard and the same will be updated in return name, calculation and prints.
note
This has no impact to the returns that are already filed or in read only state.
Import
- An import issue with formulae in excel workbook was addressed. Error messaging was added to highlight the specific cells causing import failure.
- DTR Transactions import – issue with allocation errors fixed.
- Extended max character length accepted for source tax code in mappings.
- Improvements to import details screen, import progress percentage tracker will be shown for all the import jobs by default.
- Improvement in error messaging when user trying to Edit/Bulk Edit transactions in cases ofUpload Partially Completedimports.
- Fix for the reported prod issues, related to import failed scenario.
Reports
- Refactoring of intrastat, purchase, and turnover reconciliation reports to better handle large volumes of data.
- Improvements were made to intrastat, purchase and turnover reconciliation reports to show better messaging when report output is blank (no transactions present vs no mismatches found), similar to existing functionality on GL reconciliation report.
- Improvements were made to functional output of intrastat reconciliation report to better handle disregarded tax code scenarios.
- Fixed issue with custom fields not exporting correctly to Excel from custom reports.
- Enhancement to existing Box Number report to include box number details from annual return. A new column,Box Number-Annualwas added to the report. Covers all the jurisdictions where we support annual templates.