Revised 11/14/2025
RELEASE NOTES: November 20, 2025
akoyaGO release notes give all users information about bug fixes, enhancements, and new features in the current release. This document describes all changes as of 11/20/2025. Documentation will be updated or created to reflect these changes. If you have questions, please contact your account manager or akoyaGO Support. Please be aware that you may need to refresh your browser, clear your browser cache, or log out/log back in to see the following changes after the day of the release.
akoyaGO
Bug Fixes
o We have enabled in-app notifications for all users, ensuring everyone receives timely updates regardless of their role. Previously, team users could not see in-app notifications.
O We have fixed an issue where saving a ‘Spouse/Partner’ connection on a Contact record would fail if the linked Contact record lacked an email address.
Enhancements
o Events and Event Attendees tables, previously accessible only to accounting users, are now enabled for non-accounting clients. This update revises navigation and security roles to grant access to these tables.
o A duplicate detection rule has been implemented that examines the Tax ID field on Constituents. This rule prevents the creation of duplicate records during data entry, ensuring data integrity.
o The system now enforces uniqueness on the Constituent and Contact Number. This prevents issues related to duplicate contact or constituent numbers, ensuring accurate linking and record identification.
o The tab on the non-accounting Scholarship form previously labeled "Scholarship Requests" has been relabeled to "Requested Scholarships" to align with table names and documentation.
New Features
o akoyaGO now supports the insertion of subgrids of child records directly into letter templates. This enhancement allows users to include detailed lists, such as request or gift payments. This improvement ensures that letters maintain best practices while providing the same level of detail previously achievable with Cloud Flows.
akoyaGO with Accounting
Bug Fixes
o General (affects all workspaces)
We have enabled in-app notifications for all users, ensuring everyone receives timely updates regardless of their role. Previously, team users could not see in-app notifications.
The workflow for sending payments to accounting previously did not check whether a payment record had already been processed. The update now validates that only payments with a blank or "Error" Payment Status are allowed to be sent.
o Grants Management
We've resolved an issue where the Document No. and External Document No. fields were incorrectly populated with the check number when sending to accounting. Now, these fields will correctly display the CRM Payment Number, ensuring data integrity and consistency across financial documents.
o Donor Management
We have fixed a bug in which Gift Payment adjustments were not processing when the only adjustment made was the addition or removal of a gift fee.
o Fund Management
We have improved visibility of fund handling notes by ensuring they display as banners, making important information easily accessible.
We have corrected the calculation of the Gifts Paid/Pledged field on Fund to use Net Amount instead of Amount to account for payment reversals to ensure accurate financial reporting.
We have standardized character limits for the Title fields in scheduled distributions and requests for consistency. Before this fix, users were experiencing errors when trying to create process scheduled distributions when the title exceeded 250 characters. The max. character limit on Title is now 250 characters.
An issue was identified where the "Total Foundation Matching Grants" field on Fund did not update to reflect inactive records. This bug has been resolved to ensure that the column accurately accounts for all records, including those that are deactivated. This fix ensures more reliable financial reporting and improves the accuracy of the foundation's grant tracking.
Enhancements
o General (affects all workspaces)
A duplicate detection rule has been implemented that examines the Tax ID field on Constituents. This rule prevents the creation of duplicate records during data entry, ensuring data integrity.
The system now enforces uniqueness on the Constituent and Contact Number. This prevents issues related to duplicate contact or constituent numbers, ensuring accurate linking and record identification.
o Grants Management
A new field called "Fund Acknowledgment Name" has been added to the Request Payment form in akoyaGO CRM. This field automatically populates with "Anonymous" if the fund or request is marked as anonymous. Otherwise, it displays the Fund Formal Name. This enhancement simplifies the creation of award letters by dynamically including the granting fund name or indicating anonymity, based on the fund's status.
An issue was identified where users could incorrectly send inactive request and gift payment records to accounting. This bug has been resolved by implementing a validation check that prevents inactive records from being sent to accounting. Users will now receive an error message stating, "Inactive records cannot be sent to accounting," ensuring that only active records are processed.
When initiating a refund for either a gift or grant, the posting date will now default to the current date instead of the original posting date. This change ensures that refunds are accurately recorded as they occur, reflecting the most likely scenario where a refund is posted on the current date rather than the original payment date.
o Donor Management
We have improved the way recurring gift transactions are managed when errors occur. Now, if a transaction fails and shows an "Error" status, it won't be retried automatically. Instead, staff members can choose from the following options:
Retry Now: This option retries the transaction immediately.
Retry at the Next Occurrence: This option retries at the next occurrence date and updates the status back to active or something other than error.
These changes ensure that the foundation staff has control over when charges are made, preventing any unexpected transactions for donors.
We have improved the way error information is presented for recurring gifts with error status. Now, when a donor encounters an issue with their recurring gift, they can view detailed error information directly on their account page in GOdonate. This enhancement ensures donors are well-informed about any issues and can take appropriate action more promptly.
We've streamlined the process of managing donors where the type is set as "Organization." Now, when you change the Donor Constituent on the Donor form, if the Primary Contact field will automatically populate with the Primary Contact from the Donor Constituent's record. This simplifies the creation of organization donors by leveraging existing information, ensuring a more efficient workflow. Users retain the ability to modify the Primary Contact after this automatic update, providing flexibility to make adjustments as needed.
The Gift Payment quick create form now incorporates dynamic field logic based on Payment Type. For instance, when a payment type of "pledge" is selected, the "Estimated Pledge Paydate" field becomes visible.
New Features
o General (affects all workspaces)
akoyaGO now supports the insertion of subgrids of child records directly into letter templates. This enhancement allows users to include detailed lists, such as request or gift payments. This improvement ensures that letters maintain best practices while providing the same level of detail previously achievable with Cloud Flows.
Business Central
Bug Fixes
o An issue was identified where deactivating funds in the akoyaGO CRM did not consistently block the fund in Business Central. This inconsistency could lead to funds receiving unauthorized postings. The synchronization process has been improved to ensure that deactivating a fund in CRM now reliably blocks it in BC, preventing any unwanted transactions.
o Users were experiencing an issue where clearing a voided ACH check overwrote data for a subsequent valid payment, reverting the payment status to "Received." The system now includes logic to recognize and ignore records that should not be affected by voided checks. This ensures that only the latest transaction controls the status, preventing unintended overwrites.
o Customer Refunds were failing when a privacy-blocked customer's refund was attempted and the General Journal did not have a default document number. This update provides a prompt for a posting date and a fallback mechanism to avoid insertion errors.
o During CRM merge operations, if only the secondary record is coupled, the process was failing by mistakenly using the AccountID instead of the CRM Contact Id. This update corrects the identifier used for coupling.
Enhancements
o A new feature has been introduced in Business Central that allows users to export their 1099 data to Excel to provide detailed financial data to external parties for printing and processing. The export includes essential columns such as Vendor ID No., Vendor Name, Vendor Address, Tax ID, 1099 Code, and 1099 Amount. This functionality ensures that all necessary data is readily available and organized for compliance and reporting purposes.
o ACH Remittance files will now include the description field from the vendor ledger entry, as well as the fund number and name.
o In this update, we've removed obsolete events and code from our system to enhance performance and maintain backward compatibility with Business Central version 27. The refactoring aligns with the new posting buffer design, ensuring a seamless transition and improved functionality in your invoice posting processes. This change is backward compatible, allowing for smooth operation across versions 26 and 27.
o We've introduced a new "Create Payment" button within the Vendor Ledger Entries. This feature is intended as an alternative to 'Suggest Vendor Payments'. Additionally, the system will perform a verification check through GOverify to prevent unauthorized payments. This enhancement aims to streamline the payment process and improve accuracy in financial transactions.
o The 1099 Liability field, removed during recent changes, has been reintroduced on Purchase Invoice lines. The system now prompts users when adding or removing IRS Form details to ensure synchronization of related tax attributes.
o The CRM merge process has been updated to handle scenarios where only one record is coupled to Business Central. The new logic supports flipping constituent numbers when necessary, and cancels merges when duplicate key conflicts are detected.
GOapply
Bug Fixes
o We have fixed a bug in which GOapply Users created via GOapply bulk import users were not receiving the invitation email if they were also GOfund users.
o A bug was identified where users could no longer display a dropdown list populated by a view for lookup fields in the Simple Form Builder. Instead, the only option was to use a panel. This issue has been resolved, and users can now choose between adding a panel or using a view to populate dropdown lists for lookup fields on requests.
o Value precision in the Simple Form Builder was not considering values ending in 0. For example, when entering $1000.10, the system incorrectly displayed it as $1000.1. The issue has been resolved by implementing a new function to handle currency value formatting. This ensures that the specified precision is retained, and trailing zeros are preserved. Now, currency inputs like $1000.10 will be displayed correctly without losing the trailing zero.
o We have resolved an issue where users encountered an error during the manual resubmission process of the GOapply application at Stage 3. This fix ensures that the resubmission process now completes successfully without interruptions.
o During registration in GOapply, users experienced a scrolling issue that prevented the selection of countries beyond Democratic Republic of the Congo. This update addresses the scrolling limitation.
o The GOapply password reset function was failing after the out-of-the-box email template name was modified. The new fix ensures that the password reset process references the email template using its GUID rather than its name, avoiding errors.
o GOapply Reviewer bug fixes
We have fixed a bug in which the Reviewer Request Score was not producing an average weighted score (when applicable according to Review Group settings).
We have addressed an issue where pending requests were not creating a review group application record if the request was already in review in another group. This fix ensures that if the original grant data is absent, requests can be seamlessly added to any review group matching the opportunity and phase.
The "Add to Review Group" button on Scholarship type Requests has been fixed to ensure that requests are only added to a review group if the student has opted in to the scholarship and ensures that only eligible and opted-in requests are added to Review Groups, improving the efficiency and accuracy of the review process.
Enhancements
o When dragging a mapped question into the form, both the question name and the question title will now default to the label that appears in CRM for that field. This change eliminates the need for users to manually adjust the question name to match the title, ensuring consistency and efficiency in form creation.
o The Active GOapply Status Tracking System View has been updated to improve user experience. The sort order has been changed so that the most recent records appear at the top, making it easier for users to track the latest status updates.
o The email template for existing GOapply users has been updated to include clearer messaging. The new language informs the recipient that they have been added to access the portal and instructs them to log in with their existing credentials.
o GOapply Opportunity forms now display a real-time character count for both the Summary and Description fields, including HTML formatting characters. This assists client program staff in adhering to maximum content length requirements.
o The CRM process named "Create GOapply Status Tracking" has been relabeled to indicate that it is deprecated. Users are advised to utilize the new "GOapply Advance To" functionality on Request instead.
o We've removed tables and fields from the GOapply CRM workspace related to GOapply V1 as that version is obsolete. The following changes have been implemented:
Removed Unnecessary Tabs: The "Pages" tab on Phases and the "GOapply v1 theme" column from the GOapply settings view have been removed to declutter the interface and improve navigation.
Deprecated Tables: Certain tables in the related menu, such as "Pages," "Fields," and "Entity Mappings," have been marked as deprecated to streamline data management and focus on essential functionalities.
o GOapply Reviewer Enhancements
A new setting has been added on the Review Group settings to allow individual reviewers to download attachments associated with their review group applications. This feature enhances accessibility to supporting documentation.
Reviewers now have the ability to download the complete submitted PDF along with any attachments from a GOapply Phase via a setting in Review Group settings. This enhancement provides comprehensive access to application documents during review.
A new report has been added called GOapply Review Responses by Reviewer that allows users to generate an out-of-the-box report similar to the GOapply Review Responses except it can be sorted by Reviewer, enabling users to view all responses by a Reviewer in a single, organized format. This enhancement provides a comprehensive record of how different applications were scored by individual reviewers.
GOfund
Bug Fixes
o We have fixed a bug in which GOapply Users created via GOapply bulk import users were not receiving the invitation email if they were also GOfund users.
o A bug in the grant recommendation process allowed a draft grant to remain in the shopping cart even after being submitted via the "Edit" page, leading to potential duplicate submissions.
o The GOfund Gift and Grant History views have been improved to enhance data accuracy. Records with a Payment Status of "Error" or "Reversed" are now excluded from these views. This ensures that only valid and successful transactions are displayed, providing users with a clearer and more reliable financial history.
o GOfund for Non-Accounting: The Funding Opportunity section, previously missing from the home page of the non-accounting app, is now visible. This fix ensures users can access all relevant funding opportunities directly from the home page, improving the overall user experience and accessibility.
o GOfund for Non-Accounting: A missing customization option for the Organization label in the non-accounting GOfund Settings has been added. This allows non-accounting users to tailor the "Grantee/Recipient Options" section to their requirements.
Enhancements
o We have introduced a new field that captures the last login date for GOfund users. This addition is designed to enhance the management of user interactions and communication strategies. Key aspects include:
New Field: A new field has been added to Contacts to capture the date and time a GOfund user last logged in.
Enhanced User Management: This feature enables the creation of views in Contacts to display the 'last logged in' date, helping to identify users who have logged in, never logged in, or logged in recently.
Improved Communication: With the ability to track login activity, targeted communications can be developed to encourage portal usage among invitees.
o The "Donor Portal Connections" view has been enhanced to include a "Last GOfund Sign In" column. This provides administrators with better insight into which donors have activated their GOfund accounts.
GOdonate
Bug Fixes
o An error was identified in the GOdonate system where the character limit for the "In memory or honor of" fields did not match between the GOdonate form and the CRM. This discrepancy caused gift and gift payment transactions to fail when a donor was added. The character limits have now been aligned to ensure consistency across both platforms, preventing such errors and improving the reliability of the donation process.