In Febuary 2025, GCPay released the following features, enhancements, and bug fixes:
ePayments & Waiver Exchange Enhancements - Manual Holds and Waiver Settings
GCPay is excited to share a series of improvements to the ePayments & Waiver Exchange feature, including expanded waiver functionality and manual holds. The best way to learn about these updates is to watch the video below or read the feature article.
Comments / Holds
Users now have the option to add comments and apply holds to payables. Comments and holds may be added by users with the following permissions:
- Treasury Assistants can only remove their own holds.
- Treasury Officers can remove any holds, including those placed by other users.
- Admins can remove any holds, including those placed by other users.
Waiver / Template Settings Update
GCPay has decoupled the Payment Exchange waiver setting from the Requirement Trigger, which means a Payment Exchange waiver can be required at any point in the AFP submission and approval workflow. This is particularly helpful for waivers that require notarization, as it allows a GC to require the waiver after the AFP is approved, avoiding the scenario where a subcontractor is forced to notarize a waiver for an AFP that is ultimately rejected.
GCPay also introduced a Payment Control setting in the General Options. This setting allows a user to designate any waiver / template as a requirement for payment. This setting does not involve the "Unofficial" watermark process of the Payment Exchange setting, but it does prevent an AFP from being paid if the waiver / template is Outstanding. This feature was designed for users that want to ensure all documents, including conditional waivers, tier vendor waivers, sworn statements, etc. are collected and accepted before payment is released.
Report Updates
- Unexported Applications for Payment Report
This report has historically retuned unexported AFPs that are in Approved status. This update will allow users to pull unexported AFPs in any status. - Compliance Report
This report has historically returned compliance requirements with a status of Required, Expired, and Expiring Soon for SOVs that were not fully billed. In other words, this report has not historically returned complaince requirements that are verified or those requirements that belong to fully billed SOVs. This enhancement will return all compliance requirements, regardless of status, and it will allow the user to include compliance requirements from fully billed contracts. Additionally, columsn have been added to the report for Expiration Date, Limit, and Last Upload.
Bug Fixes and Small Updates
- Fixed Required Digital Signatures Bug
To ensure Waivers/Templates are digitally signed when the Require Digital Signatures is selected, we have removed the Waiver/Template cover sheet that previously allowed subcontractors to submit documents via email or fax. This fix prevents users from bypassing the digital signature requirement. - Fixed Queued Payments Bug
Queued payables associated with a subsidiary entity now display at the top level. Previously, only payables associated with the top-level entity displayed, meaning company level treasury users could only queue payments for subsidiary entities at the project level.