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 LX & BPCS Tip of the Week: Year-End for Finance
George Moroses

Infor LX & BPCS Tip of the Week: Year-End for Finance

Year-End is always a busy time!

So busy that it's easy to forget things that must be done in your ERP system to close out the year properly and set you up for a good start to the following year. Here are some things 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.
  • Make sure to close out all purchase contracts and PO’s before year-end. Make sure no receipts are allowed against any of the contract line items after year-end.
  • 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.
  • Discuss cutoff dates for removing Archived BOMS and Closed/Canceled Mfg Orders
  • Run PRF900 to update performance measurements and purge closed shop orders


Finance Specific Items:

  • Set up the financial periods for 2021.
  • Open period January in 2021.
  • Finalize any outstanding transactions from the current year (2020).
  • Remember to 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 2021 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 2021.
  • Determine for cash-flow purposes, what purchase invoices won’t be paid until 2021.

Previous Article Infor LX & BPCS Tip of the Week: Year End
Next Article Infor LN & Baan Tip of the Week: Year End
Print
26008 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

245678910Last

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.

Currency differences can make the financial analysis and reconciliation more complex. These types of currency differences can occur:

  • Currency differences
    Currency result caused by fluctuations in the exchange rate, for example, if the rate differs between the invoice date and the payment date.

  • Exchange gain and loss
    Currency result caused by the use of different exchange rate types, for example, the Sales rate type and the Internal rate type, or if using the rate determiner you have changed the exchange rate for a transaction during the order handling procedure.

  • Translation gain and loss
    Currency result caused by the use of different currencies during the order handling procedure, for example, if the order currency or the payment currency differs from the invoice currency.

  • Destination gain and loss
    Currency result caused by different results when the transaction currency is converted to the various home currencies. Destination gain and loss can only occur in an independent currency system.

To support good reconciliation possibilities, currency differences and exchange gain and loss are posted to these accounts:

245678910Last

Theme picker

Categories