Mobile App Features
New corporate wellbeing channel
We’re excited to introduce a new feature designed to enhance customer satisfaction by allowing them to send their own corporate content to their employees via the CPNow mobile app. Customers will be able to segment these contents down to a specific pay group level. This feature aims to improves content visibility and streamlines content management across various paygroups and countries within a client's organization.
The content sent will then be submitted and processed via an endpoint and delivered directly to the mobile app for seamless integration, at this time, only the CPNow team will be authorized to create and send these messages.
- Client should send the content request to the following emailcorporatecpnow@cloudpay.net.
- The language version of the content depends on the EE's mobile app settings.
- The client can create as many translations as the mobile app has available.
Client Service Web App Features
Billing report generation and submission through SFTP path
CloudPay NOW is now generating a Billing report at the end of each month and automatically submitting it to CloudPay Billing team through the configured SFTP path. This report will be generated right after the last day of the month will be over, to make sure it will include all transactions made during that billing month. It will include all companies and their corresponding legal entities and pay groups (besides CloudPay Cloudees), so that Cloudpay Billing team can accurately calculate how much CloudPay should bill each client at the end of each month.
Enhanced File Status section available in the ‘‘Overview”
We have improved the file status section in the Overview feature to enable CS admins to monitor each generated file within CloudPay NOW for all pay groups at once. CS admins will the able to filter the new Overview section by file status and month/year. By filtering by status “failed” or “submission failed”, CS Admins will be able to check for potential errors for all pay groups. “Failed” represents a file which couldn’t be automatically generated. “Submission failed” represents a file whose automatic submission through the configured SFTP path was not successful. By clicking on the “GO” button, the CS Admin will be redirected to the File Management section of that specific pay group, to see the details of the selected file.
Implementation Consultant: Web App Features
New "Reseller” configuration available
Reseller is a new feature that allows the implementation consultant to identify the origin of a new customer: from Cloudpay or from other resellers. When choosing to create a new customer account, this field will be mandatory. On the other hand, this new feature will allow pre-filling some values according to the configuration of each reseller.
Clear Identification: Client accounts will be clearly distinguished by the reseller or not.
New automatic default configuration feature for "Resellers”
As an implementation consultant, when setting up a new company that is coming through a Reseller (ex: Santander), the majority of the details will be pre-filled automatically based on the Reseller-specific contract configuration, making the set up much quicker and less time consuming by ensuring consistency throughout all clients coming from that same Reseller.
New specific pre-defined set up for Santander clients as a "Reseller"
When setting up a client from Santander the client's fields that are common to that reseller may have the option to be pre-filled. This configuration's business rules will have a different behavior depending on the bank account of EEs they will have different number of requests.
The following configurations will be set as default.
- Name: Santander
- Payroll Engine: CloudPay Payroll Customer
- Payroll Advance: Active
- Business Events: Active
- Default Locale: Spanish-Spain
- Maximum nº of requests per pay period: 3
- Minimum nº of requests per pay period: 3
- Maximum amount per request: 10
- Minimum amount per request: 10,000
- Available over accrued ratio: 50%
Activation of Payslips-only pay groups in MDH
A new option is now available in MDH for Implementation Consultants to be able to configure and activate Payslips-only pay groups and allow their data synchronization between MDH and CloudPay NOW platform. Furthermore, this new option will allow Implementation Consultants to activate Payslips-only paygroups even before the first pay cycle is closed. Whereas, if the pay group to be activated has Pay on Demand in its service scope, its activation will still require the first pay cycle to be first processed and closed for CloudPay NOW to be able to receive the NET salary of the employees of that pay group and calculate their available balance.
Improvements and Bug Fixes
New option to terminate an employee manually in MDH
We detected some cases in which MDH was still showing that an employee was ACTIVE even though both Payroll and CloudPay NOW platforms were showing that employee as TERMINATED. In order to align all platforms, avoid discrepancies and preventing potential future issues, we implemented a new option in MDH to allow MDH admins to change the status of an employee to a terminated state. This new feature is not applicable if the status from a terminated employee needs to be changed to live.
Reconditioned employee bank details synching process between MDH and CPN
We implemented a fix to address potential bank detail synchronization issues between MDH and CloudPay NOW. Previously, these issues occurred when MDH attempted to update an already ACTIVATED bank account in CloudPayNOW based on payroll updates. Before the fix, CloudPay NOW would reject such updates. However, with the recent adjustment, CloudPay NOW will now accept new bank account details submitted via MDH or a Master Data template for existing employees.
Automatically set the new bank account as default/preferred payment method on both mobile and web application for new bank accounts
Additionally, when a new bank account is received via Payroll or MDH, CloudPayNOW will validate the account through the payment provider. If the validation succeeds, CloudPay NOW will update the employee's Default payment method to the new bank account for Pay on Demand requests. Employees will still have the option to change their Default payment method at any time through the mobile app. However, if the payment provider validation fails, CloudPay NOW will record the new bank account as FAILED without designating it as the employee's Default payment method.
Employee details are now showing correct information on the “Master data reports” and “Requests report” when previewed
We fixed a bug issue that was showing several discrepancies in the Reportingfeature when intending to generate a master data report and/or a request report as well. When filters were set up, the preview page would sometimes show random dates in the employee's personal information.
The date and time display for requests and files are now aligned and corrected based on each Legal Entity's local time
We've corrected the date and time values shown in the web app in accordance to the local time configured of each legal entity. When viewing individual files and transactions, the date and time values are now aligned and they no longer shown as CEST.
Error message fix when employee request remains in state of processing due to missing funds
We have introduced a new notification mechanism to address issues with transactions originating from Ebury that previously remained in a processing state without a clear explanation. With this update, Client Service (CS) admins will now receive specific details in the back office indicating signs of insufficient funds, when this is the reason for a request remaining in a processing state. This enhancement enables admins to better understand the issue and promptly contact the payment provider to resolve funding-related problems.
Reconditioned the logic behind SFTP path configuration
When configuring an SFTP path for the submission of CloudPay NOW files of a specific Legal Entity, the two SFTP path configuration fields, one for the Payroll/P&D file and one for the Reconciliation file, are now independent from each other. Meaning, Implementation Consultants can now configure one of them without necessarily having to configure the other one as well.
Prevent account deletion in bank payment file generation for CS Admins
We have implemented a fix to prevent the regeneration of a bank payment file in CloudPay NOW from erroneously removing payment information when an employee has multiple accounts for salary distribution. As a matter of fact, CloudPay allows employees to split their salary across various accounts). In such cases, CloudPay NOW was previously only processing Pay on Demand deductions for one account, leading to the deletion of the rest of the accounts from the regenerated bank payment file. With the fix we put in place, the report will now reflect Pay on Demand deductions applied to all relevant accounts, ensuring no accounts are omitted, to avoid inaccuracies in the salary distribution and potential payment issues for employees. Please be aware that the only case in which CloudPay NOW will omit accounts from the regenerated bank payment file will be when the balance of those accounts after the deductions is zero.
Announcements
New audit tracking and timestamps for changes/modifications regarding legal entities and pay groups
To enhance user management controls, we have implemented an audit tracking system for all changes made to legal entities and pay group data within our system. This system captures user information and timestamps for every creation or modification, providing transparency and accountability.
- Log in to post comments