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
9942 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

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

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:

1345678910Last

Theme picker

Categories