France is introducing mandatory electronic invoicing and electronic reporting via an Platform Agreed (plateforme agréée, PA), starting September 2026. This post walks you through how to process electronic invoices using SAP Document and Reporting Compliance as your approved platform (plateforme agréée, PA), covering each step and the corresponding document statuses.

Domestic Customer Invoices: Creation

The process begins when you post a customer invoice. SAP Document and Reporting Compliance automatically creates an electronic document under the Domestic Customer Invoice process, with an initial status of eDcoument Created.

At this point, you can preview the XML that will be sent to SAP Document and Reporting Compliance, cloud edition via Display > Display/Preview XML.

From here, you have two options:

• Display Local XML / Display PDF – the electronic document is sent to the cloud edition, which returns the final XML in local format and PDF visualizations (in both French and English) for your review.   Please note that this integration is asynchronous, so the push integration must be fully configured before use. If any errors occur, they can be reviewed in the Resolve Errors app within SAP Document and Reporting Compliance, cloud edition.
• Submit – either manually or using a background job (EDOC_BACKGROUND).

Domestic Customer Invoices: Submission

Upon submission, the electronic document moves through the following statuses:

1. Sending to Service Requested
2. Sent to Service
3. Acknowledged by Service — if the invoice is received successfully in SAP Document and Reporting Compliance, cloud edition. The status updates to Rejected by Service when the cloud edition is unable to accept the electronic document — for example, when resubmitting a file that has already been acknowledged.
4. Service Error— if any error occurs while processing the invoice – for example if schematron validation fails, PDF creation fails, etc.

If an error occurs, the details will appear in the application log (Goto > Application Log) and, if the issues relate to faulty invoices, you will find schematron validation results in the electronic document history (Goto > History). Look for the file saved with variant ERROR — this file includes all results (including warnings), so focus only on entries classified as fatal. Once you've fixed the root cause, use the Submit button to resubmit.

▎Note: If the document is stuck at Sending to Service Requested, you are most likely missing SAP Notes or configuration settings.

If no errors occurs, the final XML and PDF are generated, pushed back to ERP and stored as attachment in the electronic document history, and the electronic document status is updated to Accepted by the Service.

▎Note: These files are pushed into ERP — there is no pull mechanism available, so integration must be fully set up beforehand. If this status transition does not occur, check the Resolve Errors app for issues in the mappings, file creation, or the push to ERP.

PPF Registration (Status CDAR_200)

After the invoice in local format is created, a registration status CDAR_200 is sent to the Public Invoicing Portal (Portail Public de Facturation, PPF). This registration request is also returned to ERP and stored in the electronic document history.

You can track the PPF status in the PPF Status and PPF Status Description fields in the EDOC_COCKPIT or the Manage Electronic Documents app. After the CDAR_200 registration is created and transmitted, the PPF Status Description updates to PPF Request Generated and, subsequently, to Registered with PPF.

PPF then sends an acknowledgement that is processed through SAP Document and Reporting Compliance, cloud edition and integrated back to ERP, updating the field to PPF Acknowledgement Received.

▎Important: If the PPF acknowledgement is not received (i.e., the PPF Status Description does not change to PPF Acknowledgement Received), neither Peppol transmission to the recipient nor Flow 1 to PPF are initiated.

Domestic Customer Invoices: Exchange

Invoice sent to recipient via Peppol Network

After acknowledgement of 200 registration, the document is sent to recipient via Peppol Network. The exchange status is tracked through the electronic document status:

▎Note:  Please refer to Domestic Supplier Invoices: Receipt to understand when these CDAR statuses are sent for buyers using SAP Document and Reporting Compliance.

▎Note: If the recipient PA does not receive (acknowledge) the invoice, the status remains Accepted by Service, even if the document has already been transmitted via Peppol Network. To check whether transmission via Peppol Network was initiated, use the app Monitor Documents app (Peppol monitor) in the cloud edition. If any failure occurred, the document is in status Sending failed. Any issues with pushing recipient acknowledgements can also be investigated in the Monitor Documents app.

At this stage, the invoice can be processed from a business perspective.

Depending on buyer responses, the following optional and required statuses may follow:

Invoice tax data sent to PPF (Flow 1)

After acknowledgement, PPF has up to 1 hour to reject the document. If no rejection is received within that window, the document is deemed accepted. At the earliest point between acceptance, rejection, or the 1-hour timeout, the electronic document is updated and transmission of Flow 1 to PPF is initiated.

The Flow 1 sends tax data to PPF and the exchange status is tracked in the PPF Status and PPF Status Description fields:

• Flow 1 Data Submitted
• Flow 1 Submission Failed
• Flow 1 Data Accepted
• Flow 1 Data Rejected

▎Note: If Flow 1 fails, reprocessing is not currently supported. Further options are being evaluated.

Domestic Supplier Invoices: Receipt

