Infor LN3 min readNetray Engineering TeamPublished February 14, 2026

Infor LN Accounts Receivable Setup and Credit Management

Short answer

The Accounts Receivable module in Infor LN manages the order-to-cash cycle from sales invoice generation through cash receipt allocation. Configured through sessions like tfacr0110s (Sales Invoices) and tfacr0520m (Receipts), the AR module directly impacts cash flow velocity and DSO metrics. Proper credit management, dunning automation, and payment matching configuration ensure maximum collection efficiency.

AR Invoice Management and Revenue Recognition

Infor LN generates AR invoices from sales orders, service orders, and project milestones. Session tfacr0110s manages invoice creation, while the composing and printing framework (tfacr0401m) controls invoice document formatting. Revenue recognition rules can be configured to comply with ASC 606 and IFRS 15 standards, supporting deferred revenue schedules and milestone-based recognition.

Configure invoice composing and printing in tfacr0401m with templates supporting multi-language and multi-currency output
Set up revenue recognition schedules for subscription, milestone, and percentage-of-completion billing models
Define automatic invoice numbering sequences per company and financial group in tfacr0100s
Configure credit note and debit note processing workflows for returns, disputes, and price adjustments
Enable electronic invoicing (e-invoicing) output formats for compliance with regional tax authority requirements

Credit Management and Risk Control

Infor LN credit management operates through session tfacr0130m, controlling credit limits, risk scoring, and order hold policies per business partner. The credit check engine evaluates open orders, outstanding invoices, and payment history to determine whether new sales orders should proceed or be held for review.

Define credit limit policies in tfacr0130m with separate limits per currency and per business partner group
Configure credit check triggers at order entry, order release, and shipment confirmation stages
Set up automatic credit hold and release workflows based on payment receipt and aging thresholds
Establish credit scoring models using payment history, order frequency, and external credit bureau data

Dunning Procedures and Cash Collection

Automated dunning in Infor LN uses session tfacr0145m to define dunning levels, escalation timelines, and communication templates. Each dunning level specifies the days overdue threshold, letter template, and escalation action. Proper dunning configuration reduces DSO by 10-15 days on average and ensures consistent collection practices across all customer segments.

Configure multi-level dunning procedures in tfacr0145m with escalating severity from reminder to legal action
Set up automatic payment matching in tfacr0520m using reference number, amount, and customer matching algorithms
Define write-off policies and approval thresholds for uncollectable balances with proper GL impact tracking

Try it here, free

Infor LN Sales Order Tables Reference (tdsls400, tdsls401 and related)

Open full tool

Searchable field-level map of the LN 10.x order-to-cash tables: quotations, contracts, sales orders, actual deliveries, history, invoices and business partner roles.

Download:

