Infor LN integration for SaaS companies
Complex, multi-company manufacturers run Infor LN, in Infor's cloud as CloudSuite Industrial Enterprise or on their own servers. Unity connects your product to it, syncing business partners, items, sales orders, invoices, payments and service work through LN's own APIs, under your brand, managed by our team.
- Customers
- Orders
- Payments
- Shipments
- LN 10.x and later
- Cloud or on-premises
- Multiple companies
- Service module
Infor LN models customers as business partners with separate sold-to, ship-to, invoice-to and pay-by roles, and splits logistics and finance across companies, so an integration has to get that structure right before a single order can post. Unity calls LN's own APIs directly, not through ION, so integration traffic doesn't count against your customer's Infor ION usage. That works the same in Infor's cloud and, through a lightweight Intelligrate agent inside the customer's network, for LN on their own servers. Our team builds the integration, delivers it under your brand and keeps it running through LN updates.
Infor LN records Unity maps for SaaS products
Each map works through LN's own business logic, so records land with the company, terms and pricing your customer's team expects.
| LN record | Typical direction | What it's used for |
|---|---|---|
| Business partners and roles | Both ways | The accounts your app serves, with sold-to, ship-to, invoice-to and pay-by roles set up the way LN expects |
| Items and inventory by warehouse | From LN | Items, units and on-hand quantities by warehouse and enterprise unit |
| Prices and contracts | From LN | Price books and sales contracts, so your app quotes what LN will invoice |
| Sales quotations and sales orders | Both ways | Quotes and orders captured in your app, created in LN with the right roles, warehouse and terms |
| Shipments and tracking | Both ways | Shipped quantities, carriers and tracking numbers that keep customers and invoices current |
| Customer invoices and open balances | From LN | Open invoices, credit notes and balances for payments, collections and customer portals |
| Receipts and payments | To LN | Payments collected in your app, matched to the right open invoices in cash management |
| Suppliers, purchase orders and supplier invoices | Both ways | Buy-from and pay-to partners, POs and bills for procurement and AP automation |
| Production orders and project status | From LN | Production order and project progress for scheduling, shop-floor and order-status tools |
| Field service (LN Service) | ||
| Installed base and serialized items | Both ways | Equipment at each customer site, with configuration and warranty details |
| Service contracts | From LN | Coverage and entitlements, so technicians know what is billable |
| Service calls and service orders | Both ways | Calls and work orders dispatched to technicians in your app, with completion returned to LN |
| Service order costs | To LN | Labor, materials and expenses recorded in the field, ready to invoice in LN |
LN's own APIs, not ION or direct database writes
Unity works with LN the way it expects, wherever it runs.
LN's APIs directly, not through ION
Unity calls LN's own APIs instead of routing through ION, so integration traffic doesn't count against your customer's ION usage. In Infor's cloud there's nothing to install on your customer's side.
On-premises LN through the agent
For LN on the customer's own servers, a lightweight Intelligrate agent inside their network calls the same APIs. It connects out, so no inbound firewall ports are opened.
Logistic and financial companies
LN often splits a business across several logistic and financial companies. Unity routes each record to the right company and keeps their data separate.
Enterprise units and warehouses
Unity maps your app's locations to LN's enterprise units and warehouses, so orders ship from the right place and post to the right books.
Infor LN problems we've already solved
These are the issues that stall do-it-yourself LN integrations, and how Unity handles each one.
An order fails because a role is missing
LN won't accept an order for a sold-to partner without the matching ship-to and invoice-to roles. Unity creates or links each role first, then the order.
Records that land in the wrong company
Orders, invoices and payments can belong to different logistic and financial companies. Unity routes each one by the customer's setup, so finance sees it where it belongs.
Field work that never gets invoiced
Service order costs must be released before LN can invoice them, and contract coverage decides what's billable. Unity checks coverage and records each cost against the right service order.
Integrations that break when a customer moves to Infor's cloud
Moving LN from on-premises to CloudSuite Industrial Enterprise changes how integrations connect. Unity manages the move as part of the service, so your product keeps working.
Which SaaS products connect to Infor LN?
Payments and accounts receivable
Pull open invoices into your platform, collect payment, and record receipts in LN against the right invoices.
Transportation management (TMS)
Send shipments from LN to your TMS for load planning, then return carriers, tracking numbers and freight costs.
Field service management
Dispatch service calls and orders to your field service app, check contract coverage, and return labor and parts for invoicing.
CRM, CPQ and quoting
Give reps partner balances, prices and order status, and turn quotes into LN sales quotations or orders.
Procurement, AP automation and supplier portals
Sync suppliers and purchase orders, push approved supplier invoices, and return payment status to your app.
Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your Infor LN integration, put your brand on it, monitor it, fix errors and handle upgrades. Integration updates can even flow into your own help desk. See how Unity works for SaaS.
Infor LN integration questions
Which Infor LN versions does Unity support?
Infor LN 10.x and later on the customer's own servers, and CloudSuite Industrial Enterprise in Infor's cloud.
Is CloudSuite Industrial Enterprise the same as LN?
Yes. Infor CloudSuite Industrial Enterprise is Infor's cloud delivery of LN, formerly Baan. It's a different ERP from CloudSuite Industrial (SyteLine), with its own records and APIs.
Does Unity connect to LN through Infor ION?
No. Unity calls LN's own APIs directly, so integration traffic doesn't count against your customer's ION usage.
Does Unity integrate with LN's service module?
Yes. Unity syncs installed base, service contracts, service calls, service orders and service order costs, so field service apps can dispatch work and send it back to LN for invoicing.
How long does an Infor LN integration take?
A first LN integration typically goes live in ten to sixteen weeks. Each new customer after that is mostly configuration, since the maps are already built.
Your customers run other ERPs too
- All Unity integrations for SaaS
- SAP Business One
- All Microsoft Dynamics integrations
- Microsoft Dynamics 365 Business Central
- Microsoft Dynamics 365 Finance & Supply Chain
- Microsoft Dynamics GP
- Epicor Prophet 21
- All Epicor integrations
- Epicor Kinetic
- All Infor integrations
- Infor SyteLine / CloudSuite Industrial
- Infor VISUAL
- Infor M3
- Infor SX.e
- Infor XA
- NetSuite
- Acumatica