Easy EDI Interface

Receive EDIFACT orders and send shipment and invoice messages through one secured cloud endpoint, using Business Central's standard mapping tools.

Track each EDI message in Business Central

Retail and industrial customers want to exchange EDIFACT, not e-mail. Easy EDI Interface connects Business Central to a secured endpoint on Azure API Management. A partner's message arrives as base64 XML; a stylesheet converts it to standardised XML, which Business Central's standard Data Exchange framework maps into a sales order. Posting a shipment or invoice sends a DESADV or INVOIC back through the same route. Each message appears in a Business Central queue with its payload, status and any error. The sales team can see what arrived or failed, then reprocess messages themselves.

Key features

Connect standard Business Central Data Exchange Definitions, APIs and posting events.

ORDERS → sales order

Incoming EDIFACT orders become sales orders through the agreement's Data Exchange Definition; the created document is linked to the message.

INVOIC and DESADV out

Posting a sales invoice or shipment creates the outbound message for partners with an outbound agreement.

One secured endpoint

Azure API Management receives base64-encoded XML and applies the stylesheet; Business Central only ever sees standardised XML.

Adjust mappings without custom code

Each agreement uses a standard Business Central Data Exchange Definition. Consultants can adjust the mapping without deploying custom code.

A queue you can see

Payload, status, timestamps and errors per message; reprocess requested or failed entries from the page.

Agreements per partner

Customer or vendor, sender and receiver IDs (GLN), direction, message type, encoding and character set — all on one card.

Built for

Suppliers whose customers mandate EDI, and who want it to live inside Business Central.

Sales operations

Orders arrive as sales orders, complete; the queue shows what came in and what needs a look.

Finance and logistics

Shipment advice and invoices leave automatically when the document posts.

EDI administrators and partners

Agreements and Data Exchange Definitions are maintained in Business Central; a new partner is configuration, not a project.

What is inside

A Business Central app plus an Azure API Management endpoint; both are part of Easy EDI Interface.

Transport and transformation

  • API endpointA Business Central API page receives the queue entry from API Management.
  • Base64 XML payloadThe message body is stored as a blob with the entry.
  • Stylesheet stepAPI Management converts the partner format into standardised XML before mapping.

Inbound messages

  • ORDERSImported through the agreement's Data Exchange Definition into a sales order.
  • GENRALGeneral-purpose import through a configured Data Exchange Definition.
  • RECADVReceive EDIFACT receiving advice from your trading partners in Business Central.

Outbound messages

  • INVOICExport of a posted sales invoice for partners with an outbound agreement.
  • DESADVExport of a posted sales shipment.
  • PRICATSend EDIFACT price catalogues from Business Central to your trading partners.

Trading-partner agreements

  • Customer or vendorThe agreement identifies the partner and its source record.
  • IdentifiersSender, receiver and provider IDs with their formats, including GLN.
  • Per-agreement processingDirection, message type, Data Exchange Definition, encoding, character set and URL decoding.

Queue and recovery

  • Status trackingRequested, processing, error, completed — plus document states such as open, released, shipped.
  • Errors and reprocessingThe handler logs the error; staff reprocess requested or failed entries manually.
  • Payload inspection and cleanupPages show payload and error; old entries can be deleted.

Monitoring and document linkage

  • Role-centre cuesInbound requested, error and open; outbound requested, error and completed.
  • Sales lifecycle updatesRelease, reopen, posting and shipment events update the linked message.
  • Posting-triggered exportSales posting invokes the outbound handlers for the resulting shipment and invoice.

From partner message to Business Central document

Receive ORDERS, GENRAL and RECADV; send INVOIC, DESADV and PRICAT. Posting a sales invoice or shipment triggers INVOIC or DESADV respectively.

  1. Trading partnerEDIFACT ORDERS, GENRAL
  2. Azure API ManagementSecured endpoint, XSLT to standard XML
  3. Message queuePayload, status, errors
  4. Business CentralSales order via Data Exchange

Inbound today

  • ORDERS → sales order
  • GENRAL → your Data Exchange mapping
  • RECADV → receiving advice from your trading partner

Outbound today

  • Posted sales shipment → DESADV
  • Posted sales invoice → INVOIC
  • Price catalogue → PRICAT

Message types

ORDERSGENRALDESADVINVOICRECADVPRICAT

An order, shipment and invoice exchange

Agreements define the mapping; the queue shows each message's details and status.

Diagram. A trading partner sends EDIFACT ORDERS and GENRAL to Azure API Management, a secured endpoint that takes base64 XML and converts it with XSLT to standardised XML, and receives INVOIC and DESADV back. Inside Business Central online with Easy EDI Interface, a message queue holds payload, status and errors and allows manual reprocessing; agreements hold partner, GLN, direction and Data Exchange Definition; standard documents are created, ORDERS to sales order, GENRAL to your mapping, posted shipment to DESADV, posted invoice to INVOIC, and release, post and ship events update the queue. A footer states that mapping is standard Business Central Data Exchange, a consultant changes a definition, not code.
  • Azure API Management
  • BC Data Exchange framework
  • EDIFACT
  • GLN identifiers

At a glance

  • EDIFACT ORDERS into sales orders
  • GENRAL through your own Data Exchange Definition
  • DESADV from posted shipments, INVOIC from posted invoices
  • RECADV receiving advice in, PRICAT price catalogues out
  • Secured Azure API Management endpoint with XSLT transformation
  • Standard Business Central Data Exchange mapping — no code
  • Agreements per customer or vendor with GLN identifiers
  • Message queue with payload, status, errors and manual reprocessing
  • Role-centre cues for inbound and outbound traffic
  • Sales lifecycle events update the linked message

Updates with Business Central online

Our apps are built for Dynamics 365 Business Central online and follow Microsoft's release rhythm. Updates are managed through Business Central online, rather than a separate on-premises installation.

Two major releases a year

Every app is validated against the next Business Central release before Microsoft rolls it out, to check compatibility ahead of the update.

Monthly updates included

Fixes and improvements ship through AppSource and your Business Central admin center, with the same monthly cadence as the platform.

Current and previous release supported

You can stay on the release schedule your organisation prefers; we support the current major version and the one before it.

See Easy EDI Interface in action

Book a short demo and we will walk one of your partner's EDIFACT orders from the endpoint to a sales order, live.