SAP Community - SAP Document and Reporting Compliance

KSeF 2.0: Setup and Integrate Your System with the Cloud Edition

2025-11-25T16:32:47.300000+01:00

This blog post was updated on December 23, 2025, to include the latest changes related to the pre-production and production environment.

The original plan from the Poland authorities to introduce mandatory e-invoices through KSeF in 2024 was postponed. The delay was used to rebuild the infrastructure and launch KSeF 2.0. With that, some of the changes are reflected in the following:

The new KSeF 2.0 is not compatible with KSeF 1.0, meaning it significantly impacts how you setup and integrate your system.
A new FA (3) schema version for electronic invoice formatting is introduced.
The authentication method based on token will be phased out by 2026. As a result, SAP will support only certificate-based authentication for KSeF 2.0 (only tokens were supported for KSeF 1.0).

You can already setup your business system for the new invoice format required with KSef 2.0 and update the integration requirements to use SAP Document and Reporting Compliance, cloud edition.

Be aware that KSeF has different environments that should be assigned to different service plans of the cloud edition, as follows:

KSeF 2.0 Test Environment - Test Plan of the cloud edition
KSeF 2.0 Demo (Pre-Prod) Environment - Test Plan of the cloud edition
KSeF 2.0 Production Environment: Standard Plan of the cloud edition

Please note that existing integration remains applicable for production environment of KSeF 1.0 until the legal mandate comes into effect, at the end of January 2026. You can already test new integration with test and pre-production environment of KSeF 2.0. Be aware of the period indicated by KSeF to apply changes to your production environment.

Depending on when you integrated your business system with the cloud edition, the steps to setup your system for KSeF 2.0 can vary. Before starting, make sure the E-Invoices Through KSeF (PL) process is active in the Activate Processes app - the process that should be activated is the same if you configured your system for KSeF 1.0 (in this case, it is already active), or if you are configuring your system for KSeF 2.0 now.

For the integration, you need to perform the general integration settings. For that, consider according to your business system:

Please, also consider the following:

You should perform all the steps described under the Establishing Connection from Cloud Edition to Business System section, including configuring the Cloud Connector. This is a technical prerequisite and does not require additional license.
If you use processes other than Peppol Exchange, Argentina, Romania, Serbia, or Slovakia, you might have done these steps already and there are no additional steps for now.
If you have onboarded the cloud edition after April 2023, you don’t need to create a new service binding when performing the steps for the new integration.
Once these settings are completed, the system automatically sets the integration with KSeF 2.0.

If you have configured your system for KSeF 1.0, you have already made process-specific configuration using your NIP number. The system ignores that configuration, but you can also delete it, if you prefer. For KSeF 2.0, you can find detailed information by accessing the KSeF 2.0: Certificate & Authorization for Establishing Connection with the Cloud Edition blog post.

Besides the integration with the cloud edition, there are steps that you have to perform in your business systems related to the new invoice format.

For SAP ERP, SAP S/4HANA, or SAP S/4HANA Cloud Private Edition, see the following:

Implement SAP Note 367668.
Do the configuration to adapt your business system to the legal mandate. For more information, see:
- SAP S/4HANA or SAP S/4HANA Cloud Private Edition
- SAP ERP

Even if you already implemented KSeF 1.0, please review the complete Customizing section, as new configuration nodes and new configuration values have been introduced with KSeF 2.0.

In the Define Process Communication Through Cloud Services Customizing activity, update the Service option to Cloud Edition: Standard Integration.

In your productive system, that this setting should be made only in the period indicated by KSeF to move to their production environment.

For SAP S/4HANA Cloud Public Edition, see the following:

Do the configuration to adapt your business system to the legal mandate. The business system documentation is available in the PDF file delivered with SAP Notes 3687266 and 3689736.

Even if you already implemented KSeF 1.0, please review the complete Customizing section, as new configuration nodes and new configuration values have been introduced with KSeF 2.0.

In the Define Process Communication Through Cloud Services configuration step, update the Service option to Cloud Edition: Standard Integration.

In your productive system, that this setting should be made only in the period indicated by KSeF to move to their production environment.

For more information, you can access the Regulatory Change Manager for Mandatory e-Invoicing through KSeF in Poland.

Best regards,

Document and Reporting Compliance Cloud Edition: A New Generation of Global Tax Compliance

2025-11-30T20:06:50.742000+01:00

In a world where governments are rapidly digitizing tax controls, companies must ensure real-time reporting, accurate e-invoicing, and seamless integration with local authorities. SAP has long supported these needs through its Document and Reporting Compliance (DRC) solution embedded in SAP S/4HANA.

As regulatory demands increase and cloud adoption accelerates, SAP introduced Document and Reporting Compliance, Cloud Edition—a next-generation, cloud-native platform designed to help enterprises respond faster, comply globally, and scale efficiently.

This article explains both solutions and highlights the key differences that set the Cloud Edition apart.

What Is SAP Document and Reporting Compliance (DRC)?

DRC is the integrated compliance framework within SAP S/4HANA, built to support:

Electronic invoicing (eDocuments)
Legal reporting (SAF-T, VAT, Intrastat, etc.)
Indirect tax submissions
Real-time government integrations
Audit and compliance workflows

DRC leverages SAP S/4HANA’s core capabilities, using:

Embedded data models
Fiori apps
Integration with finance and logistics
Local add-ons for country-specific mandates

It is ideal for companies that run S/4HANA (on-premise, private cloud or public cloud) and want compliance deeply integrated into transactional flows.

What Is Document and Reporting Compliance, Cloud Edition?

DRC Cloud Edition is SAP’s standalone, cloud-native compliance platform built on SAP Business Technology Platform (BTP).

It is designed to:

Support global e-invoicing mandates
Manage content-rich regulatory reporting
Centralize compliance across multiple ERP systems
Provide API-based connections to government platforms
Deliver continuous updates through the cloud

Unlike DRC embedded in S/4HANA, the Cloud Edition does not depend on the ERP release cycle, allowing SAP to push compliance updates faster and support new regulations more rapidly.

Key Differentiators: DRC vs. DRC Cloud Edition

Below are the main areas where the Cloud Edition differentiates itself from the traditional DRC embedded in S/4HANA.

1. Deployment Architecture

Aspect DRC (Embedded) DRC Cloud Edition

Location	Runs inside SAP S/4HANA	Runs outside ERP, on SAP BTP
Dependencies	Tied to ERP version & upgrades	Independent of ERP release cycle
Updates	Delivered with S/4HANA feature packs	Continuous cloud updates

Benefit: Faster adoption of new regulatory requirements with minimal impact on the ERP.

2. Multi-ERP and Non-SAP Integration

Aspect DRC DRC Cloud Edition

Supported systems	Primarily SAP S/4HANA	Multi-ERP, multi-system, including non-SAP
Consolidation	Usually per ERP instance	Centralized compliance hub

Benefit: Ideal for companies with multiple ERPs, global rollouts, or hybrid landscapes.

3. Scalability and Global Coverage

DRC Cloud Edition can scale more easily across countries.
SAP delivers regulatory content globally through cloud content packages.
Government API connectivity is managed centrally.

Benefit: Enterprises expand into new jurisdictions without large ERP projects.

4. Government Integrations and Connectivity

DRC Cloud Edition offers:

Managed API gateways to tax authorities
Continuous monitoring of government system changes
Central message tracking across countries

Benefit: Reduces IT workload and ensures higher resilience for e-invoicing and e-reporting.

5. Innovation, AI and Extensibility

Because it sits on SAP BTP, DRC Cloud Edition can leverage:

AI-driven anomaly detection
Intelligent validation of documents
Faster extensibility via low-code tools
Cloud automation services

Benefit: More innovation potential compared to the ERP-embedded DRC.

6. Upgrade Effort and Maintenance

Aspect DRC (Embedded) DRC Cloud Edition

Customer effort	Must test with ERP upgrades	Minimal customer testing
Updates	Periodic	Continuous and automatic
Maintenance	Shared between ERP team and tax compliance	Fully handled in the cloud

Benefit: Lower TCO and faster compliance readiness.

When to Choose Each Solution?

Choose DRC (Embedded in S/4HANA) if:

You want compliance tightly integrated into transactional finance and logistics.
You prefer a single solution inside S/4HANA.
You operate primarily in countries already supported within DRC.

Choose DRC Cloud Edition if:

You need global multi-country e-invoicing with fast deployment.
You operate multiple ERPs or hybrid landscapes.
You want rapid response to changing government mandates.
You need a future-proof cloud strategy with continuous innovation.

Conclusion

SAP Document and Reporting Compliance Cloud Edition represents the evolution of digital tax compliance—faster, more scalable, and designed for a global, multi-system world.

While the traditional DRC embedded in S/4HANA remains a strong and deeply integrated option, the Cloud Edition expands capabilities with:

Cloud-native architecture
Faster regulatory updates
Centralized global management
Support for multiple ERPs
Continuous innovation via SAP BTP

Together, both solutions equip organizations to meet today’s regulatory environment and future-proof their compliance landscape.

KSeF 2.0 Test Environment: Automate the Retrieval of Electronic Documents with the Cloud Edition

2025-12-05T09:50:51.185000+01:00

You are setting up your system for the new invoice format required for KSeF 2.0 and want to understand how to test automated retrieval of invoices from the tax authority portal to achieve end-to-end processing of electronic documents.

With the Schedule Jobs app in SAP Document and Reporting Compliance, cloud edition, you can create one job that automates the retrieval of supplier or self-billing invoices from the tax authority portal to your business system (for example, SAP S/4HANA or SAP ERP) . This makes the following activities in your business system obsolete:

Processing eDocument Inbound Messages
Processing Incoming Messages with Additional Filters
Processing eDocument Status Message
Processing Status Messages for Multiple eDocuments

Meaning, you no longer use the eDocument Inbound Message Handler for these activities. Instead, you use Schedule Jobs app.

How it works?

You schedule a job in the SAP Document and Reporting Compliance, cloud edition. The system automatically creates a request based on the job configuration.
The cloud edition takes invoice data from Krajowy System e-Faktur (KSeF), a platform from the Polish tax authority used to exchange electronic invoices.
The cloud edition decrypts retrieved invoices, creates visualization as PDF files and pushes to the destination business system selected for the job.
The business system creates the electronic document and updates its status. The XML (FA(3)) and PDF files are available in the history of the electronic document. Here you can also check if any duplicate documents were retrieved.
Note: To see the attached XML (FA(3)) and PDF files, select the electronic document and open Attachments in the Manage Electronic Documents app, or History in the eDocument Cockpit transaction.

Test Use Cases

In this blog, I share details on two key scenarios for downloading invoices that you might want to apply with the Schedule Jobs app:

Downloading purchase invoices
Downloading sales invoices for self-billing

Prerequisites

You have already performed the general integration settings for test environment as described in this blog: KSeF 2.0 Test Environment: Setup and Integrate Your System with the Cloud Edition.

Now, you can test configuring automated jobs for retrieving your invoices from tax authority portal using the Schedule Jobs app. To access the app, go to the SAP Document and Reporting Compliance, cloud edition launchpad in your associated SAP BTP subaccount. See Scheduling Jobs.

Configuration is guided through a step-by-step wizard:

Define the general settings for the job, by selecting:
- Process Flow: Retrieving Documents for E-Invoices Through KseF (PL)
- Identification Number: Select the NIP number you have set for communication type E-Invoices Through KSeF 2.0 (PL). See Managing Communication Settings.
Configure additional properties required by KSeF 2.0 to provide the data to the cloud edition. This is where you pay attention to achieve the scenarios.
Scenario 1: You want to schedule job to retrieve invoices where your company is the buyer.
- subjectType: Subject2 (Buyer)
- dateType: Issue (Use for KSeF 2.0 test environment).
  Note: Later, for production, it’s recommended to use PermanentStorage (based on archival date) to avoid missing invoices.
Scenario 2: You want to schedule a job to retrieve invoices issued under self-invoicing mode where your company acts as the seller.
- subjectType: Subject1 (Seller)
- dateType: Issue (Use for KSeF 2.0 test environment).
  Note: Later, for production, it’s recommended to use PermanentStorage (based on archival date) to avoid missing invoices.
- sellerNIP: Your company NIP number
- isSelfInvoicing: Select the checkbox
Define the frequency of your job. Example configuration can be:
- Every 2 hours – the cloud edition will send a request for retrieving the invoices every 2 hours and will get the invoices created in between.
- One-Time – you can use this to get the invoices for a certain period in the past, for example, the period before the first run of your recurring job.
  
  Note: You can have only one recurring job per combination of process flow and identification number and as many one-time jobs as you need. For example, If you already have created a recurring job for Retrieving Documents for E-Invoices Through KseF (PL) for NIP number 123XXXXXXX, you will be able to create only one-time jobs. To create a recurring job with different parameters, you must first delete the existing one.
Select the destination you created for the business system in which you want to receive the documents. See Setting Up Connectivity.

Once you save your configuration, you can monitor the results of your job runs – time details, status, results, troubleshooting steps. See Viewing Results of a Job Run.

For more information on KSeF 2.0 related features covered by SAP, you can access the Regulatory Change Manager for Mandatory e-Invoicing through KSeF in Poland.

SAP & 1099 Reporting: How S/4HANA Supports US Tax Compliance

2025-12-09T05:08:17.211000+01:00

1. Overview of 1099 / U.S. Withholding Tax Reporting in SAP

1.1 What is 1099 Reporting?

In the U.S., businesses must issue 1099 forms to certain payees (vendors, service providers, contractors) when payments meet IRS thresholds, commonly $600 per year for non-employee compensation. The forms report payment amounts and are submitted to the IRS.

1099 covers many categories:

1099-NEC: Nonemployee compensation (services, contractors)
1099-MISC: Other income types (rent, royalties, prizes)
1099-INT: Interest income
1099-K: Payment card or third-party network transactions
1099-G: Government payments, such as unemployment benefits
1042-S: Payments to foreign persons or entities subject to withholding

A robust system must handle multiple vendor types, vendor master data, withholding tax codes, and aggregation logic for accurate year-end reporting.

1.2 SAP’s 1099 / Withholding Tax Functionality

In legacy SAP ERP or ECC, companies often used built-in withholding-tax and 1099 reporting functionality. With S/4HANA, SAP introduced improved compliance reporting via the Document and Reporting Compliance (DRC) module. This integrates statutory and withholding tax reporting, including U.S. 1099 and 1042-S, directly in S/4HANA.

