Date: July 31, 2025
Payroll: Tax Engine Update
Background: We have recently updated our tax engine.
What’s new?
The following states have some withholding calculation updates:
IA, KY, NM, NY, OH, PA, WA
Payroll Reports: Department added to Arrears Summary Report
Background: Department is a critical field for many of our clients, particularly those in the staffing industry who rely on it for accurate tracking and reporting. This field was missing from the Arrears Summary Report, limiting its usefulness for organizations that need to analyze data by department.
What’s new?
We’ve added the Department field to the Arrears Summary Report. This enhancement provides greater reporting flexibility and ensures that clients can now view arrears data segmented by the department.
/msdyn_blobfile/$value)
Pay Code Setup: Hire Date and Rehire Date available for maximums
Background: Previously when setting an annual maximum for a deduction or benefit code, the maximum would reset only at the start of the calendar year (January 1). This limitation created challenges for clients who wanted the maximum to align with an employee’s hire or rehire date rather than the calendar year.
What’s new?
We have added two new options for resetting annual maximums on deduction and benefit codes: Hire Date and Rehire Date. These new options provide greater flexibility, allowing clients to tailor maximum resets to each employee’s employment timeline.
You can learn more about Deduction Codes here.
/msdyn_blobfile/$value)
General Ledger: Dimension mapping based on Location State
Background: Clients using Dimension mapping for Location State previously had to manually update their mappings each time a new work location was added. This ongoing maintenance was time consuming and prone to errors, especially for organizations with frequent changes or distributed workforces.
What’s new?
We have introduced new mapping parameters that automatically incorporate Location State into Dimension mappings. This enhancement simplifies setup and maintenance by dynamically handling location data, including special cases like Work From Home, Washington D.C., and Puerto Rico, without requiring constant manual updates.
You can learn more about our General Ledger settings here.
/msdyn_blobfile/$value)
rapid! Instant Pay Enhancements: Updated Workflow
Background: Our previous rapid! Instant Pay workflow led to confusion regarding the status of employee payments. All wages initially appeared in the ACH file and were only removed once confirmation from rapid! was received. This created a risk of duplicate payments if clients downloaded and processed the ACH file before instant payments were fully funded.
What’s new?
We’ve made several enhancements to improve clarity and control in the rapid! Instant Pay workflow:
- Wages Still Begin in the ACH File
- All payments continue to default into the ACH file initially.
- New UI Controls for Managing Instant Payments
- Clients can now select specific entries in the ACH file and click “Switch to Instant” to move them into the instant payment process.
- Automatic Removal from ACH File
- Entries moved to Instant Pay are automatically removed from the ACH file, reducing the risk of duplicate payments.
- Submit Instant Payments via the Modal
- After moving entries, clients can exit the modal and click “Fund Instant Payment” to initiate submission to rapid!.
- Improved Visibility with Status Indicators
- A new Instant Payment tab allows clients to track payment statuses with clear indicators:
- Pending
- Successful
- Failed
- Unknown (rare; should be verified in rapid! and either marked as Submitted or reset to Pending for resubmission)
- A new Instant Payment tab allows clients to track payment statuses with clear indicators:
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
rapid! Instant Pay Enhancements: Pay Run Review and Submit Update
Background: Clients using rapid! Instant Pay have asked for better visibility into which employees are set up with rapid! cards during payroll processing. Previously there was no clear indication during the pay run of which employees were using rapid!, making it harder to manage and verify payment methods.
What’s new?
We have added a new Pay Card column during the Review and Submit step of a pay run. Here’s how it works:
- If an employee has a Direct Deposit payment method and a rapid! card set up on their employee profile, the column will display "rapid!"
- If the employee is paid by Direct Deposit without a rapid! card or by paper check, the column will be blank.
Additionally, the payment method summary counts at the top of the pay run screen now includes rapid! as a separate payment type, giving clients a clearer breakdown of how payments are being distributed.