Payentry NextGen Version 1.47 Release Notes

Version 1.47, which was released on July 16th at 11:00pm eastern, includes the changes outlined below.

 

———————————————————————————————————————————————————————————

 

Development Tags

 

• SOC Field Updated on Employee Demographics

• New Secondary TTOC Field on Employee Demographics

• Fixed - ZayZoon Single Sign-On

 

Development Tag Details

 

SOC Field Updated on Employee Demographics (PENG-326)

 

The SOC (Standard Occupation Code) field on the Employee Demographics screen has been updated from a free-text field to a structured dropdown list. The dropdown is populated with Detailed Occupation SOC Codes and their corresponding TTOC values.

 

The SOC field now validates against the SSOC table. Employees whose existing SOC exactly matches a valid Detailed Occupation code are unaffected. Employees with a non-matching SOC will display a blank field and require correction.

 

Two SQL queries were shared as part of the M3 Q2 release that can be used to identify and correct SOC data issues.

 

New Secondary TTOC Field on Employee Demographics (PENG-407)

 

A new Secondary TTOC field has been added on the Employee Demographics screen to support employees who require a second Treasury Tipped Occupation Code reported in Box 14b of the 2026 W-2.

 

When Secondary TTOC Is Required

 

Leave the field blank unless one of the following situations applies:

• Employee performs tipped work under two occupations – If an employee performs tipped work under two separate detailed occupation codes (for example, server and bartender), enter the second occupation’s TTOC.

• Employee receives qualifying and non-qualifying tipped income – If an employee receives tips from both a qualifying and non-qualifying occupation, enter 000 as the Secondary TTOC. This Treasury-designated indicator identifies non-qualifying tipped income.

 

Fixed - ZayZoon Single Sign-On (PENG-417)

 

Fixed an issue where clicking the ZayZoon Single Sign-On (SSO) link could result in an error for some users. This affected users whose login names contain a backslash (for example, company-level logins formatted like XXXX\username).

 

——————————————————————————————————————————————————————————

 

Please report any problems to MPAY support via the CRM Portal.

 

You are receiving this email as a member of MPAY's product Information Contact List. To be removed from further product information notifications, please open a ticket with MPAY support through the CRM portal.