S/4HANA supports generation of print forms for 1099/1042-S reports (e.g., 1099-MISC, 1099-INT, 1099-K, 1042-S) out of the box. The “Generic Withholding Tax Report” or “Run Statutory Reports” function in DRC enables organizations to comply with IRS reporting requirements.

SAP maintains structured tables to hold 1099 statutory reporting data, ensuring vendor and payment information is stored consistently for extraction, reconciliation, and audit purposes.

2. Core Components in S/4HANA for 1099 Reporting

2.1 Vendor / Business Partner Master Data

Vendors or business partners must have correct tax identifiers (TIN, SSN, EIN) registered under the relevant tax category for 1099 eligibility.
For foreign vendors requiring 1099-NEC or 1042-S reporting, tax numbers and treaty status must be correctly maintained.
Vendor role assignment must be configured correctly so the DRC module knows which suppliers are 1099-eligible.

Accurate vendor master data is the foundation of successful 1099 reporting.

2.2 Withholding Tax Configuration & Codes

The SAP withholding tax framework must capture payments subject to withholding or 1099 reporting.
Withholding tax codes must be defined and assigned to the relevant 1099 or 1042-S form type, ensuring that SAP correctly identifies reportable payments.
Proper mapping to G/L accounts and configuration of threshold rules is essential to avoid missing or incorrect 1099 reporting.

2.3 Statutory Reporting Module (DRC)

S/4HANA’s DRC module provides a Fiori application for running statutory reports. It generates 1099-MISC, 1099-NEC, 1099-K, and 1042-S reports by reading data from withholding tax ledgers, vendor master records, and payment documents.
The module aggregates and formats output according to IRS specifications, ensuring compliance with print or electronic filing requirements.
SAP provides updates to reflect changes in IRS rules, such as the reintroduction of 1099-NEC in 2020.

2.4 Database Storage: Structured Tables

S/4HANA uses dedicated tables to store 1099 reporting data, including vendor IDs, document references, withholding tax details, and report totals.
HANA-native storage ensures high performance, fast data retrieval, and easier extraction for e-filing or auditing purposes.

2.5 Output / Filing

DRC supports generating IRS-compliant 1099 forms for print and electronic formats.
For advanced compliance, S/4HANA can integrate with third-party solutions for electronic filing and tax reporting automation.
Integration simplifies multi-state compliance and large-volume reporting.

3. Key Challenges & Known Issues in 1099 Reporting on S/4HANA

3.1 Missing or Incorrect Tax Numbers

Missing or incorrectly maintained TINs or SSNs in vendor master data are a leading cause of 1099 reporting failures.
Vendor roles and tax categories must be accurately configured to ensure correct inclusion in 1099 runs.

3.2 Withholding / Payment Configuration Issues

Payments may not be captured in 1099 reporting if withholding tax codes are missing or incorrectly assigned.
Cleared payments without proper withholding tax line items can lead to incomplete reporting.

3.3 Foreign Vendors & 1042-S Reporting

Payments to foreign vendors must be distinguished from domestic 1099 reporting.
Proper classification, treaty status, and withholding tax codes are necessary to avoid reporting errors.

3.4 IRS Rule Changes

Recent IRS changes, such as the separation of nonemployee compensation to 1099-NEC, require updates to SAP configuration and reporting templates.

3.5 System Limitations

In certain cases, foreign vendors may be incorrectly included or excluded in 1099 runs.
Layout issues in generated forms, such as missing recipient copies, can occur if configuration is not properly maintained.
Migration from legacy SAP or non-SAP systems may introduce data inconsistencies affecting 1099 reporting.

4. Implementing 1099 Reporting in S/4HANA — Step-by-Step Guide

4.1 Implementation Steps

Enable Withholding Tax / 1099 Feature Scope
- Activate statutory reporting and U.S.-specific features.
Vendor Master Data Review & Cleanup
- Verify TINs, vendor roles, and U.S. tax categories.
- Ensure foreign vendors needing 1042-S reporting are correctly classified.
Define Withholding Tax Codes
- Create or configure codes for each 1099 or 1042-S type.
- Map to correct G/L accounts and reporting categories.
Configure Statutory Reporting
- Set parameters for company code, reporting year, vendor selection, and tax number filters.
- Test in a sandbox system before production.
Test Data Scenarios
- Include domestic and foreign vendors, cross-currency payments, partial payments, and credit memos.
Generate Output
- Run DRC reports to create IRS-compliant 1099/1042-S forms.
- Validate totals, vendor information, and format compliance.
Reconciliation & Audit
- Reconcile SAP payments and 1099 totals.
- Archive master data snapshots and final output for audit.

5. Enhancements & Integrations

5.1 Integration with External Compliance Tools

Integration with third-party tax engines can help automate e-filing, multi-state reporting, and complex compliance requirements.

5.2 Custom Reporting & Analytics

Structured data allows creation of custom reports or dashboards to monitor 1099 exposure, vendor payments, and audit readiness.

5.3 Multi-Entity / Global Compliance

Organizations with U.S. and non-U.S. subsidiaries can consolidate statutory reporting in a single SAP-based compliance hub.

6. Real-Life Lessons & Common Pitfalls

Incorrect Vendor Master Data — Ensure TINs and vendor roles are accurate.
Payments Without Correct Withholding — Enforce AP process discipline.
Foreign Vendor Misclassification — Use proper 1042-S settings.
IRS Form Changes — Update configuration for new forms and thresholds.
High Volume Payments — Optimize HANA-native storage and extraction.
Non-SAP Payments — Ensure external payments are captured for 1099 compliance.

7. Third-Party Tools: When to Consider

SAP S/4HANA + DRC can handle core 1099 reporting.
For complex or high-volume scenarios, external tools can provide e-filing, vendor outreach, and multi-state automation.
Hybrid approaches combine SAP data integrity with external compliance automation.

8. Known Issues & SAP Limitations

Incorrect inclusion of foreign vendors
Layout issues in generated forms
Migration challenges from legacy systems
Empty reports despite payments due to configuration changes

9. Best-Practice Recommendations

Maintain clean vendor master data year-round.
Standardize AP and payment processes.
Run periodic mock 1099 runs.
Centralize compliance governance.
Leverage third-party compliance tools where necessary.
Archive all data and reports for audit purposes.
Stay current with IRS and SAP updates.

10. Future Outlook

Deeper integration with external tax engines
Improved foreign vendor and 1042-S support
Enhanced analytics and dashboards
Automated compliance workflows
Global compliance consolidation

Conclusion

SAP S/4HANA with Document & Reporting Compliance provides a unified, auditable, and scalable approach for 1099 reporting. Success depends on accurate vendor data, proper configuration, disciplined AP processes, and governance. Proper implementation allows SAP to become the backbone of your U.S. statutory compliance, ensuring accurate and timely reporting for all 1099 and 1042-S obligations.

euBP in Germany: Generating a Certificate File in Germany’s ITSG Trust Center Portal

2025-12-11T06:24:33.569000+01:00

Note:  The steps and processes described here are accurate as of the time of writing, but it's essential to stay updated with any changes on the ITSG portal that may affect this procedure. Detailed description in German can be found here: https://www.itsg.de/wp-content/uploads/Trust-Center-Registrierungsportal.pdf

Introduction

In this blog post, I will guide you through the process of generating a certificate file in ITSG Trust Center portal using POSTIDENT. This certificate is essential for establishing a connection between the SAP Document and Reporting Compliance, cloud edition (hereafter referred to as the "cloud edition") and the German pension insurance authority's system. This will allow you to submit the required financial accounting data from your business system SAP S/4HANA Cloud Public Edition integrated with the cloud edition to the pension insurance authority's system. The requirement is also known as euBP, an abbreviation of the local name Elektronisch unterstützte Betriebsprüfung, or "electronically supported company audit" in English.

About ITSG

ITSG, which stands for Information technology service point of the statutory health insurance GmbH, operates the ITSG Trust Center to create and manage certificates and facilitate secure electronic data exchange in the health and social services sectors.

Registration at ITSG Trust Center Portal

Access the registration portal of the ITSG Trust Center using the address https://registrierungsportal.itsg.de/regportal/client/de/login . For a new activity, choose the "Register" button and for an existing activity, choose the "Log On" button.

Log on the portal

Step 1 Enter Subscriber Number

First enter the company number, the special sender number or the paying office number for the application as a unique participant number that is to be used in electronic data exchange.

Enter subscriber number

Step 2 Enter Personal Data of Contact Person

The entry of the personal data of the contact person is divided into two areas: contact data and logon data.

Enter contact data

Enter logon data

Note: The first name and last name of the contact person must be entered in full according to the valid German identity card, valid German passport or the official identity cards and passport corresponding to the German identity card. If the name is incomplete or deviates, this leads to a rejection in the registration portal during identity verification after a POSTIDENT procedure.

Step 3 Confirm Email Address

After entering the contact data and logon data, a confirmation e-mail is sent to the specified e-mail address with an activation link for confirmation.

confirmation page

After confirmation, the logon can be performed with the logon data.

Logon after confirmation

Step 4 Start Identity Verification

The contact person must use the registration portal to carry out identification with a POSTIDENT procedure at Deutsche Post AG. The postal identification variant is only possible in Germany. Alternatively, online identification function with online ID function is supported, nut only a German identity card with activated electronic identity (eID) is permitted.

More information can be found: https://www.deutschepost.de/de/p/postident/privatkunden/faq.html

Identity verification

Step 5 Complete Identity Verification

After the identification has been carried out using a POSTIDENT procedure, the registration portal checks the electronic confirmation from the POSTIDENT system to determine whether the first names and last names entered in step 2 (possibly also double names and titles for last names) match completely and in the sequence specified in the identification documentation.

Complete identity verification

After successful identification, you must log on to the registration portal again to continue the further steps. If the identity verification was not completed successfully, you can start a new registration with a new identification using the “Restart Registration” button.

Step 6 Confirm Company Address

The applicant's address is checked against lists of the issuing agencies and must then be confirmed by the contact person. If the displayed address is correct and current, click the “Address is correct” button to proceed to the next step. At the end of the certification, an activation code for activating the security module is sent to the assigned company address of the applicant.

If your company is based outside Germany, you have the option of selecting the country here. As a contact person, you can also enter your name and, for example, manually add department to the displayed address of the applicant.

If the displayed address does not correspond to the actual company address of the applicant, a generated release letter cannot be delivered correctly later in the registration process. In this case, please arrange your adjustment of the company address at the issuing agency for your trading partner number.

Step 7 Select Billing Address and Delivery

By default, your invoice will use the previously confirmed applicant company address from step 6. If the invoice is to be sent to a different billing address, use a different billing address and enter the billing address.

Use a different billing address

Enter address

As an alternative, you can choose a delivery by e-mail. To do this, set a checkmark for "Use electronic delivery of invoice" and specify the e-mail address.

Electronic delivery

Step 8 Registration as a Collection Center

Optionally, you can register as a reporting office to transfer notifications for other company numbers in the employer procedure or for other institute indicators in the service provider procedure.

Step 9 Certificate Request Inbound Check

The registration portal checks in the background whether the applicant has submitted a technical certificate request that was created using the security module to the Trust Center. The execution of this step is divided into the three substeps: Generation of Electronic Keys, Transfer of Files to Trust Center, and Receipt Check of Certificate Request.

Generation of Electronic Keys

A GUID transaction number (GUID for short) is now assigned, which is used as a reference between the data in the registration portal and the technical data for generating the certificate from the applicant's system. The GUID consists of 36 characters. It is recommend that you use a technically supported copy and paste of the characters to avoid spelling errors or character shifts.

GUID

Working with the Separate Security Module

The security module is essential for applying for the electronic certificate at the ITSG Trust Center. This operation on the applicant's system is not supported by the registration portal. Therefore, you're recommended to actively log off the registration portal. Otherwise, the logoff takes place automatically.

In the security module, the key data for generating the electronic key pair (consisting of the public and private key) of the applicant must be entered manually and a certificate must be applied for. This key data must clearly match the request data entered in the registration portal.

The following are the key data required:

· Participant number - alternatively, company number, special sender number, paying office number, etc.

· Applicant Name (Company Name)

· Contact Full Name

After entering the required information, the security module generates the key pair (consisting of public and private key) with the hash code of the request key required for certification (public key of the participant in the request file). The private key remains in the IT system of the applicant.

The generated request key is stored by the security module in a so-called Request file (p10 format) to check the hash code by the contact person for a match in a subsequent request step (example extract of a hash code: E1D07A4B.….FC781).

The security module generates a so-called safety module. Hash code file (pdf format) with the hash code in SHA256 format. This contains the following information for a unique assignment:

The participant number - alternatively, company number, test company number, sender number, paying office number, etc.
Name of the company (company name)
Contact Name
Hash Code of Request Key (SHA256 Format)

Submitting the Files to the Trust Center

After the security module has generated the electronic key and a PDF file with the hash code has been saved, the two files must be transferred to the Trust Center with the request file (for example, 12345678.p10) and the hash code. The transfer of the files to the Trust Center depends on the selected request form and the supported functions in the used software (with or without OSTC online interface).

If the software used does not support the OSTC online interface of the Trust Center, you must manually transfer the two files with the request file and the hash code (PDF file) to the trust center. Optionally, a self-declaration for a reporting office (PDF file) can be transferred in addition to the request.

Initial applications without OSTC online interface

Call up the Web address https://www.itsg-trust.de/zap/home in a browser.

Initial application without OSTC interface

To uniquely assign the files to be transferred, you must specify the GUID transaction number (see substep Generation of Electronic Keys). After this, the three files are transferred to the Trust Center. The portal confirms the successful transfer with an internal transaction number (e.g. UP123456).

Request File
Hash Code File
Self-declaration reporting office (optional)

Initial application or online subsequent application via the OSTC online interface
For an online application using the OSTC online interface, all required application data and components (without self-declaration reporting office) are transferred automatically using the online interface. Only the GUID transaction number generated by the registration portal must be entered manually in the security module.

After execution, the applicant receives an online order number from the OSTC system, e.g. OE123456 for online initial application or e.g. OF123456 for an online follow-up application.

Inbound Check of Certificate Request

After you have successfully transferred your files to the ITSG Trust Center either via the upload portal or the OSTC online interface, the registration portal checks in the background whether you have transferred your file with the certificate request to the Trust Center with the corresponding GUID.

The transferred request file that contains the public key of the participant key is compared with the content of the hash code file during the inbound check by the Trust Center. After receiving the request file and the hash code file, the registration portal provides the Trust Center with the complete application data for the final check. If you have logged out of the registration portal or have been automatically logged out, you will need to log in again.

