Connect Infor to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Infor and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Infor EDI
Infor CloudSuite, M3 and LN all model trading documents well; the work we do is translating between a partner's EDIFACT, TRADACOMS or X12 message and the Business Object Documents Infor expects, then keeping the identifier mapping stable as partners and items change.
One managed platform, no custom code
XEDI maps Infor to your trading partners and validates every document, so data flows straight into the systems your teams already use.
BODs, ION and the translation in between
Infor moves data internally as Business Object Documents, routed through ION. A trading partner sends EDIFACT, TRADACOMS or X12. Neither knows about the other, so the integration translates in both directions and has to agree with Infor on which BOD represents an inbound order and which represents a despatch.
Because ION is event driven, timing matters more than it does in a batch integration. A despatch published before the shipment is confirmed produces an advice the partner cannot reconcile against what arrives.
CloudSuite, M3 and LN are not one product
Infor is a family rather than a system. CloudSuite Industrial, M3 and LN hold customers, items and locations differently, and a mapping built against one does not transfer to another without rework.
Getting the target confirmed at the start avoids the common outcome where a build is scoped against M3 and delivered against a CloudSuite tenant with different entity names.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox. Orders arrive and your team is notified, without waiting on the Infor integration.
Each document derives from the one before: the order becomes the despatch advice, amended where the delivery differs, with SSCC labels for the pallets, then the invoice on delivery. Delivery of that invoice is confirmed in the dashboard rather than assumed.
The integration sits over that workflow and automates it, so documents land as the Business Object Documents Infor expects and outbound flows are raised from them. Smaller teams run on the portal alone; our API serves enterprises wanting finer granularity. An Infor integration is the middle, holding the same documents in the system your operation runs on.
Documents you can exchange
- Purchase orders
- Order acknowledgements
- Despatch advice and advanced shipping notices
- Invoices
- Credit notes where required
- Product and price data where required
Built for Infor teams
Whoever owns Infor in your business, XEDI keeps EDI accurate and hands-off.
- Manufacturers running Infor CloudSuite or M3
- Distributors on Infor LN
- Supply chain and logistics teams
- Finance and accounts receivable teams
- EDI coordinators
Infor EDI document types
The document set differs by partner and by which Infor product you run, but these are the usual flows.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Inbound retailer demand, translated into the order BOD and creating a customer order against the right entity. | Partner to Infor |
| Order acknowledgements | Confirmation of accepted, amended and rejected lines. | Infor to partner |
| Advanced shipping notices | Despatch advice built from the Infor shipment, with pack detail where the partner requires it. | Infor to partner |
| Invoices | Invoices referenced to the order and delivery for automatic matching. | Infor to partner |
| Product and price data | Item and price master data for partners maintaining a catalogue. | Infor to partner |
How to connect Infor with EDI using XEDI
Infor connections are usually staged per partner, with the first taking the longest because it settles the BOD mapping the rest reuse.
-
01
Confirm the Infor records, fields and workflows that should exchange EDI data.
-
02
Map trading partner documents to the right customers, items, locations and finance fields.
-
03
Configure validation, connection routing and exception alerts in XEDI.
-
04
Test the required document flows with each trading partner.
-
05
Monitor live transactions and refine partner-specific mapping rules.
Ready to connect Infor?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Infor EDI
Common requirements
- Infor access or import/export method
- Customer, supplier, product and location identifiers
- Trading partner EDI specifications
- Invoice, tax and fulfilment rules
- Connection method such as AS2, SFTP, API or mailbox routing
What we need from you to build it
Only the things we cannot hold for you. Each partner's requirements are already ours, so the first connection goes live considerably faster.
- Which Infor product
- CloudSuite, M3 or LN, and the specific tenant or environment, since entity structures differ between them.
- ION connection point
- How documents enter and leave, and who can change the routing when a partner adds a document type.
- Customer and address mapping
- Each partner mapped to an Infor customer record, with their delivery points resolvable without manual matching.
- Item and unit data
- GTINs at each packaging level and the conversion between the partner's ordering unit and your stocking unit.
- Which partners you trade with
- The partners in scope, now and next. Their document set, standard and connection route are already held by us.
Why suppliers choose XEDI for Infor
- Most partners are already connected, so identifying which Infor product you run does not delay trading.
- One connection covers EDIFACT, TRADACOMS and X12, so partners in different regions do not each need a project.
- Partner rules are validated before a document is published into ION, so errors surface in the message rather than downstream.
- A new partner is not a development cycle. We build and verify the connection before it carries live documents.
- Full message traceability, which is what finance needs when an invoice is queried later.
- Partners raise problems with us rather than with your team, and we rectify them on your behalf before they affect trading.
Can XEDI integrate Infor with EDI trading partners?
Yes. XEDI can connect Infor workflows with trading partner EDI requirements and automate common order, fulfilment and invoice document flows.
Which documents can be exchanged with Infor EDI?
Common flows include purchase orders, order acknowledgements, despatch advice or ASN messages, invoices and credit notes where required.
Plan your Infor EDI setup
Everything you need to scope, map and go live with Infor, in one place.