Hi everyone,
This blog post continues our series on France Electronic Reporting.
If you would like to understand the information that is available to help you navigate on the mandate, see France Electronic Reporting via Approved Platform: An Overview of the Information Available .
In this blog post, I would like to share some lessons learned during the testing phase of the solution and hopefully help many of you who are in the process of implementing the solution.
Process and eDocument Types Determination
You can find more information on the settings required for the eDocument creation under specific processes and eDocument types here:
- SAP S/4HANA and SAP S/4HANA Cloud Private Edition: Determining Processes and eDocument Types for Electronic Invoicing and Reporting via Approved Platform.
- SAP S/4HANA Cloud Public Edition: Determining Processes and eDocument Types for Electronic Invoicing and Reporting via Approved Platform.
A similar graphic is planned for SAP ERP. Stay tuned!
Setting Up Your System Based on Business Scenarios
We understand that setting up the system might be one of the main challenges you might face while implementing the solution. You can find information about the required configuration settings in the following topics:
- Getting Started with Electronic Reporting: If you select the graphic, you find and overview of the different steps and activities required depending on if you are setting up the connection with the service for the electronic submission to the government portal or if you are preparing your system for the eDocument creation under specific process, eDocument type, or if you're mapping information across different systems.
- Under each report, you can also find the list of settings required for that report. Some links take you to the generic settings shared with electronic invoicing which are lower in the page.
Depending on the scenario, you might wonder if you need different settings. See some examples of business scenarios listed below:
Business Scenario | Report | eDocument Process | eDocument Type |
You are posting an accounting document (source type FI_INVOICE) that is from business-to-business (B2B) international transactions via standard transactions, such as the Enter Customer Invoice (FB70) transaction.
| B2B international transactions are relevant to the Customer Invoice List.
| Source for Invoice Reporting | France Int. B2B Customer Inv. (FR_B2BINVI) |
| You are posting an accounting document (source type FI_INVOICE) that is from business-to-consumer (B2C) transactions via standard transactions, such as the Enter Customer Invoice (FB70) transaction.
| B2C transactions are relevant to the Customer Invoice List. | Source for Invoice Reporting | France B2C Customer Invoice (FR_B2CINV) |
You are posting a billing document (source type SD_INVOICE) that is from business-to-business (B2B) international transactions via standard transactions, such as the Create Billing Document (VF01) transaction. | B2B international transactions are relevant to the Customer Invoice List.
| Source for Invoice Reporting
| France Int. B2B Customer Inv. (FR_B2BINVI) |
You are posting a billing document (source type SD_INVOICE) that is from business-to-consumer (B2C) transactions via standard transactions, such as the Create Billing Document (VF01) transaction. | B2C transactions are relevant to the Customer Invoice List. | Source for Invoice Reporting | France B2C Customer Invoice (FR_B2CINV) |
You are posting an accounting document (source type FI_INVOICE) via standard transactions, such as the Enter Vendor Invoice (FB60) transaction for Intra-EU acquisitions. | B2B international transactions are relevant to the Supplier Invoice List.
| Source for Invoice Reporting
| France Int. B2B Supplier Invoice (FR_B2BSEU) |
You are posting an invoice verification (source type INV_VERIF) via standard transactions, such as the Enter Incoming Invoice (MIRO) transaction. | This scenario might be relevant for international self-billing (ERS) and intra-EU acquisition and could be relevant for the Supplier Invoice List. | Source for Invoice Reporting | France Int. B2B Supplier Invoice (FR_B2BSEU) |
You are posting incoming payments related to customer invoices via standard transactions, such as the Post Incoming Payments (F-28) transaction. | B2B international transactions are relevant for the Payment List. | Source for Payment Reporting | France Int. B2B Customer Payt (FR_B2BPAYI) |
You are posting incoming payments related to customer invoices via standard transactions, such as the Post Incoming Payments (F-28) transaction. | B2C transactions are relevant for the Payment List. | Source for Payment Reporting | France B2C Customer Payment (FR_B2CPAY) |
General rule: You can find the relevant Customizing activities per report on the help portal.
For illustrating them alongside specific source document types, see the checklist below.
Quick Setting Checklist
Configure the activities listed below as needed. Use the last column to identify the applicable reports and source document types for each activity.
Activity Name | Activity ID / View Technical Name | Link to Product Documentation | Applicable Reports & Source Types |
Report Setup (SAP S/4HANA 2021 and higher / SAP S/4HANA Cloud Public Edition) | |||
Setting Up Your Statutory Reporting | ID: 101071 | SAP S/4HANA Cloud Public Edition: Getting Started with Electronic Reporting | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Process Determination | |||
Assigning Application Interface Framework Interface and Version to System Interface | View: EDOINTAIFV | SAP S/4HANA Cloud Public Edition: Not applicable | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Activating Additional eDocument Instance Creation | ID: 102637 | SAP S/4HANA Cloud Public Edition: Activating Additional eDocument Instance Creation | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Defining Mapping Class Determination | View: EDOMAPCLASSDETV | SAP S/4HANA Cloud Public Edition: Not applicable | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Defining Process Step Determination | View: EDOPROCSTEPDETV | SAP S/4HANA Cloud Public Edition: Not applicable | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Defining Process Step Interface Determination | View: EDOPROCSPINTDET | SAP S/4HANA Cloud Public Edition: Not applicable | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Assigning eDocument Type to Accounting Document Type | ID: 102188 | SAP S/4HANA Cloud Public Edition: Assigning eDocument Type to Accounting Document Type | Relevant for Customer Invoice List and source type FI_INVOICE |
Assigning eDocument Type to Settlement Document Type | ID: 105385 | SAP S/4HANA Cloud Public Edition: Assigning eDocument Type to Settlement Document Type | Relevant for Customer Invoice List and source type STLMT_INV |
Assigning eDocument Type to Contract Accounting Document Type | ID: 106675 | SAP S/4HANA Cloud Public Edition: Assigning eDocument Type to Contract Accounting Document Type | Relevant for Customer Invoice List and source type CI_DOCUM |
Assigning eDocument Type to Invoice Verification Transaction | ID: 102187 | SAP S/4HANA Cloud Public Edition: Assigning eDocument Type to Invoice Verification Transactions (Mandatory) | Relevant for Supplier Invoice List and source type INV_VERIF |
Process Type Determination | |||
Defining Process Type and Invoice Attributes for Accounting Document Type | ID: 107158 | SAP S/4HANA Cloud Public Edition: Defining Process Type and Invoice Attributes for Accounting Document Type | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Defining Process Type for Sales Area of Billing Document | ID: 107159 | SAP S/4HANA Cloud Public Edition: Defining Process Type for Sales Area of Billing Document | Relevant for Customer Invoice List and source type SD_INVOICE |
eDocument Activation | |||
Activating Source Type Documents for Company Code | ID: 102190 | SAP S/4HANA Cloud Public Edition: Activating Source Type Documents for Company Code | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Settings for Company Code | |||
Maintaining VAT Registration Number for Company Code | ID: 105675 | SAP S/4HANA Cloud Public Edition: Settings for Company Code | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Maintaining SIRET Number for Company Code | ID: 102739 | SAP S/4HANA Cloud Public Edition: Settings for Company Code | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Maintaining SIREN Number for Company Code | ID: 102739 | SAP S/4HANA Cloud Public Edition: Settings for Company Code | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Maintaining VAT Regime for Company Code | ID: 102739 | SAP S/4HANA Cloud Public Edition: Settings for Company Code | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Maintaining Option for VAT on Debits for Company Code (Optional) | ID: 102739 | SAP S/4HANA Cloud Public Edition: Settings for Company Code | Relevant for Payment List and source types FI_INVOICE, FICA_DOC, EXT_PAYRCP |
Maintaining Fiscal Year Variant (required for eReporting period alignment) | ID: 102712 | SAP S/4HANA Cloud Public Edition: Maintaining Fiscal Year Variant | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Mapping and Additional Settings | |||
Mapping Source Document Types | ID: 107234 | SAP S/4HANA Cloud Public Edition: Mapping Source Document Types | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Mapping Sales Organization to Customer Partner Functions | ID: 107241 | SAP S/4HANA Cloud Public Edition: Mapping Sales Organization to Customer Partner Functions | Relevant for Customer Invoice List and source type SD_INVOICE |
Maintaining Additional Attributes for Tax Codes | ID: 107164 | SAP S/4HANA Cloud Public Edition: Maintaining Additional Attributes for Tax Codes | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Mapping Invoice Types to External Values | ID: 107240 | SAP S/4HANA Cloud Public Edition: Mapping Invoice Types to External Values | Relevant for Customer Invoice List and source type SD_INVOICE |
Defining Fix Values for Sender ID (Caution: use production value 0087, not quality value 0568) | View: /N/AIF/CUST | SAP S/4HANA Cloud Public Edition: Not applicable (use Configure Value Mapping app for Allowance Charge Accounts) | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Maintaining Notes for Company Codes | ID: 107333 | SAP S/4HANA Cloud Public Edition: Maintaining Notes for Company Codes | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Mapping Units of Measure to ISO Codes | ID: 107468 | SAP S/4HANA Cloud Public Edition: Mapping Units of Measure to ISO Codes | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Mapping Allowance Charge Conditions | ID: 107468 | SAP S/4HANA Cloud Public Edition: Mapping Allowance Charge Conditions | Relevant for Customer Invoice List and source types FI_INVOICE, SD_INVOICE, STLMT_INV, CI_DOCUM, EXT_DOC |
Note:
- External documents (EXT_DOC / EXT_PAYRCP) are only relevant for SAP S/4HANA, SAP S/4HANA Cloud Private Edition, and SAP ERP.
- Contract Accounting (CI_DOCUM / FICA_DOC) is only relevant for SAP S/4HANA Cloud Public Edition and SAP S/4HANA and SAP S/4HANA Cloud Private Edition 2020 and higher.
We hope that this checklist helps you find the required settings based on the most common business scenarios. Let us know if you encounter other scenarios or questions in the comments section below.
Until next time,
Ailane Kuhn
Source link