Inbound check

After a successful check from the registration portal that the certificate request with the corresponding GUID was transmitted to the Trust Center, the registration is automatically taken to the last step 10 and a release letter is sent.

Step 10 Enter a Tagging Code

After submitting the complete certificate application, the applicant receives and must complete the registration process by entering a release code in the registration portal.

The letter sent by the Trust Center to the applicant contains an activation code and the hash code of the key submitted for certification. Once the release letter has been received, the contact person or an authorized representative of the applicant must log on to the registration portal again. First, the hash code of the certification application must be visually checked for compliance with the release letter. You can then enter the activation code to complete the registration.

Enter activation code

The Trust Center now certifies the public key transmitted by the applicant and also transfers this key to the corresponding public directories of the Trust Center. As a result, the applicant is activated as a participant in electronic data exchange with employers or electronic data exchange with service providers.

You can use the participant number and the order number on the page https://www.itsg- trust.de/all/oav.php to register for online application tracking and view the status of your certification application.

Transferring Certified Participant Keys and Activation

The certified public key of the applicant is stored in a certificate file (e.g. B. 12345678.p7c) for the transfer. The contact person is informed by e-mail.

The certificate file is available for download via the online application tracking on the page https://www.itsg-trust.de/all/oav.php . The transfer of the certified key must be triggered manually by the applicant.

Configuring the Key Data and Certificate File in SAP BTP Cockpit

When you configure the communication settings between your business system SAP S4/HANA Cloud Public Edition and the German pension insurance authority's system, you need to enter the key data (such as company number or sender number) as identification number. When configuring the authentication settings, the certificate file should be uploaded.

Communication setting

Authentication Setting

For more information, see the documentation Integration with a Service for Electronic Submission on the SAP Help Portal.

I hope you find this information helpful. If you have any further questions, feel free to leave a comment on this blog post or discover more information in the following documentation:

Important Update: Tax Reporting Date Change for Canadian Company Codes

2025-12-11T21:12:48.173000+01:00

✨At SAP, your feedback truly matters—and we take it seriously. Based on your input, we’ve introduced an important change: the Tax Reporting Date will now always default to the Posting Date when creating accounting documents for Canadian company codes.

📊This means that SAP Document and Reporting Compliance (DRC) sales tax reports for Canada will now use the posting date as the tax reporting date.

🔍What’s Changing?

✅The Tax Reporting Date is always suggested as the Posting Date for Canadian company codes, regardless of the T001-XSTDT configuration.
🛠Standard Enhancement Implementation VATDATE_VALUES_DEFAULT_SAP from BAdI Definition VATDATE_RULES has been adjusted.

Depending on your SAP S/4HANA version:

💻SAP S/4HANA & SAP S/4HANA Cloud, Private Edition:
Please review SAP Note 3678561 – DRC Canada: Corrections to Tax Reporting Date.
Changes were made in the standard Enhancement Implementation VATDATE_VALUES_DEFAULT_SAP of BAdI VATDATE_VALUES. If you have a custom implementation of this BAdI, changes will not be reflected.
☁️SAP S/4HANA Public Cloud:
Starting December 14, 2025, your sales tax DRC reports will automatically use the posting date as the tax reporting date.
🆕New Customers:
The updated logic will apply by default.

📌Example:
If you receive and post a vendor invoice in January 2026 (posting date), but the document date is December 2025, DRC will include the invoice in the January 2026 tax report.

📚Want to Learn More?
For more details about SAP Document and Reporting Compliance for Canada, please visit the SAP Help Portal.

Key Apps for GSTR-6 and ISD Management: India

2025-12-16T07:02:59.741000+01:00

This blog provides a summary of the apps and their functions required to file GSTR-6 in SAP S/4HANA Cloud (formerly known as SAP S/4HANA Cloud Public Edition).

GSTR-6 is the mandatory monthly return for an Input Service Distributor (ISD), a critical compliance piece for large enterprises with centralized procurement, such as software companies with multiple offices under the same PAN. The ISD mechanism allows the Head Office to receive input service invoices (like consulting or software licenses) centrally and then distribute the associated Input Tax Credit (ITC) to the unit locations where the services are actually consumed.

The SAP S/4HANA system manages this distribution automatically through ISD program known as J1IG_ISDN . It calculates how much of the total ITC each branch should get. This calculation is usually based on a fair measure, like the turnover (sales) of each branch relative to the others and maintained in configuration settings.

SAP generates special internal documents (ISD invoices) that formally transfer the tax credit to each branch. This allows the individual branches to legally reduce their own tax bill by the credit they received.

Here are the apps that assist users in creating ISD invoices and filing GSTR-6 returns:

Re-distribute and Create ISD Invoices
eDocument Cockpit/ Manage Electronic Documents
Resolve Electronic Document Inconsistencies

Run Statuary Reports

I. Re-distribute and Create ISD Invoices:

This app helps users to create, display and redistribute Input Service Distribution invoices. Users select the filter criteria like Company code, Fiscal Year, ISD Business Place and selection of documents based on posting date. Further, based on the selection, A processing action can be triggered to view the ISD distribution, Change ISD distribution or to Post ISD distribution and create ISD invoices.

App Name/ Launcher Title	Re-distribute and Create ISD Invoices
App ID	J1IG_ISDN
Business Catalogue	SAP_FIN_BC_GLO_GSTISD_IN_PC
Business Catalogue Description	Globalization - Input Service Distribution for India
Business Role	SAP_BR_PURCHASER_IN
Business Role Description	Purchaser for India

II. EDOCUMENT Cockpit/ Manage Electronic Documents

Users can use either eDocument Cockpit app or Manage Electronic Document App to work with electronic documents.

App Name/ Launcher Title	Manage Electronic Documents
App ID	F4306
Business Catalogue	SAP_SD_BC_GLO_EDOC_PC
Business Catalogue Description	Globalization - Electronic Documents
Business Role	SAP_BR_BILLING_CLERK
Business Role Description	Billing Clerk

App Name/ Launcher Title	eDocument Cockpit
App ID	EDOC_COCKPIT
Business Catalogue	SAP_SD_BC_GLO_EDOC_PC
Business Catalogue Description	Globalization - Electronic Documents
Business Role	SAP_BR_BILLING_CLERK
Business Role Description	Billing Clerk

eDocument cockpit app allows users to process electronic documents (eDocuments) that are created automatically based on source documents. Users can display eDocuments, submit documents in XML to external systems and monitor the respective status for subsequent actions.

What are the differences between the Manage Electronic Documents app and eDocument Cockpit app?

III. Resolve Electronic Document Inconsistencies

This is the app where users can review inconsistencies in the documents for example a document is available in GSTR-6A but missing in Book of accounts or if a document is missing in Tax authority but available in Book of accounts. Users then decide to accept the documents based on available info or may wait for the correction of the records. Only the accepted documents are picked by ISD distribution program. Please note this is the same action you will be navigated to 'Prepare ITC' action mentioned in following step IV - Run Statuary Reports.

App Name/ Launcher Title	Resolve Electronic Document Inconsistencies - India
App ID	F8406
Business Catalogue	SAP_SD_BC_GLO_EDC_IN_PC
Business Catalogue Description	Globalization - Electronic Documents Consistency for India
Business Role	SAP_BR_BILLING_CLERK_IN
Business Role Description	Billing Clerk for India

IV. Run Statuary Reports

This is the main App where GSTR-6 filing steps are performed. There are 5 actions/steps involved as shown below:

App Name/ Launcher Title	Run Statutory Reports
App ID	F1515
Business Catalogue	SAP_FIN_BC_GL_REPORTING_CN_PC
Business Catalogue Description	General Ledger - Reporting for India
Business Role
Business Role Description	General Ledger Accountant for India

We have gone through the 4 important apps for GSTR-6 Filing. This concludes this blog for GSTR-6 Filing starting from ISD distribution to reconcile and file your returns. Please ensure you have assigned the required business roles to locate these applications. Refer to Fiori Application Libary for latest information about catalogues, roles and spaces. Further resources can be accessed through SAP Help Portal:

GSTR6 Report

Invoice Submission to the Singapore Tax Authority: How to Automate Invoice Note Filling in XML Files

2025-12-18T11:09:57.209000+01:00

Are you a GST-registered business in Singapore subject to the GST InvoiceNow Requirement? If so, you need to submit invoice data electronically to the Inland Revenue Authority of Singapore (IRAS). This may include providing invoice notes in XML files submitted to IRAS. This blog provides guidance on how you can automate this step.

A few quick notes:

SAP Document and Reporting Compliance, cloud edition is the solution to support GST InvoiceNow requirements. For an overview, check out this blog: SAP Document and Reporting Compliance for Singapore GST InvoiceNow.
This blog applies to SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, SAP S/4HANA, and SAP ERP.
This blog quotes information from some IRAS guidelines. The quoted information is accurate as of the publication date of the blog. As these IRAS guidelines are subject to change, we recommend checking the latest versions for the most current information.

What Is an Invoice Note?

Here’s the definition of invoice note from TX2 - Annex - Data Specifications, which can be downloaded from here:

A textual note that gives unstructured information that is relevant to the Invoice as a whole such as the reason for any correction or assignment note in case the invoice has been factored.

An invoice note is displayed in one of these XML elements, depending on the invoice type:

ubl:Invoice / cbc:Note for invoices
ubl:CreditNote / cbc:Note for credit notes

IRAS specifies the scenarios where an invoice note is mandatory, such as credit notes and self-billing invoices. For certain special scenarios, IRAS prescribes their note texts. For example, according to the e-Tax Guide “Adopting GST InvoiceNow Requirement for GST-registered Businesses (First Edition)”, you must include this exact note text in self-billing invoices:

The invoice is a Buyer Created Tax Invoice. The tax shown is your output tax due to the Comptroller of GST.

The Challenge: Automating Beyond the Standard

To include an invoice note in a submitted XML file, you need to enter the note text in a specific source document field. For those scenarios that require specific note texts, it would be a great time-saver if the system can fill in them automatically. The standard solution already does this for these scenarios:

Self-billing invoices
Customer invoices with the GST category code SRCA-S (Customer accounting supply made by supplier)
Supplier invoices with the GST category code TXCA (Standard-rated purchases of prescribed goods subject to customer accounting)

What about other scenarios? Manually entering invoice notes is really time-consuming and prone to error.

The Solution: BAdI to the Rescue

You can define your own logic for populating invoice notes using the following Business Add-Ins (BAdIs):

Product	BAdI
SAP S/4HANA SAP S/4HANA Cloud Private Edition SAP ERP	EDOC_ADAPTOR: SET_OUTPUT_DATA method
SAP S/4HANA Cloud Public Edition	EDOC_ADAPTOR_Cloud: SET_OUTPUT_DATA method

In this blog, we'll show you how to create a BAdI implementation that populates invoice notes for customer invoices (eDocument type: SGC5C_INV) in these scenarios based on the tax code:

Scenario	Invoice Note Text Prescribed by IRAS	Tax Code You Use
Gross Margin Scheme	The transaction is under the Gross Margin Scheme.	S1
Approved Marine Fuel Trader Scheme	The Payment of GST is not required under the AMFT Scheme.	Z1
Discounted Sale Price Scheme	The transaction is under the Discounted Sale Price Scheme.	Z2

Step-by-Step Guide: Sample BAdI Implementation in SAP S/4HANA, SAP S/4HANA Cloud Private Edition, and SAP ERP

Step 1: Create a customer package.

Some objects are created when you create a BAdI implementation. To transport these objects across a customer landscape, create a customer package or choose an existing customer package.

Step 2: Create an enhancement implementation.

In this example, we create an implementation named ZEI_EDOC_ADAPTOR_SG_C5 by doing the following:

Call up the SE19 transaction.
Select the New BAdI radio button in the Create Implementation section and enter ES_EDOCUMENT in the Enhancement Spot field. Choose Create.
Enter ZEI_EDOC_ADAPTOR_SG_C5 as the enhancement implementation name and Implementation: eDocument Adaptor Singapore as the short text. Choose Continue.

When prompted for a package, enter the package created or chosen in step 1.
In the window that appears next, do the following:
- Enter ZEI_EDOC_ADAPTOR_SG_C5 as the BAdI implementation name.
- Enter ZCL_EDOC_ADAPTOR_SG_C5 as the implementation class.
- Select the BAdI definition EDOC_ADAPTOR.
Choose Continue. When prompted for a package, enter the package created or chosen in step 1.
Activate your changes.
Expand the tree for the BAdI implementation you just created. Double-click Filter Values.
In the filter values details on the right, choose Create Filter Combination.
In the Choose Filter dialog, select COUNTRY. Choose Continue.
Double-click the COUNTRY filter.
In the Display Filter Value dialog, enter SG as Value 1 and select = as Comparator 1. Choose Continue.

The filter combination you just created looks like this:

Step 3: Update the ZCL_EDOC_ADAPTOR_SG_C5 class.

Call up the SE24 transaction.
Enter the object type ZCL_EDOC_ADAPTOR_SG_C5. Choose Change.
Double-click the method IF_EDOC_ADAPTOR~SET_OUTPUT_DATA.
Add the sample code below into this method:

        FIELD-SYMBOLS: <fs_mwskz> TYPE mwskz,
                       <fs_tax_data_tab> TYPE any,
                       <fs_tax_data> TYPE any.

        io_source->get_data_reference(
          RECEIVING
            rd_data = DATA(lv_data)
        ).

        IF lv_data IS NOT INITIAL.
          ASSIGN COMPONENT 'TAX_DATA' OF STRUCTURE lv_data->* to <fs_tax_data_tab>.
          IF <fs_tax_data_tab> IS ASSIGNED.
            LOOP AT <fs_tax_data_tab> ASSIGNING <fs_tax_data>.
              ASSIGN COMPONENT 'MWSKZ' OF STRUCTURE <fs_tax_data> TO <fs_mwskz>.
              IF sy-subrc = 0.
                CASE <fs_mwskz>.
                  WHEN 'S1'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The transaction is under the Gross Margin Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN 'Z1'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The Payment of GST is not required under the AMFT Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN 'Z2'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The transaction is under the Discounted Sale Price Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN OTHERS.
                ENDCASE.
              ENDIF.
            ENDLOOP.
          ENDIF.
        ENDIF.

5. Save and activate your changes.

Guidance for Customers Using SAP S/4HANA Cloud Public Edition

You need to add the sample code below into the SET_OUTPUT_DATA method of the EDOC_ADAPTOR_Cloud BAdI:

