REPAY ERP & eCommerce Release Notes logo
Back to Homepage Subscribe to Updates

ERP & eCommerce Release Notes

Labels

  • All Posts
  • REPAY ClickToPay
  • REPAY Payables Platform
  • Acumatica
  • CDK Global
  • eCommerce
  • Microsoft Dynamics 365
  • Sage 100
  • Sage 300
  • Sage Intacct
  • Sage X3
  • SAP Business One
  • Announcement
  • Compatibility
  • Hotfix

Jump to Month

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • November 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • January 2022
  • December 2021
  • October 2021
  • August 2021
  • July 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • January 2017
REPAY Payables Platform
2 years ago

REPAY Accounts Payable: cPayPlus Version 273.3


Release Date: January 19, 2023

This version addresses issues with payment groups that affected users of the CDK Global platform. Payment groups have generated names consisting of the customerID-dueDate (for example, ACME2201-2023-04-12 would contain payments for invoices from ACME that are due April 12th).

TicketTypeDescription
CPAY-1713FixIf you entered invoices with the same due date and vendor as invoices already captured in a payment group, the additional invoices weren't added as a new payment to the existing payment group. Creating the new payment failed.
CPAY-1764FixAdded logic to ignore custom suffixes (for example, -HOLD) in a payment group name. Previously, if a payment group was placed on hold, entering more invoices with the same vendor and due date failed to create a payment because of a customerID-dueDate naming conflict. (When a set of payments is placed on hold, the payment group name is appended with the suffix -HOLD.)

Now, a new payment group with the customerID-dueDate name is created with the payment added.