E-Invoice Processing with Docspire Enterprise

 Docspire Enterprise simplifies e-invoice processing. Parse ZUGFeRD, xRechnung, and Peppol XML invoices. Validate against EN 16931.  

E-invoicing mandates are rolling out across Europe. Germany requires every B2B invoice in EN 16931 format by January 2028. France begins mandatory issuance for large enterprises in September 2026. Belgium already mandated Peppol BIS for all B2B transactions since January. 

For AP teams, this means a growing volume of structured XML invoices arriving in different standards, each with its own schema and validation rules. ZUGFeRD is a PDF with an embedded XML payload that carries legally binding invoice data. XRechnung file is a pure XML validated against KoSIT specs. A Peppol BIS transmission is structured data moving through a certified access point.  

Docspire Enterprise provides a single pipeline that parses, validates, and transforms documents using their respective schemas, rules, and compliance requirements. 

What Makes E-Invoice Different 

Most AP automation tools are designed for processing scanned paper invoices and emailed PDFs. They use OCR and AI extraction to pull fields from unstructured documents. That works for traditional invoices.  

An E-invoice requires a different method. 

E-invoices are already structured XML files. It does not require extraction; it needs parsing against the right schema, with the right validation rules for the specific standard being used. 

However, like PDF invoices, e-invoices also have variations: 

• ZUGFeRD is a hybrid format. A PDF/A-3 container with a UN/CEFACT Cross Industry Invoice (CII) XML embedded inside it. The XML is the legally relevant part. The PDF is for human readability. ZUGFeRD supports multiple profiles from MINIMUM (basic metadata only) through EXTENDED (full invoice detail). Only profiles 2.0.1 and above, at COMFORT or EXTENDED level, are mandate-ready under EN 16931. 
• xRechnung is Germany’s national implementation of EN 16931. Pure XML with no PDF wrapper. It supports both UBL 2.1 and CII syntax. It carries strict mandatory field requirements and is validated against KoSIT specifications. If you send invoices to German public sector entities, this is what they expect. 
• Peppol BIS Billing 3.0 is UBL 2.1 transmitted through the Peppol network via certified access points. It is the standard for cross-border invoicing and is mandatory for B2B in Belgium. The UK is also moving toward a Peppol-based model for its 2029 e-invoicing mandate. 

One invoice standard uses CII XML inside a PDF. Another uses standalone UBL XML. A third uses UBL XML over a network protocol. Your system needs to handle all three invoice formats, then transform and validate them.

How Docspire Enterprise Processes E-invoices 

Docspire Enterprise treats e-invoices as what they are: structured XML that needs parsing against the correct schema, validation against the right rules, and transformation into a format your financial systems can consume. 

Docspire Enterprise handles this in four stages.

 

Stage 1: Ingest and classify

Documents arrive through multiple channels. API uploads, email ingestion, Peppol access point integration, or manual upload through the web interface. 

Docspire automatically classifies the incoming file.  

• Is it a ZUGFeRD PDF with embedded XML?  

• Is it a standalone xRechnung?  

• Is it a Peppol BIS transmission?  

• Is it a PDF, an image, or a Word document? 

The classification determines which parsing path the document takes. 

For ZUGFeRD files, Docspire extracts the embedded XML from the PDF container. For xRechnung, the XML is processed directly. For Peppol transmissions, the BIS Billing payload is received through the network integration. For the traditional formats, it follows the AI extraction and adaptive OCR pipeline. 

Stage 2: XML parsing with schema validation 

This is where the Docspire desktop client does the heavy lifting. 

Every e-invoice is fundamentally an XML document. To parse XML reliably, you need XSD (XML Schema Definition) files that define the structure, data types, and constraints for that specific standard. 

In the Docspire desktop client, you configure the XML source by providing two things: 

• The XML file path pointing to your e-invoice documents 

• The XSD file path pointing to the schema definitions for the standard being used 

The XSD tells the parser exactly what to expect. Location of the invoice number, date formatting, mandatory fields, and the validity of the values of tax category codes. 

If you do not have the XSD for a particular format, Docspire can generate XSD schemas on the fly directly from sample XML files. Useful when you encounter a new variant or a supplier-specific customization for the first time. 

Once configured, Docspire parses the XML against the schema and produces a structured preview. Every field, every nested element, every line item is visible before it moves downstream. 

Stage 3: Validation and compliance 

Parsing is only half the job. The extracted data needs validation before it is entered into your financial systems. 

Docspire runs a multi-layer validation process: 

1. EN 16931 compliance. Checks mandatory fields as per European standards, correct data types, and valid code lists. 
2. Peppol verification. Transmission metadata matched against invoice content. 
3. Three-way matching. Invoice amount against the purchase order and the goods received note. Line items, quantities, and GL codes aligned. 
4. Duplicate detection. Invoice number and supplier combination checked against processing history. 
5. Bank detail confirmation. Payment details matched against the supplier master record. 

