How Infor EDI Managed Service connects to Infor M3
Standard Infor ION integration
M3 publishes and consumes business documents through Infor ION. The managed service connects as an ION endpoint, so customer orders, shipping and invoicing data pass as BODs or equivalent ION documents, and ION handles routing and monitoring.
Pre-built trading partner connections
Infor's managed service provides partner connectivity on its side. You still configure each trading partner relationship, document types and code cross-references; only the transport and translation engine is supplied.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Trading partner | Infor M3 | Purchase orders and changes | Partner sends via the managed service; ION delivers to M3 |
| Infor M3 | Trading partner | Order acknowledgements | Order confirmed in M3 |
| Infor M3 | Trading partner | Advance ship notices | Delivery confirmed in M3 |
| Infor M3 | Trading partner | Invoices | Invoicing run in M3 |
| Infor M3 | Supplier | Purchase orders | PO released in M3 |
Setting it up
- 1Confirm ION is in placeVerify the M3 environment is connected to ION and that the ION API and Grid are healthy before adding another endpoint.
- 2Scope partners and transactionsDocument which partners, message types and versions are in scope. Compare with what the managed service already supports for each partner.
- 3Configure the M3 connection pointDefine the document flows in ION between M3 and the managed service, including which M3 document triggers an outbound message.
- 4Load cross-reference dataPopulate partner item numbers, ship-to codes, units of measure and payment term mappings before sending test documents.
- 5Run partner testingExecute each partner's test cycle and keep evidence of accepted test documents.
- 6Set up monitoringUse ION monitoring plus the service's own tracking, and name an owner for failed documents.
- 7Cut over in stagesMove partners one by one and retire legacy EDI channels only after clean invoice cycles.
What usually breaks
- !Assuming 'pre-built' removes the mapping work: partner item numbers, ship-to codes and tax data still need customer-specific setup.
- !ION documents stuck in an error queue while the managed service reports success, because two monitors are never compared.
- !Business document versions changed after an M3 or ION upgrade, silently breaking an outbound mapping.
- !Duplicate orders when a partner resends a transmission and the M3 side has no unique reference check.
- !Advance ship notices sent before pack, lot or serial data is complete in M3.
- !Unclear support split between Infor, the ERP partner and the trading partner, so a failure bounces between three teams.
A private AI layer across both systems
Cross-monitor reconciliation
A private assistant that reads ION error queues and the managed service's message log can list documents seen by one and missing from the other, as a read-only report.
Error explanation and fix drafts
For a rejected order, it explains the cause in plain language and drafts the missing cross-reference row for a person to review before anything is written.
Upgrade impact checks
Before an M3 or ION upgrade, compare the BOD versions in use with the mappings and flag partners likely to be affected.
Customer service answers
Let order desk staff ask where a partner's order stands and get an answer combining M3 and EDI status, within their M3 role permissions.
Try it here, free
EDI Trading Partner Setup Checklist
A practical checklist for onboarding a new EDI trading partner from first contact through go-live and monitoring.
When something else fits better
- A third-party managed EDI provider with an M3 connector, if your partner network or region is better served elsewhere.
- Direct partner portals for one or two low-volume customers, avoiding a managed contract.
- An in-house EDI translator only when you have specialised formats and the staff to run it.
Frequently asked questions
Do I need ION for this?
Yes, the standard connection is described as ION-based, so M3 must be connected to Infor ION. If you have not deployed ION yet, factor that into the project scope, since it is also the base for other Infor integrations.
Is a managed EDI service compatible with an on-premises M3?
The managed service runs on Infor's side while M3 can remain on-premises, linked through ION. The data crossing that boundary is business documents, so check that this satisfies your own data-handling policy.
What still needs custom work?
Partner-specific code mapping, extra fields, special label or packaging data and any non-standard document variants. Pre-built links remove the transport and translation basics, not the master-data alignment.
How do I see failures?
Look at both ION monitoring and the managed service tracking. Neither alone proves delivery. Assign one owner who checks both and compares them against M3 order and delivery records.
Pairing documented at www.enterprisetimes.co.uk/2017/02/27/infor-streamlines-edi-m3/ . Infor EDI Managed Service is a product of Infor; Netray is independent and not affiliated with either vendor.