Infor LN Sales Invoice Not Transferred to Financials
Infor LN sales invoice not transferred to financials integration transactions stuck
Also searched as
- Infor LN invoice posted but not in general ledger
- LN integration transactions error invoicing to finance
- Infor LN invoice not appearing in accounts receivable
- LN integration mapping scheme missing invoice posting
Short answer
When a sales invoice exists in LN Invoicing but not in accounts receivable or the general ledger, the posting stopped in integration transactions. The usual causes are a missing integration mapping scheme, a closed or blocked financial period, an invalid ledger account or dimension, or an unprocessed integration transaction that needs to be reprocessed after the data is corrected.
Applies to: Infor LN 10.x with Invoicing and Financials in the same or separate companies; the integration concept is also used in earlier Baan releases
How to trace and fix the missing posting
- 1Confirm the invoice status in the invoicing session: printed, posted or transferred. Note the invoice number, invoicing company and date.
- 2Open the integration transaction overview for the financial company and filter on the source module and the invoice reference.
- 3Check the status of the transaction: pending, error, processed. Open the error text for any transaction in error.
- 4Verify the integration mapping scheme for sales invoices exists for the relevant legal entity and transaction type, and has a ledger account for each line type (revenue, tax, receivable).
- 5Confirm the financial period for the posting date is open for the module, and that the fiscal year exists.
- 6Check the ledger accounts and dimensions used are active and valid for the company, and that mandatory dimensions are filled.
- 7Correct the mapping or master data, then reprocess the integration transaction instead of re-invoicing.
- 8Verify the document appears in accounts receivable and the ledger, and reconcile the invoice total with the posting total.
Where the posting can stop
Invoicing in LN produces the commercial document. The accounting entry is produced through integration: the invoicing module writes integration transactions that the financial side picks up and turns into accounts receivable and general ledger entries using a mapping scheme. If an invoice exists and the ledger entry does not, look at the integration transactions, not at the invoice itself.
A pending transaction that has not been processed often means the processing session or job has not run. An error transaction has run and failed. The two need different responses: start the job in the first case, fix the cause in the second.
Mapping schemes and account determination
Account determination is driven by the integration mapping scheme. For each transaction type and line type, it decides which ledger account is debited and credited, based on criteria such as item group, customer group, tax code or product line. If no mapping row matches the invoice, there is no account to post to, and the transaction errors.
A new item group, a new tax code or a new customer group is a typical trigger: an invoice for the first time uses a combination nobody mapped. Add the mapping, or add a catch-all row for the combination if your policy permits one, and reprocess.
Typical mapping inputs Transaction type: sales invoice Line type: goods / freight / tax Criteria: item group, customer group, tax code, product line Result: ledger account + dimensions
Periods, blocked accounts and dimensions
Even with a correct mapping the posting fails if the period is closed. Month-end is when this appears, because invoices dated in a closed period cannot post. The right fix is a decision, not a click: either the finance team reopens the period for the module, or the invoice date is corrected to an open one if rules allow.
Check ledger accounts for a blocked flag and for dimension requirements. If a cost centre or project dimension is mandatory for a revenue account and the invoice line carries none, the posting stops. Fill the dimension on the source data or relax the rule through the finance owner.
Reprocessing, reconciliation and prevention
Once the cause is fixed, reprocess the transaction. Do not issue a credit note and a new invoice just to get a posting; that creates two legal documents and a messy audit trail. After processing, reconcile the invoiced total for the period with the receivables control account.
To prevent repeats, add a daily check for integration transactions in error and review it before month-end close. Reconciling invoicing to the ledger weekly will find a stuck transaction in days instead of at quarter end.
Common pitfalls
- !Re-invoicing instead of reprocessing the failed integration transaction.
- !Treating pending transactions as errors when the processing job has simply not run.
- !Opening a closed period without finance approval to push one invoice through.
- !Adding a mapping row that is too broad and posting future invoices to the wrong account.
- !Ignoring mandatory dimensions on revenue accounts.
- !Discovering stuck transactions only at month-end.
How an ERP-grounded AI assistant handles this
ERPray can list integration transactions in error with their first error text, group them by missing mapping or closed period, and compare invoiced totals with receivables for the period. It shows the query used and follows LN roles, and it does not post or reprocess. A finance user does that with approval.
Frequently asked questions
Why is my LN invoice printed but not in accounts receivable?
The accounting posting runs through integration transactions. Check whether the transaction is pending, in error, or processed. Errors usually point to a missing mapping scheme row, a closed period, or an invalid ledger account or dimension.
Should I cancel and re-issue the invoice?
No. Fix the cause and reprocess the integration transaction. Re-issuing creates a second legal document and a credit note, which complicates the audit trail and customer statements.
What does a missing mapping scheme mean?
LN cannot determine which ledger accounts to post to for that transaction type and criteria combination. Add the missing mapping row for the item group, customer group or tax code involved, then reprocess.
Why does this happen near month-end?
Periods are closed and cut-offs applied then, so invoices dated in a closed period fail to post. Agree with finance whether to reopen the period or correct the date, and review errors daily during close.
Related
How to process a sales order to invoice in Infor LN
In Infor LN a sales order moves from order entry to cash through four linked steps: create and approve the Sales Orders session, release the order lines to Warehousing so a warehouse order is generated, confirm the outbound shipment, and then run the invoicing session that composes and posts the sales invoice to Financials. Each step hands off through an integration document, so a stuck invoice almost always traces back to a missing or unconfirmed step earlier in the chain.
How-toHow to close a financial period in Infor LN
Closing a period in Infor LN is not a single click; it requires clearing every module's outstanding integration transactions into Financials first, reconciling each subledger (AR, AP, inventory, WIP) to the general ledger, and only then closing the period through Periods and Fiscal Years, which blocks further posting to it. Skipping the reconciliation step and closing early is what causes stuck or orphaned transactions that have to be reopened and reworked later.
Error fixInfor LN: finalize run fails or gets stuck
Finalize sessions such as Cost Price Calculation, Sales Invoicing, and Period-End Statistics run as a broadly locked, largely exclusive batch step, so they most often fail because another user has the module open, a prior finalize run did not close cleanly, or a specific record has bad master data. Read the finalize log for the exact record or reason code, not just the failure message.
How-toHow to calculate item cost prices in Infor LN
Infor LN calculates an item's cost price by rolling up material, labor, machine, subcontract and overhead costs defined against cost components, using the item's bill of material and routing as the calculation base for manufactured items and purchase price for bought items. The calculation can run in simulation mode to preview the result or in update mode to actually change the item's standard cost, which then drives inventory valuation and variance reporting going forward.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
AI for ERPInfor LN AI for Engineer-to-Order Industrial Machinery Builders
Private AI on Infor LN for engineer-to-order machinery builders: project cost, engineering BOM changes, long-lead purchasing and CE file support, on-prem.
Stuck on Infor LN?
Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.