api

A unified API for compliant e-invoicing across countries

Use the same API structure, the same data model, and the same integration logic across countries, while DDD handles local invoicing, tax, and reporting complexity in the background.

Our actual API payload object, maximally standardized across all countries.

Loading data…

Convert standardised .JSON payload into local .XML and reports to tax portals

One unified API Standardized JSON Same steps Talk to us Add a country fast

B2C / B2B / B2G Issued invoices Received invoices Return documents Supported countries

DDDI_Save AddCustomer API ReturnDoc 99% gov changes handled

API docs Public API playground TEST mode PROD mode

How to

From one API connection to compliant invoice flows

Start free integration

01 Set up one API model

Map your invoice flows once and connect through one standardized API model.

02 Send standardized data

Use the same core data model and same steps across countries.

03 Receive compliant output

Get back the required invoices, documents, or links through the same connected model

04 Expand without rebuilding

Add countries, flows, and end-clients without changing your core integration.

What unified API really means in practice

We have abstracted and standartized the input in DDD to the maximum degree. You keep one connection across the countries, while we transform your invoice data into the local formats, required for each market. This way you never deal with local XMLs.

Same API structure across countries
Same core payload logic across invoice flows
Local formats, tax logic, and reporting handled by DDD
Return requested documents through the same model

What unified API really means in practice

Cover every invoice type without rebuilding the logic

All invoice documents can run through the same API structure, without becoming separate integration projects.

Basic invoicesStorno invoicesCorrective invoicesPro-forma invoices

Advance invoicesCredit notesSelf-invoices

B2C, B2B, and B2G invoice flows through one API

Support B2C, B2B, and B2G flows

The same unified API can route consumer, business, and government invoice flows through the right local compliance path, without separate integrations for each buyer type.

Consumer, business, and government invoice flows
One API model across buyer types
Local routing handled behind the API
Expand flows without rebuilding your integration

Generate e-invoices, fiscalize, and send compliant PDFs

DDD takes your standardized invoice data and converts it into the required local outputs, from structured e-invoice formats to fiscalization proof data, compliant PDFs, and tax authority submissions where required.

Generate local e-invoice formats
Create compliant PDFs with required proof data
Support fiscalization and QR-code requirements
Submit or prepare data for local tax authority flows

Generate e-invoices, fiscalize, and send compliant PDFs

Standardization for both outgoing and incoming invoices

One structure for every invoice direction, document type, and local requirement.

Issued invoices

Create e-invoices
Create localized PDFs
Distribute invoices through supported channels
Get requested invoice documents back as links or files

Received invoices

Standardize received invoices in one structure data format
Keep the same API logic across markets
Route invoice data into internal workflows
Retrieve structured invoice outputs consistently

Start free integration

Add a new country without changing the integration model

With DDD, adding a new country does not mean rebuilding invoicing compliance from scratch. You simply onboard a new legal entity / client, and start using the service.

Same API structure when adding countries
Same connection model across markets
Faster rollout into new countries
Less engineering overhead during expansion

Reuse the same API across end-clients

Software providers can reuse the same API model across multiple customer environments. Each end-client gets a separate authentication code, company setup, and country configuration, while your product keeps one integration pattern.

Same API model across multiple end-clients
Separate authentication per client setup
Easier multi-client rollout
Supporting APIs for customer setup, invoice data, and document retrieval

Local tax logic is built into the layer

DDD helps handle local invoicing requirements behind the API layer, including VAT rates, tax codes, exemption logic, and local compliance rules where supported.

Built-in local VAT rates
Exemption rules and exemption clauses included
Local VAT code mapping
Compliance logic handled inside the API layer

99% of government changes handled automatically

DDD keeps your invoicing flow aligned with changing tax authority requirements, so your team does not need to rebuild country-specific logic every time formats, validations, or reporting rules change.

Format and validation updates handled by DDD
Reporting rule changes maintained centrally
Less country-specific logic to maintain in your system
Fewer compliance updates for your development team

99% of government changes handled automatically

Built to support higher invoice volumes with mass API

DDD helps you process larger volumes of invoices with a mass API, that handles thousands of invoice objects in one "object of objects".

High-volume invoice processing
Support for bulk invoice flows (e.g. utility, telecom, SaaS providers...)
Thousands of invoices, one API request
Alternatively: file preparation, processing, notification and download

Integrate once, expand across countries through one API

Use one API structure across invoice flows, countries, and customer setups, while DDD handles local formats, tax logic, fiscalization, and reporting requirements in the background.

USE CASE

This is how it's done.

“The APIs are shared, clean and flexible. It was very easy and clear for us.”

FAQ