March 25, 2026

Enhancements

• Why it matters:
  Reduces accidental recurring gifts and improves donor confidence, especially in fast‑paced or language‑barrier environments.

Note: This feature allows the Giving Manager to specify which funds default to Recurring and which default to One-Time. As the donor selects different funds from the drop-down menu, the giving form will switch between Recurring and One-Time accordingly, and vice versa.

Learn More!

 

March 10, 2026

Enhancements

ChMS Engine Update for ParishSOFT Donor Match

• What changed 
  The ChMS Engine was updated to recognize new ParishSOFT donor validation responses during contribution submission. When donor-related validation errors are returned (member not associated with family, mismatched organization, or fund organization), the engine now performs a donor match retry. If realignment fails, the error is logged and surfaced for admin resolution.
• Why it matters 
  This prevents contributions from being applied to incorrect members or families and ensures donor alignment issues are resolved when automated matching cannot be completed successfully.

Tiny Font Size for Portrait Mode Printing

• What changed 
  Adjusted report rendering logic to address extremely small font sizes when printing reports in portrait mode.
• Why it matters 
  Restores report readability and consistency for users printing in portrait orientation.

Rock RMS – Handle Whitespace Values Returned from APIs

• What changed 
  Whitespace-only values returned from Rock RMS APIs are now treated as empty strings during processing.
• Why it matters 
  Prevents fund refresh failures and allows integrations to complete successfully when API fields contain only whitespace.

Bug Fixes

Integrate People Fix

• What changed 
  Multiple issues in the Integrate People (ChMS) workflow were resolved, including subscription handling, category mapping, integration enablement behavior, fund creation logic, and cleanup of stale People ChMS configuration data.
• Why it matters 
  Improves stability and consistency across People and Giving integrations.

Retry Returns Failing Due to OfflineTransactionsEnabled Criteria

• What changed 
  Corrected Retry Returns logic so ACH returns and refunds are properly submitted when OfflineTransactionsEnabled is disabled for ParishSoft.
• Why it matters 
  Restores accurate return and refund reporting in ChMS systems and ensures donor giving histories remain correct.

Admin – Org Merge 500 Error

• What changed 
  Fixed a 500-error encountered when accessing Org Merge during billing. The Org Merge menu option was also reorganized under Accounts.
• Why it matters 
  Admins can now safely perform org merges without encountering errors.

CICD Admin – Invoice Report Showing Multiple Line Items

• What changed 
  Resolved an issue where invoice reports displayed duplicate line items when multiple payment records existed for the same payment method.
• Why it matters 
  Ensures invoice reports accurately reflect billing data and reduces admin confusion.

Infrastructure / Internal Improvements

• Automated test restructuring and stability improvements (Playwright)
• CICD and reporting accuracy fixes
• Improved logging and diagnostics for fraud and integration scenarios

March 2, 2026

Bug Fixes

HOTFIX: L2/L3 Element Lengths

We resolved an issue introduced by recent Gateway updates affecting Level 2 and Level 3 (L2/L3) data handling. These changes were causing Gateway API portal requests from Workday to fail for Amplify customer invoice payments due to field length constraints.

This fix updates the L2/L3 elements to ensure they comply with the required field-length specifications, preventing transaction failures due to invalid data sizes. As a result, invoice payment processing through Workday now completes successfully without interruption.

February 24, 2026

Enhancements

More Reliable Syncing of Imported Transactions

What’s improved:

• We’ve corrected an issue that prevented the system from recognizing imported recurring gifts. 
• Imported recurring gifts now behave consistently with native recurring gifts. 

This ensures imported transactions are processed correctly and appear accurately in transaction reports.

Improved Processing of Kiosk & POS (TriPos) Transactions

What’s improved:

• Transactions are now processed and validated by the kiosk before being recorded in the system.

This improves transaction reliability, prevents invalid submissions, and ensures accurate reporting and capacity management by only counting completed transactions.

More Control Over Kiosk & POS (TriPos) Forms

What’s improved:

• Forms displayed on kiosks now enforce kiosk-specific rules, including disabling recurring gifts and restricting fund selection.

This prevents invalid transactions and ensures kiosk forms align with merchant account and payment processing requirements.

More Complete Reporting of Offline Transactions

What’s improved:

• The Gifts Report now correctly populates the Source field for offline transactions created through the Bulk Donation feature. Inapplicable action menu options are hidden for offline records.

Reports are clearer and more accurate, and users are prevented from attempting actions that do not apply to offline donations.

Bug Fixes

Non-Existing Fund on a Transaction Caused an Error Message

What’s fixed:

• Reports and exports were updated to safely handle transactions that reference funds that no longer exist, preventing exceptions during editing or reporting.

This improves system stability and ensures imported or legacy transactions do not break reports or user workflows.

Missing Donor Information Caused an Error Message

What’s fixed:

• A missing payment profile caused an error message.
• An empty email address caused an error message.

Account Updater can now process more edge cases without errors, reducing failed updates and improving reliability in production.

Legacy Mobile Apps Users Unable to Submit Donations

What’s fixed:

• Legacy Mobile Apps were unable to accept new one-time and recurring gifts. 

Legacy mobile clients can once again process gifts without backend failures, minimizing disruption for users on older applications.

January 27, 2026

Enhancements

More Reliable Settlement Testing

We’ve improved how settlement testing works behind the scenes to make results more predictable and dependable.

What this means for you:

• Settlement processing is now easier to test and validate
• Fewer unexpected issues caused by changes outside the system
• More consistent behavior when reviewing settlement scenarios

This helps ensure settlements behave as expected before changes reach production.

Improved Handling of MinistryOne Transactions

We corrected how MinistryOne transactions are identified within FMS.

What’s improved:

• MinistryOne transactions now use the correct source classification
• Older source values are still supported to prevent disruptions

This ensures transactions flow correctly and appear consistently in reports.

More Control Over Donor Transaction History Views

Admins can now control how much transaction history is shown by default on donor profiles.

What’s new:

• A configurable default date range for donor transaction history

This reduces the need to repeatedly adjust filters and makes reviewing donor activity faster.

Smoother Rock Sync Experience

We’ve made several improvements to Rock syncing to increase accuracy and clarity.

What’s improved:

• Multi‑fund donations no longer create duplicate imports
• Transactions that are skipped now clearly show a “skipped” status
• Fraud‑declined transactions receive unique order numbers for clearer tracking

These updates improve reliability and make sync behavior easier to understand.

Bug Fixes

Complete Donor Statement Exports

We fixed an issue that could cause missing donor records when exporting statements.

What’s fixed:

• Using “Select All” now correctly includes every donor in the export
• Merged or repeated donor records are handled consistently

This ensures CSV exports fully match the donor list you expect.

Consistent MinistryOne Reporting

We resolved a reporting issue related to outdated transaction source values.

What’s fixed:

• MinistryOne transactions are now consistently classified
• Reporting discrepancies caused by older source values are eliminated

Security Improvements

Continued Security and Compliance Enhancements

We made behind‑the‑scenes updates to strengthen security and meet modern standards.

What this means for you:

• Improved handling of sensitive data during testing
• More secure validation patterns across the platform
• Continued alignment with security scanning requirements

These updates help keep Giving and FMS secure and reliable.

Updated March 26, 2026 12:17