Every e-invoicing project starts with the same decision — where should compliance logic live? This is the page we send architects and CTOs to before any conversation about tooling.
| 1. Native / Embedded Module | 2. E-Invoicing Connector | 3. E-Invoicing Middleware | |
|---|---|---|---|
| What is it? | E-invoicing built directly inside the ERP. | A bridge connecting ERP/POS to an external e-invoicing provider. | A separate platform sitting between multiple ERPs/POS and the ASP/Access Point/Peppol network. |
| Architecture | ERP → E-Invoicing → ASP/AP | ERP → Connector → ASP/AP | ERP/POS → Connector → Middleware → ASP/AP → Peppol |
| Key features | Invoice validation, XML generation, tax rules, signing, submission, response, QR, status and reconciliation. | API integration, field mapping, data transformation, submission, response and error handling. | Multiple ERP connectors, data enrichment, validation, compliance engine, XML/signing, submission, monitoring, reconciliation, dashboards, multi-country support. |
| Advantages | Excellent ERP integration, seamless user experience, real-time accounting, no separate application. | Faster implementation, good for legacy ERP, lower ERP customization, relatively simple. | Supports multiple ERPs/POS, centralized compliance, scalable, multi-country, centralized monitoring and reconciliation, ERP-independent. |
| Disadvantages | High development effort; regulatory changes require ERP updates; difficult to support multiple ERPs/countries. | Limited functionality; depends on external e-invoicing platform; integration and synchronization issues can arise. | Higher architecture complexity, infrastructure and maintenance costs; requires strong security and monitoring. |
| Best for | ERP vendors and organizations wanting fully embedded e-invoicing. | Customers needing a simple connection from an existing ERP to an ASP. | Large organizations, groups with multiple ERPs/POS, and e-invoicing solution providers. |
dsConnectMW is architected as an e-invoicing middleware and compliance platform — not merely a connector. Connectors are components within dsConnectMW; the platform delivers the broader compliance, transformation, monitoring and reconciliation layer across every ERP and country you operate in.
ERP/POS → ERP Connector → dsConnectMW → ASP/Access Point → Peppol Network
Answer all three questions to see the recommended architecture.