Integrations & API: Connect your existing systems, don't replace them.
OXS.eco does not work in isolation. Built integrations such as Diamant, the REST API and open interfaces connect OXS.eco to your existing ERP, accounting and line-of-business systems: no system change, no double data entry.
How OXS.eco connects
Several integration routes are available, depending on your system landscape and your requirements.
REST API
The OXS.eco REST API covers programmatic integration: upload documents, start workflows, query case files, write to the archive and read from it.
Custom integration
Custom integrations for your accounting, transport or line-of-business system (Diamant or DATEV, for example), set up on a project basis with no development effort on your side. Every integration is custom-built; the logic follows your process.
Email & PEPPOL
Receive e-invoices by email or through the PEPPOL network, validate them automatically and hand them into the approval workflow. Validation findings appear in the workspace as an open task.
EDI / EDIFACT
Structured business documents from EDI processes (purchase orders, delivery notes, invoices) are connected on a project basis on request, not as a standard feature.
What we clarify before we connect a system
Five topics we work through once with your IT team, your accounting team and your process owners before the first interface goes live.
Integrations in detail
What sits behind the most important integrations, the typical data flows and the usual setup effort per integration.
OXS.eco connects to Diamant through the direct integration that runs in production. Live today: the handover of reviewed journal entries to Diamant and the daily payment status reconciliation, whose frequency you determine. Possible on a project basis: taking over vendor and cost center master data plus purchase order matching (3-way match), provided your ERP supplies the data.
Setup effort depends on the document type mapping and on the number of interfaces. Customer-specific configurations and the particularities of your system are clarified in the preliminary call.
DATEV is the de facto accounting standard among German mid-sized companies. Through the DATEV interface (DATEV format or the Rechnungsdatenservice) we connect DATEV-capable systems on a project basis: reviewed documents and accounting data are handed over in structured form, just as with the Diamant integration. The specific route and the effort for your setup are clarified in the preliminary call.
Where no direct integration exists, the OXS.eco REST API takes over. Documented to OpenAPI, OAuth 2.0 for authentication, webhook triggers for events such as document received, approval granted or archiving completed.
A secured VPN connection between your systems and OXS.eco can be set up in addition. Your staff do not need a VPN for that; they work in the browser.
Typical use cases: connecting a custom ERP or an industry-specific system, your own dashboards, automated audit reports, master data maintenance from a headless CMS.
The API documentation is provided as part of the rollout project. Once you place the order you receive a test integration environment alongside the production environment for the development phase.
OXS.eco receives e-invoices from the PEPPOL network; we set the connection up on a project basis. Incoming XRechnung files are validated against DIN EN 16931, moved into the approval workflow and archived in a way that is aligned with GoBD. Outgoing XRechnung files can be generated from ERP or accounting data.
Since 2025 the PEPPOL connection has been relevant for every domestic B2B company; see the e-invoicing mandate.
→ The e-invoicing mandate 2025–2028 explained · → XRechnung in detail
Structured EDI messages: INVOIC (invoice), ORDERS (purchase order), DESADV (despatch advice) and RECADV (receipt advice) are received through AS2 or your existing EDI provider, parsed and moved into the matching workflow.
EDI is connected on a project basis on request, not as a standard feature. Typical sectors: retail with supplier EDI, manufacturing with OEM integration, logistics with freight data. Subset maintenance and mappings are discussed during setup.
Going deeper: Technical details are clarified in a technical call with your IT team. Request a technical call →
Typical systems in your industry
Nine industries, their most important systems and a direct route to the matching industry page. Integrations are built on a project basis; the one running in production is Diamant.
Logistics & transport
Diamant/4, ANAXCO D, Soloplan CarLo, DATEV
View the industry page →Freight forwarding
ANAXCO D, Soloplan CarLo, ATLAS/customs, Diamant/4
View the industry page →Financial services & banking
OSPlus, agree21, SAP for Banking, XRechnung
View the industry page →Insurance
BiPRO, GDV-Datensatz, Diamant/4, DATEV
View the industry page →Public sector
Infoma newsystem, OZG-RE/ZRE, AKDB OK.FIS, XRechnung
View the industry page →Construction
BRZ, RIB iTWO, Diamant/4, DATEV
View the industry page →Retail & wholesale
LS Central, DSFinV-K/TSE, EDI INVOIC, DATEV
View the industry page →Healthcare
medatixx, CGM, tomedo, DATEV
View the industry page →Industry & manufacturing
proALPHA, SAP S/4HANA, Diamant/4, DATEV
View the industry page →Your system is not listed?
Custom integration via CSV, ODBC or REST API.
Discuss integrations →Frequently asked questions about integrations & the API
No. OXS.eco integrates into your existing system landscape through open interfaces. No system change, no double data entry.
Only for customer-specific use cases. Standard integrations via REST API and PEPPOL run without custom code. If you want to build your own workflows or dashboards, you get the API documentation and a test integration environment as part of the project. MAAS sits in on the architecture session.
Vendors, cost centers, entities and document types are imported during the project from your leading system, typically ERP or accounting, by export/import or through the REST API. Whether and how often an ongoing sync is needed after that is something we define together.
Every handover is logged with status, timestamp and the person who processed it. If a process runs into an error it lands in the error work basket and your administrator receives an email automatically. Failed handovers do not block the rest of the process.
Yes. For bulk volumes OXS.eco exports documents together to your SFTP server instead of sending individual emails. Directory, naming scheme and frequency are defined during the project.
In many cases yes: industry systems such as OSPlus, agree21, Soloplan CarLo, Infoma newsystem, LS Central, proALPHA or BRZ are connected on a project basis through the REST API, file interfaces or standard formats. In principle any system can be connected that is able to export, import or provide an interface. Which systems it makes sense to connect first is clarified in the preliminary call.
Hélène TinetInitial call, demo & onboarding
Discuss your integration in 15 minutes.
A REST API is in place for every one of our customers today, plus SFTP, email intake and direct integrations such as the one to Diamant. Which route fits you depends on your systems. We work that out in a meeting with your IT team.
Related solutions