What Is Integration Transaction?
Also known as: LN integration transaction, logistics finance integration
Definition
An integration transaction is the record Infor LN creates when a logistic event such as a receipt, issue, shipment or production completion must post to finance. Mapping schemes translate each transaction into the correct debit and credit ledger accounts and dimensions.
Integration Transaction Explained
Logistics and finance are separate packages in LN, and integration transactions are the bridge between them. Every event with a financial consequence - receiving purchased material, issuing components to a production order, completing production, shipping to a customer, revaluing inventory - generates an integration transaction that records what happened, to which item, in which quantity and at which value, along with the context needed to determine the accounting treatment.
That context is what the mapping schemes consume. Mapping elements typically include the type of business event, the item group, the warehouse, the business partner, the cost component and, in project environments, the project. Each combination resolves to a debit account, a credit account and the dimensions that go with them. Because the mapping is configuration, the same physical event can post differently for different item groups, warehouses or legal entities without any code.
Posting runs then convert integration transactions into ledger entries in the appropriate financial company, determined by the enterprise unit associated with the logistical scope. Until they are posted, the transactions sit in a staging state, which is deliberate: it allows validation, review and correction of mapping problems before anything reaches the general ledger, and it gives a clean audit path from any ledger entry back to the physical event that caused it.
The operational failure mode is unmapped transactions. If an event occurs for a combination that the mapping does not cover, the transaction cannot be posted and it accumulates in an error state. Because these are usually discovered at period close, when finance finds that inventory in logistics does not agree with the ledger, monitoring the unmapped and unposted queues throughout the period rather than at month end is one of the highest-value habits an LN finance team can build.
Why It Matters
- Integration transactions are the audit trail from a physical movement to a ledger entry, which is what makes reconciliation possible.
- Mapping is configuration, so accounting treatment can vary by item group, warehouse or entity without development.
- Unmapped transactions block period close and are almost always discovered at the worst possible moment.
- Every new item group, warehouse or cost component introduced later needs mapping coverage or it silently breaks posting.
In Practice
Build a daily check on unposted and unmapped integration transactions rather than reviewing at month end. The typical trigger is a newly created item group or warehouse that nobody added to the mapping scheme, and it may generate transactions for weeks before finance notices. A short daily report turns a painful close into a same-day configuration fix.
Frequently Asked Questions
Why do integration transactions fail to post?
Almost always because the mapping scheme has no rule covering the combination of elements on the transaction. A new item group, warehouse, cost component, business partner group or project introduced after the original configuration is the usual cause. The transaction stays unposted until mapping is added, after which it can be reprocessed and will post with its original date and value.
How do integration transactions help reconciliation?
They provide the traceable link between a physical event and its ledger entry. When inventory value in logistics does not agree with the inventory account in the general ledger, the integration transaction list shows exactly which events posted, which are unposted and which failed to map. That turns a whole-of-ledger investigation into a targeted review of a specific transaction queue.
Related Terms
Financial Company
A financial company in Baan and Infor LN is a company number that owns the general ledger: the chart of accounts, dimensions, fiscal calendars, currency setup and all financial transactions for one or more logistic companies linked to it.
Cost Component
A cost component in Infor LN is a bucket that classifies part of an item's cost - material, operation, subcontracting, surcharge or general cost - so standard and actual cost prices can be broken down, rolled up through the bill of material and compared.
Warehouse Order
A warehouse order is the execution document in Infor LN Warehousing that carries out an inbound, outbound or transfer movement. It is generated from an originating order such as a sales, purchase, production or transfer order, and its order type defines the procedure steps.
Go Deeper
Infor LN Upgrade Cost Estimator
Estimate the services cost and timeline for an Infor LN version upgrade or CloudSuite migration based on your users, sites, customizations, and integrations.
Infor LN Implementation Cost: What to Budget
Infor LN implementation cost typically runs $500K to $5M+. See budget breakdowns by phase, license-to-services ratios, and the cost drivers for 2026 projects.
Infor LN to CloudSuite: Migration Playbook
Infor LN to CloudSuite migration playbook: Baan and LN version paths, extension conversion, ION integration rework, timelines, and defense compliance steps.
Working with Integration Transaction in a live environment? Our engineers do this every day - and our AI agents automate most of it.