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

Understanding Taxability Rules Is Key To Sales Tax Compliance

Avalara for Infor LN | Baan | Infor LX | BPCS

Product taxability may seem straightforward because there are generally only two options: taxable or exempt.
Yet that seemingly simple contrast fails to truly capture the inherent complexity of sales tax compliance. In fact, it’s a multistep process that starts with determining where a business has sales tax nexus. Knowing whether the products or services one sells are taxable or exempt is critical to the compliance process, from start to finish.

The good news is that you don’t have to be a tax expert, nor do you need to stay up on the latest tax rules and regulations in each state or country where you do business. Avalara handles all of this for you and Crossroads RMC provides the integration to Infor LN, Infor LX, Baan, and BPCS to make staying compliant a no-brainer.

End-to-End Sales Tax Automation by Avalara



Want to learn more?

Join us on Tuesday, February 9th for a free presentation by tax compliance experts at Avalara.

We’ll cover:

  • The impact of COVID-19 in 2020 and its influence on 2021
  • Why understanding economic nexus and its triggers are more important now than ever
  • New tax obligations resulting from increased marketplace sales
  • The international market and changes to cross-border e-commerce compliance
  • Answers to your questions – LIVE!

Don’t miss this in-depth review of the 2020 sales tax changes you need to know about in order to have a successful 2021.

Register Today>

Previous Article Infor LX & BPCS Finance Tip: Items without costs, CST101D
Next Article Infor LN & Baan Tip: Remove Posted Payment/Direct Debit Batches
Print
25749 Rate this article:
5.0
Crossroads RMC

Crossroads RMCCrossroads RMC

Other posts by Crossroads RMC

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

In Baan IV, users define series and numbers in the Maintain First Free Numbers (tcmcs0147m000) session. In the Type of Number field, users must select the type of documents for which the series will be used. The generated document numbers are always numeric and can consist of up to six characters.

 

In LN, users must define number groups in the Number Groups (tcmcs0151m000) session and then in the First Free Numbers (tcmcs0150m000) session, define the series and numbers of each number group. Users assign the number groups to various purposes in the corresponding sessions. For example, in the Sales Order Parameters (tdsls0100s400) session, users can select the number group for sales orders and sales schedules. In the Sales Offices (tdsls0512m000) session, users can then select a series of that number group for the sales orders generated by a specific sales office. As the series codes can be alphanumeric, the generated document numbers can be alphanumeric and they can consist of up to nine characters.

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.
First139140141142144146147148Last

Theme picker

Categories