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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Financial Year End – Have you done all you need to do?

Came across an article online from Lauber CFO’s, and thought I would share. Here is a checklist for things to consider in order to finish out the year and help you plan for 2016:

  • Is your accounting records up to date so that you can make a projection of how the current year will turn out?
  • Are all account reconciliations currently up to date to facilitate the closing of the books after year-end?
  • Are there accounts receivable that should be reserved for or written off prior to the end of the year?
  • If your business carries inventory, do you need to plan a physical count as of the end of the year?
  • Has depreciation on your fixed assets been recorded during the year? Have you considered depreciation on current year additions?
  • Have all new asset purchases and bank loans been recorded on your books?
  • Are there any liabilities, for example, pending legal actions or warranty issues, which will need to be recorded prior to the year-end? 
  • Do you have a plan in place to properly “cut-off” revenue at year-end to properly match revenue and expense?
  • Will there be bonuses, profit sharing contributions, or discretionary retirement plan contributions paid prior to the end of the year? How will these payments affect cash flow?
  • Will you be in compliance with your bank covenants at year-end?
  • Do you need to make arrangements to receive statements as of the end of the year for the cash value of life insurance, loan balances, etc.?
Previous Article Increase Inbound Supply Visibility
Next Article BPCS/LX Tip of the Week: Financial Year End – Have you done all you need to do?
Print
43351 Rate this article:
No rating
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

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

123457910Last

Theme picker

Categories