Tip:
For a step-by-step guide on how to implement this BAdI, check out the following blog:
Enhancing the Standard XML File for Electronic Documents using the BAdI EDOC_ADAPTOR_CLOUD

        FIELD-SYMBOLS: <fs_mwskz> TYPE mwskz,
                       <fs_tax_data_tab> TYPE any,
                       <fs_tax_data> TYPE any.

        io_source->get_data_reference(
          RECEIVING
            rd_data = DATA(lv_data)
        ).

        IF lv_data IS NOT INITIAL.
          ASSIGN COMPONENT 'TAX_DATA' OF STRUCTURE lv_data->* to <fs_tax_data_tab>.
          IF <fs_tax_data_tab> IS ASSIGNED.
            LOOP AT <fs_tax_data_tab> ASSIGNING <fs_tax_data>.
              ASSIGN COMPONENT 'MWSKZ' OF STRUCTURE <fs_tax_data> TO <fs_mwskz>.
              IF sy-subrc = 0.
                CASE <fs_mwskz>.
                  WHEN 'S1'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The transaction is under the Gross Margin Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN 'Z1'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The Payment of GST is not required under the AMFT Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN 'Z2'.
                        IF iv_edoc_type = 'SGC5C_INV'.
                            output_inv-invoice-note-base-base-content = 'The transaction is under the Discounted Sale Price Scheme.'.
                            cs_output_data = output_inv.
                        ENDIF.
                  WHEN OTHERS.
                ENDCASE.
              ENDIF.
            ENDLOOP.
          ENDIF.
        ENDIF.

Wrapping Up

Hope this blog is helpful for you. We'd love to hear feedback from you. Feel free to share comments below. Let's learn from each other!

To learn more about the solution, refer to the following documentation on SAP Help Portal, which covers business task procedures, configuration, and more:

Product	Documentation Links
SAP S/4HANA, SAP S/4HANA Cloud Private Edition	Electronic Customer Invoices: Submission to the Tax Authority Electronic Supplier Invoices: Submission to the Tax Authority
SAP ERP	Electronic Customer Invoices: Submission to the Tax Authority Electronic Supplier Invoices: Submission to the Tax Authority
SAP S/4HANA Cloud Public Edition	Electronic Customer Invoices: Submission to the Tax Authority Electronic Supplier Invoices: Submission to the Tax Authority

KSeF 2.0: Certificate & Authorization for Establishing Connection with the Cloud Edition

2025-12-18T15:19:30.712000+01:00

The Polish authorities have postponed their original plan to introduce mandatory e-invoices through KSeF in 2024. This delay has been used to rebuild the infrastructure and launch KSeF 2.0, bringing significant changes to the authentication process, meaning the following:

For KSeF 1.0, you used a token-based authentication. This method will be phased out by 2026.
For KSeF 2.0, you, as an SAP customer, use a certificate-based authentication.

This blog post guides you through the steps of authenticating your system with the KSeF 2.0 environment. As a prerequisite, you have already performed the general integration settings as described in this blog post: KSeF 2.0: Setup and Integrate Your System with the Cloud Edition.

KSeF Environments

KSeF 2.0 operates across three different environments, as follows:

Test Environment

Supports both FA (2) and FA (3) schemas

Flexible authentication - can work without real certificates, only an auto-generated certificate in the API

Ideal for initial development and testing

Connects with the test plan of the cloud edition

Note: You only need to create a communication setting associated with your NIP number, uploading certificates is not necessary. However, if you choose to upload a certificate, the system considers your certificate for the authentication.

Pre-production (Demo) Environment

Supports only FA (3) schema

Requires certificate authentication

Mirror of production for final validation

Connects with the test plan of the cloud edition

Production Environment

Supports only FA (3)

Requires certificate authentication

Live operational system

Connects with the standard plan of the cloud edition

Note: The FA (3) schema version supports structured invoice attachments, but their use requires approval from the Ministry of Finance.  

Certificate and Key

KSeF certificates are generated through dedicated applications provided by the Polish Ministry of Finance. The application you use depends on your target environment:

Test and Pre-production Environments: Use the KSeF 2.0 app

Production Environment: Use the MCU (Moduł Certyfikatów i Uprawnień) app until the KSeF 2.0 app becomes available for production

To access these applications and generate your certificate, you authenticate using different methods depending on whether you're logging in as a physical person or as a company.

Login as a Physical Person

If you authenticate as an individual, you have the following two options:

Electronic Trusted Profile

A fast and free authentication method for individuals

No purchase required

Qualified Electronic Signature

Purchased from a certification authority

The primary method before Electronic Trusted Profile was introduced

Note: When using either of these methods, the generated certificate is linked to the NIP of the person authenticating to the KSeF 2.0 app or MCU app. This means:

All invoices signed with this certificate are linked to the personal NIP

The company must submit the ZAW-FA form to associate the company with the authenticated person

Only one person can be authorized through the ZAW-FA form

This authorized person can then grant permissions to other employees within the company

Login as a Company

Qualified Electronic Seal

Used by organizations and based on the entity's Tax Identification Number

Purchased from a certification authority

Not a new requirement introduced by KSeF, but many companies may not have one yet

Note: When using a qualified electronic seal, the generated certificate is linked to the company's NIP, which means:

The ZAW-FA form is not required
Invoices are issued in the name of the company without any reference to a personal NIP
This provides a cleaner separation between company operations and individual employees

Use the following links to access the appropriate KSeF application for your environment:

Test Environment: KSeF 2.0 Test App

Pre-production (Demo) Environment: KSeF 2.0 Demo App

Production Environment: MCU App

For additional guidance and support, the Ministry of Finance provides comprehensive e-learning materials through their "Środy z KSeF" (Wednesdays with KSeF) program. Access these resources at: KSeF E-Learning Portal

SAP Document and Reporting Compliance, cloud edition requires valid KSeF certificates regardless of the authentication method you used to access the KSeF 2.0 app or MCU app. Whether you authenticated as a physical person or as a company, ensure you have generated both the certificate and key files from the tax authority portal before proceeding with system configuration.

You can learn more about how to submit applications for certificates and download certificates from the KSeF portal. For more information, see Moduł Certyfikatów i Uprawnień (MCU).

Note: The duration of the authentication process in the KSeF System Certificates and Entitlements Module (MCU) using a qualified certificate depends on the issuer of the given certificate (CA - Certification Authority).

KSeF verifies the validity of the certificate through the services provided by the relevant certification center. In the event of temporary unavailability or delays on the part of the certificate issuer, the authentication time may be extended.

We emphasize that:

KSeF is not responsible for the duration of the certificate verification,

Before configuring your system, ensure you have generated the certificate and key files from the tax authority portal.

System Configuration

To upload your certificate and key, perform the following steps:

1. In the SAP Document and Reporting Compliance, cloud edition launchpad, access the Manage Communication Settings - External Parties app and create a communication setting.

Give the communication setting a name.
Select the E-Invoices Through KSeF 2.0 (PL) communication type.
Enter the NIP number as the identification number.
Choose Create.

2. Open your communication setting and choose "Client Certificate and Key" as the authentication setting.

3. Enter the certificate and key generated from the tax authority portal, along with the password:

For Certificate, upload the .crt file.
For Key, upload the .key file.

4. For test or pre-prod environment only: Under Additional Properties, add Tax Authority System with value "test" or "pre-prod" to indicate test or pre-production environment, respectively.

5. (Relevant only for customer invoices) Create an additional communication setting to enable the offline mode.

Give the communication setting a name.
Select the E-Invoices Through KSeF 2.0 (PL) - QR Code communication type.
Enter the NIP number as the identification number.
Choose Create.

6. Open your communication setting and choose "Client Certificate and Key" as the authentication setting.

7. Enter the certificate and key generated from the tax authority portal, along with the password:

For Certificate, upload the .crt file.
For Key, upload the .key file.

Note that previously, you were able to connect with the test environment of KSeF 2.0 without creating a communication setting in the Manage Communication Settings app. Now, you need a communication setting. This means the following:

If you have a communication setting for E-Invoices Through KSeF 2.0 (PL) without a certificate and have added "test" as Tax Authority System for the additional property, you connect to the test environment of KSeF 2.0 with self-generated certificate.
If you have a communication setting for E-Invoices Through KSeF 2.0 (PL) with certificates and have added “test” as Tax Authority System for the additional property, you connect to the test environment of KSeF 2.0 with your certificate.
If you have a communication setting for E-Invoices Through KSeF 2.0 (PL) with certificates and have added “pre-prod” as Tax Authority System for the additional property, you connect to the pre-prod environment of KSeF 2.0.

It is not possible to connect to the test environment of KSeF 2.0 without maintaining the additional property.

For more information, access our official documentation on the SAP Help Portal. See Managing Communication Settings | SAP Help Portal.

Legal Change - YATIRIMTESVIK scenario support through Extensibility in DRC Türkiye

2025-12-22T05:46:34.048000+01:00

This blog post introduces a guide on how to implement the new legal requirement released by GIB (GELİR İDARESİ BAŞKANLIĞI) for invoices issued under a valid Investment Incentive Certificate (Yatırım Teşvik Belgesi – YTB) through Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud.

Background
We have already published a Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud on how S/4HANA Public Cloud customers can leverage developer extensibility to modify content of XMLs produced during electronic invoice submissions, pertaining to specific business and legal requirements.

Note for: SAP S/4HANA Private Cloud and ECC environments:

In SAP S/4HANA Private Cloud and ECC environments, the exact same process exists through extensibility, however the BAdi implementation would have to be done for EDOC_ADAPTOR instead of EDOC_ADAPTOR_CLOUD.

What’s New?
GIB has published a legal requirement pertaining to invoices issued under valid Investment Incentive Certificate which impacts a few companies on 21st November, 2025. In this blog we would aim to address the requirement through the learnings of the previous blog highlighted in the background.

What’s the technical specifications of the requirement?
Currently system does not automatically determine whether a billing or finance document is YTB-related or not. The customer must explicitly indicate that the invoice belongs to a YTB investment project and provide the necessary values. As part of the legal requirement authority following is an easy requirement with an UBL (Universal Business Language, an ISO standard XML) representation:

New Profile IDs
- YATIRIMTESVIK – for eInvoicing scenarios
- EARSIVFATURA – for eArchive scenarios
New Invoice Type Codes under each invoicing scenarios
- YATIRIMTESVIK – for eInvoicing scenarios.
  - SATIS – Sales invoices
  - ISTISNA – Exception invoices
  - IADE – Refund or Return invoices
- EARSIVFATURA – for eArchive scenarios
  - YTBSATIS – consumer/eArchive sales invoice
  - YTBISTISNA – consumer/eArchive exception invoices
  - YTBIADE – consumer/eArchive refund/return invoices
Mapping of new identification tag - ContractDocumentReference
- ID field should be the filled up with the incentive certificate number
  - schemeID of this would be "YTBNO"
- IssueDate should be filled up with the investment certificate date in DD/MM/YYYY format
Adjustments to existing tag - TaxTotal
- The waived VAT amount should be shown in XPath TaxTotal/TaxSubtotal/TaxAmount only if profileID is YATIRIMTESVIK with invoice type value is ISTISNA, or profileID is EARSIVFATURA with invoice type value is YTBISTISNA.
- Reason codes similar to tax exemption reason codes have been introduced as part of the technical structure from GIB available at their website. These reason codes have to be filled in XPath TaxTotal/TaxSubtotal/TaxCategory/TaxExemptionReasonCode.
- Subsequently new reason code descriptions have also been introduced as part of the technical structure which should go in the XPath TaxTotal/TaxSubtotal/TaxCategory/TaxExemptionReason corresponding the reason code filled in above step.

Adjustments to existing tag - InvoiceLine
- For YTB related scenarios the XPath tag InvoiceLine/Item/CommodityClassification/ItemClassificationCode should be filled with 01, 02, 03, or 04 in case of the scenario of profile ID of YATIRIMTESVIK/EARSIVFATURA.
- In case the ItemClassificationCode is 01 (Machine Equipment), and reason code in TaxExemptionReason is 308 as per the legal requirement, then
  - XPath tag InvoiceLine/Item/Name should be filled with machin name
  - XPath tag InvoiceLine/Item/ItemInstance/Name should be filled with Machine ID.
  - XPath tag InvoiceLine/Item/ItemInstance/ProductTraceID should be filled with the Machine Sequence Number/Equivalent details

How does a sample code looks like using Developer Extensibility?

The prerequisites, roles and BAdI Enhancement Implementation names have already been mentioned in our previous blog (details - Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud ).

Let's illustrate how this can be tailored to suit the above legal requirement.

    FIELD-SYMBOLS:
      <lfs_cs_doc_data>      TYPE edo_tr_inv_ubl_format_req,
      <fs_invoice_tab>       TYPE edo_tr_e_doc_turkey_invoic_tab,
      <fs_invoice_el>        TYPE edo_tr_e_doc_turkey_invoice_el,
      <fs_payment_means_tab> TYPE edo_tr_payment_means_tab,
      <fs_add_doc_ref>       TYPE edo_tr_additional_document_tab.

    ASSIGN COMPONENT 'DOC_DATA' OF STRUCTURE cs_output_data TO FIELD-SYMBOL(<lv_data>).
    IF <lv_data> IS ASSIGNED.
      IF iv_edoc_type = 'TR_BINV'. "Turkey Basic eInvoice
        IF iv_interface_id NE 'TR_GETSTATUS_REQ'.
          ASSIGN COMPONENT 'PARAMETERS' OF STRUCTURE cs_output_data TO <lv_data>.
          IF <lv_data> IS ASSIGNED.
            ASSIGN cs_output_data TO <lfs_cs_doc_data>.
            IF <lfs_cs_doc_data> IS ASSIGNED.
              ASSIGN <lfs_cs_doc_data>-parameters-package-elements TO <fs_invoice_tab>.
              IF <fs_invoice_tab> IS ASSIGNED.
                LOOP AT <fs_invoice_tab> ASSIGNING <fs_invoice_el>.
* This is just a sample implementation, you can decide on the conditional assignment based on your business needs.
                  <fs_invoice_el>-element_list-invoice-profile_id-base-base-content = 'YATIRIMTESVIK'.
                  <fs_invoice_el>-element_list-invoice-invoice_type_code-base-base-content = 'SATIS'.
" Filling up ContractDocumentReference
                  <fs_invoice_el>-element_list-invoice-contract_document_reference =
                    VALUE #( ( id-base-base-content = '1234567890'
                               id-base-base-scheme_id = 'YTBNO'
                               issue_date-base-content = '19990912' ) ).