Supplier invoices are received in the SAP business system via Peppol Network through SAP Document and Reporting Compliance, cloud edition, which acts as the approved platform.

Before you begin:

• Routing rules are mandatory, even if you use only one business system. See the SAP Help documentation (https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/managing…) for setup guidance.
• If errors occur during receipt:
  • Check the app Resolve Errors in the cloud edition. Here you can find invoices that could not be pushed to the business system.
  • If no errors seen in Resolve Errors app, use the Monitor Documents app (Peppol Monitor) in the cloud edition to view detailed logs and reprocess failed documents.

When an electronic invoice is received, SAP Document and Reporting Compliance, cloud edition first validates the document. If validation fails, one of the following CDAR statuses is returned to the buyer depending on which check failed:

• Routing error (CDAR_221) – This is triggered when the address of invoice recipient is not registered with SAP as PA (Endpoint ID doesn't match PartyLegalEntity ID – SIREN).
• Inadmissible (CDAR_501) – This is sent if XSD Schema validation fails (syntax error).
• Rejected by Receiver Platform (CDAR_213) – This is sent if schematron validation fails (semantic error).

If any validation fails, the electronic invoice will appear in the Monitor Documents app (Peppol Monitor) in SAP Document and Reporting Compliance, cloud edition with a status of Rejected.

If all validations pass, the invoice is accepted and CDAR_202 (Received by Receiver Platform) is sent to the buyer.

SAP Document and Reporting Compliance, cloud edition then converts the supplier invoice and generates the PDF visualization, in both French and English. Once successful, the invoice is pushed to the business system and CDAR_203 (Received by Customer) is sent to the buyer.

Any errors related to routing rules or the push to the business system can be investigated and resolved in the Resolve Errors app in SAP Document and Reporting Compliance, cloud edition.

▎Note: In the Monitor Documents app (Peppol Monitor), these invoices appear as Document Pushed in green. This status indicates the document has been pushed for processing after CDAR_203 — it does not confirm that the invoice has been successfully pushed to the business system.

The invoice is created asynchronously in the target business system — SAP ERP, SAP S/4HANA Cloud Private Edition, SAP S/4HANA, and SAP S/4HANA Cloud Public Edition, SAP Business Network, or SAP Ariba Invoicing.

For SAP ERP, SAP S/4HANA, and SAP S/4HANA Cloud, the invoice is created as an electronic document under the Domestic Supplier Invoices process, and CDAR_204 (Acknowledged by Customer) is sent to the buyer.

If the acknowledgement is not processed automatically, users can trigger it manually via EDOC_COCKPIT (or the Manage Electronic Documents app).

SAP Document and Reporting Compliance also offers integration with SAP Invoice Management by OpenText, and supports extensibility for automating invoice posting with other solutions.

For more details on processing supplier invoices, see these SAP Community blog posts:

Payment Received for Domestic Customer Invoices

For invoices related to services where VAT is due based on payment (as opposed to invoice date), sellers must report a Payment Received status (CDAR_212).

When a customer invoice is cleared, SAP Document and Reporting Compliance automatically creates an electronic document under the Domestic Customer Payment process. A few things to note:

• If a single payment clears multiple invoices, one electronic document is created per cleared invoice.
• For partial payments, each instalment creates a separate electronic document, but the customer invoice status is not updated until the invoice is fully paid.

The processing flow mirrors the customer invoice process with the electronic documents being updated with following statuses:

1. Sending to Service Requested
2. Sent to Service
3. Acknowledged by Service — if the invoice is received successfully. The status updates to Rejected by Service when SAP Document and Reporting Compliance, cloud edition is unable to accept the electronic document — for example, when resubmitting a file that has already been acknowledged.
4. Error at Service — if any error occurs while processing the electronic document for creation of CDAR_212.

Once the cloud edition acknowledges the electronic documents, the final XML format (CDAR_212) is generated and pushed back to ERP, and the electronic document status is updated to Accepted by the Service.

At this point, CDAR_212 is sent to both the seller and PPF. If both transmissions succeed and CDAR_212 is accepted by both recipient and PPF, the electronic document status is updated to Payment Received Status Sent.

If a failure occurs, it will be either a rejection or a technical error from PPF or the Receiver Platform (Buyer’s PA):

• Technical error — the electronic document status is set to Error at Service. Use the Retry button in the eDocument Cockpit to reprocess.
• Rejected by PPF — the electronic document status is set to Rejected by Public Portal and the PPF status description is Rejected by PPF. The document must be resubmitted.
•  Rejected by Receiver Platform (Buyer’s PA) — the electronic document status is set to Rejected by Customer. The document must be resubmitted.

  Summary: CDAR Statuses

Sent by seller

Sent by buyer

▎ Note: If an invoice is Rejected by Receiving Platform (CDAR_213), this must also be reported to both PPF and the Seller.