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 LN & Baan Period End & Fiscal Year End Processing Checklist

Year-end is always a busy time and it is easy to forget things that must be done in your ERP system to close out the year properly and also set you up for a good start to the following year. Here are some things that you should make sure to add to your to-do 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 (for environments without Manufacturing only).

Prepare for Year-End Close

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

_____ Check for any applicable sales and purchase invoices/returns and post.

_____ 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)

Finance Specific Items:

_____ Set up the financial periods for 2022 (fiscal, reporting, and tax, as applicable).

_____ Open period January in 2022.

_____ Finalize any outstanding transactions from the current year (2021).

_____ Soft-close any open periods in 2021.

General Baan/LN Tips:

_____ 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.

_____ Make sure that calendars are set up for the new year with holidays properly indicated.

_____ Check jobs to make sure any that are hard-coded with dates will point at the new year.


Want even more tips for year-end processing? See the following documents in the Infor Knowledge Base:

 KB 

 Content 

 1879191  

 Document including step by step procedure, possible error/warning messages, and more (Infor LN) 

 1147023 

 Step by step procedure description (Infor LN)

 1116239 

 Step by step procedure description (Infor LN)

 1117334

 Step by step procedure description (Infor LN; Portuguese)

 1171300 

 Step by step procedure description (Baan IV) 

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 LX & BPCS Period End & Fiscal Year End Processing Checklist
Next Article Infor LN & Baan | Infor LX & BPCS Tip: Time for the dreaded three words?
Print
22660 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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