akoyaGO

Enhancements

• When data is removed from the Original Grant field, the Decision Date field will no longer be required, allowing users to save the form after removing the original grant amount.
• The Decision Date field on the Request will no longer auto-populate when the Original Grant is manually entered.

Bug Fixes

• Removed the Payment Processing Dashboard from the non-accounting app as it is not utilized.

 

  akoyaGO with Accounting

Enhancements

General (affects all areas)

• The Interfund quick create form will now auto populate default accounts as defined in Accounting Settings.

Grants Management

• The Request Payment and Payment or Requirement business process flows have been retired to simplify the experience and reduce duplicate/legacy pathways. This will result in fewer competing workflows and smoother user experience. Best practice is to utilize quick create forms to create records as they will contain all required fields to send to accounting.
   
• When data is removed from the Original Grant field, the Decision Date field will no longer be required, allowing users to save the form after removing the original grant amount.
   
• Request Payment adjustments/reversals will now show the owner as the user who initiated the action rather than inheriting the owner of the original payment record for enhanced accountability and clear audit trails.
   
• When using the quick create form to create a new Request, the Title will default to [Request Type] to [Applicant]. The Fund Name has been removed from the Title as default behavior.

Donor Management

• The Gift Payment business process flow has been retired to simplify the experience and reduce duplicate/legacy pathways. This will result in fewer competing workflows and smoother user experience. Best practice is to utilize quick create forms to create records as they will contain all required fields to send to accounting.
• Gift Payment adjustments/reversals will now show the owner as the user who initiated the action rather than inheriting the owner of the original payment record for enhanced accountability and clear audit trails.

 

Bug Fixes

Grants Management

• We have fixed a bug in which GOverify was not running on payment creation when the payment was created by using the approval button on Request and Est. Grant Pay Date was blank. GOverify will now run in that scenario.
   
• In cases where users are shown a popup after clicking Send to Accounting, when the account is unusual for example, selecting ‘Cancel’ would send the payment to accounting anyway. ‘Cancel’ should cancel the action entirely.

Donor Management

• Recurring gift emails are now associated with the correct recurring gift record, improving tracking and reducing confusion when reviewing communication history.
   
• In cases where users are shown a popup after clicking Send to Accounting, when the account is unusual for example, selecting ‘Cancel’ would send the payment to accounting anyway. ‘Cancel’ should cancel the action entirely.
   
• We have fixed a bug in which duplicate gift payments were being created when the Auto Create Next Gift option was selected. This was happening on subsequent recurrences after the creation of the initial gift.

New Features

• Pledge Redesign: Pledge processing has been redesigned. Users can automate scheduling pledge payments, write off pledge accruals, and run pledge reporting. More information is available in the Pledges knowledge article.

 

  Business Central

Enhancements

• The Net Asset Close feature will now include the Function dimension so that net asset entries can be grouped by Function.

Bug Fixes

• We have fixed a bug in which the Cleared Date field was not reliably updated on Request or Gift payments after bank reconciliation.
   
• The Net Asset Close process will now require that a Journal Template/Batch be chosen in order to run the process.

 

  GOapply

Enhancements

• We have added a tool to retry/resubmit third-party responses after a failure. Some submissions failed due to third-party storage limits, and users had limited ways to recover without manual intervention.
  • This can be found in the Diagnostics dropdown tool in Status Tracking records.
     
• Organizations can now customize the message users see after completing a phase, better matching your tone and next-step guidance.
   
• Email Confirmed, Status, and Status Reason fields on GOapply Users have been locked as they should not be manually updated.
   
• Two new system views have been added to the GOapply Users table – GOapply Users Pending Approval and GOapply Users Pending Email Verification.
   
• GOapply Reviewer Enhancements
  • We have made it so that if Anonymous = Yes in Review Group settings, the Primary Contact column will be hidden in the view of review group applications to ensure true applicant anonymity.

Bug Fixes

• We have fixed a bug in which when scholarship matching criteria were blank, the system didn’t handle that scenario as intended. If Opt In Enabled = Yes on the Scholarship but the criteria is blank, the scholarship should still be available for matching.
   
• We have fixed a bug in which, in the case that third-party response file uploads had the same name, the second was overriding the first and resulting in only one file being saved. Going forward, duplicate file names will not override each other and both will be allowed to exist.
   
• In cases where a submitted scholarship application was moved back to In Progress to allow applicant edits, the submitted PDF was not updating with those edits after the applicant resubmitted. This has been fixed and the most current submitted PDF file will be saved to the status tracking record.
   
• We have fixed a bug in which checkbox field types added to the Organization Profile were not rendering the choices correctly. The selection options will align with the options listed in the CRM field.
   
• Simple Form Builder: We have fixed a bug where the number input would multiply by 100 when the value precision was set to 0. When the value precision is set to 0, the form will only accept whole numbers in that field.
   
• We have fixed a bug in which the ZIP Code field in the pre-mapped Fiscal Sponsor/Payee panel was not allowing applicants to input a value.
   
• We have fixed a bug in which the Add to Review Group button was missing from the toolbar on Status Tracking records in the akoyaGO (nonaccounting) app.
   
• We have fixed a bug in which Program was not mapping when it was set as a default value in the form builder.
   
• We have fixed a bug in which default values were not working when the question was not visible to the applicant.
   
• Imported GOapply Users via the Add GOapply Users table will not longer be processed if their user record does not contain an email address.

 

  GOfund

Bug Fixes

• We have fixed a bug in which users were experiencing an error when trying to submit a recurring grant recommendation.
   
• We have fixed a bug in which the fund Start Date Mode was overriding the Fund Statement start date when the mode was set to Fiscal Year. In this scenario the default start date will be the first day of the fiscal year ONLY IF Fund Statement Start Date does not contain data. Otherwise, the default start date will be the date listed in Fund Statement Start Date.
   
• Attempts to Repeat This Grant to organizations that have since had their nonprofit status Revoked will not be allowed. GOfund will now validate that organizations do not have a Tax Status of Revoked before submitting a grant recommendation.
   
• When address fields had been removed from the GOfund Eligible Constituents view, the list of organizations to recommend to would display No location under each. If address fields have been removed from that view, the list will simply display the organization name.

 

  GOdonate

Enhancements

• A new tool has been created on GOdonate Transactions (CRM) where users can create the gift(s) in the case that the process was disrupted and the gift(s) didn’t get created.

Bug Fixes

• Some GOdonate transactions in a “Requires Payment Method” Payment Status couldn’t be deactivated cleanly, leading to confusing errors. We have updated the handling so the system can respond more appropriately when users attempt this action.
   
• We have fixed a bug in which the hamburger stack icon was not displaying correctly on dark backgrounds.
   
• We have fixed a bug in which donors were receiving duplicate gift confirmation emails.
   
• Funds with long Formal Fund Names will now wrap in the dropdown funds list under the Donate Now button.