Introducing SAP Document and Reporting Compliance

Objectives

After completing this lesson, you will be able to:

  • Explain the end-to-end process flow and SAP Document and Reporting Compliance from end user perspective
  • Distinguish the different deployment options for SAP Document and Reporting Compliance
  • Describe the high level architecture of SAP Document and Reporting Compliance in SAP S/4HANA Cloud Public Edition
  • Outline what a compliance task is, and which ones are supported by SAP Document and Reporting Compliance

End-to-End Process Flow

SAP Document and Reporting Compliance is an end-to-end solution for all types of mandates and, as a result, it offers the possibility to transform your processes end-to-end.

When it comes to the end-to-end process, we see heterogeneous setups:

  • Certain organizations have electronic documents managed within AP/AR teams, so a part of the process is managed by, for example, billing clerks, and others, by the GL or tax accountant.

  • Other organizations have established a new centralized team responsible for compliance.

Taking into account that all kind of setups exist, our solution is flexible to be set up to meet the needs of your organization. We follow standard SAP role and authorization concepts.

When it comes to the actual process, everything starts with business documents that, upon creation, generate electronic documents in real-time without any manual intervention. As these are created, they are automatically processed so the system takes care of validations, determines the receiver, includes the digital signature, and electronically transmits the documents. While this is all automated with no-touches when no failures occur, the documents are consolidated in a dashboard, centralized worldwide so they can be easily monitored.

If any failure occurs, the system can be set up to reprocess automatically, to limit manual interactions and minimize effort as much as possible. When required, failures can be easily followed-up via the holistic dashboard that allows for seamless navigation to underlying invoices, and the completion of corrections, within a few clicks.

In addition to this worldwide monitoring, additional consistency checks can be run continuously to avoid discrepancies against the authorities' records, and allow seamless transition to statutory reporting once we get to month-end. This is facilitated via an holistic dashboard that allows the Compliance Team or Tax Accountant to review electronic documents, and ensure there are no documents with open actions. If any are, they can take this into account, initiate periodic reporting, and initiate the task within the same place.

When it comes to statutory reporting, the solution supports it end-to-end, with a fully digitized process in the system. From adjustments and controls that no longer rely on Excel, to drill-down to underlying data and approvals via workflow integration prior to submission. Embedded analytics enable data-driven insights and full digital traceability. From the final report, regardless of the level of granularity, it always allows to drill-down to the underlying documents within a few clicks. The same applies to approvers that no longer rely on offline data, and can review and approve prior submissions. Once approval has been gathered, SAP Document and Reporting Compliance allows seamless completion of the submission, either electronically (where supported), or via file upload and manual typing in accordance with Governments' specifications.

Hopefully this gives you an overview of the end-to-end process that is fully digitized in the system, enabling a future-proofing audit trail.

This doesn't just apply to the legal content provided out-of-the-box. Design tools are made available so that additional scenarios or reports can be easily added or extended, to ensure the one process can truly be streamlined worldwide.

The End-User Perspective

End-to-End Process from the End-User Perspective

To get a detailed overview of the individual features, and a glance at what the solution looks like, check out the End-to-End Process video from an end-users' perspective.

SAP ERP Central Component Versus SAP S/4HANA Cloud

Let's look at the components of SAP Document and Reporting Compliance:

  1. SAP S/4HANA Cloud, ECC, and other business platforms. This source system provides:
  • Local mappings and formats based on local regulations

  • Full integration with business processes

  • Real-time business monitoring and seamless corrections across all types of mandates, worldwide

The country-specific content is embedded in the source systems where business processes are supported end-to-end. SAP Document and Reporting Compliance provides a global framework that is implemented once, and allows for the management of all e-documents and statutory reporting scenarios. The framework is global, but has country-specific content that can be plugged-in to meet the local requirements. This is clear to users who can run the same process for all countries, and produce trustworthy e-documents or statutory reports from the system of record, with no offline manipulations.

2. Submission via SAP Business Technology Platform. This block provides:

  • Authentication, encryption, and digital signatures based on local regulations

  • Secure communication via:
    • Country integration flows ready to be deployed on SAP Integration Suite

    • Ready-to-use services on SAP Business Technology Platform

Whether a submission via cloud services is possible, depends on the availability on the authorities' side. However, when available, we enable direct electronic transmission to tax authorities. We have different options depending on the country and scenario, in some cases we provide content to be deployed on the SAP Integration Suite, and in other cases, we provide a ready-to-use service. However, in all scenarios, we provide the final content that can be accepted by the tax authorities. The only difference is in the maintenance of the integration layer that enables the transmission. This is also where we take care of digital signatures, encryption, and other requirements that might need data retrieval via API. It's an integral part of the solution to produce the final file, ready to be accepted by tax authorities. Going forward, the clear strategy will be to provide document exchange as a service, where possible.

3. Recipient (varying per country). This layer provides:

  • Validation and approval or rejection

  • Electronic responses that are automatically processed, stored in the system, and compared to the original record (e-documents or report) with full traceability

The last box depicts the recipient. SAP Document and Reporting Compliance takes care of the connection to the authorities or networks.

SAP S/4HANA Cloud

Let's look at the different deployment options.

One SAP S/4HANA system

This is the easiest deployment model. All processes run in the SAP S/4HANA Cloud, fully reconciled, and on live data.

High-Level Building Blocks

In this section, we will have a look at the high-level building blocks of the SAP Document and Reporting Compliance product family. Files are generated in the ERP system, and communicated via a cloud service, to the authorities. In case the authorities do not provide an API, the file is submitted manually via mail, USB-stick, or government portals.

1. SAP S/4HANA Cloud

SAP Document and Reporting Compliance

  • Common building blocks like activation
  • A common dashboard to monitor document and reporting compliance

