Maintenance update 27.0.2609.566 Published February 27, 2026
Periodically, Sparkrock may publish maintenance updates between releases. This maintenance update replaces previously released updates. All maintenance updates are cumulative.
Problems that are resolved in this maintenance update
The following problems are resolved in this maintenance update.
Finance and Procurement
| Description | |
|---|---|
| When an employee has two active assignments within the same pay period due to a mid-period pay increase, and a payout request is processed after the new assignment has started, the compensation journal loads the payout amount from the previous assignment instead of the active assignment. The payout calculation does not validate whether the assignment that is associated with the payout is active on the payout decision date. As a result, the payout line may reflect the amount from an inactive assignment. |
|
| When a bank reconciliation is posted from the Bank Acc. Reconciliation page, Sparkrock Impact uses the Statement Date on the General FastTab to populate the Date Cleared field on the applicable Bank Account Ledger Entry and Check Ledger Entry records. The posting logic does not consider the available line-level cleared date fields, such as Date Cleared On Check Ledger Entry or Transaction Date. As a result, the cleared date may not reflect the most accurate date that is associated with the reconciled transaction. |
|
| Sparkrock Impact does not provide a standardized set of finance APIs for external systems to securely retrieve and manage core financial data and journal structures. To learn more, go to New finance APIs. |
|
| The full Social Insurance Number (SIN) and business account number are printed on T4A slips, which presents a security risk. To learn more, go to Mask sensitive information on vendor T4A slips. |
HR Management
| Description | |
|---|---|
| Sparkrock Impact requires code changes that involve adding an event to the HR request worksheet functionality. To learn more about events, go to Events in AL. |
Payroll Administration
| Description | |
|---|---|
| When a value is entered in the Vendor Bank Account Code field on the Primo Payday Integration Setup page and validation fails, Sparkrock Impact displays a generic error message that provides insufficient detail to identify the affected record. The error can occur in multiple scenarios that relate to existing payroll employee direct deposit configurations and vendor bank account validations, such as missing email addresses or conflicts with electronic payment settings. Because the message does not indicate which record is causing the issue, users must manually review multiple records to determine the source of the problem. As a result, troubleshooting may take a significant amount of time and delay integration setup and payroll processing. |
Related information
New for Sparkrock Impact
Finance and procurement maintenance updates
HR management maintenance updates
Payroll administration maintenance updates
Feedback
To send feedback about this page, select the following link: