Skip to content

Release 1.5

Released 2026-11-04. Install links: Sandbox · Production.

Version 1.5 lets each fund carry its own receivable account, recalculates gifts when a GAU's accounting fields change, and fixes the Global Settings tab refreshing before its deployment finished.

Critical changes

Receivables can now be split by fund. Each General Accounting Unit can name a Receivable GAU: the GAU whose GL Code and name take the open (unpaid, not written-off) share of committed gifts allocated to it. GAUs with no Receivable GAU keep using the default receivables account, so an org that configures nothing sees no change.

What to expect after upgrading:

  • The upgrade itself does not recalculate anything. The open receivables of existing gifts stay on the default receivables account until each gift is reconciled.
  • Setting a Receivable GAU on a fund recalculates every committed gift allocated to that fund: immediately in real-time mode, or queued for the daily job in scheduled mode. Each gift's receivable is then reversed on the default account and entered again on the fund's receivable account.
  • The upgrade adds a Trigger Handler record, GAU_RunSubledger_TDTM on General Accounting Unit, which drives that recalculation. Confirm it exists and is active under NPSP Settings → System Tools → Trigger Configuration.
  • Add the Receivable GAU field to your General Accounting Unit page layout. See Receivable GAUs.

New

  • Receivable GAU on General Accounting Unit, with read-only formula fields showing the resolved receivable GL Code and name on GAUs and allocations, like the existing write-off fields. The open amount of a committed gift is split across its allocations in proportion to their amounts, rounded to the cent so the shares always add up to the open amount; any unallocated amount goes to the default receivables account. See Receivable scenarios.
  • Changing a GAU's name, GL Code, Receivable GAU or Write-Off GAU recalculates the committed gifts allocated to it, or queues them in scheduled mode.

Changed

  • A payment written off after the subledger already ran in the same transaction (for example through a flow that writes off a payment after another change) is routed through its GAU write-off accounts instead of entirely to the default write-off account.
  • A missing or inactive default payment, receivables or write-off account stops the calculation with a message naming the Default Accounts tab, instead of an unexplained error or a journal entry with a type label as its GL code.
  • Opportunities flagged Do Not Create Journal Entries are no longer marked Queued for Journal Entry Creation in scheduled mode.
  • The Fundraising Subledger Reports folder no longer carries a share to a user that only existed in the original development org. Set the folder's sharing in your org as you would for any report folder.

Fixed

  • In Fundraising Subledger Settings → Global Settings, the Enable Subledger and Disable Subledger buttons, the default record owner and the calculation mode now wait for their deployment to finish before the tab refreshes. The Enable Subledger button no longer reverts to its old label until the page is reloaded, and a failed deployment shows its error and puts the setting back.

Notes for administrators

  • The custom user lookup component from earlier versions is still installed but inert; it does nothing and references no code. It and its controller are removed in release 1.6, which will require upgrading through 1.5 first.