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

Infor LX & BPCS Period End & Fiscal Year End Processing Checklist

Infor LX & BPCS Year-End Close Checklist

Year-end is always a busy time and it is easy to forget all the things that must be done in your Infor ERP system to close out the year properly and set you up for success the following year. Here are some things you should have on your checklist:

The year-end close process provides an opportunity to:

_____ Remove discontinued items.

_____ Remove sold purchase receipts.

_____ Remove lot attributes for sold lots.

_____ Update standard cost based on current cost field (only for environments without Manufacturing).


Preparing for Year-End Close:

_____ Conduct full physical inventory and update quantities before actual year-end or establish a strong cycle-counting program.

_____ Make sure to close out all purchase contracts and PO’s. Make sure no receipts are allowed against any of the contract line items.

_____ Prepare users for a year-end push to complete all year-to-date inventory adjustments, receipts, and invoicing.

_____ Determine how to handle new year transactions without posting.

_____ Determine what new standard costs should be entered for the upcoming year. (Manufacturing)

_____ Discuss cutoff dates for removing Archived BOMS and Closed/Canceled Mfg Orders. (Manufacturing)

_____ Run PRF900 to update performance measurements and purge closed shop orders.

Finance Specific Items:

_____ Set up the financial periods for 2022. Do this before the new year begins.

_____ Open period January in 2022. 

_____ Finalize any outstanding transactions from the current year - 2021.

_____ COPY the CEA Book for the new year. Creating the Book requires the user to set up all the Journal Sources, while Copying ensures that every needed record is in place.

General LX & BPCS Items:

_____ Run ACP920 (1099 Report) before running ACP910 (Year End Close), as the Close Program clears the 1099 Payments History.

_____ Issue any old sales invoices.

_____ Fix any outstanding financial integration errors.

_____ Set up new integration mapping for 2022 as needed.

_____ Test the mapping in a test environment prior to the new year.

_____ Review & update jobs as needed to ensure they will process in 2022.

_____ Determine for cash-flow purposes, what purchase invoices won’t be paid until 2022.


Want even more tips for month-end and year-end processing? See the attached document that covers LX and BPCS Period End and Fiscal Year-End Processing and provides details regarding what each program does and what files are updated.
LX & BPCS Period End & Fiscal Year End Processing Document>

Need help? Contact us and we’ll be happy to walk you through what needs to be done to ensure that everything is done correctly and completely. 1.800.762.2077 or solutions@crossroadsrmc.com
 

Previous Article Infor LN & Baan Tip: Using the “Use Up” Functionality in Infor LN
Next Article Infor LN & Baan Period End & Fiscal Year End Processing Checklist
Print
14783 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