Released April 10, 2023

Installation Steps

Step 1: Check system requirements


  • macOS 10.14 Mojave
  • macOS 10.15 Catalina
  • macOS 11 Big Sur
  • macOS 12 Monterey
  • macOS 13 Ventura

CDM+ 12.1 runs natively on Apple Silicon and Intel.


  • Windows 10 x64 (1703 or later)
  • Windows 11 x64
  • Windows Server 2019 x64

Step 2: Backup your data

Back up all databases that will be updated to the new version. If you subscribe to CDM+ SAAS or Data Hosting you can contact support to make a backup or simply rely on the nightly backup.

Step 3: Download the installer

Click the link above to download the installer for your platform.

Step 4: Install the new version

Follow the Installing CDM+ guide to install CDM+. This will remove previous versions of CDM+ from your computer. 

Step 5: Update your database(s)

Open CDM+ and update your database(s) to the current version. 

Issues resolved in CDM+ 12.1.0 Beta 4


  • CDM-10897 Bug - Selecting 'Suffix' for email/phone number fields does not print a person's suffix name
  • CDM-10923 Bug - Text Giving Fees do not use 0 values from engage.fee_percentage
  • CDM-10970 Bug - Should not be able to delete a giving unit with a recurring or future one-time gift
  • CDM-10734 Story - Mark recurring gifts as cancelled when their payment method expires
  • CDM-10855 Story - Ability to add the default giving unit email address to Giving Unit results and reports
  • CDM-10881 Story - Make fcrecurringsetup an updatable view
  • CDM-10898 Story - Enhance transaction sync to validate any recurring setups create within the past week
  • CDM-10903 Story - Create view for checkGiftReport
  • CDM-10907 Story - Create view for DepositDesignationDetailByDepositDate
  • CDM-10908 Story - Create view for DonorsTransactionInformationSettlementDate
  • CDM-10911 Story - Create view for AccountSchedules
  • CDM-10919 Story - Create view for PCADepositDetailDesignationDetailwithContactInfo
  • CDM-10924 Story - Database function to calculate next occurrence of a recurring gift
  • CDM-10928 Story - Sort CheckGiftReport results
  • CDM-10931 Story - Sort DepositDesignationDetail results

Database API

  • CDM-10963 Story - Update pay endpoints to use for DonorID instead of fcgivingunit.code

Event Registration

  • CDM-10920 Story - Create view for PCAEventDepositDetails


  • CDM-10993 Bug - Users migrated to Paragon cannot process deposits
  • CDM-10999 Bug - Error occurs when processing deposits from Tempe

Payment Processing

  • CDM-10958 Bug - Updating a Tempe transaction through the view triggers for fgStewardshipTechnologiesTransaction will create a placeholder account for the given donor and payment type if one does not already exist, even if one is not needed
  • CDM-10978 Bug - Linking a merchant asset account can fail if some assets are inactive
  • CDM-10982 Bug - Typo in error when linking a merchant to an inactive asset account
  • CDM-10983 Bug - Typo in error when deleting an online recurring setup from outside of the API
  • CDM-10718 Story - Add pay.account_holder_link
  • CDM-10719 Story - Add pay.account
  • CDM-10720 Story - Add pay.schedule and pay.schedule_link
  • CDM-10721 Story - Add pay.transaction
  • CDM-10722 Story - Add pay.transaction_link
  • CDM-10727 Story - Add recurrence.schedule
  • CDM-10729 Story - Add database function to define frequencies throughout the program
  • CDM-10751 Story - Add status call to Tempe for pay.processor
  • CDM-10837 Story - Make fgstewardshiptechnologiestransaction an updatable view
  • CDM-10844 Story - Ability to merge tempe customers
  • CDM-10851 Story - Can use Deposit Processing through Tempe
  • CDM-10888 Story - Add Tempe Sandbox/Production results to pay.get_processors
  • CDM-10890 Story - Add table pay.settings
  • CDM-10905 Story - Use pay.account for expiring card notifications
  • CDM-10906 Story - Add account_type and check_type columns to pay.account
  • CDM-10910 Story - Create view for VerifyTransaction
  • CDM-10912 Story - Create view for DonorInformationOne
  • CDM-10918 Story - Add a utility to calculate the next occurrence of a recurrence schedule
  • CDM-10921 Story - Don't return an error if giving detail is inserted with null transactionreferencenumber
  • CDM-10927 Story - Return early in sync giver to sst if processor is not EGS
  • CDM-10933 Story - Update validate_bank_information trigger to prevent having Business and Savings account and check types
  • CDM-10939 Story - Add a view for SearchTransactions endpoint
  • CDM-10952 Story - Ability to query pde from a CDM+ database
  • CDM-10966 Story - Process Transaction Auth file
  • CDM-10967 Story - Process Transaction Settle file
  • CDM-10968 Story - Process Deposit Fee file
  • CDM-10971 Story - Offset and send out notifications for refunded and failed transactions
  • CDM-10980 Story - Refactor Search Transactions View
  • CDM-10988 Story - Send out notices for recurring transactions
  • CDM-10991 Story - Allow "0" in pay settings for payment/payroll merchant ID's
  • CDM-10995 Story - Repair recurring transactions for users who have migrated to Tempe
  • CDM-11008 Story - Handle repeat attempts at failed transactions


  • CDM-10899 Bug - Test mode is enabled when saving new payroll credentials

Record Frame

  • CDM-10779 Bug - Line Item Detail Blacked Out on Ledger Entry Screen on Ventura

Stewardship Technology

  • CDM-10936 Bug - Syncing historical recurring setups is using the start date when querying the SST endpoint, and should be using the created date

UCC Profiles Portal

  • CDM-10887 Story - Create database columns for small church profile

User Customizations

  • CDM-10975 Story - Update PCA views to return church code instead of ID


  • CDM-10884 Bug - Tax table utilities does not show for all Suran users