The DocuWare E-Invoicing Service > Creating tab is currently only available for French legal entities.
On this tab, you configure the generation of e-reports for invoices stored as individual records in DocuWare. Your invoice data, including header information and line items, is stored in index fields and table fields and serves as the source for generating a compliant e-invoice for e-reporting submission to the DGFiP. Populating these index fields is a necessary prerequisite to generate e-reports from data stored in DocuWare.
Select the file cabinet and Document Processing configuration DocuWare uses to convert your index data into a France CII Invoice CIUS e-invoice for e-reporting.
DocuWare does not support the direct creation of e-report files. E-Reports are always generated from a compliant e-invoice, either created from your DocuWare index data using this configuration, or provided as an existing structured e-invoice file submitted directly via the workflow endpoint tax-reports/create.
Information: Your responsibilities
DocuWare E-Invoicing Service validates, submits, and traces e-reports derived from the generated e-invoice. The following responsibilities remain with your legal entity:
Content accuracy: The correctness of the declared content is your responsibility. DocuWare guarantees structural conformance of the generated e-invoice (France CII Invoice CIUS), not its content and its tax accuracy.
Reporting periodicity: You are responsible for ensuring e-reports are submitted within the applicable deadlines: monthly, quarterly, or as required under your applicable VAT regime. DocuWare submits what it receives when it receives it via DocuWare Workflow.
Long-term archiving: The legal archiving obligation for the underlying invoices rests with your legal entity. DocuWare retains the submitted e-invoice, the original submission, and the PPF responses. With appropriate procedural documentation in place, DocuWare can serve as an audit-proof tool to support this requirement and provide full traceability for tax and compliance purposes.
Exclusivity: If your legal entity already submits e-reports through another system or channel for the same reporting scope, you must align this before activating e-reporting in DocuWare E-Invoicing Service to avoid duplicate reporting. Contact DocuWare Support before activating.
When do you need to trigger e-reporting manually?
For French legal entities, e-reporting obligations apply to both incoming and outgoing invoices. Depending on the transport channel and invoice type, e-reporting is either handled automatically by the DocuWare E-Invoicing Service or must be triggered manually via a DocuWare workflow.
Automatic e-reporting | no manual action required:
The following scenarios are handled automatically by the DocuWare E-Invoicing Service as part of the invoice transmission process:
Incoming invoices received via the Peppol network as domestic e-invoices
Outgoing B2B and B2G e-invoices sent via the Peppol network
Outgoing B2C simplified e-invoices sent via the Peppol network
Manual e-reporting | workflow configuration required:
The following scenarios require you to configure and trigger e-report submission manually via a DocuWare workflow:Incoming invoices received via email in an e-invoice format: The e-report is generated via send e-invoice to the tax report endpoint.
Incoming invoices received via email as a PDF or non-structured document: The e-report is generated via e-invoice from index data stored in DocuWare.
Outgoing B2B e-invoices sent via email in an e-invoice format: The e-report is generated via send e-invoice to the tax report endpoint.
Outgoing invoices sent via email as a PDF: The e-report is generated via e-invoice from index data stored in DocuWare.
For manual e-reporting scenarios, see the configuration steps below and the workflow instructions in the article Understanding E-Reporting with DocuWare E-Invoicing Service (coming soon).
How e-reporting creation works in general
E-reporting creation spans four steps across different DocuWare components. Only step 3, the E-Reporting Creation table, is configured on this Creating tab; the others are prepared beforehand or run afterward.
Data Extraction: Extract your invoice data into DocuWare index fields and table fields.
Document Processing Configuration: Configure a Document Processing Configuration to map your index fields to the France CII Invoice CIUS format.
E-Reporting Creation Table: Now you can configure this Creating tab, link your file cabinet to the Document Processing configuration.
Sending E-Reports with DocuWare Workflow: In the Workflow Designer, configure and trigger the e-report submission to DGFiP.
1. Data Extraction
Your invoice data must be available as index field and table field values in DocuWare before e-invoices can be generated for e-reporting. You can use the following standard DocuWare functions to extract and populate index fields from existing documents:
IDP (Intelligent Document Processing): Extracts structured data from your documents using configured extraction rules.
Intelligent Indexing: A self-learning system that automatically captures and indexes document content, reducing manual effort and improving accuracy during archiving.
API: Populate index fields programmatically via the DocuWare API.
You are responsible for ensuring that your index field data is complete and correct before triggering e-report generation.
2. Document Processing configuration
You must create and configure a Document Processing configuration to map your DocuWare index fields and table fields to the France CII Invoice CIUS e-invoice format. This mapping defines how your index field values are translated into the structured e-invoice that DocuWare submits to the DGFiP.
For details on the required field mapping for e-reporting, see Understanding E-Reporting with DocuWare E-Invoicing Service. (coming soon)
3. E-Reporting Creation Table
In the configuration table, link the file cabinet containing your invoice data to the Document Processing configuration.
Column | Description |
|---|---|
File Cabinet | Select the file cabinet that contains your index data used to generate e-invoices for e-reporting. |
Document Processing Configuration | Select the Document Processing Configuration that maps your index fields and table fields to the France CII Invoice CIUS format. |
Use the + button to add a row. Use the − button to remove a row. Use the ↺ button to reload available options.
If your invoice data is already available as a compliant structured e-invoice file, you can call the endpoint POST /v1/tax-reports/create directly from your DocuWare workflow without using this table configuration. This table is only required for the conversion of index data into an e-invoice for e-reporting purposes.
4. Sending E-Reports with DocuWare Workflow
You trigger the submission of e-reports to DGFiP from within a DocuWare workflow. In the Workflow Designer, you configure a web service activity to call the e-reporting endpoint. The path you select in the workflow determines whether e-reports are generated from your index data or from an existing e-invoice file.
For workflow configuration instructions, see How-to set up workflows for DocuWare E-Invoicing Service.
Information: resources helping you validate your e-invoices
The following resources help you validate your e-invoice structure and business rules during implementation. Use the demo documents and specifications to test your configuration with sample data before going live.
Next step to configuration: Permissions tab