" Filling up TaxTotal
                  <fs_invoice_el>-element_list-invoice-tax_total =
                    VALUE #( ( tax_subtotal =
                    VALUE #( ( tax_amount-base-content = '123.40'
                               tax_amount-base-currency_id = 'TRY'
                               tax_category-tax_exemption_reason_code-base-base-content = '308'
                               tax_category-tax_exemption_reason-base-base-content = 'Delivery of Investment Goods under Incentive Scheme 13/d' ) ) ) ).
" Filling up InvoiceLine
                  LOOP AT <fs_invoice_el>-element_list-invoice-invoice_line ASSIGNING FIELD-SYMBOL(<lfs_invoice_line>).
                    <lfs_invoice_line>-item-commodity_classification = VALUE #( ( item_classification_code-base-base-content = '01' ) ).
                    READ TABLE <lfs_invoice_line>-item-commodity_classification ASSIGNING FIELD-SYMBOL(<lfs_comm_class>)
                      WITH KEY item_classification_code-base-base-content = '01'.
                    IF sy-subrc IS INITIAL.
                      <lfs_invoice_line>-item-name-base-base-content = 'Machine Name'.
                      <lfs_invoice_line>-item-item_instance = VALUE #( ( serial_id-base-base-content = '9999999999'
                                                                         product_trace_id-base-base-content = '7878787878787878' ) ).
                    ENDIF.
                  ENDLOOP.
                ENDLOOP.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.

Spoiler

Disclaimer - This is just a sample code; actual business conditions are not depicted through this.

Result:

When you display the XML file of the electronic document in the eDocument Cockpit (EDOC_COCKPIT) corresponding to the above invoicing scenario, you will see that the mentioned tags populated. Please note that based on actual submission of this document to authorized service provider, error handling and troubleshooting can be tackled.

Conclusion
With recent enhancements to the Türkiye Document and Reporting Compliance solution, SAP has made it significantly easier to cater to targeted and industry specific legal requirements in electronic document outputs.

This improvement gives you more flexibility and helps ensure compliance with Türkiye’s legal requirements. This blog is the first of the many blogs coming up to demonstrate legal requirements in an easy consumable way

Canada T4A-NR 2025 Regulatory Changes: SAP Document and Reporting Compliance(DRC)

2026-01-09T08:25:14.256000+01:00

Towards the end of 2025, the Canada Revenue Agency (CRA) rolled out updates to the T4A-NR slip, summary forms, and the T619 XML schema. These changes, which will affect filings due on or before the last day of February 2026, have been seamlessly integrated into SAP Document and Reporting Compliance (DRC) solutions, SAP S/4HANA Cloud Public Edition, and SAP S/4HANA Cloud Private Edition /On-Premise. Here’s a detailed look at what these updates entail and how SAP is ensuring compliance.

Key Regulatory Changes

Updated CRA Forms: The CRA has released new 2025 versions of the T4A-NR slip and the T4A-NR Summary (T4A-NR-SUM) for the 2025 tax year. While the content changes are minimal, using the correct form version is essential to avoid filing issues.
T619 XML Schema Updates:

Mandatory Language Code: To ensure consistent language identification for CRA communications, the T619 electronic transmittal now requires a language code to specify English or French, denoted by “E” or “F” for every submission. Previously optional, this field is now mandatory for 2025 filings.
No Empty Fields in XML: A new validation rule mandates that any optional XML element with no data must be omitted entirely. This means if a data field doesn’t apply or is blank, the system should not generate that XML tag at all, as including empty tags can lead to file rejection by the CRA.

SAP's Support of Regulatory Changes

As part ofSAP’s end-to-end compliance vision, the SAP Globalization Product Management team has proactively delivered the necessary updates to accommodate these CRA changes, to ensure that customers can generate compliant T4A-NR slips, summaries, and XML files across SAP Cloud ERP solutions:

SAP Document and Reporting Compliance for SAP S/4HANA Cloud Public Edition: The T4A-NR form and summary Adobe print forms have been updated in the SAP Document and Reporting Compliance (DRC) and SAP S/4HANA Public Cloud to match the CRA’s 2025 PDF layout. Electronic filing content for T4A-NR has been enhanced to output XML according to the new schema, delivered via the regular quarterly release.
SAP Document and Reporting Compliance for SAP S/4HANA Cloud Private Edition/On-Premise: SAP Note 3691523 – “Canada T4A-NR Withholding Tax Reporting: Legal Changes 2025” was released, along with a support package containing the updated forms and electronic report definitions. Applying this note or support pack will ensure the system produces the correct 2025 forms and XML.

Next Steps

Review and Implement SAP Update: Ensure your SAP S/4HANA system has the 2025 year-end legal change for T4A-NR applied. For SAP S/4HANA On-Premise, apply SAP Note 3691523. For SAP S/4HANA Cloud, confirm you’re on the latest release that includes the T4A-NR changes. Implement these updates before year-end processing.

Test Your Reporting: Generate a sample T4A-NR slip, summary, and XML file in a test environment. Verify that the slip and summary display “2025” and the latest form text. Ensure the language element is present and correctly set, and confirm that there are no empty tags in the file.

Consult CRA Resources: Refer to the CRA’s official XML specifications page for the updated schema download and guidance for 2025/2026 filings. The CRA’s T4A-NR guide (RC4445) for 2025, updated December 2025, is also a helpful reference. Links to the schema files and CRA documentation are available on the CRA website.

Call to Action

SAP customers and partners can avoid last-minute scrambles and ensure a smooth tax filing season by taking the following actions:

Review our published "What's New" SAP Help Portal documentation, apply, and test the delivered SAP changes promptly.
Engage your IT or SAP support team to confirm that your system is outputting the new form and schema correctly. Leverage the Regulatory Change Manager for agility in adapting to new legal requirements.
Visit the CRA’s XML specification page for the official schema and test your files against it. With proper preparation, you’ll be ready to file your 2025 T4A‑NR returns without issues.
Connect with us via the SAP support channels or Canada Localization Workzone if questions arise during this update process.

Legal Change - IDIS scenario support through Extensibility in DRC Türkiye

2026-01-12T10:36:54.888000+01:00

This blog post provides a step-by-step guide on how to implement the new legal requirement released by GIB (GELİR İDARESİ BAŞKANLIĞI) for eInvoice and eDespatch under the Construction Rebar Tracking System (IDIS) using Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud.

Background:
We have already published a blog titled Developer Extensibility for Document and Reporting Compliance Türkiye in SAP S/4HANA Public Cloud which explains how SAP S/4HANA Public Cloud customers can leverage developer extensibility to modify the content of XML files generated during electronic invoice submissions, in accordance with specific business and legal requirements.

Note for SAP S/4HANA Private Cloud and ECC environments:
In SAP S/4HANA Private Cloud and SAP ECC environments, the same extensibility approach is available. However, in these systems, the BAdI implementation must be carried out for EDOC_ADAPTOR instead of EDOC_ADAPTOR_CLOUD.

What’s New?
GIB has published a legal requirement for invoices issued under the Construction Rebar Tracking System, which impacts certain companies starting from 21st November 2025. In this blog, we aim to address this requirement by building on the learnings from the previous blog highlighted in the background.

What are the technical specifications of the requirement?
Currently, the system does not automatically determine whether a billing or finance document is related to the Construction Rebar Tracking System. Customers must explicitly indicate that the invoice belongs to a Construction Rebar Tracking System and provide the required values.
As part of the legal requirements published by the authorities, the following new Profile IDs must be used in the UBL (Universal Business Language, an ISO standard XML) representation:

IDIS - for eInvoice Scenarios
IDISIRSALIYE – for eDespatch scenarios

eInvoice

ProfileID for IDIS Scenario
For IDIS-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDIS.
- Cardinality: 1 (Mandatory)
- This value determines that the invoice belongs to the IDIS scenario
- The solution will automatically populate this value for applicable
Shipment Number (Sevkiyat Numarası) at Header Level:
- Mapped to: Invoice/AccountingSupplierParty/Party/PartyIdentification
  SE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.
  Example: SE-1345840
- IssueDate should be filled with the investment certificate date in DD/MM/YYYY format
Tag Number (Etiket Numarası) at Item Level:
- Invoice/InvoiceLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits.
  SchemeID should be ETIKETNO.
  Example: CV0152457

Sample code:
The prerequisites, roles and BAdI Enhancement Implementation names have already been mentioned in our previous blog.

FIELD-SYMBOLS:
  <lfs_cs_doc_data>      TYPE edo_tr_inv_ubl_format_req,
  <fs_invoice_tab>       TYPE edo_tr_e_doc_turkey_invoic_tab,
  <fs_invoice_el>        TYPE edo_tr_e_doc_turkey_invoice_el,
  <fs_add_doc_ref>       TYPE edo_tr_additional_document_tab.

ASSIGN COMPONENT 'DOC_DATA' OF STRUCTURE cs_output_data TO FIELD-SYMBOL(<lv_data>).
IF <lv_data> IS ASSIGNED.
  IF iv_edoc_type = 'TR_BINV'. "Turkey Basic eInvoice
    IF iv_interface_id NE 'TR_GETSTATUS_REQ'.
      ASSIGN COMPONENT 'PARAMETERS' OF STRUCTURE cs_output_data TO <lv_data>.
      IF <lv_data> IS ASSIGNED.
        ASSIGN cs_output_data TO <lfs_cs_doc_data>.
        IF <lfs_cs_doc_data> IS ASSIGNED.
          ASSIGN <lfs_cs_doc_data>-parameters-package-elements TO <fs_invoice_tab>.
          IF <fs_invoice_tab> IS ASSIGNED.
            LOOP AT <fs_invoice_tab> ASSIGNING <fs_invoice_el>.
* This is just a sample implementation, you can decide on the conditional assignment based on your business needs.
              <fs_invoice_el>-element_list-invoice-profile_id-base-base-content = 'IDIS'.
              <fs_invoice_el>-element_list-invoice-invoice_type_code-base-base-content = 'SATIS'.
              " Filling up ACCOUNTING_SUPPLIER_PARTY
              <fs_invoice_el>-element_list-invoice-accounting_supplier_party-party-party_identification =
                VALUE #( ( id-base-base-content = 'SE-1345840'
                           id-base-base-scheme_id = 'SEVKIYATNO'
                           issue_date-base-content = '19990912' ) ).
              " Filling up InvoiceLine
              LOOP AT <fs_invoice_el>-element_list-invoice-invoice_line ASSIGNING FIELD-SYMBOL(<lfs_invoice_line>).

                <lfs_invoice_line>-id-base-base-scheme_id = 'ETIKETNO'.
                <lfs_invoice_line>-id-base-base-content = 'CV0152457'.

              ENDLOOP.
            ENDLOOP.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
  ENDIF.
ENDIF.

This is only a sample code and does not represent the actual business conditions.

eDespatch

ProfileID for IDISIRSALIYE Scenario
For IDISIRSALIYE-relevant invoices, the ProfileID in the UBL-TR XML will be set to IDISIRSALIYE.
- Cardinality: 1 (Mandatory)
- This value determines that the invoice belongs to the IDISIRSALIYE scenario
- The solution will automatically populate this value for applicable
Shipment Number (Sevkiyat Numarası) at Header Level:
- Mapped to: /DespatchAdvice/DespatchSupplierParty/Party/PartyIdentification
  SE-<number> with schemeID as SEVKIYATINO – This would carry the shipment number prefixed with SE. The total number of characters is 10.
  Example: SE-1345840
- IssueDate should be filled with the investment certificate date in DD/MM/YYYY format
Tag Number (Etiket Numarası) at Item Level:
- /DespatchAdvice/DespatchLine/Item/AdditionalItemIdentification/ID should be filled with tag number generated within the scope of IDIS (Rebar Monitoring System). This number is a 9-character alphanumeric value, where the first 2 characters are letters followed by 7 numeric digits.
  SchemeID should be ETIKETNO.
  Example: CV0152457

Result:
When you display the XML file of the electronic document in the eDocument Cockpit (EDOC_COCKPIT) corresponding to the above invoicing scenario, you will see that the mentioned tags are populated accordingly. Please note that any error handling and troubleshooting will depend on the actual submission of this document to the authorized service provider.

Conclusion:
With recent enhancements to the Türkiye Document and Reporting Compliance solution, SAP has made it significantly easier to tailor electronic document outputs.
This improvement gives you more flexibility and helps ensure compliance with Türkiye’s legal requirements.

New Events for Outbound Nota Fiscal

2026-01-20T14:48:41.847000+01:00

Hi everyone!

Today, I would like to share with you some impactful insights directly from an SAP Note, which outlines a streamlined approach for sending the events listed in the NF-e Technical Note 2025.002 v1.30, published October 2025.

You can implement these changes in the outbound invoicing option for Brazil by following the instructions on SAP Note 3692197 and SAP Note 3689265.

Check out the latest updates and features in our What's New session on the SAP Help Portal:

SAP S/4HANA: New Events for Outbound Nota Fiscal

SAP ERP: New Events for Outbound Nota Fiscal

The Process

To send these events, you need to create a specific structure, as described in the "Manual da SEFAZ". You should create the new structure through the SEND_GENERIC_EVENT method from the CL_NFE_CLOUD_NFE_PROCESSOR class. This effectively sends the events using the IS_GENERIC_EVENT parameter, which is essential for declaring the structure.

You have to name this structure as ZNFE_MAP_EVENT_XXXXXX. You replace the XXXXXX for the number of supported events from the NF-e Technical Note 2025.002 v1.30. For example: ZNFE_MAP_EVENT_112110.

In this structure, you'll find control fields and event-specific fields that are mapped directly to the XML event. You have to build the DET_EVENTO structure, which can vary depending on the type of event. The field names differ between the backend system and their appearance in the cloud solution. Check the following example:

The structure of the event 112110 (Informação de efetivo pagamento integral para liberar crédito presumido do adquirente) is denoted as ZNFE_MAP_EVENT_112110. This structure has the following string fields and their equivalent in the cloud solution, following the rules of name conversion:

ATTR_VERSAO -> converted to a__versao to create the XML (you can check the rule to create XML attributes instead of elements in SAP Note 3692197)

DESC_EVENTO -> descEvento

C_ORGAO_AUTOR -> cOrgaoAutor

TP_AUTOR -> tpAutor

VER_APLIC -> verAplic

