Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: Automated Approach to Your Cash Application Process with ARP

Advanced Remittance Processing, ARP, provides an automated approach to your cash application process. ARP works together with Accounts Receivable to save valuable time and resources by automatically applying incoming payments to open receivables during daily batch processing. You can easily and efficiently resolve unapplied remittances online.

Advanced Remittance Processing (ARP) is an automatic cash application process that allows you to perform the following functions:

  • Receive lockbox deposits electronically from your banks on the day the payments are deposited
  • Automatically apply the majority of the day's receipts to open items in accounts receivable in one batch process
  • Perform online disposition of exceptions the system encounters during the automatic cash application process
  • Generate a complete set of daily reports and maintain historical deposit and payment information online to allow you to audit all cash applications

The ARP automatic cash application process can be summarized in a series of operations that highlight the labor savings provided. ARP processing requires some setup to ensure that the process operates as efficiently as possible.

ARP allows you to perform the following operations:

  • Receive/Edit Bank Transmission of Lockbox Deposits
  • Identify/Assign Customer Numbers
  • Select Customer Open Items
  • Summarize Open Items Extracted
  • Check Application Against Open Items
  • Produce Reports Recapping Check Application Process
  • Create Disposition and On-Account Payment Records
  • Report Check Differences
  • Create Applied Checks Interface Records to Accounts Receivable
  • Flag Disposition Records as Temporarily Paid on Ledger File
  • Update A/R Ledger and Audit Files
  • Open Item Extraction

Previous Article Revamp Your Productivity: Discover Crossroads RMC's Ultimate Solution
Next Article Infor LN & Baan Tip: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)
Print
8465 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

In previous releases of LN, the Assembly Control Bill of Material (BOM) offered limited flexibility. For each end item configuration, users were required to create unique Engineering Modules, which are used to determine the assembly parts that are consumed in a specific Line Station during a specific operation.

If LN is integrated with Design Studio, previously called Infor CPQ, BOM structures can be maintained in Design Studio for Assembly Control. These structures can include non-configurable parts that are directly linked to configurable items. When communicating these structures to LN using the Assembly Control, Product Variant Structure (tiapl3510m000) session, the structures were rejected because non-configurable parts were not supported by the session logic.

In this release, BOM structures that include non-configurable parts can now be accepted in LN. Consequently, if LN is integrated with Design Studio, it is no longer required to use the Engineering Module. Using the Engineering Module has become optional.

First4950515254565758Last

Theme picker

Categories