Latest Release: October 2026 (20.3.238)

Entering a negative gift

Staff users can reduce the amount attributed to a financial entity (fund) or gift item by entering a gift with a negative amount. A negative gift typically represents money moving out of a fund rather than money received from a donor.

Key features

• A new Enter negative credit screen under Fundraising for selecting a contact and product and entering a negative gift amount.
• Supports transaction options including batch selection, transaction date override, order type, and source code.
• Includes an option to suppress the order confirmation email sent to the contact.
• Negative gifts can be reversed but cannot be unapplied or adjusted.

Key use cases

• Transferring fundraising funds: When gifts must be moved from the original fund (financial entity) to a different fund as a lump sum (rather than gift by gift), enter a negative gift on the source fund and an offsetting positive gift on the destination fund.
• Applying administrative or processing fees: When a percentage of gifts to a restricted fund needs to be assessed as a fee after the gift is received, set up a dedicated gift item for the fee (for example, “Gift Expenses” or “Stripe fees”) pointed at the same fund as the original gift, with its GL account set to an expense account. Enter a negative gift for the fee amount against that gift item, selecting a payment method for the offsetting cash or Accounts Payable entry.
• Splitting funds to a foundation receiving fees: When a foundation takes a small fee on funds raised for a chapter or affiliated charity, a negative gift removes the fee amount from the fundraising fund. An offsetting gift adds it to the foundation's operating fund, keeping both the accounting system and iMIS reporting in sync.

How it works

Go to Fundraising > Enter negative gift. Select a contact and product, enter a credit amount, and set the transaction options, then click Submit. For more information, see Entering and reversing negative gifts.

Additional display type options for value list fields in Form Builder

Form Builder now offers more flexibility in how value list fields appear to users. Form designers can choose a display type that best fits the field's purpose, the number of available values, and the experience they want to give respondents. Single-select fields can appear as drop-downs or radio buttons, and multi-select fields can appear as checkboxes or as a multi-select drop-down with type-to-filter support.

Key features

• Display type options for single-select fields: Values can be shown as a drop-down or as radio buttons. The first option is selected by default.
• Display type options for multi-select fields: Values can be shown as checkboxes or as a multi-select drop-down.
• Type-to-filter in multi-select drop-downs: Users can type to narrow the list and then select multiple options, which makes long lists easier to work with.
• Contextual availability: The display type options are hidden when Add as text field is selected, since the field is then captured as free text rather than from a value list.

Key use cases

• Short lists with high visibility: Use radio buttons for single-select fields with only a few values, so respondents can see every choice at a glance without opening a menu.
• Compact forms: Use a drop-down for single-select fields with many values to save space and keep the form clean.
• "Select all that apply" questions: Use checkboxes for multi-select fields with a manageable number of values, so respondents can see and choose several at once.
• Long multi-select lists: Use the multi-select drop-down with type-to-filter for large lists, such as chapters, interests, or committees, where scrolling through checkboxes would be cumbersome.

How it works

In Form Builder, add or select a value list field on the form. In the field's properties, locate the Display type options:

• For a single-select field, choose Drop-down or Radio buttons. The first option in the list is selected by default.
• For a multi-select field, choose Checkboxes or Multi-select drop-down. With the multi-select drop-down, users can type to filter the list and select multiple options.

Additional Enhancements

• One-off payments for Stripe direct debits - Stripe direct debits now support one-off payments in addition to recurring (AutoPay) payments, across all supported regions and transaction types. An AutoPay license is not required. The Retrieve processed payments from Pay Central scheduled task must be enabled and scheduled so that iMIS receives the final payment status.

Upgrade changes

• More selective sanitization of encoded characters - Sanitization introduced in HotFix #1 for the July 2026 (20.3.231) release now evaluates spaces and special characters, such as %20 for a space, as in the following HTML: <a href="https://www.example.org/documents/Annual%20Report.pdf">Annual Report</a>. This change allows staff users to link to files with spaces or special characters in their names when editing RiSE pages. Disallowed input, such as malicious scripts, is still sanitized.
• Spaces in communication hyperlinks are encoded automatically - Previously, if a hyperlink in a communication contained a space in its address, the external service that delivers the email replaced the space with a plus sign (+), and recipients who clicked the link were taken to an error page. Now, iMIS encodes spaces as %20 before the message is handed off for delivery, and the delivery service leaves the encoded address unchanged. This applies to both Advanced Email and regular email communications. Staff users no longer need to type %20 in place of spaces when adding a link.
• Amplitude Analytics requires cookie consent - Amplitude Analytics now loads only when the cookie consent banner is enabled and a visitor accepts Analytics and statistics cookies. If the visitor rejects these cookies, has not yet responded to the banner, or the banner is disabled, Amplitude Analytics does not load and no Amplitude cookies are placed.
• iMIS Assistant cookies are now essential cookies - Cookies related to the iMIS Assistant are now considered essential cookies, so the iMIS Assistant is not affected by cookie consent choices. Staff users can use the iMIS Assistant on the Staff site even if Amplitude Analytics cookies are rejected, have not been accepted yet, or the cookie consent banner is disabled.
• Embedded iframes restored in event Additional information fields - Embedded iframes from external sites, such as a YouTube or Vimeo video player, can again be entered into the Additional information field on an event, program item, and registration option. Content removed by sanitization introduced in the July 2026 (20.3.231) release must be re-entered.
• Better handling of undefined event contacts - Events whose Event contact was deleted in iMIS 2017 no longer fail to load after upgrading to iMIS EMS. These events now load and can be edited normally. The related step has been removed from the pre-upgrade checklist because it is no longer needed.

Previous Releases

See 2026: Release Notes.