Integration updates

Accounts Payable Invoice Automation solutions

Several external solutions are available for Accounts Payable Invoice Automation. Typically, these solutions are used as an ERP agnostic tool for purchase invoice processing. The ERP is used as the backbone for purchase orders, warehouse receipts, master data, open entry control, payments, and management reporting.

To enable the interface between LN CE and external AP invoice automation solutions, functionality has been added to LN CE to support sending and receiving required data to and from these external solutions.

BODs have been added and modified, so master data, project-, order-, and receipt-related data is sent from LN CE and consumed in the AP invoice automation solution. The external solution sends purchase invoice, matching, and approval information to LN CE through a BDE/web service. In LN CE, this information is stored in staging tables and a success or error message is returned. To view the data in the staging tables, these sessions have been added:

  • External Invoices (tfacp7100m000)
  • External Invoice (tfacp7600m000)
  • Receipts by External Invoice (tfacp7105m000)
  • Cost Lines by External Invoice (tfacp7110m000)
  • Project Costs by External Invoice Cost Lines (tfacp7111m000)
  • Subcontracting by External Invoice (tfacp7120m000)
  • Tax Lines by External Invoice (tfacp7121m000)

The Register and Process External Invoices (tfacp7200m000) session has been added to generate registration, matching, and approval transactions in LN CE. The generated purchase invoice document number is stored in the staging tables, along with the information whether the process succeeded or failed. This information can then be retrieved by the AP invoice automation solution through a BDE/web service.

If the process failed, these new sessions can be used:

  • Reverse Register and Process External Invoices (tfacp7200m100)
  • Error Log (tfacp2580m000)

After the invoice data is processed successfully, the purchase invoice information is available for open entry control, financial and management reports, and the payment process in LN CE. When the purchase invoice is paid, the PayableTracker BOD is used to provide the payment date and payment batch number to the AP invoice automation solution.

If the AP invoice automation package supports functionality to allocate costs to a project, then the interface ensures that the correct transactions are generated in Financials and Project. To support this, the Cost Amount in Home Currency (Debit) field has been added to these sessions:

  • Cost Entry (tpppc2605m000)
  • Material Costs (tpppc2111m000 / tpppc2511m000)
  • Labor Costs (tpppc2131m000 / tpppc2531m000)
  • Equipment Costs (tpppc2151m000 / tpppc2551m000)
  • Subcontracting Costs (tpppc2171m000 / tpppc2571m000)
  • Sundry Costs (tpppc2191m000 / tpppc2591m000)

The Cost Amount in Home Currency (Debit) field is now also available in many of the reports linked to the Print Costs (tpppc2411m000) session.

Optionally, you can log history for the staging tables, which can be viewed in these new sessions:

  • External Invoices History (tfacp7550m000)
  • External Invoice Receipts History (tfacp7555m000)
  • External Invoice Cost Lines History (tfacp7560m000)
  • External Invoice Cost Lines Project Costs (tfacp7561m000)
  • External Invoice Subcontracting (tfacp7570m000)
  • External Invoice Tax Lines History (tfacp7571m000)

For more information, see KB Article 2263967 on the Infor Support Portal.

Infor Automotive Exchange

Hardware and software versions for control units
If an automotive supplier produces electronic control units, the hardware version, the software version, and the part generation status of these items must be printed on shipping documents and published in the Advance Shipping Notice (ASN) if required by the OEM.

These fields are maintained in the LN Business Partner Item Revision and transferred to Automotive Exchange so that the correct container labels and shipping documents can be printed and the correct ASN can be published.

Transport order documents
Car manufacturers in the automotive industry can now receive EDI Transport Order documents from their suppliers. EDI Transport Order documents are sent from the supplier to the customer or carrier prior to shipment, to confirm that the agreed goods are ready for shipment.

Publication of an EDI Transport Order is triggered from a load in LN CE. As a precondition, handling units must be created for all shipments that belong to a specific load.

In Automotive Exchange, the corresponding BODs are received and the required EDI format is created, for example EDIFACT DESADV.

Infor Supplier Exchange

These new features are supported for Supplier Exchange:

Configurable items in procurement
Sometimes, it is required to order configurable items from a supplier, instead of ordering multiple different item numbers. This is the case if the purchased parts have multiple variations. For example, a driver's seat of a car has multiple options, such as the type of seat cover, the color of the seat, and the type of stitching. During the sales process of the car, all options are specified and must be communicated to the supplier of the driver's seat.
Now, purchase schedules can be used to communicate all features and options of a configurable item to suppliers. Both forecast data and pull call-offs can be communicated. Classic orders, classic EDI, and Supplier Exchange are supported as transmission methods.
Modification of RFQs with Pending Approval status
See the topic with the same title in Procurement.


In the accounting of leased fixed assets, multiple regulations apply. Public and private companies must record and summarize the financial transactions of a lease and report the results in the financial statements. Leased assets, both capital lease and operation lease, must be included in the balance sheet and profit and loss statements, and the financial transactions must be recorded.

To help organizations achieve compliance and eliminate accounting errors, LN CE can now be integrated with LeaseQuery.

LeaseQuery is a third party software application that includes software for these lease accounting standards:

  • US: GAAP-FASB (ASC 842)
  • World: IFRS (IFRS Chapter 16)
  • State and local government: GAAP-GASB (GASB87)

In the integration, LeaseQuery is the system of record for all leased assets. The master data is stored in this application as well as the subledger, the lease payments, ad hoc reporting, and disclosures. By clicking a button, all transactions are transferred to LN CE through an API.

In LN CE, the transactions are received, processed, and converted to a standard Journal Voucher transaction BOD, which is then consumed by the LN General Ledger. A finance batch and non-finalized transactions are created. After finalizing, all ledger accounts and dimensions are updated based on the mapping in LeaseQuery.

The integration requires this software:

  • Infor LN CE
  • License for Product ID 7056 (Infor LN Adapter), which is required for BOD enablement
  • LEASEQUERY (LeaseQuery©) with the latest updates
  • Infor ION 12 or later, including the connector

LN ION content pack v22

Infor LN ION Content pack v22 is now available and includes new workflows, BODs, and drill back views.

These document authorization workflows have been added:

  • Supplier Claim
  • Customer Claim

These new BODs are supported by LN CE and available in ION:

  • Sync.LnTaxCode
  • Sync.LnRemittanceAgreement

Drill back views have been updated.

For more information, see KB Article 1915676 on the Infor Support Portal.