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 and external AP invoice automation solutions, functionality has been added to LN 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 and consumed in the AP invoice automation solution. The external solution sends purchase invoice, matching, and approval information to LN through a BDE/web service. In LN, 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. 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. 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.