Additional Bug Patches for January 2026
💳 Custom Tax Deductible Overrides Ignored on Charges
Custom tax deductible amounts entered directly on individual charges were not always reflected on tax statements, causing the system to fall back to charge type defaults instead.
Custom tax deductible amounts entered directly on individual charges were not always reflected on tax statements, causing the system to fall back to charge type defaults instead.
This has been patched so charge level overrides are now fully respected during statement generation, giving you precise control over tax deductibility and ensuring statements accurately reflect the values you entered.
Module: Setting Tax Deductible Amounts
📝 Draft Receipts Incorrectly Numbered and Posted to Statements
Draft tax receipts were sometimes treated as official, receiving receipt numbers and appearing in the Statements tab instead of being clearly identified as drafts.
Draft tax receipts were sometimes treated as official, receiving receipt numbers and appearing in the Statements tab instead of being clearly identified as drafts.
This has been patched so the Draft Mode setting is now consistently honored, ensuring draft receipts are clearly marked, excluded from statements, and never mistaken for final records. This provides greater confidence and accuracy, especially for Canadian sites using CRA tax mode, while protecting all organizations from premature or incorrect receipt posting.
Module: Generating Receipts
📨 Legacy Mail Workflow Blocked when new Rich Text Editor Enabled
Sites using the new Rich Text Editor were unable to complete Legacy Mail workflows for billing or contribution paper mailings.
Sites using the new Rich Text Editor were unable to complete Legacy Mail workflows for billing or contribution paper mailings.
This has been patched so all steps in the Legacy Mail process now advance smoothly, allowing you to generate and send paper mailings without interruption and maintain reliable communication with your community.
💰 Quick Refund Incorrectly Disabled for New Payments
Newly created payments could incorrectly show refund warnings or appear ineligible for Quick Refund even when they were within the allowed timeframe.
Newly created payments could incorrectly show refund warnings or appear ineligible for Quick Refund even when they were within the allowed timeframe.
This has been patched so refund eligibility is now evaluated correctly, restoring Quick Refund when appropriate and making it easier to process timely refunds with confidence.
Module: Quick Refunds