Known Issues · SFDO Accounting Subledger
Customers with large numbers of Ledger Entries (>200k) may see time outs in the Accounting Scheduled Job. Because that job queries for null values in the Accounting Set Name and Primary Object Id fields, and because null values are not included in indexes by default, the nonselective query times out....
In Review ·Reported By 3 ·Updated 12 days ago
If a User creates a $0 Opportunity, with a $0 Allocation, when the Accounting Subledger Batch Job runs appearing successful but instead no Ledger Entries are generated.
In Review ·Reported By 2 ·Updated 12 days ago
Users can now customize Accounting Sets to map data in source records to fields in Ledger Entries, including the Transaction Date. If one record in an Accounting Scheduled Job has a Transaction Date that does not fall within an open Accounting Period, it causes all records in the batch to fail, even...
In Review ·Reported By 0 ·Updated 12 days ago
If a user reduces the Payment Amount on a paid Payment after initial Ledger Entries were generated, adjustment Ledger Entries will be created representing the correction. The Fulfills An Accrual field is incorrectly checked on the adjustment Payment Ledger Entry record.
In Review ·Reported By 1 ·Updated 19 days ago
When support for Multiple Accounting Sets is enabled, Accounting Data Record Type filters are not respected in active Accounting Sets. Accounting Subledger creates Ledger Entries for all active Accounting Sets, regardless of record type.
In Review ·Reported By 1 ·Updated 2022-04-18
When using Accounting Subledger for NPSP, if customer writes off a pledged Opportunity payment, a Ledger Entry record is created that credits the original GAU Allocation instead of the receivables account identified by the Default Accrued Account Code. The resulting Ledger Entry records do not properly...
Fixed in version SFDO 234.4 ·Reported By 1 ·Updated 2022-02-16
Users can now set the Transaction Date on Ledger Entries to a different value than their creation date. This can be achieved by creating and configuring an Accounting Set and mapping a date field in your source records to the required Transaction Date field. However, the transaction date on the ledger...
No Fix ·Reported By 1 ·Updated 2022-01-13
When the Payment is not created at the same time as the opportunity, the Payment allocation converts all the allocations to Percentage allocations when creating the Allocations on the Payment. And these Payment Allocations Percentages that are determined are truncated. When the nightly Subledger Accounting...
Fixed in version NPSP 3.210 ·Reported By 6 ·Updated 2021-12-15
When using a custom Accounting Set that leverages: - 4 Objects - Relationship to Primary and Relationship to Secondary have different relationship names from the tertiary object -- ex. relationship to Opportunity is named npsp__Allocation and relationship to custom Payment Object is GAU_Allocation This...
Fixed in version Accounting Subledger 1.36 ·Reported By 2 ·Updated 2021-12-06
In an Org that has Accounting Subledger installed with a single-object Accounting Set Active, changing the Fund Name does not generate the correct data. If you change the Fund Name of the Allocation Ledger Entries are reversed and redone, but not the Payment and Transaction.
No Fix ·Reported By 0 ·Updated 2021-11-11
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.