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: Setting Up Interest Invoicing

You can set up interest invoicing in Accounts Receivable and in the General Ledger.

To set up interest invoicing, use these sessions:

Invoice-to Business Partner (tccom4112s000)
For invoice-to business partners for which you want to raise interest invoices, select the Charge Interest check box.

Mapping Scheme (tfgld4573m000)
Use this session to define the mapping of the Interest Invoice / Revenues Analysis integration document type.

Interest Percentages (tfacr5102m000)
Use this session to define the interest percentages for each financial business-partner group, and for different periods of days.

Interest Invoice Related Data (tfacr5101s000)
Use this session to define whether interest must be calculated on unpaid invoices, partly paid invoices, interest invoices, and/or fully paid invoices. You can also indicate that LN must take advance payments, unallocated payments, and credit notes into account for the generation of interest invoices.

Optionally, set conditions
Example: LN only generates an interest invoice advice entry if these conditions are met: The total of all advice entries in one currency is higher than the allowed minimum amount of an interest invoice defined in the Minimum Amount for Interest Invoice field.

The invoice is overdue for a greater number of days than the number of days defined in the Minimum Days for Interest Invoice field.

Previous Article Top Ten Proven Tips to Maximize Uptime & Boost Performance
Next Article BPCS/LX Tip of the Week: Summarize Transactions by Account or Journal Source
Print
31487 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

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.

135678910Last

Theme picker

Tips: LN | Baan

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...


TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

135678910Last

Theme picker

Categories