API updates:
We’ve introduced an important update to how employee email addresses are handled in the PayEvo ecosystem.
Once an employee has been added and invited, their email address can no longer be modified via the API.
This change ensures:
Consistent identity mapping across systems
Improved data integrity after user provisioning
Reduced risk of mismatched or orphaned user records
How to update an email address:
If an email change is required, it must be handled through the UI:
Revoke the employee’s access
Update the email address
Re-invite the employee
This enforces a clear lifecycle for identity changes and aligns API behavior with platform-level user management.
Frontend Fix: Nickname Handling
We’ve resolved an issue where clearing an employee’s nickname appeared successful but did not persist.
What’s changed:
Users can now set the Nickname to an empty value successfully
When no nickname is present, the system will display the employee’s First Name instead
Employee List and Employee Card views now consistently follow this behavior
This fix ensures expected editing behavior and consistent display across the platform.
Reports Fix: Remittance Report Filtering & Year Selector
We’ve fixed a production issue where the Remittance Report could fail to load correctly due to filter-related errors.
What’s changed:
Resolved a crash caused by pre-applied filters on load
Fixed an issue where the report would stop rendering after reload
Added persistence for the Year Selector and applied filters
Reports now load reliably with previously selected filters intact
This ensures a smoother and more predictable reporting experience, especially when revisiting filtered reports.
Keywords: Employee API
396
Can't find what you are looking for? We can take a more direct look to help resolve your matter — Create Case or Contact Us