Issues Fixed in Mekorma x96, Hotfix 3 (x96.39) released Thursday, July 17, 2025.
- Invoice Capture
-
- The invoice document/PDF isn’t getting attached to the PO invoice when you create a purchasing invoice from the Invoice Capture Validation window. This hotfix solves the issue.
- If you create an invoice from an email in the Invoice Capture Validation window and then delete the invoice, the email may no longer be displayed in the Invoice Capture Validation window so cannot be reprocessed. This issue has been resolved with this hotfix.
- If you create a purchasing invoice from an email in the Invoice Capture Validation window, delete the invoice, and then try to create a purchasing invoice from the same email, an error message that the invoice has already been created for this row is displayed. With this hotfix, you can create a purchasing invoice without the error message.
- The invoice document/PDF isn’t getting attached to the PO invoice when you create a purchasing invoice from the Invoice Capture Validation window. This hotfix solves the issue.
- Vendor Validation
-
- If you select to place vendor records on hold when the vendor validation returns a warning or an error, vendor records are placed on hold if the validation services are offline during a validation. In Hotfix 3, vendor records will not be placed on hold when validation services are offline during the vendor validation process.
- If you select to place vendor records on hold when the vendor validation returns a warning or an error, vendor records are placed on hold if the validation services are offline during a validation. In Hotfix 3, vendor records will not be placed on hold when validation services are offline during the vendor validation process.
Issues Fixed in Mekorma x96, Hotfix 2 (x96.36) released Thursday, June 5, 2025.
- Mekorma Payment Hub
-
- When running table maintenance, users may experience significant delays or encounter a SQL error on table ME240447 when upgrading to the latest build of bx94 (b94.21) or x96 (b96.27). This hotfix release includes performance improvements and has eliminated the SQL error.
- When running table maintenance, users may experience significant delays or encounter a SQL error on table ME240447 when upgrading to the latest build of bx94 (b94.21) or x96 (b96.27). This hotfix release includes performance improvements and has eliminated the SQL error.
- Mekorma Action Board
-
- In the Action Board window, newly created users cannot see batches that were created before their user ID was created in Dynamics GP. This hotfix release allows all users with proper access to view the batch IDs that were created before the user IDs were created.
- In the Action Board window, newly created users cannot see batches that were created before their user ID was created in Dynamics GP. This hotfix release allows all users with proper access to view the batch IDs that were created before the user IDs were created.
- Multi-Entity Management/Action Board
-
- With Multi-Entity Management (MEM In the Action Board window, newly created users cannot see batches that were created before their user ID was created in Dynamics GP. This hotfix release allows all users with proper access to view the batch IDs that were created before the user IDs were created.
- User access to a MEM entity is not applied properly if the user doesn’t have access to all companies in Dynamics GP. This hotfix release allows user access to a MEM entity if the user has access to the company and does not require the user to have access to all companies.
- With Multi-Entity Management (MEM In the Action Board window, newly created users cannot see batches that were created before their user ID was created in Dynamics GP. This hotfix release allows all users with proper access to view the batch IDs that were created before the user IDs were created.
- Invoice Capture
-
- When running table maintenance, an Invoice Capture script is only run for the company that the user is currently logged into and not all companies with Invoice Capture set up. With this hotfix release, table maintenance will occur for all companies that have Invoice Capture set up.
- The Invoice Capture Validation window opens slowly (or may lock up) when there are many accumulated records in the system. This hotfix optimized the SQL function MEIC_TransactionValidation to omit irrelevant data.
- When running table maintenance, an Invoice Capture script is only run for the company that the user is currently logged into and not all companies with Invoice Capture set up. With this hotfix release, table maintenance will occur for all companies that have Invoice Capture set up.
- Remote Payment Services (RPS)
-
- Company information is not printed on the PDF check copy for payments that are submitted to Corpay. With this hotfix release, all core MICR fields that are added to the Mekorma check will print on the PDF check copy for payments that are submitted to Corpay, including .
- Company information is not printed on the PDF check copy for payments that are submitted to Corpay. With this hotfix release, all core MICR fields that are added to the Mekorma check will print on the PDF check copy for payments that are submitted to Corpay, including .
- Mobile Workflows
-
- System Views are not created for Mobile Workflows when Payment Hub isn’t used. With this hotfix release, System Views are created for Mobile Workflows whether or not Payment Hub is used.
- System Views are not created for Mobile Workflows when Payment Hub isn’t used. With this hotfix release, System Views are created for Mobile Workflows whether or not Payment Hub is used.
- Vendor Validation
-
- The vendor Short Name and Vendor Check Name fields are not validated with the OFAC screening tool. With this hotfix release, all vendor name fields are validated with the OFAC screening tool.
- The vendor Short Name and Vendor Check Name fields are not validated with the OFAC screening tool. With this hotfix release, all vendor name fields are validated with the OFAC screening tool.
Issues Fixed in Mekorma Build x96, Hotfix 1 (x96.27) released Thursday, March 6, 2025.
- Mekorma Payment Hub
-
- Email information doesn’t save in the Approval Email Setup window if you click the Notification Events link before you click OK. In x96, Hotfix 1, email information is saved as it is entered.
- When the Payables Transaction Entry Distribution window opens, it could open behind the Payables Transaction Entry window. In x96, Hotfix 1, the Payables Transaction Entry Distribution window opens next to the Payables Transaction Entry window.
- Email information doesn’t save in the Approval Email Setup window if you click the Notification Events link before you click OK. In x96, Hotfix 1, email information is saved as it is entered.
- Mekorma Action Board
-
- When you select the Generate SafePay action in the Mekorma Action Board and change the Last Upload Date or the Upload Cutoff Date, the total amount is calculated incorrectly. In bx96 Hotfix 1, the total amount is calculated correctly when you change one or both of those dates.
- When you select the Generate SafePay action in the Mekorma Action Board, the total amount is always set to 0.00, even though the correct amount appears in the GP Safepay Upload window. In bx96 Hotfix 1, the total amount is calculated correctly.
- When you select the Generate SafePay action in the Mekorma Action Board and change the Last Upload Date or the Upload Cutoff Date, the total amount is calculated incorrectly. In bx96 Hotfix 1, the total amount is calculated correctly when you change one or both of those dates.
- Remote Payment Services
-
- Unapplied amounts in a batch aren’t sent to the remote payment services provider. In x96, Hotfix 1, unapplied amounts are sent to the remote payment services provider.
- Currently, if a batch includes a payment to an on-hold vendor, it is sent to Corpay but gets stuck in Batch Recovery when posted in Dynamics GP. In bx96 Hotfix 1, on-hold payments will stay in the original batch for local processing, while other payments move to a new batch for remote processing through Corpay.
- Unapplied amounts in a batch aren’t sent to the remote payment services provider. In x96, Hotfix 1, unapplied amounts are sent to the remote payment services provider.
Issues Fixed in Mekorma x96 (x96.20) released Thursday, November 7, 2024.
- Mekorma Payment Hub
-
- When the Omit $0 checks in Payables option is marked in the Mekorma System Options window, batches with $0 cannot be processed or posted using Mekorma Action Board. In x96, the batch is skipped for printing and displayed in the Mekorma Action Board when the Action is set to Post Batches.
- When a user requests an invoice approval and has special characters as part of their GP password, the approval email is not sent and an error message is displayed, although the batch is approved. In x96, users that request invoice approvals can have passwords that contain special characters without an error message being displayed and approval emails are sent.
- When an approver does not have access to the Edit Payment Batch window and opens the Mekorma Approval Batch Drill Down window from the Mekorma Batch Status or Mekorma Approval list views to review a pending approval payment, the batch status changes unexpectedly from Pending Approval to Open for Editing. In x96, approvers without access to the Edit Payment Batch window no longer have access to the Mekorma Approval Batch Drill Down window and batch statuses are not changed.
- When payments fall into two different thresholds which both require a single approver, some approved payments do not appear in the All Transactions view of the Mekorma Approval navigation list while the batch is still pending approval. In x96, all payments within batches pending approval will be displayed in the view.
- When the Omit $0 checks in Payables option is marked in the Mekorma System Options window, batches with $0 cannot be processed or posted using Mekorma Action Board. In x96, the batch is skipped for printing and displayed in the Mekorma Action Board when the Action is set to Post Batches.
- Mekorma Invoice Capture
- When you resize the Mekorma Invoice Capture Validation window, you can no longer use the right-click functionality in the window. You can now right-click items in the window.
- The PowerApp error “Action ‘Execute_stored_procedure_(V2)_-_Save_Documenbts_To_SQL’ failed” can occur when an email is falsely identified as an image file during the invoice capture process. The stored procedure has been updated to allow that type of document to continue through the invoice capture process.
- When an invoice has been received, the email notification received for a captured invoice incorrectly identifies the invoice PDF as not being scanned when it was scanned. The email notification now identifies the invoice PDF as being scanned.
- When you resize the Mekorma Invoice Capture Validation window, you can no longer use the right-click functionality in the window. You can now right-click items in the window.
- Multi-Entity Management
- When using the Action Board to process an EFT batch for a MEM entity that does not have the default checkbook set up for EFT, users receive an error and the batch is not processed. EFT batches are now be created and processed correctly.
- When using MEM Centralized fields on a check format and Applied Order is selected in the List Documents on Remittance field in the Payables Management Setup window, credit memos do not print on the check stub. In x96, credit memos are now printed, in the correct order, on the check stub.
- When using the Action Board to process an EFT batch for a MEM entity that does not have the default checkbook set up for EFT, users receive an error and the batch is not processed. EFT batches are now be created and processed correctly.
- Mekorma Power Approvals
- Users may encouter a blank Approval Detail screen when drilling into invoice details in the Power Approval app. This issue arises from multiple records being returned for a single voucher number. It has been resolved through improvements to the approval process code.
- Users may encouter a blank Approval Detail screen when drilling into invoice details in the Power Approval app. This issue arises from multiple records being returned for a single voucher number. It has been resolved through improvements to the approval process code.
Last modified:
July 17, 2025
Need more help with this?
We value your input. Let us know which features you want to see in our products.