Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Subscribe to newsletter

George Moroses
/ Categories: ERP Utilization Review & Process Improvement Consulting, Support, Training & Workshops, Consulting

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
22004 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

Read more

This feature provides a parameter that allows the user to enter expiration dates on the Inventory Transaction Posting screen, INV500, and Purchase Order Receipts screen, PUR5505, when they have received a lot controlled item that is not QMS controlled. This new field allows an expiration date to be entered and not overridden. A system parameter was added to Advanced Process Industries Parameters, API820D. When the parameter is set to Yes, a new lot expiration date is available in the Inventory Transaction Posting, INV500D2, and Purchase Order Receipts, PUR550D2, screens.

Read more
FirstLast

Tips: LN | Baan

Categories