Table code	Description	Physical name pattern	Key fields	Key fields to know	Join to	Main session	Notes
tdsls100	Sales quotations (header)	ttdsls100<company>	qono	qono quotation, ofbp sold-to BP, qdat quotation date, expd expiry date, qsta status, sotp order type, ccur order currency, opty opportunity	tdsls100.ofbp = tccom110.ofbp	tdsls1500m000 Sales Quotations Overview	Header of a quotation; lines are in tdsls101.
tdsls101	Sales quotation lines	ttdsls101<company>	qono, pono	item, qoor ordered quantity, cuqs sales unit, pric price, cups sales price unit, disc line discount, lsta line status, ddta planned delivery date, cwar warehouse	tdsls101.qono = tdsls100.qono; tdsls101.item = tcibd001.item	tdsls1501m000 Sales Quotation Lines	Line status lsta is separate from the header status qsta.
tdsls300	Sales contracts (header)	ttdsls300<company>	cono	cono contract, ofbp sold-to BP, icyp contract type, icap contract status, sdat effective date, edat expiry date, ccur currency, cpay payment terms, sotp order type	tdsls300.ofbp = tccom110.ofbp	tdsls3500m000 Sales Contracts	Lines with agreed quantities and prices are in tdsls301.
tdsls301	Sales contract lines	ttdsls301<company>	cono, pono	item, qoor agreed quantity, pric price, disc discount %, icap line status, qicl called quantity, qiiv invoiced quantity, sdat effective date, edat expiry date	tdsls301.cono = tdsls300.cono; tdsls401.cono and tdsls401.cpon point back to it	tdsls3501m000 Sales Contract Lines	Called and invoiced quantities show how much of the contract is used.
tdsls400	Sales orders (header)	ttdsls400<company>	orno	orno order, ofbp sold-to BP, stbp ship-to BP, itbp invoice-to BP, pfbp pay-by BP, sotp order type, odat order date, hdst header status, ccur currency, corn customer order, cofc sales office	tdsls400.ofbp = tccom110.ofbp; tdsls400.sotp = tdsls094.sotp	tdsls4100m000 Sales Orders	In SQL the columns carry a prefix: t_orno on SQL Server, t$orno on Oracle.
tdsls401	Sales order lines	ttdsls401<company>	orno, pono, sqnb	item, qoor ordered quantity, cuqs sales unit, pric price, oamt amount, ddta planned delivery date, qidl delivered quantity, invd invoice date, cwar warehouse, clyn canceled	tdsls401.orno = tdsls400.orno; tdsls401.item = tcibd001.item	tdsls4101m000 Sales Order Lines	sqnb 0 is the order line; planned delivery lines (tdsls4101m100) use higher sequence numbers.
tdsls406	Sales order actual delivery lines	ttdsls406<company>	orno, pono, sqnb, dsqn	dsqn actual delivery sequence, qidl delivered quantity, dldt actual delivery date, shpm shipment, shln shipment line, deln delivery note, invn invoice number, invd invoice date, qnvc invoice quantity, stat status	tdsls406.orno, pono, sqnb = tdsls401.orno, pono, sqnb; tdsls406.shpm = whinh430.shpm	tdsls4106m000 Sales Order Actual Delivery Lines	One row per confirmed delivery, so partial shipments create several rows per line.
tdsls450	Sales order history (header)	ttdsls450<company>	orno, trdt	trdt transaction date, ddtc customer requested delivery date, pcod delivery pattern	tdsls450.orno = tdsls400.orno	tdsls4550m000 Sales Order History	Written only when Log Order History (tdsls400.hiss) is set; confirm the full index in your data dictionary.
tdsls451	Sales order line history	ttdsls451<company>	orno, pono, trdt	trdt transaction date, ckor record type, stcd processed in statistics	tdsls451.orno, pono = tdsls401.orno, pono	tdsls4551m000 Sales Order Line History	Used for change audits and sales statistics after lines are archived or processed.
tdsls094	Sales order types	ttdsls094<company>	sotp	sotp order type, dsca description	tdsls400.sotp = tdsls094.sotp	Sales Order Types session in the tdsls module	The order type controls which activities a line passes through (see tdsls4534s000).
tdsls4534s000	Sales order line status (session, not a table)	n/a	orno, pono, sqnb	Shows the activities linked to a line, their status and whether each runs automatically	Reads tdsls400, tdsls401, tdsls406	tdsls4534s000 Sales Order Line Status	The first activity with status Free is the next step to run.
cisli305	Invoices (sales invoice header)	tcisli305<company>	sfcp, tran, idoc	stat invoice status, idat invoice date, itbp invoice-to BP, ofbp sold-to BP, cslo sales order, cshp shipment, dudt due date, amti amount	cisli305.sfcp, tran, idoc = cisli310.sfcp, tran, idoc	cisli3105m000 Invoices	The invoice number is financial company + transaction type + document number.
cisli310	Invoice lines	tcisli310<company>	sfcp, tran, idoc, line	orno order number, pono order line, item, dqua delivered quantity, shpm shipment, amti net line amount, cvat tax code, ofbp sold-to BP	cisli310.orno = tdsls400.orno and cisli310.pono = tdsls401.pono when the source is a sales order	cisli3110m000 Invoice Lines	srtp (source type) tells you which document the line came from.
tccom100	Business partners	ttccom100<company>	bpid	bpid business partner, nama name, prst status, cadr address, clan language, prbp parent BP, ccur currency	tccom100.bpid = tccom110.ofbp	tccom4500m000 Business Partners	One BP can hold several roles; each role has its own table.
tccom110	Sold-to business partners	ttccom110<company>	ofbp	ofbp sold-to BP, bpst status, cadr address, crep internal sales rep, cofc sales office, creg area, chan channel	tdsls400.ofbp = tccom110.ofbp	tccom4510m000 Sold-to Business Partners	Default order data for the customer lives here, not in tccom100.
tccom111	Ship-to business partners	ttccom111<company>	stbp	stbp ship-to BP, cadr address, bpst status, cwar warehouse, cfrw carrier/LSP	tdsls400.stbp = tccom111.stbp	tccom4511m000 Ship-to Business Partners	Ship-to address can be overridden per order (tdsls400.stad) and per line (tdsls401.stad).
tccom112	Invoice-to business partners	ttccom112<company>	itbp	itbp invoice-to BP, itst status, ccur currency, cpay payment terms, crlr credit limit, cfcg financial customer group	tdsls400.itbp = tccom112.itbp; cisli305.itbp = tccom112.itbp	tccom4512m000 Invoice-to Business Partners	Credit limit and payment terms used at invoicing come from here.
tccom114	Pay-by business partners	ttccom114<company>	pfbp	pfbp pay-by BP, bpst status, ccur currency, mrem reminder method	tdsls400.pfbp = tccom114.pfbp	tccom4114s000 Pay-by Business Partner	Drives receivables collection, not the order itself.
tccom130	Addresses	ttccom130<company>	cadr	cadr address code, nama name, namc street, ccit city, pstc postal code, ccty country, cste state/province	tdsls400.stad = tccom130.cadr; tccom110.cadr = tccom130.cadr	tccom4530m000 Addresses	Order-level address fields (ofad, stad, itad, pfad) all point here.
tcibd001	Items - general	ttcibd001<company>	item	item, dsca description, kitm item type, citg item group, cuni inventory unit	tdsls401.item = tcibd001.item	tcibd0501m000 Items	Sales-specific item data is in tdisa001; see the item master reference.

Physical tables are t + table code + company number, e.g. ttdsls400100 for company 100. Column names in SQL carry the t_ prefix on SQL Server and t$ on Oracle (t_orno, t$orno). Field names were checked against the LN 10.x online help field definitions for each session; customizations and Feature Packs can add columns, so check the data dictionary in your own VRC.

Need a tested order-to-cash query for your LN release?

Send us your LN version, database and the report you need, and we will check the joins and fields against your setup.

Optional. The tool and every export work without this. No spam.

Optimize your AR collection cycle in Infor LN—request a credit management review from Netray.

Talk to an engineer Try the free Infor LN Sales Order Tables Reference (tdsls400, tdsls401 and related)

ArchRay builder

Design the on-prem AI stack for Infor LN and Baan: model, GPUs, RAG pipeline, guardrails

See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.

Open the builder

New to Infor LN and Baan? Start with the Infor LN and Baan guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Infor SyteLine vs Infor LN: Choosing the Right Infor Manufacturing ERPInfor SyteLine vs Infor LN: which Infor ERP fits your plants, compared on scale, complexity, project manufacturing and total cost of ownership.

Software

TermsIntegration Transaction Order-to-Cash (O2C)Infor LN Financial Company Multisite (Infor LN)Enterprise Planning

Back to all resources