Cross-Border E-Invoicing For Dewesoft

Dewesoft is a global Slovenian test-and-measurement company with around €100 million in reported annual revenue. Its data-acquisition solutions support engineering teams at organisations including NASA, SpaceX, Tesla, Volvo, Audi, BMW, Caterpillar and Siemens.

With operations across 28 countries, Dewesoft manages invoicing between headquarters and local entities through its self-developed ERP. As international operations expanded, the company needed to support different cross-border invoicing requirements, including Italy’s government-run e-invoicing system and structured invoice delivery for Germany.

Background

Dewesoft already operated a mature invoicing setup:

• A self-developed ERP as the core system for invoice creation
• Headquarters managing invoicing across international operations
• Italian and German entities receiving invoices through local accounting processes
• A need to support different e-invoicing formats and delivery routes by country

Instead of modifying ERP logic for each market, Dewesoft connected its ERP to DDD Invoices as an external compliance layer.

Problem: Local compliance without ERP changes

Dewesoft needed to send invoices from headquarters to its Italian and German entities while keeping invoice creation centralised in its ERP.

Each market required a different process:

• Italy: Invoices must be prepared in the FatturaPA XML format and submitted through the Sistema di Interscambio (SdI).
• Germany: The German entity needed to receive a structured invoice that could be posted and archived in its accounting system.
• Dewesoft HQ: The ERP needed to remain the central source of invoice data, without separate country-specific compliance logic.

Embedding formats, validation rules and delivery integrations for each country into the ERP would create more maintenance work and make expansion harder.

This would lead to:

• More ERP development for each new market
• Greater risk when local rules or formats change
• Separate invoice processes across entities
• Slower onboarding for new countries
• Less flexibility to support future e-invoicing requirements

Dewesoft needed a scalable solution to apply the correct local invoice flow while keeping the core ERP unchanged.

Solution: DDD Invoices as the compliance layer

DDD Invoices connects Dewesoft’s ERP with the appropriate local e-invoicing and delivery route.

Dewesoft continues to create invoice data in its ERP. DDD Invoices receives that data, transforms it into the required structured format, applies country-specific validation and sends it through the appropriate delivery channel.

This keeps Dewesoft’s ERP focused on core business processes while DDD Invoices manages local compliance requirements externally.

Italy: FatturaPA and SdI

For invoices sent to the Italian entity, Dewesoft sends invoice data from its ERP to DDD Invoices.

DDD Invoices then:

• Converts the invoice data into FatturaPA XML
• Applies the relevant format and business-rule validation
• Submits the invoice through SdI
• Routes the processed invoice to the Italian entity through its registered SdI receiving channel

The Italian entity can then receive and post the invoice in its local accounting environment, while invoice creation remains centralised at Dewesoft headquarters.

Germany: Structured delivery

For the German entity, Dewesoft sends invoice data from the same ERP to DDD Invoices.

DDD Invoices converts the data into an EN 16931-compliant structured format, such as XRechnung or ZUGFeRD, based on the relevant transaction and receiving requirements. The structured invoice is then delivered to the German entity’s accounting environment for posting and archiving.

This gives Dewesoft a structured delivery flow for Germany without adding separate German e-invoicing logic into its ERP.

Beyond Italy and Germany

The same integration can support additional Dewesoft entities, countries and invoice flows as the business grows.

Instead of creating a new ERP customisation for every market, Dewesoft can use the existing DDD Invoices integration and configure the relevant requirements. This creates a scalable foundation for:

• Adding new legal entities and country operations
• Supporting additional structured invoice formats
• Connecting to tax-authority and clearance platforms
• Managing cross-border and intercompany invoice flows
• Keeping local compliance logic outside core ERP processes

Outcome: One ERP, multiple compliance paths

By integrating DDD Invoices, Dewesoft keeps HQ as the centre for invoice creation while subsidiaries receive invoices through market-specific compliance paths: Italy via SDI and Germany via direct delivery.

DDD Invoices acts as a single API compliance layer, connecting ERP systems to country-specific platforms without requiring ERP changes.

DDD Invoices: One compliance layer for every market

With DDD Invoices, businesses can connect their ERP through one unified API and manage invoice formats, validation rules, tax authority connections, and delivery channels across countries.

This approach preserves existing workflows while supporting international expansion. For cross-border operations, it enables one integration, multiple compliance paths, and an ERP focused on core business processes.

FAQs

Can you add e-invoicing compliance without replacing your ERP?

Yes. Dewesoft retained its ERP as the system of record for invoice creation and connected it to DDD Invoices for country-specific format conversion, validation, routing and delivery. 

Why keep e-invoicing rules outside the ERP?

Keeping local rules in an external compliance layer avoids building and maintaining separate country-specific logic in the ERP as formats, validation rules, and tax-authority requirements change. 

How does one ERP support different e-invoicing models?

The ERP sends invoice data through one standard integration. The compliance layer then applies the relevant country route, for example, submission through Italy’s SdI or structured delivery to a German entity’s accounting environment.