Issues Fixed in Mekorma x96 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.
- Occasionally, invoice documents are not scanned, but still attached to the invoice. When you open the Mekorma Invoice Capture Validation window, scanned invoices are processed, and unscanned invoices are left in a “holding” table. The holding table can grow large over time, with unneeded records. In x96, unscanned invoices will be removed from the holding table once the invoice that they are associated with is created in Dynamics GP.
- 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.
- 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:
November 8, 2024
Need more help with this?
We value your input. Let us know which features you want to see in our products.