--- title: "NxM EDI" id: "998214" type: "page" slug: "nxm-edi" published_at: "2026-09-15T07:55:40+00:00" modified_at: "2026-09-16T06:39:31+00:00" url: "https://ioi.gmbh/en/nxm-edi/" markdown_url: "https://ioi.gmbh/en/nxm-edi.md" --- NxM EDI for Microsoft Dynamics 365 Business Central # Exchange business documents without *entering* them again. With NxM EDI you exchange orders, order confirmations, delivery notes and invoices directly between Business Central and the systems of your customers and suppliers. Incoming data is created as a document in Business Central. The format and transfer channel a partner requires is configured once per partner. Your team sees status and deviations where they already work: on the document. [Discuss your EDI setup →](/en/contact/) [See document types and formats](#belege) Inside Business Central## See status and deviations on the document itself NxM EDI is embedded in Business Central. Incoming documents are created as Business Central documents, outgoing ones leave the system in the recipient’s format. Your team does not need a second application for it. 01 · Receive#### Take in incoming purchase orders Orders from your customers are converted and created as a sales order in Business Central. That reduces the manual transfer of order data and the queries that arise from transfer errors. 02 · Send#### Send documents in the recipient’s format Order confirmation, delivery note and invoice go out in the format the respective partner requires. The mapping sits in the partner’s communication profile. Your team does not pick it by hand. 03 · Check#### See deviations on the document If a supplier confirms a different quantity or delivery date, the deviation is visible on the document. You can see where a purchase order stands without asking the supplier. 04 · Act#### See what needs doing in the role centre If a document fails or the automation stops, the role centre in Business Central reports what needs attention. Open cases stay visible instead of disappearing into a log. Partner connection · Documents and formats## Exchange orders, despatch advices and invoices electronically Document types### Document types in sales and purchasing Included in the standard version. Which ones you use depends on what your partners support. Sales - Quote and quote confirmation - Order and order confirmation - Order cancellation - Delivery - Invoice and credit memo Purchasing - Order and order confirmation - Order change - Receipt - Invoice and credit memo Other - Sales reports - Inventory reports - Product catalogue **Special cases** If a partner deviates from the standard, the format can be adapted. Data formats### Data formats your partners require From trading standards to electronic invoicing for public sector clients. Electronic invoicing - XRechnung - ZUGFeRD - Peppol BIS Trade - EDIFACT - ANSI X12 - UBL - HANCOM Other - XML and OIOUBL - EHF - more on request **Public sector** For invoices to German federal, state and municipal bodies, XRechnung and ZUGFeRD are the common formats. Partner connection · Channels and reach## An EDI connection that matches your business partners Transfer channels### Transfer channels Which protocols NxM EDI supports. The choice is usually your partner’s, not yours. Common - AS2 - SFTP - FTPS Classic - FTP - X.400 - Email Network and interface - VAN - Web services - Peppol access point **More** Additional protocols on request. Reach### One network instead of many single lines VAN stands for Value Added Network: a clearing point that forwards your documents to your partners’ systems. You connect once instead of building a separate line to every partner. Own network - Distribution to partners worldwide - Test and production kept separate Connected networks - Peppol - IBM - Basware - Strålfors Logging - Every transfer is recorded **Judgement call** Whether the network or a direct connection pays off depends on how many partners you serve and what they require. Operations## Monitored EDI operation that takes load off your IT EDI runs quietly until a certificate expires, a partner changes their format or a file gets stuck. NxM offers services for those cases, booked separately. Which ones apply depends on the operating model you choose. #### Operational monitoring as an added service On request, the NxM support department monitors the business documents you send through the conversion, sending and return phases. The service is booked separately and requires an NxM cloud installation. #### Errors are worked on, not just reported When the support team spots an error, it fixes the error and gets back to you if your input is needed. Your IT does not have to watch the transfers itself. #### Notifications on your terms In the Gateway you define who is informed about which event. Notifications can also be sent to customers and suppliers. #### Cloud operation: the technology sits with NxM With the cloud option, certificate management, connection monitoring and format changes sit with NxM. EDI incidents go to NxM support rather than to your office. Operations · Traceability## Every transfer stays traceable Trace### Trace What happened to a document can be evidenced afterwards. History - History of all EDI transactions - Incoming and outgoing logs - View acknowledgements **Access** Via browser, tablet and smartphone. Control### Control Settings you make yourself, without raising a support ticket. Administration - Manage integration agreements - Set up notifications - Test and production kept separate **Day to day** Daily work runs from the Gateway. Extensions## Add-on modules for further business processes The standard covers document exchange. The following modules come on top when your process needs them. They are not part of the base scope. Module#### Product catalogue: exchange item and price data You publish item and price information in a structured way and take in your suppliers’ data. Relevant when price lists arrive as spreadsheets by email today and are maintained by hand. Module#### Intercompany: documents between your own companies The built-in intercompany module covers additional document types, including order changes, and offers more control. Relevant for groups with several legal entities. Module#### Supplier portal: partners without their own EDI connection Suppliers update a purchase order themselves and add the invoice, the goods delivered and the place of delivery. Relevant when some of your suppliers are too small for an EDI connection of their own. Module#### PDF and SMS: further output channels Documents also go out as PDF, messages by SMS. This is set per communication profile. Relevant for partners who do not accept a structured document. System and licence## Requirements and licensing at a glance Requirements### Requirements What has to be in place on your side. ERP system - Dynamics 365 Business Central - Dynamics NAV Integration - Fully integrated into Business Central - Its own role centre - Access from PC, tablet and smartphone Operating model - NxM cloud - Your own installation **Note** Operational monitoring is available only with an NxM cloud installation. Licensing### Licensing Monthly subscription. The scope follows your actual data traffic. Basis - Number of licences - Number of connections and formats Optional - Support agreement, monthly - Operational monitoring - Add-on modules Company size - Small companies - Mid-market - Groups of companies **Purchase** Licensing and advice through IO Integrated. FAQ## Frequently asked questions. What does NxM EDI cost? + NxM EDI is licensed as a monthly subscription. The price follows the number of licences plus the number of connections and formats you actually need. A company with two trading partners does not pay like one with forty. A support agreement and operational monitoring are billed separately. We will work it through against your own volumes. Do we need our own EDI specialists? + Not necessarily. With the NxM cloud, certificate management, connection monitoring and format changes sit with NxM, and with operational monitoring booked on top, NxM support watches the transfers. Your team works in Business Central and sees the status on the document. With your own installation, more responsibility stays in house. Does it work with Dynamics NAV as well? + Yes. NxM EDI exists for Dynamics 365 Business Central and for Dynamics NAV. If a move to Business Central is on your agenda anyway, tell us. Then we plan document exchange into that project instead of setting it up twice. Our customer requires a format that is not listed here. + That is the normal case in EDI, not the exception. Alongside the EDIFACT, X12, UBL, XML, Peppol, EHF, HANCOM, XRechnung and ZUGFeRD standards, custom formats can be mapped. Send us your partner’s specification and we will work out what it means in detail. How does a rollout work? + It starts with your partner list: who do you exchange which documents with, and what do those partners require in terms of format and transfer channel. That determines how many connections are set up and which document types you need. Three things are then decided: the operating model, meaning NxM cloud or your own installation, the scope of the added services, and which modules beyond document exchange make sense. What does IO Integrated do, and what does NxM do? + We are your contact for licensing and advise you on choosing modules and fitting them into your Business Central. NxM is responsible for the EDI platform and for operational monitoring. Who takes on which part of the setup is agreed before the project starts. ## Discuss EDI for your Business Central. The partner list first, the effort second. Tell us which customers and suppliers you exchange documents with, and which formats and transfer channels they require. That determines which connections you need and how extensive the rollout will be. [Discuss your EDI setup →](/en/contact/) [or give us a quick call: +49 214 8402 3000](tel:004921484023000) ✓ We start from your list of customers and suppliers ✓ Which document types and formats are covered ✓ Which connections and modules come into question ✓ Operating model: NxM cloud or your own installation