Statutory reporting Framework

  • Reporting Task Dashboard to monitor all reporting obligations worldwide, and their status
  • Generic Business configuration to represent the company structure from a reporting perspective
  • Country-specific business configuration to customize the individual reporting obligation to the individual company's needs in their respective countries
  • Cloud communication-specific configuration to set up connectivity with SAP Business Technology Platform and the authorities
  • A design time to extend or build reports

eDocuments Framework

  • eDocuments cockpit (ABAP and FIORI) to monitor the status of electronic documents and solve errors.
  • Business configuration (Documents - Company code - API mapping) to adjust the solution to the individual company's needs
  • Process-specific configuration to comply with a local regulation
  • Cloud process-specific configuration (for example, Peppol)
  • Process manager (eDoc type and eDoc process) to automate the real-time reporting
  • Inbound process handler
  • AIF configuration to specify the mapping from source document to external document

Brazil Nota fiscal

  • NFE3 for utilities
    • Business configuration to set up NFE3 for utilities
  • NFE3 for SD and MM
    • Monitor and Business configuration for NFE3 for SD and MM

2. SAP Business Technology Platform

For the online submission, SAP Business Technology Platform is used. Scenarios can be divided into SAP managed (Software as a Service, SaaS) or customer managed (Platform as a Service, PaaS).

SAP managed scenarios

  • SAP Document and Reporting Compliance service consists of data replication and report generation. For ECC customers, data is being replicated, the final statutory report is generated, and then submitted. For SAP S/4HANA Cloud customers, the service doesn't replicate data, and only submits the final report.
  • SAP Document and Reporting Compliance, Cloud edition covers the Peppol scenarios. It connects the backend system to the Peppol network, and distributes individual documents (invoices) to the corresponding business partner.
  • SAP Document and Reporting Compliance, Brazil NFE inbound and outbound, manage the distribution of NFE documents in Brazil.

Over the course of 2023, these solutions will be merged into one product.

Customer managed scenarios

In these scenarios, customers manage their own instance of SAP Integration Suite, and deploy and maintain the SAP delivered iFlows themselves.

3. Authorities

The authorities offer a manual (mail or USB-stick), digital (mail or portal) or online (API) submission.

In the first case, there is no online submission involved, the file is simply downloaded from the backend. In all other cases, the submission is via SAP Business Technology Platform.

Supported Types of Legal Obligations

In this section, you will learn which compliance tasks SAP Document and Reporting Compliance covers. The coverage spans across 57 countries and >400 reports and scenarios. However, legal obligations can be broadly classified into the following groups:

  • VAT and Withholding Tax Reports
    • Whenever a taxable event happens, for example, a good is sold, the ERP system keeps track of the taxes and persists them in a database. In these cases, depending on the jurisdiction, the tax is imposed on the company's sale. Otherwise, the company has to withhold a certain amount of taxes from the business partner and pay it on his behalf, to the authorities.

    • At month-end or quarter-end, an advance return is filed to tell the authorities the estimated outstanding tax liability, and subsequently, a payment is made. At the end of the year, a final tax statement is produced, and the company either has to pay more taxes or will receive a refund. These reports are mostly on tax box level, that is, many transactions of the same type are aggregated into one tax box, but sometimes they are also on a more detailed level. In the latter case, the reports would include information on individual transactions.

  • Financial statements and fixed asset reports
    • These reports are generally filed periodically, and expose financial or asset information to the authorities

    • Generic reports are delivered as part of the standard that can then be adapted to the respective country's needs. For some countries, a localized report is available

  • Payments and Ledger reports
    • These reports expose all line items of a certain ledger

  • EC sales list
    • In most European countries, an EC sales list report has to be filed

    • These reports summarize sales or transfers of goods into other European countries to determine if VAT has been properly paid

  • Cashflow reports
    • As the name suggests, this type of report summarizes all cash flows of a certain period

    • Like for financial statements, a generic report is available, and in some countries, a localized report is available also

  • E-Invoicing scenarios
    • In many countries, electronic invoices have to be sent in a certain format. The formats differ, but these scenarios are almost always executed in real-time

    • A company can be the customer or the supplier, therefore, send or receive invoices

    • Inbound invoice handling can be automated to directly create the follow-up documents

  • E-Reporting
    • In some countries, delivery notes or transport registrations have to be sent to the authorities before goods can be shipped

    • Payment receipts inform the authorities or business partners that a payment has been received

    • For some taxable events, a tax certificate has to be sent (for example, withholding tax), and the authorities require a copy of the books

    • Payroll reports send employee information to the authorities

We will learn more on how to identify the exact coverage of the solution, in the next chapter.

Countries and their Respective Legal Obligations

To find a full list of all supported compliance tasks, navigate to the respective SAP S/4HANA Cloud help portal page:

This table gives you an overview, country by country, and obligation by obligation.

  • The list of scenarios can be filtered and downloaded. At the top, you can change the page to the respective SAP S/4HANA Cloud release you need.

  • Filter by country to find the scenarios per country

  • The task column gives the name of the legal obligation in logon and local language. It also provides the link to each obligation's help portal, how to use it, and how to set it up.

  • The task description contains a detailed description of the scenario, and the respective produced file formats. These vary from task to task, as the locally required format varies.

  • In column supported submission type, the relevant submission channel is listed. It varies from manual filing, where the solution provides the file format, and it has to be manually uploaded to a fully automated submission via an API.

  • In column technical information, the relevant information for the implementation and incident handling is given.

  • Column predecessor states which ABAP report is being replaced by the respective SAP Document and Reporting Compliance task and if so, when the old report was sunset.

After this short introduction on how to find out the existing scope, learn more about the future scope in the next section.

Log in to track your progress & complete quizzes