Service · Custom software

Systems integration

Take a supplier in Upper Styria machining metal parts for the car industry. Call-offs from German customers arrive via EDI, yet get printed out and keyed into the ERP. Production orders travel to the machines in Excel, quality data sits in a separate database, and the customer insists on an invoice format nobody enjoys filling in by hand. Over the years individual links have appeared, each built by a different firm and none documented. When one breaks, people only notice once a delivery goes missing. Integration here does not mean bolting on yet another link. It means bringing order: deciding which system owns which data, routing interfaces through one central point and watching them so an error surfaces before it reaches a customer.

EDI
EDIFACT and VDA with customers
E-invoicing
ebInterface, PEPPOL, ZUGFeRD
OpenAPI
every interface documented
Monitoring
alerts before customers notice

Everything this covers

From an overview of every link to an operation where you can see at any time what is running and what is stuck.

Settle the details with an engineer

Interface map

All systems and data flows in one picture: who sends what to whom, how often, in which format and who is responsible when it fails.

Leading systems

Items, customers, prices, orders, stock: each data type is maintained in exactly one system. Every other system only reads it.

Middleware instead of sprawl

Rather than many point-to-point connections, a central integration layer, for example n8n, Azure Logic Apps or a lean custom service, depending on volume and existing infrastructure.

ERP and shop floor

Connecting Business Central, SAP Business One, Mesonic WinLine, BMD or Odoo with production, warehouse and quality systems via API, database or file exchange.

Customers and suppliers

EDI messages such as call-offs, despatch advice and invoices; e-invoices as ebInterface, over PEPPOL, or as ZUGFeRD and XRechnung for German trading partners.

Error handling

Retries, queues and readable error messages sent to the responsible person, not to a shared mailbox nobody checks.

Documentation

Each interface with a description, data format, owner and test cases, so a different provider could maintain it too.

Our working method

We start with the overview and the links causing the most manual effort or risk. Everything else follows by priority.

01

Stocktake

Talks with business units and IT, a review of existing connections and the interface map.

02

Target picture

Leading systems, integration layer and order of work, signed off by management.

03

Staged delivery

One interface at a time, each tested against copies of real data and run in parallel for a while.

04

Operation

Monitoring, alerting and maintenance, including adjustments when a partner changes its format or API.

The costliest interface is the one nobody feels responsible for. When the ERP partner, the machine vendor and the web agency all point at each other, the fault just sits there. Assign an owner to every link and have it built so that any error can be clearly attributed to one side.

Frequently asked questions

With two or three links, not necessarily. From roughly five systems exchanging data, a central hub saves maintenance effort, because monitoring, logging and error handling are built once.

That can be handled through database access, import and export files or the vendor's own tools. Such links are more sensitive to updates, so we watch them closely and document the dependencies.

Under a maintenance agreement, we are the first point of contact. Our monitoring shows which side the fault is on, and we coordinate with the ERP partner or customer rather than leaving you to mediate.

That depends on your customers. Some require ebInterface or PEPPOL, and German clients increasingly ask for XRechnung or ZUGFeRD. We check what your ERP already supports and only add what is missing.

Let us tidy up your interfaces

Name your key systems and the places where things snag today. We will suggest a sensible first step.

Availability
Monday to Friday, 8:00-17:00 Austrian time (CET/CEST), reply within one working day
Meetings
By video on Microsoft Teams or Google Meet

We only use cookies that are technically required: to run the website and to remember the location you picked. There are no advertising or tracking cookies. Details are in the privacy notice.