Skip to content

Release 1.4

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

Version 1.4 changes how the subledger tells GL accounts apart, adds a settings tab for the default receivables and write-off accounts, and makes every settings deployment report its result.

Critical changes

Accounts are identified by GL Code and GL Account Name together. Earlier versions netted journal entries by GL Code alone, so two payment accounts or two GAUs that share a code were treated as one account and took whichever name was found first. From 1.4 each code and name pair is its own account.

What to expect after upgrading:

  • Opportunities are not recalculated by the upgrade itself. An opportunity is reconciled the next time it, a payment or an allocation changes, or when you run the subledger on it manually.
  • When an opportunity whose existing entries carry one name for a code is reconciled, the subledger reverses the amount under the old name and enters it again under the name of the payment account or GAU that produced it. Existing entries are never edited or deleted.
  • If no payment accounts or GAUs in your org share a GL Code, nothing changes.

To review which accounts share a code, compare the GL Codes in Fundraising Subledger Settings → Manage Payment Accounts and on your GAUs.

New

  • Default Accounts tab in Fundraising Subledger Settings, where you edit the GL Code, GL Account Name and Active flag of the default receivables and write-off accounts. See Default accounts.
  • The Default Record Owner in Global Settings uses Salesforce's standard record picker, limited to active users, with the username shown beside each name. See Global settings.

Changed

  • Payments made through two payment accounts that share a GL Code get separate journal entries, one per account name. Moving a payment from one such account to another reverses the first and debits the second.
  • A journal entry's General Accounting Unit lookup now matches the GAU with the same GL Code and name, instead of the first GAU found with the code.
  • Accounting Period Settings waits for its deployment to finish and shows the outcome, instead of a "queued" message.
  • Every settings tab that deploys metadata disables Save and Cancel while the deployment is in flight.
  • A default receivables or write-off account cannot be deactivated from the settings app, because the subledger needs an active account of each type.

Fixed

  • The deployment spinner in the settings app cleared only after a page reload.

Notes for administrators

  • The custom user lookup component from earlier versions is still installed but no longer used. It is removed in a later release.
  • Known issue: after clicking Enable Subledger the button keeps its old label until the page is reloaded. The setting is saved.