Check the XML file obtained after the name conversion. To download the XML file, follow the steps mentioned in SAP Note 3692197.

<detEvento versao="1"> 
   <descEvento>Informação de efetivo pagamento integral para liberar crédito presumido do adquirente</descEvento> 
   <cOrgaoAutor>35</cOrgaoAutor> 
   <tpAutor>1</tpAutor> 
   <verAplic>1</verAplic> 
   <indQuitacao>1</indQuitacao> 
</detEvento>

DET_EVENTO Structure Declaration

Create the structure  ZNFE_MAP_EVENT_112110. Ensure the structure matches the following definition:

TYPES: 
  BEGIN OF ZNFE_MAP_EVENT_112110, 
    a__versao        TYPE string, " XML Attribute 
    desc_evento      TYPE string, 
    c_orgao_autor    TYPE string, 
    tp_autor         TYPE string, 
    ver_aplic        TYPE string, 
    ind_quitacao     TYPE string, 
  END OF ZNFE_MAP_EVENT_112110.

Populating DET_EVENTO

You populate the DET_EVENTO  using assignment based on input parameters of the program. Check the following example:

DATA : ls_event_112110 TYPE ZNFE_MAP_EVENT_112110. 
ls_event_112110-a__versao = p_ver.         " Version - XML attribute 
ls_event_112110-desc_evento = p_desc.     " Event description 
ls_event_112110-c_orgao_autor = p_orgaut. " Author organization code 
ls_event_112110-tp_autor = p_tpaut.       " Type of authority 
ls_event_112110-ver_aplic = p_verapp.     " Application version 
ls_event_112110-ind_quitacao = p_indqui.  " Settlement indicator

Steps to Send a Generic Event

Step 1: Declare and Populate IS_GENERIC_EVENT

The IS_GENERIC_EVENT structure contains high-level control fields required for all types of events, including details such as issuing state, issuer's CNPJ, and access key (P_ACCKEY). Use the following template to populate the structure:

DATA : ls_generic_event        TYPE nfe_cloud_nfe_map_gnrc_evt. 
ls_generic_event-uuid                = lo_uuid_generator->generate_uuid( ). " Unique identifier 
ls_generic_event-authorize_uuid      = p_authid.                           " Reference UUID 
ls_generic_event-issuing_state       = p_state.                           " State code 
ls_generic_event-environment_type    = 'HOMOLOGATION'.                    " Environment 
ls_generic_event-issuing_type        = 'NORMAL'.                          " Issuing type 
ls_generic_event-issuer_identifier   = p_issuer.                          " Issuer CNPJ 
ls_generic_event-receiver_identifier = '74544297000192'.                " Receiver CNPJ

Step 2: Declare and Populate Specific DET_EVENTO

Based on the event type (P_TYPE), decide the specific structure for DET_EVENTO. For example:

If P_TYPE = '112110', use the predefined structure ZNFE_MAP_EVENT_112110: 

DATA : ls_event_112110 TYPE ZNFE_MAP_EVENT_112110. 
ls_event_112110-a__versao = p_ver.         " Attributes mapped as XML attributes 
ls_event_112110-desc_evento = p_desc. 
ls_event_112110-c_orgao_autor = p_orgaut. 
ls_event_112110-tp_autor = p_tpaut. 
ls_event_112110-ver_aplic = p_verapp. 
ls_event_112110-ind_quitacao = p_indqui. 
ls_generic_event-event_info-det_evento->* = ls_event_112110.  " Assigning DET_EVENTO structure

Step 3: Send the Event

Invoke the SEND_GENERIC_EVENT method:

TRY. 
  ls_result = lo_processor->send_generic_event( 
      is_generic_event       = ls_generic_event 
      is_company_definition  = ls_company_defition ). 
CATCH cx_nfe_cloud_invalid_value INTO lx_invalid_value. 
  lx_invalid_value->raise_message( ). 
  RETURN. 
ENDTRY.

Checking Event Status

To verify the status of sent events, follow these steps:

Service Locator: Use CREATE_SERVICE_LOCATOR_OBJECT from the CL_J_1BNFE_CF_MONITOR class.

Service Type Parameter: Reference C_SERVICE_EVENT_STATUS from CL_J_1BNFE_CF_CONSTANT.

Map Events and Generate JSON: Utilize the STRUCTURE_SERIALIZATION method from CL_J_1BNFE_CF_EVENT_UPDATE.

Client and OA2C Creation: Use SET_REQUEST_JSON and SEND_REQUEST_TO_CLOUD methods from CL_J_1BNFE_CF_SERVICE_COMM.

Transform JSON Response: Apply GET_RESPONSE_FROM_CLOUD to convert the response into an NF-e format.

Develop Response Structure: EVENT_TABLE_DESERIALIZATION method helps integrate this into an NF-e structure.

Building Your Application

Beyond these steps, you'll need to develop or extend your applications to:

Fill in necessary event data.

Trigger creation and submission based on business processes.

Implement error handling, logging, and monitoring according to your compliance standards.

That's a wrap for today! I hope this guide serves as a handy reference for anyone navigating the intricacies of sending events in SAP. Stay tuned for more insights and happy coding!

Until next time,

Natália

SAP e-Invoicing Application Engineer

SAP ERP公有云2602版本中国本地化亮点解析：增值税发票管理与财务功能优化

2026-01-23T07:13:14.961000+01:00

SAP ERP公有云2602版本为中国用户带来了一系列实用的本地化功能优化，这些更新旨在帮助企业更好地满足中国税务合规要求，提升财务管理效率。本文将详细介绍以下更新内容：

基于SAP Document and Reporting Compliance的更新
- 中国增值税发票管理更新
- 中国现金流量表更新
- 电子凭证会计数据标准解决方案更新
中国现金流量表（IDCNCASH）旧方案迭代更新

中国增值税发票管理(基于SAP Document and Reporting Compliance)更新

销项增值税发票管理功能更新- SAP金税接口（GTI）新增配置：计费折扣税

在大多数客户系统中，计费折扣税(Tax Discount Amount，简称TDA)通常不在SAP销售与分销(SD)模块中计算。为了在中国增值税发票中准确体现这一金额，SAP金税接口(GTI)在设计之初采用了自行计算的方式。

简而言之，GTI一直采用以下方式计算TDA:

从SD获取不含税额(Net Value)
获取税额(Tax Amount)
获取折扣金额(Discount Amount)
在GTI中独立计算税收折扣金额(TDA)

在某些特殊场景下，为确保最终税额的准确性，GTI会调整含税总额(Gross Amount)，以确保在扣除折扣后的税额在金税系统和财务中是一致的。这导致SAP销售订单与GTI开具发票上的含税总额出现差异，给业务用户的日常工作带来困扰。

从CE2602版本开始，SAP GTI提供了标准配置选项，允许用户直接从SD模块获取税收折扣金额，而非在GTI中重新计算。

具体步骤：

使用新增标准配置项定义TDA金额设置：用户在配置“金税流程的缺省值” - “计费折扣税”中，输入在SD中定义的条件类型Condition Type ID。
图1：新增“计费折扣税“金额设置
设置折扣金额（Discount Amount）属性：用户还需在Define GTI Tax Invoice Keys再次确认‘Price Mode’配置，以保证GTI计算正确：
- 如果客户在SD为折扣金额的定价条件设置是含税，那么金税中Price Mode需选择‘Discount Amount with VAT’；
- 如果客户在SD为折扣金额的定价条件设置是不含税，那么金税中Price Mode需选择‘Discount Amount without VAT’；

通过这种方式，这一改进有效解决了数据不一致的问题，减少因系统差异导致的业务混乱，让业务流程更加顺畅。

销项增值税发票管理功能更新 – “备注”延长至630个字符

在关于全面数字化电子发票（FDEI）使用常见问题清单的更新公告中，提到一项变更涉及 “备注”字段的字符长度限制，主要变化是从之前的230个字符延长至630个字符。同时，字符计数方法也进行了更新：一个汉字计为三个字符，而每个数字和英文字母计为一个字符。

图2: 支持正常读写超过230个字符的备注字段

这次调整意味着企业在开具电子发票时，可以在备注栏填写更详细的交易信息。例如，合同编号、项目名称、特殊说明等内容都能更完整地记录，减少了因字数限制而需要简化描述的困扰。

使用FDEI的纳税人，建议征询当地税务机关获取最新的FDEI的常见问题清单。

欢迎访问SAP Regulatory Change Manager了解该法律变更及SAP产品功能变更的更多信息。

销项增值税发票管理功能更新 – “行项目限制”扩展至2000行

开具全电发票的模版中，对“发票明细行数“的最新要求（填表说明）是：超过2000行后可能会导致系统异常无法开具发票。

从CE2602起，使用中国增值税发票管理来开具全面数字化电子发票（FDEI）的企业，可以在Define GTI Tax Invoice Keys中配置“行项目限制”为2000，系统会自动拆分超过2000行限制的电子发票。

图3: 设置行项目限制为2000

引入这个新配置，可使生成的发票文件不超过税局服务器承载能力，符合限制要求，确保生成的发票文件都能成功上传。

欢迎访问SAP Regulatory Change Manager了解该法律变更及SAP产品功能变更的更多信息。

进项增值税发票管理功能更新 – 发票入账标识

在金税系统的全电发票流程中，发票入账标识是一项重要的新功能。简单来说，当买方将全电发票标记为"已入账"后，卖方就无法单方面撤销该发票了。如果卖方确实需要撤销，必须先获得买方的批准才能操作。

这项功能的核心目的是防止供应商随意撤销发票，保护买方的权益。需要特别注意的是，这里的"入账"概念与SAP系统中的财务凭证过账是两回事——前者是税务层面的标识，后者是企业内部的财务处理。

从CE2602起，在进项增值税发票管理解决方案中，我们新增“同步发票入账”流程，在业务系统和金税系统之间同步发票入账信息。

图4: 显示发票入账状态

具体步骤：

对于非直连场景：

用户首先在金税系统中维护进项增值税发票的入账信息。然后，用户在SAP业务系统中，使用“管理增值税进项发票”应用，选择新按钮“同步发票入账”，更新入账期间、入账类型、发票入账同步日期，并指定是否入账发票以保持信息同步。

图5: 非直连场景下的同步发票入账

2. 对于直连场景：

用户使用“管理增值税进项发票”应用，选择新按钮“同步发票入账”，维护入账期间、入账类型并通过 API 将数据发送到金税系统以完成入账。

图6: 直连场景下的同步发票入账

然后，处理结果会从金税系统写回SAP业务系统。

图7: 金税系统处理结果写回SAP

目前系统支持以下发票入账类型（与金税系统保持一致）：

02：入账（企业所得税税前扣除）
03：入账（企业所得税不扣除）
04：入账（个人所得税经营所得税前扣除）
05：入账（个人所得税经营所得不扣除）
06：入账撤销

已入账状态同步至税局后，表示买方已确认发票详情，并准备将其用于会计和税务目的。如果需要撤销已入账的发票，卖方必须获得买方的批准。这意味着在发票被标记为“已入账”后，任何更改都需要双方的知情和同意。

引入发票入账信息管理这一新流程，为交易增加了安全性，确保发票信息的不可变性，同时保护买方的利益。

进项增值税发票管理功能更新 – 发票常规信息的新增字段

为进一步完善进项发票的同步信息，从CE2602起，我们还添加了以下常规信息字段：

图8: 常规信息新增字段

（新增）发票风险等级：
- 01：正常
- 02：异常凭证
- 03：疑似异常凭证

请注意，管理进项增值税申报应用中不提供风险级别为异常的发票。

（新增）特定要素类型：
- 01, 成品油
- 02, 稀土
- 03, 建筑服务
- 04, 货物运输服务
- 05, 不动产销售服务
- 06, 不动产经营租赁服务
- 07, 代收车船税
- 08, 通行费
- 09, 旅客运输服务
- 10, 医疗服务（住院）
- 11, 医疗服务（门诊）
- 12, 自产农产品销售
- 13, 拖拉机和联合收割机
- 14, 机动车
- 15, 二手车
- 16, 农产品收购
- 17, 光伏收购
- 18, 卷烟
- 20, 农产品
（新增）蓝字发票号码
（增强）用途：
- 0：未使用
- 1：已申请抵扣
- 2: 已申请退税
- 3: 已申请代办退税
- 4: 已勾选不抵扣（历史数据）
- 5: 已申请代办退税（历史数据）
- 6: 已申请不抵扣
- 7: 内销转出口
- 8: 出口转内销
- 9: 准予退税
- 10: 不予退税
- 11: 冬奥退税

中国现金流量表(基于SAP Document and Reporting Compliance)更新

基于SAP Document and Reporting Compliance的中国现金流量表（报表ID:CN_CASHFLOW_N）和SAP Group Reporting 集团报表解决方案，都使用交易类型Transaction Type（ACDOCA- RMVCT）字段作为手动判断来补充自动确定逻辑。然而，这导致了在同一交易中需要使用两种不同的交易类型用于出具单体财务报表和合并报表，从而引发财务报告过程中字段使用冲突。

基于SAP Document and Reporting Compliance的中国现金流量表（报表ID:CN_CASHFLOW_N），此前在定义限制参数时，仅支持交易类型 Transaction Type、功能范围 Functional Area和税码Tax Code。

从CE2602起，基于SAP Document and Reporting Compliance的中国现金流量表将支持灵活的自定义限制参数，包括ACDOCA表中SAP标准字段以及自定义字段作为限制参数，以替代交易类型，从而解决了上述字段使用冲突的问题。

图9：支持用户定义更多限制参数（除交易类型、功区域和税码之外）：

图10：支持客户使用自定义字段用于限制参数

通过引入更灵活的参数定义，企业可以更好地适应其特定的财务报告需求。这不仅简化了报告流程，还减少了由于交易类型冲突而导致的错误和不一致性。最终，这将提高财务报告的准确性和效率，使企业能够更好地做出战略决策。

电子凭证会计数据标准解决方案(基于SAP Document and Reporting Compliance)更新

由中华人民共和国财政部机九部门联合制定的《电子凭证会计数据标准》为电子凭证会计信息化处理提供了统一的技术规范和结构化数据标准，支持包含结构化数据的电子凭证用于接收、报销、入账、归档等全流程各环节。

从CE2602起，SAP中国本地化团队将通过分阶段的方式，发布符合《电子凭证会计数据标准》的本地化新功能，以及对现有财务本地化方案的增强。

