/
Paycode Request Process (Payroll → Technology Services)

Paycode Request Process (Payroll → Technology Services)

Purpose

This document defines the technical process and acceptance criteria used by Technology Services when implementing new or modified paycodes requested by Payroll.

Specific paycodes referenced within this document are examples only and do not limit the applicability of this process.

⚠️Required Payroll Intake Questions (Pre‑Build)

The following questions must be answered by Payroll before Technology Services begins any paycode configuration or mapping work.
Requests missing this information are considered incomplete and may be delayed.

What type of pay is the code?

Field: htype_name
Provided By: Payroll

Payroll must specify the pay type classification for the paycode.

Why this is required:

  • Determines how WFM categorizes the time

  • Impacts payroll calculation logic

  • Drives downstream reporting and compliance behavior

What is the Lawson earn code?

Field: earn_code
Provided By: Payroll

Payroll must identify the Lawson earnings code that the WFM paycode will map to.

Why this is required:

  • Required for WFM → Lawson mapping (LAWSON_SM.xml)

  • Controls how earnings are calculated in Lawson

  • Prevents payroll errors (e.g., PR530 contract/assignment errors)

  • Ensures consistency across payroll, finance, and reporting systems

Infor WFM → Lawson Mapping (Required)

Owner: Infrastructure Application Analyst

  • Workforce Management (WFM) paycodes are:

    • Properly configured

    • Mapped to the correct Lawson earnings codes

  • Mappings are updated in the appropriate payroll export configuration (e.g., LAWSON_SM.xml).

  • Each WFM tcode_name correctly maps to its corresponding Lawson earn_code.

  • Values from the DevOps configuration file are input into the Infor WFM Payroll Close Export Wizard

    • Infor WFM > Maintenance > Payroll Settings > Payroll Close > Payroll Export Task

      • Edit LAWSON_SM and paste the configuration file into the XML text box, press Save

✅ Example (Non‑Exhaustive):
Additional‑pay or caseload‑type time codes (e.g., ADC‑style codes such as ADCA, ADCB, etc.)

These codes are examples only and are not required for every request.

  • Mapping logic aligns with version‑controlled configuration checked into the WFM Payroll repository (Bitbucket) when applicable.

MHC Line Associations for Paystub Earnings/Deductions

Owner: Infrastructure Application Analyst

  • MHC Doc Express paycodes are:

    • Properly configured

    • Mapped to the correct Lawson earnings codes

  • Mappings are updated in the appropriate MHC Line Maintenance within the corresponding Fiscal Yr Pay Account

    • Sign in to FinMHC-3 via RDP

      • Open DE45 (Doc Express App)

        • Choose the correct fiscal yr account

          • Click Administration

            • Edit Accounts

            • Import Routine (Setup)

            • Misc Tab

            • Maintain Line Items Button

            • Scroll to the bottom and add the new paycode

2. Infor WFM Lawson Pay Code Configuration (Required)

  • After, Corresponding Pay Codes exist in Lawson for all newly introduced WFM time codes.

  • Pay Codes are configured appropriately based on business intent, such as:

    • Contract vs. non‑contract earnings

    • Additional or supplemental pay

  • Configuration does not introduce unintended dependencies on:

    • Employee contracts

    • Assignments

    • Contract year data (unless explicitly required)

3. FinReporting Validation (Required)

Owner: DevOps
Support: Infrastructure Application Analyst

  • FinReporting processes (e.g., “WFM → Lawson Time Inload”) successfully:

    • Consume updated WFM exports

    • Preserve all new or modified paycodes

  • The process does not:

    • Drop paycodes

    • Rename or remap paycodes unexpectedly

    • Add contract or contract‑year data for non‑contract paycodes

4. WFM Payroll Export Job Validation (Required)

Owner: DevOps

  • The WFM Payroll Export job (e.g., LAWSON_SM | Payroll Export to Lawson):

    • Includes all newly configured paycodes

    • Executes successfully

    • Produces output compatible with Lawson payroll processing

5. Payroll Run Validation (Required)

Owner: Payroll
Support: Infrastructure Application Analyst

  • Payroll processing in Lawson completes successfully.

  • Jobs such as PR530 are complete with no errors related to:

    • Pay Codes not tied to Employee Contract

    • Pay Codes not tied to Assignment

  • No manual corrections are required to resolve paycode‑related errors.

6. Business Validation & Acknowledgement (Required)

Owner: Payroll

  • Payroll confirms:

    • Paycodes load correctly

    • Earnings are calculated as expected

  • Business stakeholders acknowledge resolution in the Jira ticket comments.

 

✅ Example:
Payroll confirmation by a designated payroll analyst and acknowledgment by impacted stakeholders (names will vary by request).

 

A paycode request may be closed when all applicable conditions are satisfied:

✅ WFM configuration completed
✅ Lawson Pay Codes configured
✅ WFM → Lawson mappings validated
✅ Interfaces and reporting validated
✅ Payroll export job successful
✅ Payroll run completes without paycode errors
✅ Payroll and stakeholders confirm expected results
✅ Jira ticket documented and closed

Job Area Responsibility Summary

Job Area

Responsibilities

Job Area

Responsibilities

Infrastructure Application Analyst

Infor WFM setup, Infor Lawson Pay Code configuration in WFM, technical documentation

DevOps

Export jobs, integrations, FinReporting validation, and environment integrity

Payroll

Business rules, payroll execution, final validation and sign‑off

Notes

  • Specific paycodes referenced in tickets (e.g., ADC, ADEC) are examples only.

  • This process applies to all payroll‑impacting paycode requests, regardless of naming or use case.

  • Always follow version control and change management standards for configuration artifacts.

  • This KB is based on completed implementation work documented in: