Acumatica: Version 24.0215.0
Release Date: February 16, 2024
This release lets you configure ClickToPay imports as payments or prepayments and fixes issues reported by our customers. It also includes a tool for validating REPAY configuration settings to assist in troubleshooting.
Release Notes
Ticket | Type | Description |
---|---|---|
ERP-4101 | Feature | Processing Center settings. You can't refund a payment to a card that is different from the card originally charged. When you select Allow Unlinked Refunds for a REPAY credit card processing center, this warning message is displayed: |
ERP-4131 | Feature | Banking > ClickToPay Setup. You can set the default document import type separately for invoices (A/R invoices and Sales Order invoices) and sales orders. On the ClickToPay Setup screen:
|
Multiple | Feature | ClickToPay. You can set default import types at the customer level and override them at the individual document level. To:
|
ERP-4132 | Feature | Banking > Processes > Process ClickToPay Payments. The new confirmation screen lets you override the import default for individual payments. In the Default Import Type column, double-click to change the import type before clicking RUN PROCESS. |
ERP-4136 | Feature | When processing ClickToPay payments, the REPAY customization now takes into account the import type for every invoice or sales order included in a payment and creates the correct number of documents in Payment and Applications. |
ERP-4144 | Feature | Receivables. To assist in troubleshooting, additional details are sent to the payment gateway in Merchant Defined Fields 9, 10 and 11. |
ERP-4287 | Feature | Payables. Additional details from the payment and vendor are now sent and accessible in REPAY Payables. From:
|
ERP-4289 | Feature | Payables > REPAY Payment Group Approvals. You can expand a payment group to see which payments and invoices are included. From there, click a payment reference number to display the payment. |
ERP-4290, ERP-4291 | Feature | Payables > Checks and Payments. On the Payment screen, payment details have been moved to the REPAY tab. When an error occurs, a user-friendly explanation is provided so that you can correct the issue and resync the payment. |
Multiple | Feature | The AR configuration validator checks REPAY touchpoints and settings and identifies those that aren't configured correctly. The validator is intended for partners and integrators to use during the initial setup of REPAY for Acumatica, but can also be used for troubleshooting. To run a scan, go to Banking > Inquiries, select Validate REPAY Accounts Receivable, and then click VALIDATE. Results are shown on the Accounts Receivable Validation Detail tab and related fields to be corrected are flagged on these Acumatica screens:
|
Bug Fixes and Production Support
Ticket | Type | Description |
---|---|---|
ERP-4899 | Fix | Payables. When a void request was sent from Acumatica to REPAY Payables, the status wasn't synced back to Acumatica. Now it shows Cancelled. |
ERP-5063 | Fix | ClickToPay. Importing a payment with a surcharge invoice attached failed because the customer's policy required sign-off on all invoices. On ClickToPay Setup, we added a new option – Prevent Surcharge Invoice Auto Release. With this option enabled, surcharge invoices are created, and payments applied, but a user must release them. |
ERP-5432 | Fix | Payments and Applications. You couldn't validate a card payment for a settled transaction. |
ERP-5845 | Fix | Payables. Corrected an issue introduced in the last release where if a payment group contained payments to the same vendor, REPAY Payables combined them and listed the total amount under the number of the last payment in the sequence and listed all invoices under that combined payment. This prevented syncing those payments back to Acumatica or voiding them. |
ERP-5866 | Fix | A customer's third-party customization conflicted with the latest REPAY ClickToPay customization. Updating flags on sales order line items resulted in this error:Object reference not set to an instance of an objectAdded a null reference check in the ClickToPay customization to prevent this issue. |
Downloads
IMPORTANT: To avoid conflicts with other modifications or customization projects, we strongly advise that you install and test REPAY Base and ClickToPay customization projects in a staging or sandbox environment before deploying them to production. If you run into issues, please contact Support.
Base Customization Projects | 2022 R1 | 2022 R2 | 2023 R1 | 2023 R2 |
ClickToPay Customization Projects | 2022 R1 | 2022 R2 | 2023 R1 | 2023 R2 |