Keeping pace with the ever-changing regulatory environment is a challenge; tax return file is a good use case of such legal format changes in many countries. Keeping them updated as per latest regulations from standard delivery is a challenge.
In this blog, we will explain the new feature of possibility to generate custom tax return files in SAP Business ByDesign. This would enable the partners to adapt tax return files to relevant format according to specific country regulations. This feature has been made available to be consumed even for pre-localized and non-localized country tax return(by using the generic tax return).
Partners/Customers would now have 2 approaches to amend a given tax return file format and content.
Approach 1: Edit values in SAP generated tax return files
To do this, the partners would need to implement the enhancement option
PDI AE Multiple Usage Withholding Tax File Generation BAdI for withholding tax return files(Available with release 2108)
in the SAP Cloud Applications Studio with relevant filter conditions. The implementation can be done for a combination of tax country and tax return type. Please refer example snapshot below.
Enhancement Implementation Filter
In the implementation, partners would have the option to edit SAP generated file content. We would recommend partner to edit this content judiciously. Please refer example implementation in below snapshot.
Approach 2: Generate a new custom tax return file
Please note that knowledge of XSL Transformation would be a pre-requisite to generate these valid custom tax return files.
The brief steps to be followed for the partners/customers to achieve this would be as below
Electronic Submission indicator is used to determine if an electronic file should be generated when releasing a tax return. If the indicator is unchecked, no file is created.
To do so, follow the path Tax ManagementCompany Tax Arrangements. Search for required company. Click Edit. Under Tax Return Arrangements, check the Electronic Submission checkbox.
If the electronic submission indicator is unchecked and non-editable, you need to first maintain a dummy XSL transformation.
Step 2: Create XSL Transformation
In case the partner wants to see the exact content of the SAP generated tax return file, then they can refer the input parameter to the enhancement option PDI AE Multiple Usage Tax File Generation BAdI for VAT or PDI AE Multiple Usage Withholding Tax File Generation BAdI for withholding tax.
However, if the partner just wants the input structure format, then they could refer the datatype ‘ProductTaxDeclaration’ for VAT return and ‘WithholdingTaxDeclaration’ for Withholding tax return in Repository Explorer of SAP Cloud Applications Studio.
Step 3: Maintain XSL Transformation in XSLT Repository
Once the XSL transformation is created, you need to maintain it in the XSL transformation repository. You can maintain the configuration in the Common Master Data Configuration using configuration type code Transformation Repository. This feature allows you to store a single or multiple customer-specific XSLT files in the repository from which dedicated transformations can be created as per your business requirements.
Ensure to maintain the Transformation Type as TXRT - XSL Transformation Tax Return while adding XSL transformation.
The steps to generate tax returns itself remain unchanged. However kindly note that for a given tax return, the custom XSL transformation file(if maintained properly) takes precedence over the standard file delivered by SAP.
Since this feature enables customization of tax return file content, if this is consumed, then SAP does not validate the modified content, the customer/partner would need to modify/validate the content themselves judiciously.
Please free to provide your queries and feedback here. Happy to help!