Previous Releases

Summary of Changes 

IFS IDEAS 6.21.0.0 has the following new Features:

Enhancements

Accounts Payable

Multiple Tax Codes per Tax Type

• The ability to record multiple tax codes per tax type has been added to the non-Argentine Invoice Entry screen.  Previously, only one tax code per tax type (VAT, WH, INC) could be added to an invoice.  If multiple tax authorities were required on a single invoice, then single tax codes had to be defined with as many tax authorities as necessary to fulfill the tax requirements of the invoice.  The Tax Code has now been added as a column in the tax grid, and a selection box has been added to allow multiple tax codes to be selected for each tax type.  The tax amounts are summed by tax type based on how many codes are selected for the tax type.

• Additionally, a new Tax Codes tab has been added to the Vendor Maintenance screen.  This allows the user to specify the tax codes that are always used by a vendor in the vendor record.  When an invoice is raised against the vendor, the available tax codes in Invoice Entry are filtered by the tax codes defined in the vendor record for quicker selection of the codes necessary for the invoice.  If no tax codes are specified for the vendor in Vendor Maintenance, then the tax code list in Invoice Entry is not filtered and all available tax codes for the Entity/Tax Type combination are displayed in the select list.

Invoice Batch Control Options

• An AP Miscellaneous code (EnforceBatchControlOnValidation) has been added to allow users to specify whether traditional batch controls will be considered as part of the invoice validation process.  The Batch Validation Process assumes that Invoice Batches are being used as financial controls to ensure the number and value of invoices entered to a batch match what was expected at the creation of the batch.  We have discovered that many of our customers do not use Invoice Batches in the traditional manner, but rather more as a logical grouping of invoices based on the data entry person and specified control period, such as a week or full accounting period.  In those cases, there is not a concern for actual vs. control totals, but instead batches are used as “work in progress” containers for invoice entry.

• The new flag will allow the user to specify if traditional batch validation logic should be enforced or ignored based on how the customer uses invoice batches in AP.  The default setting for the flag is Y (enforce batch control) but can be changed to N in the AP Miscellaneous screen.

• This option will eliminate Batch out of Balance validation errors for those customers using batches as logical groupings and allow for invoices to be approved in iApprove when the batch is still in flight.

Windows 11 Certification

IDEAS 6.21.0.0 has been certified on Windows 11.

Issues Resolved

The focus of 6.21.0.0 related to maintenance was to reduce the backlog in Accounts Payable and General Ledger.  Below are key changes made in those modules as well as Purchase Documents.

Accounts Payable

• Auto Checks

  • Corrected a condition where the check amount was incorrect on printed checks, even though the check amount in the database was correct.

• Manual Checks

  • Corrected the update of two tables that was affecting the journalization of manual payments to the GL.

• AP Reconciliation Period Report

  • Corrected a situation where payments were not included on the report when the invoice was in the previous period, but not posted, causing an Exception report to generate.

• Invoice Detail Report

  • Corrected the decimal precision on the Invoice Detail Report.

• Apply Advanced Applications

  • Corrected a condition where advance applications were given the wrong fiscal year when processing spanned activity over the year end.

• Auto Invoice

  • Added the ability to include Reference Number as a part of the Auto Invoice import.

  • Disallowed entry of discount information through Auto Invoice if the vendor is not set up for discounts in the vendor record.

• Period Control Date

  • Modified the Period Control Date screen to accept yyyy-MM-dd date. 

General Ledger

• Journal Batch Entry

  • Made allowance for saving batches where an FQA is incomplete.  Journal Batch Entry now allows the saving of an incomplete FQA and will not error on reload.  The batch will not validate until the FQA is completed.

• Journal Batch Status Report

  • Corrected a filtering issue when all entities and all journals are selected and multiple ledgers are involved.

• Journal Corrections

  • Corrected a condition where the batch is changed to a new batch without exiting the screen and the lines from the old batch remain in the screen.

• Journal Posting 

  • Corrected Posting to accept up to 50 characters in the User 1 and User 2 fields.

Purchase Documents

• Print Purchase Documents

  • Expanded the limit of PD clauses to 5000 characters from 1500.

See the 6.21.0.0 Risk Assessment for the full list of maintenance items included in this release.

Compatibility Matrix

Product Certification

Interoperability Certification

Minimum System Requirements

Hardware

This section identifies the recommended hardware requirements for each machine.

Client

Server

Software

Server Machine

• MS .Net Framework 4.8
• SQL Server
• Excel
• Crystal Reports (Installed)
• PDF Viewer (Optional)
• Web Browser (Optional)
  

Client Machine

• MS .Net Framework 4.8
• Excel
• Crystal Reports (Installed)
• PDF Viewer
• Web Browser

Web Server

• ASP.net 4.6
• ,net Framework 4.8
• .net Core Hosting Bundle 3.1