SEEBURGER Business Integration Suite (BIS) is one of the leading EDI platforms in Europe — over 40 years of experience, more than 20,000 pre-built trading partner connections, and support for every relevant EDI standard. FlexxLink is the integration client that connects Dynamics 365 Finance & SCM to SEEBURGER BIS directly, without middleware or custom mapping projects.

This page explains how the two systems work together, what you get out of the box, and what it takes to add a new trading partner.

FlexxLink is installed directly inside Dynamics 365. It manages the complete EDI logic on the D365 side — document validation, partner profiles, message routing, and monitoring. Communication with SEEBURGER BIS runs over a bidirectional web service. SEEBURGER BIS handles everything outside of D365: EDI standard translation (EDIFACT, ANSI X12, XML), AS2/SFTP transmission, and the connection to your trading partners.

The result: no separate middleware, no manual file exchange, no data leaving D365 unnecessarily. Messages flow in both directions — outbound from D365 to the partner, inbound from the partner back into D365 — fully automated.

Layer System Responsibility
ERP Dynamics 365 + FlexxLink Document processing, validation, partner profiles, monitoring
Transport REST API web service Standardized message exchange between FlexxLink and BIS
EDI platform SEEBURGER BIS EDI standard translation, AS2/SFTP transmission, partner network

20,000+ pre-built trading partner connections

SEEBURGER BIS ships with pre-built mappings for over 20,000 trading partners worldwide. For the majority of retail, automotive, and logistics partners, there is no mapping project required — the connection is configured, not developed.

Performance up to 100,000 messages per day

The FlexxLink–BIS architecture is built for high-volume scenarios. Throughput of up to 100,000 EDI messages per day is supported, making the solution suitable for large supply chains with multiple active trading partners running in parallel.

All standard EDI message types

Message type Description Direction
ORDERS Purchase order Outbound
ORDCHG Purchase order change Outbound
ORDRSP Order confirmation / response Inbound
DESADV Despatch advice (advance shipping notice) Inbound
INVOIC Invoice Inbound
REMADV Remittance advice Outbound

Configurable validation rules

FlexxLink includes a validation catalog that defines what is checked on each incoming or outgoing message. Rules can be set to run automatically — rejecting non-conforming messages before they touch D365 business logic — or to flag messages for manual review. Validation rules are configured per partner profile, so stricter requirements for key partners don't affect others.

Full message monitoring inside D365

Every message — sent, received, pending, or failed — is tracked inside Dynamics 365. No separate BIS portal access is needed for day-to-day operations. Operators can view message status, inspect payloads, and trigger resends without leaving D365.

FlexxLink also captures the SEEBURGER response for every outbound message. This means you can confirm end-to-end delivery — not just that the message left D365, but that SEEBURGER received it successfully. If a trading partner claims they never received a purchase order, the delivery confirmation is visible directly in D365.

EDI visibility on every record

FlexxLink adds EDI info panels (infoboxen) to purchase orders, sales orders, customer records, and vendor records. From any document, you can see which messages were sent or received for that specific transaction, their current status, and whether the partner interface is in test or production mode — without navigating away from the record.

Dedicated workspaces are available for purchasing, sales, and accounts payable, giving each team a central view of their EDI activity. Microsoft Teams notifications can be configured so that incoming messages trigger a Teams alert, allowing users to jump directly to the document that needs attention.

New trading partner connections are set up through configuration, not development. On the FlexxLink side, the typical steps:

  1. Create a trading partner record in FlexxLink (GLN code, account number, or barcode — whichever the partner uses)
  2. Select the message types to activate (e.g., sales order inbound, order confirmation outbound, invoice outbound)
  3. Assign validation profiles for each message type — use standard profiles or configure custom rules
  4. Set the endpoint: SEEBURGER BIS, or an alternative for partners not on the Seeburger network
  5. Switch the profile to active and run initial test messages via Postman or the Seeburger test environment

On the SEEBURGER side, partner mappings are installed and the partner endpoint is configured. If the partner is already in SEEBURGER's network (20,000+ connections), this is a standard installation step with no mapping development required.

Partners not on SEEBURGER: Most Seeburger customers have around 90% of their partners connected via BIS. For the remaining partners, FlexxLink supports alternative endpoints — Lasernet, Azure Logic Apps, or direct connections — configured at document type level. No second integration platform is needed.

SEEBURGER BIS is available in four deployment models — the FlexxLink integration works with all of them:

  • BIS: On-Premises

  • BIS: Public Cloud

  • BIS: iPaaS

  • BIS: Full service

    The combination of FlexxLink, SEEBURGER BIS and Dynamics 365 Finance & SCM offers a powerful solution for the automation and optimization of your business processes.

    By seamlessly integrating these systems, you benefit from improved data consistency, optimized processes and increased efficiency throughout the supply chain.

    With low one-off costs and short project runtimes , nothing stands in the way of connecting SEEBURGER BIS with FlexxLink.

    Frequently Asked Questions

    1Does FlexxLink require a specific SEEBURGER BIS deployment model?
    No. FlexxLink connects to SEEBURGER BIS via web service regardless of whether BIS runs on-premises, in the cloud, or as a fully managed service. The deployment model is a SEEBURGER decision, not a FlexxLink constraint.
    2How is the BIS channel configured on the SEEBURGER side?
    The BIS processes for FlexxLink look like standard BIS processes. On the BIS side, partner mappings are installed and the partner endpoint is configured per message type. This is handled by SEEBURGER or a SEEBURGER partner and does not require changes to the D365 or FlexxLink configuration.
    3Can validation rules be changed after go-live?
    Yes. Validation rules are managed in FlexxLink's configuration and can be updated at any time without a development release. Changes take effect immediately for new messages. Existing in-flight messages are not affected.
    4How is FlexxLink licensed?
    Flat subscription model with no transaction fees or hidden costs. A 30-day free trial is available. Contact Soluvine for pricing.
    5What happens when a message fails validation?
    Depending on the validation rule configuration, the message is either rejected automatically (with an error response sent back to the trading partner) or placed in a manual review queue inside D365. Operators can inspect the message, correct it if applicable, and release it for reprocessing.
    6Is it possible to connect multiple trading partners with different EDI standards?
    Yes. SEEBURGER BIS handles the standard translation layer — EDIFACT, ANSI X12, XML, and others — transparently. FlexxLink always communicates with BIS, regardless of what standard the trading partner uses on their end.

    Possibilities with FlexxLink