在CE2602版本中，用户可通过SAP Document and Reporting Compliance新增的“中国会计核算信息的结构化数据文件（会计核算数据标准）“报表类别，将入账相关的信息按照《电子凭证会计数据标准》生成XBRL 电子文件，即入账信息结构化数据文件；支持的电子凭证类型包括：

全面数字化的电子发票（不包含铁路电子客票，航空运输电子客票行程单）
增值税电子发票

（以上均包含专用发票及普通发票）

图11：新增报表类别支持

具体步骤：

使用“运行法定报表-中国总账报表“应用，输入相应报表期间、报表实体等信息后，运行并生成并管理入账信息结构化文件（XBRL文件）：

图12：运行并生成入账信息结构化文件（XBRL文件）

2. 运行成功后，用户可查看并下载入账信息结构化文件（XBRL文件），示例如下：

图13：入账信息结构化文件（XBRL文件）示例

SAP本地化团队将陆续发布更多本地化功能，以支持客户实现《电子凭证会计数据标准》中电子凭证的接收、报销、入账、归档等全流程各环节，敬请期待。

欢迎访问SAP Regulatory Change Manager了解该法律变更及SAP产品功能变更的更多信息。

中国现金流量表（IDCNCASH）旧方案迭代更新

中国现金流量表方案经历了多个阶段的发展，从最初的基于旧科目抵销确定方案的GUI报表（IDCNCASH），到基于SAP Document and Reporting Compliance的新方案（CN_CASHFLOW_N）。旧方案IDCNCASH采用了较为传统的技术架构，与SAP最新的平台和UI技术脱节，存在性能优化空间有限的问题。而新方案则充分利用了SAP Document and Reporting Compliance的优势，提供了更高效的性能和更丰富的功能。

以下是新旧方案多维度对比：

在性能方面，旧方案存在超时dump的问题，而新方案则利用HANA内存数据库的卓越设计，性能优越
在多币种支持方面，新方案能够支持所有分配给公司代码和账套的货币类型，而旧方案仅支持有限的几种货币类型
在数据源方面，新方案直接从核心财务模块的ACDOCA表取数，与其他相关报表高度一致，而旧方案的数据源与核心财务模块不一致

根据SAP 产品战略政策和产品规划，旧中国现金流量表（IDCNCASH）已进入迭代窗口。因此从CE2602起，我们正式启动旧中国现金流量表（IDCNCASH）的迭代工作。建议所有使用旧方案的客户，尽快迁移到基于SAP Document and Reporting Compliance的新现金流量表方案。为了帮助客户顺利完成迁移，SAP本地化团队为客户准备了详细的实施手册和视频教程：

从CE2602 开始，支持新旧方案的切换操作：

1. 用户可通过旧方案中的弹窗，或“新版本“开关按钮，切换至新方案。

图14：旧方案内新增弹窗并支持跳转至新方案

2. 切换至新方案后，用户可使用“新版本“开关按钮切换回旧方案；欢迎用户在”提供反馈“中，提出新方案使用过程中的问题或建议。

图15：从旧方案切换至新方案后，新方案的弹窗信息

SAP全球化部门将继续为您提供更智能、更自动化的本地化解决方案。

关于SAP ERP公有云2602版本中国本地化功能的更多信息，欢迎访问SAP Regulatory Change Manager或参考SAP帮助文档。

免责声明

本博客文章中提供的信息基于发布时的现行法律法规，相关主管部门可能随时对其进行修改。SAP保留在必要时更新本文内容的权利，但不承担持续更新的义务。

New Brazil NFe Integration with SAP Document and Reporting Compliance, could edition

2026-01-25T21:36:02.297000+01:00

Electronic Invoices (aka NF-e – Nota Fiscal) for Brazil with SAP Document and Reporting Compliance, Cloud Edition

Background
In 2017, SAP introduced NF-e integration within SAP Document and Reporting Compliance (SAP’s strategic solution for electronic invoices and statutory reporting worldwide) through two dedicated cloud services:

SAP Document and Reporting Compliance, Outbound Invoicing Option for Brazil
SAP Document and Reporting Compliance, Inbound Invoicing Option for Brazil

This era is now over: As part of its simplification strategy, SAP is now including the functionality in SAP Document and Reporting Compliance, cloud edition, delivering a comprehensive global solution with optimised processes and metrics; without requiring separate onboarding or cloud services. SAP Document and Reporting Compliance, cloud edition is SAP’s strategic, global service for e-invoicing and statutory reporting. Customers connect once and scale across countries and scenarios! It will cover Brazil NF-e in addition to more than 25 other countries (scenarios list).

Join us for the webinar on February 26, 2026 to learn about the availability of Brazil NF-e through SAP Document and Reporting, cloud edition, its impact on existing customers, migration steps and effort as well as pre-requisites. We are excited to meet you there!

SAP is now Plateforme agréée (PA) for e-invoicing and e-reporting

2026-01-25T22:25:32.930000+01:00

Excited to share that SAP is now officially recognized as a Plateforme agréée (PA) for e‑invoicing and e‑reporting for France!
This certification reinforces SAP’s commitment to supporting companies in meeting France’s 2026–2027 mandatory e‑invoicing and e‑reporting requirements. As a Plateforme agréée, SAP enables:
✔️ Secure and compliant exchange of structured e‑invoices
✔️ Automated transmission of transaction and payment data to the French tax authorities
✔️ Alignment with regulatory formats and lifecycle requirements (Factur‑X, UBL, CII, e‑reporting standards)
✔️ An end‑to‑end digital compliance journey for companies operating in France

This milestone strengthens SAP’s mission to deliver regulatory‑relief‑as‑a‑service, helping organizations adapt with confidence in a fast‑evolving regulatory landscape. The future of compliant invoicing in France is here, and SAP is ready to lead the way!

Therefore, mark your calendar on February 17, 2026 at 3pm and join our webinar to understand the latest regulatory updates, gain insights into the planned release timelines and supported capabilities with SAP Document and Reporting Compliance, cloud edition, concluded with a system demonstration and setup information. Register now

Transitioning to the New China Cash Flow Statement Solution: What You Need to Know

2026-02-09T07:21:20.487000+01:00

As regulatory reporting requirements continue to evolve, SAP is committed to providing customers with modern, efficient solutions that meet compliance needs while leveraging the latest technology capabilities. For organizations operating in China, an important transition is underway regarding the Cash Flow Statement reporting solution.

Understanding the Evolution

The legacy China Cash Flow Statement solution (IDCNCASH) has served customers well over the years, but technological advancement necessitates modernization. Since S/4HANA CE2111/OP2021, SAP has offered an enhanced solution built on the SAP Document and Reporting Compliance (DRC) platform, which provides significant improvements across multiple dimensions.

Key Advantages of the New Solution

The DRC-based Cash Flow Statement addresses several limitations of the legacy approach:

Performance and Architecture: The new solution leverages SAP HANA's in-memory database capabilities, delivering superior performance even with large data volumes. Unlike the legacy solution, which faced timeout issues with substantial datasets, the modern architecture is designed for scalability.
Data Consistency: By sourcing data directly from the ACDOCA table, the new solution ensures alignment with core financial data and other related reports. This eliminates the data inconsistencies that occasionally occurred with the legacy solution's separate data sources.
Enhanced Currency Support: While the legacy solution supported only four currency types, the new solution accommodates all currency types assigned to company codes and ledgers in S/4HANA, providing greater flexibility for multinational operations.
Proactive Error Detection: The new solution determines offsetting accounts during document posting rather than at report runtime, enabling earlier identification and resolution of issues.
Advanced Functionality: Built on the DRC platform, the solution offers scheduled tasks, historical snapshots, analytical views, and customer extension capabilities—features that support more sophisticated reporting workflows.

Migration Timeline and Support

Starting with CE2602, SAP has introduced toggle functionality allowing users to switch between the legacy and new solutions, facilitating a gradual transition.

When users open the old version app, a dialog will promote the new version app with functional benefits, and allow a direct switch to the new version app (DRC: Run Statutory Reports).

In the new app (DRC), users can submit feedback on their experience and switch back to the old app at any time.

While SAP has extended the transition window to accommodate the large user base, customers are encouraged to plan their migration proactively.

Implementation Resources

SAP has developed comprehensive implementation materials to support the transition, including detailed white papers and video tutorials.

Implementation handbook (white papers) in Chinese/English

Video tutorial: Step-by-Step Implementation Guide: SAP Document and Reporting Compliance (DRC) Cash Flow Statements

Next Steps

Customers currently using the legacy Cash Flow Statement solution should begin evaluating their migration timeline. Review SAP Note 3700711 - Replacement of Existing 'Cash Flow Statements - China' App with 'China Cash Flow Statements' Report in Document and Reporting Compliance for the latest information on the transition roadmap and consult the implementation handbook for technical guidance.

As with any significant system change, adequate planning and testing are essential. The investment in migration will position your organization to benefit from enhanced performance, improved data consistency, and access to advanced reporting capabilities that support evolving business needs.

For implementation support, please refer to the SAP Help Portal or contact your SAP representative.

FAQ:

Q1: What is SAP DRC?

A: SAP Document and Reporting Compliance is a unique and competitive statutory reporting framework that helps you manage your regulatory requirements across the globe. Statutory reporting, a component of SAP Document and Reporting Compliance, is a global solution that enables timely creation, generation, and submission of statutory reports to authorities in the correct format. It ensures compliance with complex and dynamic legal requirements. For more details, refer to SAP Help Portal for Statutory Reporting.

Q2: For S/4HANA Public Cloud customers, does the new DRC Cash Flow Statement require activation of new scope items?

A: Yes.

With 1J2, you can generate and download the China Cash Flow Statement in both PDF and TXT(CSV) format.
With additional 5XU, you can preview and edit (change the figures and regenerate files with full audit trail), perform analytics, trace back to source documents, and extend the existing report using design time.

Customers need to contact your SAP Account Executive if they have any question related to licenses.

Q3: After the legacy solution is retired, how can customers use the new solution to view historical Cash Flow data?

A: After you activate and configure the DRC cashflow report, you can run the Data Migration Tool (for Public Cloud and OP, or transaction code FIRU_CF_OFF_ACC) to display historical data in the new DRC cashflow report.

Note:

We recommend that you do the solution switch and run the migration program during year-end financial closing or at the beginning of the year.
If you purchased 5XU, you can use the drill-down tool in the analytics view for troubleshooting. If the new solution is configured correctly, the data in the new and legacy solutions should be consistent (legacy solutions use similar offsetting account determination configuration and calculation logic).
This tool only performs data migration. It can't resolve the effort required for customers to implement the new DRC cashflow report.

Q4: What existing legal reports have been replaced by SAP DRC statutory reports so far?

A: SAP Note 2480067 - Replacement of Existing Legal Reports with DRC reports provides information about the legacy ABAP legal reports that statutory reports provided with the SAP Document and Reporting Compliance framework are succeeding.

Validation Messages: CBS and IBS Configuration

2026-02-13T12:55:58.563000+01:00

As part of the transition to the new CBS (Contribuição sobre Bens e Serviços) and IBS (Imposto sobre Bens e Serviços) tax structure, SAP has introduced three new validation messages when you receive inbound electronic fiscal documents.

Understanding the New Messages

The messages address common discrepancies that may arise when processing XML documents under Brazil Tax Reform:

J1B_NFE660: Expected CBS/IBS tax rate is X but tax rate in XML is Y

This message alerts users when there's a mismatch between the expected tax rate configured in the system and the rate specified in the incoming XML document.

J1B_NFE661: CBS/IBS tax not available in XML for purchase order item X

This validation triggers when the required CBS/IBS tax information is missing from the XML for a specific purchase order item.

J1B_NFE663: Tax group CBS/IBS from XML not available in the current Tax Code

This message appears when the tax group referenced in the XML document cannot be found in the system's current tax code configuration.

You can configure each message to appear as either Warning or Error, depending on your business requirements. For detailed instructions on configuring these messages through transaction OBMSG, please refer to Configuring Messages 660, 661, and 663 in OBMSG and OBA5.

Have you found this blog post useful? If so, choose “Like”, share it with your colleagues, and follow me for similar content. 

You are welcome to leave your questions and read similar blog posts on the  SAP Document and Reporting Compliance SAP Community. Don’t forget to follow the  SAP Electronic Invoicing for Brazil (SAP Nota Fiscal Eletronica)  tag and the  SAP Document and Reporting Compliance Community  to keep up with the latest NF-e news. 

Thank you, and until next time, 
Juliana Jarotzky

GRC, Trade and Tax in SAP Cloud ERP 2602

2026-02-19T14:07:53.164000+01:00

Hello Experts,

I'm excited to share the update regarding our latest release - GRC, Trade and Tax in SAP Cloud ERP 2602. This update highlights many significant innovations from SAP Risk and Assurance Management, SAP Watch List Screening, SAP Document and Reporting Compliance, as well as SAP Cloud Identity Access Governance.

For a quick overview of the top release highlights for GRC with 2602, you can watch the video below.

Video 1. Release Highlight Video for GRC, Trade and Tax in SAP Cloud ERP 2602

This blog covers the following innovations:

SAP Document and Reporting Compliance

AI-assisted trend analysis and summary for reports (beta)
Embedded analytics to facilitate VAT adjustments
E- verify and Automated Handling of Draft VAT Returns from Authorities
Enabling Electronic Invoices Through KSeF 2.0 for Poland

SAP Risk and Assurance Management

Extended analytical and reporting capabilities: new reporting dashboards with SAP Analytics Cloud, enterprise edition

SAP Enterprise Threat Detection

Intelligent alert handling and investigation recommendations
Management-focused monitoring dashboard

SAP International Trade

Export declaration for plants abroad in the context of Registration for Indirect Taxation Abroad (RITA)

SAP Watchlist Screening

Delta Screening

SAP Document and Reporting Compliance

AI-assisted trend analysis and report summary

Tax accountants often spend significant time validating data by comparing current tax figures with previous returns. To accelerate this process, we introduce AI-assisted trend analysis for VAT returns. This feature helps tax experts by automatically uncovering hidden trends, flagging outliers, and detecting root causes for discrepancies. It provides intelligent summaries that can be used to simplify the approval process and support future audits. This innovation allows the team to move from reactive validation to proactive analysis.

Picture 1. AI-assisted trend analysis and report summary

Value Proposition

Reduce the time needed to interpret VAT data across periods, leading to faster reviews, quicker approvals, and shorter reporting cycles.
Accuracy is improved and compliance risk is reduced. This helps identify anomalies early, minimizing manual errors and lowering the risk of incorrect filings.
Easy to make clear and informative data-driven decisions.

