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

Infor LX & BPCS Finance Tip: AR Aging

An ACR system parameter allows you to specify whether to measure invoice age from the date on which you create the invoice, invoice date, or the date on which the invoice is due. You can set up a separate terms code for each customer on the system to set the basic terms of payment for that customer. For example, this term could specify the number of days an invoice can be due before it is considered past due and the number of days that a discount is available. The system uses the terms code data to calculate invoice due dates and uses system parameter information to age invoices. Whichever date you specify Accounts Receivable | Run Instructions | 27 ACR Overview to measure invoice age from, the age of an invoice is defined as the number of days between that date and the current processing date.

You also use the Accounts Receivable System Parameters program, ACR820D, to establish five generic aging buckets for your receivables. To determine the time length for each of these buckets, specify the number of aging days for each bucket. The number of aging days aging is the difference between the invoice aging date and the current processing date. You can set the time periods and assign names to each bucket according to your needs.

Each time you generate any of the receivable Trial Balance reports, the system recalculates the age of every invoice. If you use calendar months as financial periods, change the bucket definitions each month to reflect the appropriate 1-month bucket, 2-month bucket, and so on. If you use an aging system based on days, like the one described in the preceding paragraph, you do not need to change the bucket definitions.

Note that you can process future dated invoices if you use a negative age bucket and specify negative aging days.

Previous Article Infor LN & Baan Finance Tip: What Can You Do in the Financial Statements Module?
Next Article Infor LX & BPCS Materials Tip of the Week: Drop Shipments
Print
19117 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

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

First6465666769717273Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories