This article will give you all the information you need to know about the Infor Year End Regulatory Patching that will be released by the end of the year.

 

Why Year-End Updates Matter

As you probably know the YE regulatory patches

• Will keep you in compliance with your w2s,1099 and/or ACA reporting.
• They will Ensure the Lawson data is accurate for tax filings and vendor payments
• Many forms or report errors are symptoms of missing patches
• Being Current on Updates will maintain your Lawson functionality and supportability

 

TimeLine

Infor will release a KB article at the end of November. That article contains the dates, and the documentation that is needed for patching. Make sure to subscribe/follow the article so that anytime they make a change to it, you’ll get notified.

The YE communication process starts in Nov and then the downloads will be available around the beginning of December. That is when the install files, the PDF and the change documentation will be available.

Products and Documentation

To get the documentation and downloads, log into InforXtreme and go to product downloads.

You should see a link to product search on the right-hand side.

Download Search

In the Product Search box, enter the year,2025, and Year-End. That search will return many links for all platforms. Look for the one that fits your organization

You only need to download what products you actually use so if you don’t run benefits out of Lawson, then you will not need to download the benefit Patch.

 

Reviewing The Changes

For the changes, once you get your tar file, untar them and then inside there’s will be two HTML documents one of them is a Delta read me and the other one is a regular read me file.

The Delta lists the major changes. It’s a one-page high-level view of what changes are in this patch.  The regular read me file is more detailed. Review both of those and  look for any job parameter changes on any forms or in a batch jobs, if there are any, it will require you to create a new batch job because the new parameters on the batch job will cause the fields to shift or move, so the old jobs parameters could be off once the patch is installed. The documentation will tell you if the jobs must be recreated because of perimeter changes.

other changes that may occur with YE patches

• they may add fields to a form. This would impact your add-in queries and uploads.
• they might change the interface file by adding a column to an interface conversion file (ex AP520)
• Be sure to search for any database changes in the readme file by Searching for the key word dbreorg. If a DBreorg is required, it means that the structure of the database will change.
• If there are new forms with the patch, you will need to apply security rules to the new forms for the users who will need to have access to them.

Form Changes

You want to review:

• If AP145 has changes- make sure all your boxes are set up correctly
• The AP245 may have the most changes in the form. They may add new tabs and/or remove tabs. They may add/remove fields, they may move fields from one tab to another. If that is the case, it is best to add a new job with a new name for the AP245.

 

Installation

• The installation process is the same as any other CTPs.
• You download the patches into a folder/directory on the lawson server application server
• Use the lawappinstall command to preview, update on each patch and run activate after all patches have been run with update. The activate will pick up any patches that ran in update and haven’t been activated.
  • Perl GENDIR/bin/lawappinstall preview PDL
  • Perl GENDIR/bin/lawappinstall update PDL
  • Perl GENDIR/bin/lawappinstall activate PDL

 

TESTING

Test in a non-production environment first before you apply the patches to production. Test several different types of processing just to make sure that nothing has been impacted by the changes.

• Run daily processing; inquiry on forms
• run a couple of daily batch job
• process payroll and make sure that the taxes are calculated correctly
• validate the data; verify the benefits are deducted correctly
• run your month end process
• run 1099 and validate the data
• run W-2s
• run ACA (Affordable Care Act)

Recommended Timeline (Nov–Jan)

• November – Install patches in non-prod and begin testing
• December – Validate reports and reconcile data
• January – Finalize and submit W-2s/1099s

Key Takeaways

• Test early and document everything.
• Communicate timelines with HR, Payroll, and Finance teams.
• Leverage Nogalis resources for troubleshooting and guidance.