Capabilities

The analysis highlights key trends, fluctuations, and irregularities, and flags values that help to identify potential errors or compliance risks.
Provide concise summary of key VAT insights to support faster reviews, approvals, and decision-making.

Embedded analytics to facilitate VAT adjustments

During the preparation of statutory reports, tax experts require deep visibility into their data to ensure accuracy. With the 2602 release, the 'Manage Tax Items' activity within SAP Document and Reporting Compliance is enhanced with a powerful ''analyze data" option.

This provides tax experts with additional fields and the flexibility to analyze tax data to identify anomalies. Now you can easily see how invoices are mapped to your VAT returns and pinpoint any documents that might have been excluded, enabling seamless adjustments integrated directly with accounting. To further tailor the solution, you can now use extensibility to plug in your own custom analytics CDS views, allowing you to choose between standard SAP-delivered queries or your own defined views for analysis.

Video 2. Embedded analytics to facilitate VAT adjustments

Value Proposition

Advances the VAT review and adjustment by integrating analytics.
Improves accuracy and strengthens compliance through data-driven decisions.
Reduces manual effort and reliance on offline analysis and external tools.
Enhances analytical transparency and enables faster and more confident decision-making.

Capabilities

Embedded analytics within the Manage Tax Items for Legal Reporting application
Direct access to detailed VAT tax line-item records with added data points
Interactive analytical views with charts, filters, and drill-down capabilities
Trend analysis and comparisons across multiple VAT dimensions
Identification of documents for inclusion in or exclusion from VAT returns
Analysis at the point of action without switching applications
Support for efficient VAT reconciliation and compliance preparation

For more information, see: Manage Tax Items for Legal Reporting | SAP Help Portal

E- verify and Automated Handling of Draft VAT Returns from Authorities

A growing number of tax authorities are providing pre-populated, or draft, tax returns based on real-time transactional data. Our latest update helps you automate the handling of these draft returns, ensuring consistency with your company's books. With this feature, you can pull auto-populated returns from an authority's portal and automatically compare them with the returns prepared in your ERP system to identify any mismatches.

Based on the reconciliation results, you can then process actions such as submitting a delta file, accepting, or rejecting the draft. This streamlines the entire process, from review and correction to the submission of the final return.

Video 3. E- verify and Automated Handling of Draft VAT Returns from Authorities

Enabling electronic invoices through KSeF 2.0 for Poland

With the Polish Ministry of Finance enforcing the use of electronic invoices through the KSeF 2.0 platform beginning in February 2026, we are equipping you to meet this mandate head-on. SAP Document and Reporting Compliance now enables you to generate B2B e-invoices in the required XML format from both Finance (FI) and Sales & Distribution (SD), including tax invoices, correction invoices, down-payment invoices, and self-billing invoices. You can submit these invoices interactively to KSeF 2.0, visualize them in a human-readable PDF format with a QR code, and retrieve supplier invoices for automated posting.

Picture 2. Enabling electronic invoices through KSeF 2.0 for Poland

SAP Risk and Assurance Management

Extended analytical and reporting capabilities: new reporting dashboards with SAP Analytics Cloud, enterprise edition

We are introducing the new Risk and Compliance Cockpit, an SAP Analytics Cloud story that gives you an instant, comprehensive overview of your organization's compliance landscape.

This dashboard empowers compliance managers to identify process inefficiencies by visualizing compliance issues organized by type and status, with charts showing trends over time. It makes it easy to compare current performance against historical data, highlight long-term trends, and identify deviations. With insights into average issue resolution times and year-to-year analysis, this single source of truth helps you prioritize critical unresolved issues and improve operational efficiency.

Video 4. Extended analytical and reporting capabilities: new reporting dashboards with SAP Analytics Cloud, enterprise edition

Value Proposition

Get an instant overview of compliance issues, organized by type and status
Improved operational efficiency supported by trend and year-to-year analysis
Charts visualize trends over time
Overview of what to prioritize by highlighting critical unresolved issues

Capabilities

Identify inefficiencies in organizations' processes
Instant overview of compliance issues
Filter business data to examine specific categories of compliance issues
Visual and comparative analysis of data
Compare current performance while highlighting long-term trends and deviations

For more information, see: Risk and Compliance Cockpit

SAP Enterprise Threat Detection

Intelligent alert handling and investigation recommendations

In SAP Enterprise Threat Detection, cloud edition, investigations are the central hub for examining security incidents. This new capability automates and enhances this critical process.

The primary value of this feature is to decrease the manual effort required by SAP monitoring agents and increase their overall efficiency. When an agent prepares an investigation to send to a customer, they are now supported with automatic, case-specific response and mitigation recommendations.

This helps teams by automatically compiling investigation results and formulating suggestions for customers on how to address the alerts. The system intelligently generates these recommendations based on the standard operating procedure of the specific pattern that created the alert, further enhanced by predefined value lists and machine learning functionality. This ensures that the advice provided is both highly relevant and immediately actionable, allowing your security teams to move from detection to resolution faster and more effectively.

Picture 3. Intelligent alert handling and investigation recommendations

For more information, see: Generating Investigation Recommendations

Management-focused monitoring dashboard

We are introducing a powerful new monitoring dashboard within SAP Enterprise Threat Detection, cloud edition, specifically designed for management roles. In today's complex security landscape, having a clear, high-level view of your organization's cyberhealth is not just an advantage; it is a necessity. This new dashboard is for all managers and security leaders who need to quickly understand current security events, alerts, and ongoing investigations to make informed, timely decisions.

It facilitates a deeper understanding of complex security data by offering a comprehensive picture of your system's cyberhealth and protection status. The dashboard also shows the distribution of security events by various criteria, effectively highlighting the most affected systems, patterns, and users to help you focus resources where they are needed most.

To ensure the information is tailored to your specific needs, you can also create your own personalized monitoring pages with a selection of charts that are most relevant to your responsibilities..

Picture 4. Management-focused monitoring dashboard

For more information, see: Using the Monitoring Dashboard

SAP International Trade

Export declaration for plants abroad in the context of Registration for Indirect Taxation Abroad (RITA)

For businesses operating with plants abroad, ensuring the correct export declaration is crucial. In a plant abroad scenario, this feature ensures that the country of the delivering plant, rather than the country of the company code, determines the correct foreign trade organization for the customs declaration. This enhancement improves compliance with international trade regulations for businesses leveraging the "Registration for Indirect Taxation Abroad" (RITA) scope.

Value Proposition

Enhance compliance with trade regulations by ensuring the correct foreign trade organization is used for export declarations.

Capabilities

Manage your export declaration in SAP Global Trade Services using the foreign trade organization within the country of the plant abroad.
Identify plants abroad on pro forma invoice line items by considering countries where registration for indirect taxation (RITA) is enabled.

In SAP Cloud ERP, a billing document exists where goods delivery is performed via a foreign plant, for example, the plant country is different from the country of the company code.

Picture 5. Export declaration for plants abroad in the context of Registration for Indirect Taxation Abroad (RITA)

In SAP GTS, Edition for SAP HANA, the FTO of the corresponding export declaration is now determined based on the legal unit corresponding to the foreign plant used in the billing document.

Picture 6. Export declaration for plants abroad in the context of Registration for Indirect Taxation Abroad (RITA)

For more information, see: Enablement of Plants-Abroad for Export Processing and Foreign Plant

Delta screening with SAP Watch List Screening and manual release of blocked document items

Continuous compliance with sanction party lists is critical. Screening requests sent to SAP Watch List Screening will now remain active for delta screening for up to one month. This means the system automatically performs delta screenings against any changes to watch lists and updates the status of your business partners and documents accordingly, providing automatic coverage without requiring new manual screenings.

Additionally, for situations requiring manual intervention, the "Manage Documents - Trade Compliance" Fiori app now allows authorized users to manually release a trade compliance document item that is blocked. This creates a simple, straightforward, and auditable overrule process to comply with legal requirements while ensuring business continuity.

Picture 7. Delta screening with SAP Watch List Screening and manual release of blocked document items

For more information, see: Integration with SAP Watch List Screening and Delta Screening in SAP Watch List Screening

Watch the replays of our SAP Cloud ERP 2602 Early Release Series!

From January 12-16, we hosted a series of 22 expert-led live sessions to highlight the exciting innovations shipped with the SAP Cloud ERP 2602 release. Missed the live sessions? We've got you covered! Take advantage of the entire series or pick and choose the sessions most relevant to you. You will find the recording and presentation for Artificial Intelligence as well as 21 other topics of interest. Don't miss this chance and watch them on demand–anywhere, anytime.

Find all our assets

We at Cloud ERP and SCM Product Success offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

Spain Legal Form 303: Changes for 2026

2026-02-25T09:16:44.078000+01:00

The Spanish Tax Agency (AEAT) has published important updates to legal form 303 (VAT returns) in Order HAC/27/2026 on January 26, 2026, that will take effect starting with the February 2026 reporting period. These changes introduce new fields and modify the TXT file format for electronic submissions.

December 5, 2025 - Draft law for 303 Adjustments published for public consultation
January 26, 2026 - Order HAC/27/2026 officially published in BOE
February 11, 2026 - Technical specifications for 01-1T (2026)
February 13, 2026 - Technical specifications for 02-12M and 2T-4T (2026)

In this post, the changes in the legal form 303 and the customizing will be explained.

Legal form adjustments

New Hydrocarbon sales and Deductions

According to this regulation, the following fields are included in teh VAT return:

New identification field: "Sujeto pasivo con derecho a deducir pago a cuenta de entregas de gasolinas, gasóleos y biocarburantes posteriores a la ultimación del régimen de depósito distinto del aduanero" (Tax payer eligible for deductions due to the pre payments for the delivery of gasolines and biodiesel after the extraction from Bonded Deposits).
New Tax box 112: "Pago a cuenta de entregas de gasolinas, gasóleos y biocarburantes posteriores a la ultimación del régimen de depósito distinto del aduanero atribuible a la Administración del Estado" (Pre-paid amounts for the delivery of gasolines and biodiesel after the extraction from Bonded Deposits)

Use case

The following example illustrates the process:

December:
- The company A (importer company) imports 1.000L of fuel into the boded/tax warehouse. This transaction happens in a VAT suspension schema
January
- The company A sales to Company B (extractor company) 1.000L of fuel (this transaction is treated like an import):
  - Sales price: 1,5€/L
  - Tax base amount = 1.500€
  - VAT = 0€
- Before the extraction. Assumption: company B is not registered as OEA (Operador Económico Autorizado, authorized Economic operator as defined in EU 952/2013) or Trustable Operator ("operador confiable" as defined in Orden HAC/1496/2025😞
  - Settle Import VAT with the Tax Agency (legal form 380):
    - Import VAT (21%) = 1500€ x 21% = 315€.
  - Pre-payment by Company B to the Tax Agency (Legal form 319): 315€ x 110% = 346,50€.
- After pre-payment:
  - Company A ensures that Company B either made the pre-payment or is identified as Trustable Operator/OEA and authorizes the extraction. In case the extraction is authorized without this check, the Company A will be held as solidary responsible for the amount of 110% of the corresponding Import VAT.
  - Company B extracts the fuel from the bonded warehouse.
    - Purchase price: 1,5€/L
    - Tax base amount = 1.500€
    - Import VAT (21%): 315€.
February
- The company B sales 1000L to Company C (final customer).
  - Sales price: 1,7€/L
  - Tax base amount = 1.700€
  - Output VAT = 1700€ * 21% = 357€.
- VAT return (303) by Company B
  - Output VAT = 1700€ * 21% = 357€
  - Pre-payment (tax box 112) = 346,50€
  - VAT return result = 357€ - 346,50€ = 10,5€ to pay to the Tax Agency.

Document and Reporting Compliance

New report configuration parameter ES_VAT_FUEL_DEDUCTION :

The possible values are:

“0” = Not applicable (January and 1T, 2026)
“1” = Yes, taxpayer is eligible for deduction
“2” =No, taxpayer is not eligible for deductions (as of February, 2T-4T 2026)

The taxbox 112 will be visible directly in DRC preview screen:

In case you need to notify a deduction in this tax box, you need to edit this legal form and change the value in the preview screen manually . You need to make sure that once the tax box is updated:

Return type is correct. For example, if you deduct all and the VAT return result is zero, the return type needs to be “N”.
Adjust Tax box 71 by subtracting the amount in tax box 112.
In case of corrections, adjust Tax box 111 with the newly calculated value of tax box 71 by subtracting the amount in tax box 112.

Tax Box 111 Calculation

The tax Agency has adjusted the calculation rules in case of rectification VAT return for tax box 111as follows:

Rectification VAT return = Yes
Tax Box [70] (Result to pay from previous returns of same year and period) is not zero.
Tax Box [71] (Final result ) is negative.
If Tax box[70] <= ABS(Tax box[71]), then tax box [111] (Rectification amount other than discrepancy) = Tax box [70]
If Tax box[70] > ABS(Tax box[71]), then tax box [111] (Rectification amount other than discrepancy) = ABS(Tax box [71])

(Remark: ABS means absolute value, i.e., amount without sign)

TXT File Format Changes

The TXT file format has been restructured to accommodate the new fields.

The sequence of tax boxes [165] through [170] and [108] has been reordered within the file structure in records DP30301 and DP30303.
The CNAE values will change to 4 positions, instead of 3 in record structure DP30305.

Timeline

The regulation states in the final provision (disposicion final unica), that these changes will be applicable for the February reporting period: "La presente orden…se aplicará por primera vez… a las autoliquidaciones del Impuesto sobre el Valor Añadido, modelos 303, 322 y 353 correspondientes al segundo trimestre o al mes de febrero de 2026".

Since the Tax Agency has activated the TXT format for January:

S/4HANA Cloud Public Edition, the change is expected to be available on March 1st;. Due to the time constraints, in case of S/4HANA Cloud Public Edition you can check the note 3716951 - TXT file for Legal form 303 for January 2026 rejected by the Tax Agency for additional support.
S/4HANA Cloud of Private Edition, the SAP Note 3717337 - ES_VAT_DCL_M303_NATIONAL - New format for reporting year 2026

Please stay tuned to the announcement Legal Form 303 (2026) in the Regulatory Change Manager.

Disclaimer

This blog post is intended for informational purposes only and reflects a simplified configuration approach based on current legal and system understanding. It does not constitute legal or implementation advice. SAP system behavior may vary depending on version, scope, and customer-specific settings. For full compliance and implementation support, please consult your SAP implementation partner or legal advisor.