Infor LN Finance Module API Integration: BOD Publishing, REST APIs, Posting Controls and Enterprise Architecture
Infor LN exposes finance data through two main surfaces: Business Object Documents (BODs) published to Infor Intelligent Open Network (ION), and REST application programming interfaces (APIs) exposed through the ION API Gateway. The right choice depends on direction, latency and volume. Whichever surface you use, external finance transactions must respect LN’s own posting chain of integration transactions, mapping, posting and finalization. Otherwise the general ledger and the reconciliation data drift apart, and month-end close pays the price.
Why Finance Is the Hardest Infor LN Integration to Get Right
Finance is the hardest LN integration because every external transaction must balance, land in an open period and reconcile to a subledger before the close can finish.
The symptoms are familiar from Infor LN consulting engagements that follow a rushed go-live. Close is delayed while teams chase breaks between the receivables or payables subledger and the general ledger. Duplicate journals appear after an interface retry, and orphaned postings sit in the ledger with no originating document. Auditors then raise findings on journal sources that nobody formally approved.
Logistics integration is more forgiving, because a duplicate shipment status is simply overwritten by the next message. A journal posted twice is a ledger fact that needs a documented reversal in an open period.
Finance also carries constraints that logistics flows do not. Every batch must balance before finalization, and periods open and close on a controlled calendar. Enterprise LN deployments usually run several financial companies, and intercompany and intergroup flows depend on relations that must exist before anything posts. Master data gaps become posting failures.
How Finance Data Moves Inside Infor LN
Finance data in Infor LN moves from a logistic event to a finalized ledger entry through four stages: integration transaction, mapping, posting and finalization.
Operations Management, the set of non-financial LN packages, logs each logistic event as an integration transaction. Each one is identified by a transaction origin and financial transaction combination, such as Sales Order/Issue. Financials translates every combination into an integration document type, maintained in Integration Document Types (tfgld4557m000).
The financial integration concepts and components explain that LN supplies predefined document types. Some, such as Currency Difference, only log reconciliation data and cannot be mapped. Integration transactions are stored in the Integration Transactions table (tfgld482) and copied to the Reconciliation Data table (tfgld495), which remains after the integration transactions are archived.
The processing of integration transactions follows a fixed sequence:
- Map Integration Transactions (tfgld4281m000) maps transactions to ledger accounts and dimensions using the active mapping scheme version.
- Post Integration Transactions (tfgld4282m000) creates non-finalized journal entries. The user running it must belong to an integration user group.
- Finalization runs through Global Selection of Batches for Finalization (tfgld1210m000) or Finalization Run Number (tfgld1609m000), which checks that each batch balances before moving it to the general ledger.
Errors are reviewed in Print Integration Transactions Error Log (tfgld4484m000). The common causes are missing intercompany relations (tfgld0515m000), missing intergroup relations (tfgld2501m000) and closed periods in Period Status (tfgld0107m000).
Every external finance integration either feeds this chain or reads its outputs. An interface that bypasses integration transactions leaves no record in tfgld495, so the ledger may balance while the reconciliation trail is gone.
The Integration Surfaces Available for LN Financials
LN Financials can be integrated through ION BODs, LN REST APIs through the ION API Gateway, or file-based interfaces, and each surface suits a different direction, latency and volume.
ION routes published BODs through connection points and document flows to subscribing applications. Teams that have not built those flows yet can start with a step-by-step ION setup guide. REST APIs are synchronous calls from an external system that needs an answer now. File-based interfaces are a last resort where neither surface fits.
| Surface | Direction it suits best | Latency | Volume profile | Typical finance use cases | Main risk |
|---|---|---|---|---|---|
| ION BODs | Outbound from LN to subscribers | Near real time for events, scheduled for balances | High and sustained | Data lake feeds, consolidation, reporting and planning tools | Incomplete ISO or dimension setup causing rejected messages |
| LN REST APIs through the ION API Gateway | Request and response, read or write | Synchronous | Low to moderate per call | Status lookups, portal queries, targeted inbound transactions | Over-privileged service identities and uncontrolled retries |
| File-based interfaces | Inbound bulk where no supported API exists | Batch | Large and periodic | Legacy bank formats, one-off migrations | Weak traceability and manual error handling |
Polling REST APIs to replicate high-volume ledger data that a BOD already publishes is the wrong choice; it loads the gateway and still misses changes between polls.
Publishing Finance Data Out of LN Through Infor ION
Outbound finance publishing through Infor ION is reliable only when BOD parameters, ISO mappings and reporting dimensions are complete before the first message leaves LN. The sequence applies to cloud and on-premises LN alike, though scheduling and monitoring tools differ.
Preparing LN before the first BOD
BOD messaging is configured in BOD Parameters (tcbod0100m000). The Prevent BOD Publishing check box blocks publishing until setup is complete, so keep it selected until validation passes. Infor’s guide to configuring LN for BOD publishing calls for running Validate Publishing Data Setup (tcbod0300m000) at the start and end of configuration.
BODs use International Organization for Standardization (ISO) codes for currencies, countries in 2-alpha form, and languages, so those mappings in LN master data must be complete first. Financial BODs also depend on BIA Parameters (tfbia0500m000), Flexible Dimension Definitions (tfbia8501m000), Fixed Dimension Definitions (tfbia8502m000) and Mapping ERP Dimensions to Reporting Dimensions (tfbia8503m000).
Tenant is required on every BOD, accounting entity on transactional BODs, and location on transactional and balance BODs. Confirm which session maintains this mapping in your LN release before you start.
Master data versus transactional and balance BODs
Publish Financial Master Data (tfbia0200m000) sends the reference data subscribers need first. It covers CodeDefinition nouns, including flexible and fixed dimensions, business partner, tax and journal book dimensions. It also publishes Accounting Chart, Chart of Accounts, CurrencyRateType, CurrencyExchangeRateMaster and the financial calendar.
Publish Financial Transactional Data (tfbia0210m000) handles Invoice, AccountsReceivable, SupplierInvoice, PayableTransaction, ReceivableTransaction and SourceSystemJournalEntry, with options for mode, company range, verb, logical IDs and logging. Publish Financial Documents (tfbia8210m000) and Publish General Ledger Balances (tfbia8211m000), which sends SourceSystemGLMovement, run separately from event-based publishing for performance reasons, manually or in job mode.
Programs scoped within wider Infor ION integration services should treat balance publishing as a monitored scheduled job.
Running the initial load safely
An initial load is a one-time publish, and publication to ION cannot be undone. Check the log files before and after every run. This configuration order avoids most rework:
- Select Prevent BOD Publishing in tcbod0100m000 and run tcbod0300m000 to record a baseline.
- Complete ISO codes for currencies, countries and languages.
- Configure BIA Parameters and the flexible, fixed and reporting dimension mappings.
- Confirm the tenant, accounting entity and location mapping for your release.
- Rerun Validate Publishing Data Setup, then clear Prevent BOD Publishing.
- Run the master data initial load and review the logs.
- Publish transactional data, then schedule financial documents and general ledger balances in job mode.
Publishing transactional BODs before master data is the wrong order, because subscribers then receive invoices referencing accounts they have never seen.
Real-Time Access With LN REST APIs and the ION API Gateway
LN REST APIs give external systems synchronous access through the ION API Gateway, governed by entitlement, activation and authorization. The steps below follow the Cloud administration guide for the multi-tenant environment; single-tenant and on-premises customers should confirm the equivalent steps for their Infor Operating Service (OS) release.
From entitlement to first successful call
Documentation sits in Infor OS Portal under Applications, OS, API Gateway, Available APIs, Infor LN, in the row named LN/lnapi. The guide to viewing LN REST API documentation shows each service with methods such as GET, POST and PATCH, plus parameters and responses. The LN REST API setup procedure then runs in this order:
- Review the available APIs.
- Request entitlement approval.
- Complete the post-approval configuration.
- Activate services by adding and activating companies.
- Test with Try It Out in the Swagger documentation.
- Register an authorized app in the API Gateway and download the service account credentials.
- Test with a client such as Postman.
- Optionally define API authorizations and identity switching.
Authorized apps can use the Password Credentials grant, with an Infor Federation Services (IFS) user or the LN service user svc_ln, or the Client Credentials grant. When Try It Out returns 404, the user is not entitled, the service is not activated, the tenant is in admin-only or maintenance mode, or the release is not supported. A 503 means the service is not activated.
Securing finance APIs with API roles and route data authorizations
LN controls access through API identities, API roles, route authorizations and route data authorizations, which also cover POST methods. Identity switching uses the X-Infor-LnIdentity header and requires both authorization and a whitelist.
Apply least privilege per consuming system. A treasury platform and an invoice capture tool should each have their own service identity and role, limited to the routes and companies they need. Shared identities hide which system did what and undermine the API security and performance practices that apply across Infor gateway integrations. Reserve identity switching for genuine named-user control requirements.
When to build a custom OData API
Build a custom Open Data Protocol (OData) API only when no delivered service exposes the data you need. Custom APIs are maintained in the OData REST APIs session (ttadv2570m700), under Tools, REST API Management, and configured with the REST API Modeler for LN.
Changes happen inside an activity with check-out, check-in and commit. Treat that as change control: link activities to a ticket, review before commit, and keep custom finance APIs read-only unless a posting design is approved. A custom API is the wrong choice where a standard service exists, because you then own its upgrade testing.
Inbound Finance Integration Patterns
Inbound finance integration should feed LN’s posting chain as reviewable entries, never as finalized ledger records written from outside. Typical sources are bank and payment data, third-party subledgers, accounts payable (AP) invoice capture and external journal sources such as payroll or expense platforms.
First confirm which inbound BODs and REST services your LN release and entitlement support, using the API Gateway documentation for LN/lnapi.
Four principles hold across every source. Give each inbound transaction an idempotency key from the source system and reject duplicates before posting. Check Period Status (tfgld0107m000) for the target date and route late items to a defined holding process. Post as non-finalized entries so finance reviews them before finalization. Validate intercompany relations (tfgld0515m000) for anything that crosses financial companies.
Bank and payment data arrives in volume, so it suits batch handling with strict duplicate detection. AP invoice capture sends fewer, richer documents that benefit from synchronous validation. External journal sources need the strongest controls, because no logistic event stands behind them.
Auto-finalizing inbound journals is usually wrong, because it removes the review that catches a misconfigured source.
Design Decisions That Shape the Integration
Five decisions shape most LN finance integrations, and each answer depends on volume, control requirements and company structure. Multi-company groups should settle their ledger model first, because global ledger architecture decisions determine where dimensions and consolidation live.
| Decision | Option A | Option B | Choose A when | Choose B when |
|---|---|---|---|---|
| Data delivery | Event BODs | Scheduled REST polling | Subscribers need every change and volume is high | A consumer needs a small, current dataset on demand |
| Posting granularity | Per-transaction posting | Batch posting | Volume is low and users need immediate confirmation | Volume is high and finance reviews by batch |
| Finalization | Non-finalized entries | Auto-finalized entries | The source is new, external or high risk | The source is mature, validated and low value per entry |
| Publishing scope | Financial company level | Group level | Companies have separate subscribers or controls | Consolidation and reporting run on one group model |
| Dimension mapping | Map in LN | Map in middleware | LN dimensions are the reporting standard | Several ERP systems feed one common reporting model |
Failure Patterns From LN Finance Integrations
The same five failure patterns appear repeatedly after LN finance go-lives, and each has a recognizable cause and a repeatable fix.
BODs rejected because ISO mappings are incomplete
Finance BODs fail in ION or arrive with empty currency and country values. The cause is incomplete ISO codes for currencies, countries or languages in LN master data. Complete the mappings, rerun Validate Publishing Data Setup (tcbod0300m000) and republish only the affected scope.
Integration transactions stuck after a mapping scheme change
A backlog builds in tfgld4484m000 after a chart or dimension change. The new mapping scheme version does not cover every integration document type in use. Complete and activate the version, then rerun Map Integration Transactions (tfgld4281m000) for the failed transactions.
Postings failing against closed periods or missing relations
Mapped transactions fail in Post Integration Transactions (tfgld4282m000), and the error log points to closed periods in tfgld0107m000 or missing intercompany or intergroup relations. Agree a close calendar with integration owners and add relation checks to the onboarding of every new financial company.
Duplicate journals from retries
A timeout makes the source system resend, and the same journal posts twice. The design has no idempotency key or duplicate check. Fix the design as well as the data: store the source reference and reject repeats before posting.
API calls returning 404 after entitlement
The service is entitled, but calls return 404 or 503. Usually the companies were never added and activated for that service. Activate them, then retest with Try It Out before involving the consuming system.
Security, Audit and Controls
Finance integrations need the same controls as manual journals, plus evidence that every external source is known and approved. Separate the people who build integrations from the people who approve postings. Developers should not belong to production integration user groups, and finance should own finalization.
Keep service identities clean: one identity per consuming system, credentials rotated on a schedule, and unused authorized apps removed. BOD logging and REST API tracing then serve as audit evidence of what was published or received, and by which identity.
Every external journal source should be traceable to its originating system through a source reference stored on the transaction. An auditor picking any journal should get its system, message and approver without a manual search.
How the Approach Changes by Company Size
The architecture stays constant across company sizes, but governance should match the team running it.
Global enterprises with many financial companies need group-level publishing standards, a central dimension model and formal ownership of intercompany relations. They usually run BODs for analytics and consolidation and keep REST APIs to tightly scoped operational uses.
Mid-market LN customers with a small IT team should favor delivered sessions and standard BODs over custom APIs. Job-mode publishing with simple monitoring is often enough.
Growth-stage companies in their first years on CloudSuite Industrial Enterprise should design for the multi-tenant cloud from the start. That means entitlement-driven REST access, no direct database dependencies, and integration choices aligned with their wider Infor CloudSuite services roadmap, so new financial companies can be added without redesign.
Measuring Integration Health
Integration health is best measured with a few indicators drawn from LN sessions and Infor OS monitoring.
Track open mapping and posting errors in Print Integration Transactions Error Log (tfgld4484m000) and the age of non-finalized batches awaiting finalization. Monitor BOD error counts in ION monitoring, split by noun. Compare reconciliation data in tfgld495 with ledger balances to catch subledger differences early. For REST traffic, report the API failure rate by status code, separating entitlement and authorization errors from availability errors.
If these indicators already trend the wrong way, or the next close depends on a new interface, talk to our LN finance team before the integration reaches production.
Frequently Asked Questions
Does Infor LN have a REST API for finance data?
Yes. LN exposes REST APIs through the ION API Gateway, documented in Infor OS Portal under the LN/lnapi row. The finance services available depend on your LN release and entitlement.
What is the difference between BODs and REST APIs in Infor LN?
BODs are messages LN publishes to ION, suited to outbound, event-driven or scheduled volume. REST APIs are synchronous calls an external system makes through the API Gateway. Most landscapes use both.
Can external systems post journal entries directly into the LN general ledger?
They should not bypass LN’s posting chain. External journals should arrive through a supported inbound BOD or REST service, post as non-finalized entries and be finalized after review. Confirm the supported inbound options for your release in the API Gateway documentation.
Which LN sessions publish financial BODs to Infor ION?
Publish Financial Master Data (tfbia0200m000) and Publish Financial Transactional Data (tfbia0210m000) handle master and transactional data. Publish Financial Documents (tfbia8210m000) and Publish General Ledger Balances (tfbia8211m000) run separately, manually or in job mode.
How do you secure Infor LN APIs for finance integrations?
Give each consuming system its own service identity, with API roles, route authorizations and route data authorizations limited to what it needs. Restrict identity switching through the X-Infor-LnIdentity header to approved, whitelisted cases.
How long does an Infor LN finance integration project typically take?
Duration depends on the number of financial companies, the state of ISO and dimension master data, and how many inbound sources need posting controls. Entitlement approval, subscriber readiness and audit sign-off also shape the timeline, so a scoped assessment beats a generic estimate.