Accting Subledger Release Announcements

Accounting Subledger is excited to announce version 1.29 will begin pushing to Production orgs tonight for the Spring Release! Please look for this version in your org over the next couple of days, and enjoy the following enhancements:

• ACCOUNTING SUBLEDGER CAN TRACK REVENUE OR EXPENSES
  • Accounting Subledger can now categorize and track Ledger Entries for both Revenue and Expenses.
  • Specify the category of your Ledger Entries in your Accounting Set(s), using the the new Accounting Set UI (details below)
  • Activate Multiple Accounting Set Support first (as a one-time step) in Accounting settings to use this feature.
  • See Decide Between Revenue and Expense to learn more. https://powerofus.force.com/s/article/ASL-Revenue-or-Expense

• SIGNIFICANT ENHANCEMENTS TO ACCOUNTING SETS (GROWTH EDITION ONLY)
  • New UI with Extensive Changes
    • Create new Accounting Sets in three straightforward steps
    • Specify one or more source Objects from any Salesforce object when generating Ledger Entries
    • Deactivate or edit existing Accounting Sets at anytime.
  • Support for Multiple Active Accounting Sets
    • Growth users can activate multiple Accounting Sets, and set the sequence in which they run.
  • See Put Your Accounting Sets Into Action to learn more. https://powerofus.force.com/s/article/ASL-Customizable-Accounting-Sets#ariaid-title4

• GROUP BY DUE DATE AND ALLOCATION CHANGE
  • Revenue or Expense Ledger Entries (from Pledges Only) can reflect their expected date of receipt.
    • See Group Your Ledger Entries to learn more. https://powerofus.force.com/s/article/ASL-Group-Your-Ledger-Entries

• IMPROVEMENT: GROUPING SCHEME INFERRED FROM LEDGER ENTRIES
  • The grouping scheme for existing records that already have Ledger Entries uses those existing records to determine whether it started Grouping By Due Date and Allocation or Allocation only.
  • It will continue to use the grouping scheme it started with, unless all ledger entries are reversed. At that point, it will use the Grouping Scheme currently selected for the Accounting Set, or the Global Settings (if Multiple Accounting Set support is not enabled).
  • Prior to this release, the Revenue Grouping Scheme was stored on the Opportunity, rather than inferring it from its Ledger Entries.

• ACCOUNTING SCHEDULED JOB IS NOW COMPATIBLE WITH CUSTOM OBJECTS
  • You can now run the Accounting Scheduled Job and generate Ledger Entries from Standard and Custom objects to generate Ledger Entries. Configure your Accounting Set based on the source Objects that you prefer.
    • Previously, the Accounting Scheduled job would only generate Ledger Entries from Opportunities, Payments, Allocations, and GAUs.
  • See Use the Accounting Scheduled Job With Custom Objects to learn more. https://powerofus.force.com/s/article/ASL-Configure-When-Accounting-Subledger-Creates-Accounting-Data#ariaid-title5

• OTHER IMPROVEMENTS AND CHANGES
  • We fixed a merge issue concerning missing API properties from the original component.

• LABEL UPDATES
  • Ledger_Entry_Settings__c
    • Default_Payment_Method__c
      • Old Label: Default Payment Method
      • New Label: Default Payment Method (NPSP Payment)
    • Default_Pledge_Code__c
      • Old Label: Default Pledge Code
      • New Label: Default Accrued Account Code
    • Default_Write_Off_Code__c
      • Old Label: Default Write-Off Code
      • New Label: Default Write-Off Account Code
  • Ledger_Entry__c
    • Fulfills_A_Pledge__c
      • Old Label: Fulfills a Pledge
      • New Label: Fulfills an Accrual
  • Opportunity
    • Revenue_Grouping_Scheme__c
      • Old Label: Revenue Grouping Scheme
      • New Label: DEPRECATED - Revenue Grouping Scheme