Redwood Experience: Personal Payment Method Enhancements

You can now manage employee payment methods with more flexibility, while keeping payroll data consistent.

Reorder payment methods across different start dates
You can change the order of an employee’s payment methods when they have multiple payment methods with different start dates (for example, one starting 1 January and another starting 1 June). This feature is available to both administrators and self-service users to better meet the employee’s needs.

View future-dated payment methods
Employees can view personal payment methods that have a future start date. For example, on 1 February, an employee can view a payment method scheduled to start on 4 February. These are clearly marked with a Future badge until they become active.

New validations to improve usability and protect payroll integrity

• New payment methods are no longer automatically end-dated when the employee has already end-dated their only existing payment method.
• Updates to a payment method can take effect only after the date it was last used for payroll payment. For example, if a payment method was last used on 31 March, updates can start from 1 April.
• New payment methods can take effect only after the last payroll payment date. For example, if the last payment process completed on 31 March and a new payment method is created on 25 March, it can start from 1 April.
• Remaining Pay payment methods can no longer have gaps. Continuity is preserved during the create, edit, and delete actions. For example, suppose an employee end-dates a remaining pay payment method on 31-Jan-2026 but already has another method scheduled to start on 1-Apr-2026. If the employee then tries to create a new payment method on 5-Feb-2026, the application will first ensure that the future-dated method is either moved up to 5-Feb-2026 or deleted before the new method is created. 
• Delete actions (including deletion of date-effective records) are now more controlled to ensure data consistency. For example, suppose an employee has two payment methods and end-dates the remaining pay payment method on 31-Jan. The other payment method is automatically updated and becomes the remaining pay effective 1-Feb. The application then ensures that an admin can't delete this entry starting from 1-Feb.

Note: These enhancements aren't currently available for payment methods that are created or updated through HCM Data Loader uploads. 

Employees and administrators can manage payment methods more flexibly while ensuring payroll accuracy and data consistency. This includes reordering methods across different start dates, viewing future-dated methods, and preventing gaps or conflicts in remaining pay. Enhanced validations reduce errors, protect payroll integrity, and minimize administrative rework.

Steps to enable and configure

You don't need to do anything to enable this feature.