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

What are the biggest struggles manufacturers face with regard to tax compliance?

  • Tracking thousands of SKU numbers that cross taxability rules or vary in taxability based on state
  • Getting the rates right and filing the reports correctly
  • Surviving an audit (which in this business is inevitable)
  • Keeping track of all the smaller jurisdictions and their special districts
  • Ensuring a seamless process that is audit-able
  • Figuring out what is taxable and what isn’t
  • Tracking use tax

As with other manufacturing processes, having a repeatable, consistent process with sales and use tax compliance means automation. Automating sales and use tax compliance with a solution that ensures that consistent, accurate process means a solution that delivers:

  • Accurate sales and use tax calculations for collections that take into account product taxability, location, rules and regulations.
  • An exemption certificate management process that enables digital collection and storage of exemption certificates as well as transaction association and timely renewals.
  • Flow-through returns processing that provides a liability worksheet for review for each return filed, empowering your company to have oversight and visibility to all your sales and use tax liabilities and remittance.
  • Best practices in managing your sales and use tax processes and easy access to all data in case of an audit.
  • Up-to-date sales and use tax rates and information.

Using an automated solution for sales and use tax compliance helps manufacturers and distributors stay up-to-date with the latest changes in sales and use tax information. Consistency, repeatability, and accuracy help to reduce audit risk and potential negative assessments. Critical features to look for in an automated solution:

  • Easy integration with your back-end financial applications and/or inventory management software.
  • Ecommerce integration capability.
  • Geospatial technology to ensure “to the rooftop” level accuracy for locations.
  • Accuracy and speed.
  • Accessibility of information—anywhere, anytime.

Contact Crossroads RMC to learn how the Avalara - AvaTax integration can benefit your company. 800.762.2077​

Previous Article Infor LX & BPCS: What are your production orders telling you?
Next Article What is manual tax compliance costing your business?
Print
23770 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

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

First6465666769717273Last

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:

12345678910Last

Theme picker

Categories