Invoices that pass all checks move to automatic approval. Invoices that fail trigger exception handling with specific routing based on the type of failure. Schema or signature issues route to IT or compliance. Delivery failures route back to the supplier. PO mismatches the route to procurement. Budget check failures route to the approving manager. Coding issues route to the finance team. 

Stage 4: Transform and deliver 

Validated invoice data needs to reach your ERP, accounting software, or data warehouse in the format it expects. 

The Docspire dataflow designer handles transformation visually. In the desktop client, you see the complete pipeline: 

The XML source on the left shows the full parsed tree of a ZUGFerd invoice, every element from ExchangedDocumentContext through SupplyChainTradeTransaction and individual line items. 

Transformation functions in the middle handle date conversion, country code lookup, address parsing, and currency normalization. 

Destinations on the right receive the structured output. One Excel workbook contains an invoice summary sheet (voucher number, category, dates, vendor details, tax totals) and the other stores a line items sheet (position numbers, SKUs, descriptions, quantities, unit prices, VAT codes). The structured output can be downloaded as excel or written to an ERP, or CRM, or a database system. 

This is not a black box. You can see every mapping, every transformation, every data flow. When something does not look right, you know exactly where to fix it. 

E-invoice Processing pipeline in Docspire Enterprise 

The full e-invoice processing pipeline in Docspire Enterprise is straightforward. It involves the following steps: 

• Browsing UBL standard files. Open the e-invoice files across standards. ZUGFeRD, xRechnung, Peppol BIS, UBL 2.1. Each one is an XML document following the EN 16931 data model. Open a ZUGFeRD invoice to see what the raw XML looks like inside. 
• Dropping the XML source. On the Docspire desktop client, drag and drop an XML source component onto the canvas. E-invoices are XMLs at their core, so Docspire treats them as exactly that. The platform already includes a full library of XML-related components and data items ready to use. 
• Configuring XML and XSD paths. Set the XML file path (pointing to the invoice) and the XSD file path (pointing to the schema definition). The XSD is what tells the parser how to read the XML. Without it, you are guessing at structure. With it, every node maps correctly. 
• Generating XSDs on the fly. If you do not have a schema file, Docspire generates one directly from the XML. You point to a sample invoice, the platform infers the structure, and you have a working XSD immediately. No manual schema authoring required. 
• Previewing parsed output. Once parsing is configured, it shows the structured preview. Every field extracted from the XML is laid out in a clean, readable format. Invoice number, dates, vendor details, line items with quantities and prices, tax breakdowns. All mapped from the raw XML tree. 
• The full dataflow. Finally, go to the complete e-invoicing dataflow. It has XML source on the left. Transformation functions in the middle. Excel destination on the right. The entire pipeline from raw e-invoice to structured, validated output in a single visual workspace. 

The End-to-End E-Invoice Dataflow 

Docspire Enterprise fits into a broader automation architecture for e-invoice processing. 

Invoices arrive in any supported format and flow through the Docspire workflow automation engine. The engine handles EN 16931 compliance validation, Peppol verification, 3-way matching, duplicate blocking, and bank detail confirmation. 

Invoices that pass the validation route are automatically approved. Exceptions route to human review with specific context: what failed, why, and what action is needed. Reviewed invoices, re-entered the pipeline for final approval, and ERP posting. Additionally, approval workflows are fully customizable based on how invoice or payment approval works in your company. 

Docspire integrates natively with Sage, Oracle, NetSuite, SAP S/4HANA, Microsoft Dynamics 365, QuickBooks, Xero, and 100+ additional systems through database, API connectors, or via Webhooks. For organizations on the Peppol network, native access point integration and tax portal clearance are built in. 

Every step produces an auditable log. Every document carries a complete trail from ingestion through final posting. 

Docspire Supports the Transition 

Not every supplier will switch to structured e-invoicing on the same day. During the transition period, the AP teams handle a mix of paper invoice scans, PDF invoices as email attachments, and structured XML e-invoices via different exchange platforms. 

Docspire Enterprise processes all of them through the same pipeline. AI extraction for unstructured PDFs and paper scans. Schema-based parsing for structured XML invoices. The system bifurcates into its respective validation rules, data transformations, and formatting. The output is mapped into a format acceptable to your ERPs, databases, CRMs, or internal systems with complete audit trails and document processing history. One workflow for everything that arrives, regardless of format. 

The platform supports 40+ languages and multi-currency. VAT validation covers jurisdictional rules across the EU, UK, and beyond. Data residency options let you choose where your invoice data is stored and processed. 

Getting started 

Docspire Enterprise supports ZUGFeRD (all profiles), xRechnung (UBL and CII syntax), Peppol BIS Billing 3.0, and standard UBL 2.1 invoices out of the box. 

Start with a 14-day free trial or talk to our team about your e-invoicing readiness.