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 Year-End Close Checklist

As the year draws to a close, the hustle and bustle of year-end activities can sometimes lead to overlooking critical tasks within your Infor ERP system. Ensuring a proper year-end close is essential for setting the stage for success in the coming year. Here is a comprehensive checklist to guide you through the process:

Year-End Close Process Objectives:

  • Remove discontinued items.
  • Remove sold purchase receipts.
  • Remove lot attributes for sold lots.
  • Update standard cost based on the current cost field (only for environments without Manufacturing).

Preparing for Year-End Close:

  • Conduct a full physical inventory and update quantities before the actual year-end or establish a robust cycle-counting program.
  • Close out all purchase contracts and PO’s, ensuring no receipts are allowed against any 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.
  • Decide on new standard costs 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 financial periods for 2024 before the new year begins.
  • Open the January period in 2024.
  • Finalize any outstanding transactions from the current year (2023).
  • Copy the CEA Book for the new year, ensuring all Journal Sources are set up. Copying ensures that every needed record is in place.

General LX & BPCS Items:

  • Run ACP920 (1099 Report) before ACP910 (Year End Close), as the Close Program clears the 1099 Payments History.
  • Address any old sales invoices.
  • Rectify outstanding financial integration errors.
  • Set up new integration mapping for 2024 as needed.
  • Test the mapping in a test environment before the new year.
  • Review and update jobs as needed to ensure they will process in 2024.
  • Determine, for cash-flow purposes, which purchase invoices won't be paid until 2024.

For additional insights and details about each program's functionalities and the files they update during the LX and BPCS Period End and Fiscal Year-End Processing, please refer to the attached document: LX & BPCS Period End & Fiscal Year End Processing Document

If you require assistance, please don't hesitate to contact us. We are here to guide you through the process to ensure everything is completed correctly and comprehensively. Reach us at 1.800.762.2077 or solutions@crossroadsrmc.com.

Previous Article Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure
Next Article Infor LX / BPCS & Infor LN / Baan Tip: Time for the Notorious TRIO: Manual -  Physical -  Inventory
Print
10025 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

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

  • Control Date Lead Times – LX provides five separate Control Date Lead Time fields so you can specify additional lead time values for Shop Orders, Purchase Orders and Planned and Firm Planned orders. Each Control Lead Time Date represents additional time (days) required at each step in the process that needs more time (Quarantine, Stabilize), that is to say, when a component is due, and when it can be used. (working with an aerospace  precision bearing manufacturer, I had to account for the QA requirement that no measurements could be taken until the parts had been “soaked” (stored) in an atmospheric controlled environment (72 degrees, and controlled humidity) for 24 hours. This requirement added one full day of lead time between each machining operation) The MPS/MRP Generation program, as well as programs that Shop Order Material Allocation records use the five control date lead times to adjust component required dates to function in the same way as the BOM Offset Lead Time.
     
  • All programs that create MRP Planned Orders, MRP Firm Planned Orders, Shop Orders, and Purchase Orders call the Control Date Calculation program (MRP515B) to establish all five control dates. A Control Lead Time Date is used to adjust the component Required Dates data in the Material Requirements file (KMR), based on planned orders for a parent, and the FMA Required Dates data, based on shop order release dates for a parent.
First5859606163656667Last

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