How to Apply an Infor Lawson Payroll Tax Update: A 5-Step Checklist

Payroll tax updates are routine — until one goes wrong on a Friday. A missed state rate change or a withholding table that was never loaded shows up as incorrect paychecks, amended filings and a lot of uncomfortable conversations. The good news: a disciplined, repeatable process takes most of the risk out of every update.

This checklist walks through the five steps our ERP team follows when applying a payroll tax update to Infor Lawson. Watch the one-minute video above for the overview, then use the detail below as your working checklist.

Step 1: Read the release notes

Before anything is installed, understand what is actually changing.

• List every jurisdiction in the update. Federal, state and local changes often arrive together. Note new rates, wage-base changes, new or retired tax codes and any changes to reciprocity rules.
• Map the changes to your workforce. Which employees live or work in the affected states and localities? Pull a headcount by work and resident state so you know exactly who the update touches.
• Check effective dates. Some changes apply to pay dates on or after a specific date, not period end dates. Confirm which payroll cycles each change affects.
• Confirm prerequisites. Make sure your tax engine and Lawson patch levels meet the update's requirements before you schedule the work.

Step 2: Apply it in test first

Never load a tax update straight into production.

• Refresh or verify your test environment so its employee, deduction and tax data closely reflects production. A test run against stale data proves very little.
• Take a backup or snapshot of the test environment before applying the update, so you can roll back and retry cleanly.
• Apply the update exactly as you will in production and record each step, including versions and any manual configuration, so the production install is a repeat rather than an experiment.

Step 3: Run a test payroll and compare

This is where problems are caught — before they reach a paycheck.

• Process a full payroll cycle in test for the upcoming pay period.
• Compare withholding against your last live payroll. Look at federal, state and local withholding and employer taxes, employee by employee.
• Focus on the employees and states the update touches. Differences there should match the published changes. Differences anywhere else need an explanation.
• Review exceptions and error reports, not just totals. A total that ties can still hide offsetting errors.

Step 4: Fix, then promote

• Resolve every difference you cannot explain from the release notes. Common causes include missing tax codes on employee records, outdated local tax setup and reciprocity configuration.
• Document what changed — the update version, configuration adjustments, test results and sign-off. That record becomes your audit trail and your starting point for the next update.
• Promote to production before your payroll cutoff, using the steps recorded in test, through your normal change-control process. Leave enough time to react if something unexpected appears.

Step 5: Watch the first live payroll

• Review the payroll register and exception reports for the first live run before releasing payments.
• Spot-check affected employees against the results you validated in test.
• Confirm tax liability and reporting outputs look right for the affected jurisdictions.
• Only then release payments. If something looks off, it is far easier to correct before money moves.

Frequently asked questions

How often do Lawson payroll tax updates arrive?

Tax changes are published throughout the year, with heavier volume around year end and the start of a new year. Treat updates as a recurring process with a standing checklist, not a one-off project.

Who should own the update?

Payroll tax updates sit between HR/payroll and IT. The most reliable setup is a named owner who coordinates both: someone who understands the tax changes and someone who manages the Lawson environment and change control.

What if the test payroll shows differences I can't explain?

Do not promote the update. Unexplained differences usually point to configuration or employee data issues that will carry into production. Resolve and re-test first, even if it means applying the update closer to cutoff.

Can we apply an update in the middle of a payroll cycle?

Avoid it where possible. Apply updates between cycles, after the test payroll has been validated, and with enough time before the next cutoff to review the first live run.

Need a team that does this every week?

Cendien's ERP team supports Infor Lawson and CloudSuite clients with HR and payroll, financials, supply chain, reporting and integrations — including testing updates before payroll runs and documenting how your system actually works. Talk to our Infor team or read more about our Infor Lawson and CloudSuite support.