Maintenance update 27.0.2548.450 Published November 28, 2025
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 you try to post a purchase invoice, Sparkrock Impact displays the following unnecessary error message: The Purch. Rcpt. Header does not exist. Identification fields and values: No.= |
|
| When you post a foreign currency EFT payment, Sparkrock Impact creates a check ledger entry using the local currency amount instead of the foreign currency amount. This problem causes incorrect amounts to appear on the check ledger entry and results in a double currency conversion if the check is voided. |
|
| Sparkrock Impact requires a new document verification API because purchase requisition, expense claim, and payment request verification data is not shared properly with mySparkrock. |
|
| On expense claims, when you perform a lookup for Account Set Code, Sparkrock Impact displays account sets that have a blank General Ledger (G/L) account even when the selected expense type has an Expense G/L Account No. configured on the associated Expense Type Card page. This problem results in invalid account sets being selected and errors appearing when the expense claim is submitted. When an Account Set Code lookup is performed, Sparkrock Impact must only display account sets that include the configured G/L account. |
|
| Sparkrock Impact requires changes to an API because account sets data is not shared properly with mySparkrock. |
|
| Sparkrock Impact displays an error when you try to delete an attribute or attribute value even when the attribute or attribute value has not been used on any expense claims. An error must be displayed only when the attribute or attribute value has been used on an expense claim. |
|
| When you try to update the Mandatory checkbox for an attribute value on the Attribute Values - Expense Type page, Sparkrock Impact incorrectly displays the following error message: This attribute value cannot be deleted because it is used on expense records. This problem prevents users from enabling or disabling the Mandatory setting for the attribute value. |
|
| Sparkrock Impact requires changes to an API because expense attribute data is not shared properly with mySparkrock. |
|
| Sparkrock Impact requires changes to an API because mileage data for unassigned expenses is not shared properly with mySparkrock. |
HR Management
| Description | |
|---|---|
| When you create a gradual return HR request, Sparkrock Impact calculates the Leave Hours/Day value on the associated HR Request Leave Causes page using the Default Hours/Day from the HR position only for the first line on the Gradual Return FastTab. Sparkrock Impact does not calculate the Leave Hours/Day for additional gradual return lines, and manually entered values are not saved. This problem prevents the additional lines from being pulled into the compensation journal. For every line, Sparkrock Impact must use the Default Hours/Day value when calculating Leave Hours/Day. |
|
| Sparkrock Impact does not calculate allowances for time entry records from previous pay periods when the related assignment has ended. This problem causes understated earnings in the compensation journal because allowances that are eligible based on the employee’s work days are not included. If the assignment that is associated with the compensation journal lines is not active, Sparkrock Impact must use the work days from the compensation journal lines instead of using the pay period dates to determine eligibility. |
Related information
New for Sparkrock Impact
Finance and procurement maintenance updates
HR management maintenance updates
Feedback
To send feedback about this page, select the following link: