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

Tax Law Changes by the Numbers - Infor LN & Baan Integration to Avalara

Are you up to speed on all of the sale tax changes that could affect your business?

Tax Law Changes by the Numbers
A look at what's changed in 2018-2019

  • 21 states adopted economic nexus as of December 31, 2018, requiring out-of-state businesses with a certain amount of economic activity in the state to collect and remit sales tax
  • 33 states have enforced economic nexus as of June 30, 2019
  • 43 states will enforce economic nexus as of December 31, 2019
  • 7 states had marketplace facilitator sales tax laws as of December 31, 2018, requiring marketplaces to collect sales tax on behalf of their sellers
  • 15 states have marketplace facilitator sales tax laws as of June 30, 2019
  • 28 states will have marketplace facilitator sales tax laws as of January 1, 2020

The trend to tax remote sales is certain to continue, and there will be the normal slew of rate, regulation, and product taxability changes. 

Sales Tax is complicated! Crossroads RMC provides the integration from Infor LN & Baan to Avalara to make it easy. Click Here to Learn More

Previous Article Want An Automated Interface To FedEx Or UPS From Your Infor LN or Baan System?
Next Article How Are Your 2019 Goals? Get More Out of Your ERP!
Print
34725 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

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