Overview  

The Spring ’26 release brings new features, enhancements, and software corrections.  For information about release timing and cadence, see the Release Schedule.

Installation Notes 

Installation links are available here.

Configuration Changes

⚠️ Review these three important configurations and other optional changes in the Configuration Changes article.

• Before your Spring '26 Production push: Ensure Allow Activities and Track Field History are enabled on the GL Account Mapping object.
• If you use Stripe to receive payments in Accounting Seed, you must upgrade to Spring 26 by May 15, 2026.
• If you use Large Data Optimizer (LDO), then once upgraded to Spring '26 you must explicitly turn these settings on, in the Enablements page.

Contents

Updates

• Stripe Integration Upgraded to Payment Intents API
• Payments Automation for Canada
• Unit Test Updates

Software Corrections

• Financial Reports
• Bank Direct Connect and Bank Reconciliation
• Accounts Receivable
• Accounts Payable
• Large Data Optimizer
• Multi-book Accounting
• General Ledger and Other
• Orders and Inventory

Return to top

Features and Enhancements 

Financial Reports Hub

Custom Fields with Field Sets

Custom Fields are now supported in the Financial Reports Hub through field sets. Field sets let you define which additional fields are available in the report grid without changing the underlying data model. Once configured, you can select these fields as additional columns or filters in your reports. Additional filter options have also been added to the filters panel, including Date, Type, Sub Type 1, and Sub Type 2. For more information review the Financial Reports Hub Setup article.

Financial Reports Drill-down 

Drill down functionality has been added to financial reports. For report details composed of monetary calculations, you can now drill down to the transactions which comprise the total. The resulting General Ledger Drill-down report can be saved as a new report. 

See the Financial Reports Grid article for more information. 

Suppress Zero 

The option to suppress zero amounts on reports has been added to Financial Reports Hub Settings. When enabled, zero amounts for accounts that have no transactions and for accounts where transactions net a zero amount are suppressed and do not appear on the report. 

Source type for transactions 

A new column called Source Type has been added to the General Ledger report. Source type can be used on the report as a column, or to group by source document. 
 

 

Manage Large Data Optimizer in App and By Source Document

You can now enable/disable the Large Data Optimizer (LDO) feature directly from the Enablements page for AR, AP or JE.  The three settings give you complete control to turn them on or off selectively based on your organization’s needs. 

⚠️ Important: If you have LDO enabled, then once you upgrade, you must complete these configuration changes so that use of this feature is not interrupted.

Bank Direct Connect

Bank Transaction Matching - Developer Updates

Bank Direct Connect now supports custom transaction matching strategies. This feature is intended for developers and implementation partners who want to extend how bank transactions are automatically matched to source documents. Developers can implement the new BDCMatchStrategy Apex interface to plug custom matching logic into the BDC pipeline — for example, matching by vendor name similarity or against an external data source. Custom strategies are registered through a Custom Metadata record and run alongside Accounting Seed’s built-in matching, with platform safeguards (date filtering, duplicate prevention, and GL account validation) applied automatically. For more information review the BDCMatchStrategy — Developer Usage Guide. 

Coming soon - Enhancements to the Agents Package, based on this matching feature.

Bank Direct Connect - Improved Logging and Reports

Bank Transaction Download has been enhanced with improved logging and monitoring for all connected providers (Plaid, Yodlee, and Salt Edge). Each download job now records detailed success and failure counts per connected bank account, making it easier to identify which accounts experienced issues during a download. A new Bank Transaction Download Exception Report is also available, providing a structured view of failed or incomplete download events to help troubleshoot accounts that didn’t sync properly. For more information review the BDC - Troubleshooting article.

⚠️ Important - Enable Track Activities and Field History on the GL Account Mapping object; see this article for steps.

Bank Direct Connect - File Import Match Name now includes Customer Accounts

The Bank Transactions File Import Match Name feature used to have logic for Accounts with the Accounting Type set to Customer & Vendor or Vendor. In this release, this logic has been extended to include Accounts which have their Accounting Type set to Customer.

 Match Refund Cash Disbursements 

When payments to Vendors are refunded for any reason, we recommend creating negative Cash Disbursements to capture this activity. In Bank Direct Connect, the ability to match these refund bank transactions to negative cash disbursements has been added to the Unmatched Bank Transactions tab. 

See the Unmatched Bank Transactions article for more information.

Multi-Book - GL Account Control on Cash Receipts and Cash Disbursements

For Multi-Book (Accrual and Cash) ledgers, there may be times where the GL Account specified on the Cash Receipt or Cash Disbursement should be used for both Accrual and Cash ledgers during the posting process.  In other instances, the Accrual ledger should use the GL Account specified on the Cash Receipt/Cash Disbursement and the related Cash ledger should use the GL Account selected in the Unapplied Revenue GL Account (for Cash Receipts) or Prepaid Expense GL Account (for Cash Disbursements).

A new checkbox has been added to the Cash Receipt and Cash Disbursement objects to address this. On the Cash Receipt, checking "MB: Use Credit GL Account for both Accrual and Cash Ledgers" ensures the specified Credit GL Account is used across both ledgers during posting. On the Cash Disbursement, checking "MB: Use Debit GL Account for both Accrual and Cash Ledgers" applies the same logic for the Debit GL Account. Organizations not using these checkboxes will see no change to existing behavior. Review the Configuration Changes article for more information.

Note: there are no changes for Cash Only Ledgers

 

Software Corrections  

Financial Reports

• General Ledger Detail Report – Missing Source Record
  In the Financial Reports Hub, the Source Record field was blank on the General Ledger Detail report for transactions posted before the Winter ’26 release. This has been fixed.
• Ledger Inquiry report exported to Excel 
  For some Standard Financial Report users, exporting the Ledger Inquiry report showed an Excel error and resulted in empty Excel files. The issue was related to diacritical marks. The Excel error may still be seen as this is related to the file format and is a platform limitation. However, the Excel export now shows the Ledger Inquiry data as required.

Bank Direct Connect (BDC) and Bank Reconciliation

• Bank Feed Connection Not Refreshing
  Some Bank Direct Connect users experienced bank feed connections that would not refresh, preventing new transactions from being imported. This issue has been resolved. To learn more on troubleshooting bank transactions refresh errors, see article.
• With Plaid as the provider, the system attempted to download transactions from all connected Financial Institution Accounts (FIA), including those that were not mapped to a ledger and GL Account, causing a delay. This issue has been fixed.
• Bank Rules scroll bar issue
  The scroll bar was not displayed on the BDC
  Create Rule screen when there were three or more actions. This issue has been resolved.
• Create PDF Summary in Bank Reconciliation
  The Create PDF Summary and Create Excel Summary buttons on the Bank Reconciliation record did not generate output in some cases. Error handling has been improved and this issue has been resolved.

Accounts Receivable 

• Sola ACH “On Hold” Status Mapping
  Sola ACH payments with an “On Hold” status from the payment processor are now being handled correctly as payments in a pending status in Accounting Seed.
• Send Billing PDF Error
  Non-admin users received an error when attempting to send a Billing PDF via email. This issue has been resolved.
  • Negative Cash Receipts on Activity Statements
    Negative Cash Receipts were not being displayed correctly on Activity Statements. This has been corrected; they are now displayed once and with the Type set to “refund”. Cash receipts that are voided (both positive and negative) continue to be displayed once and show their Type value as “reversed”.
  • Negative Cash Receipts that were fully applied to billings were displayed on Activity Statement PDFs with a Type of “paid” instead of “refund”. This has also been fixed.
• Recurring Billing Line and GL Variable selection 
  In some instances, certain GL variables could not be selected on the Recurring Billing Line. This was due to a special character in the Advanced Line Manager Description/Comment. The issue has been resolved, and special characters no longer affect the selection of the GL Variable.
• Unable to save Global Default Payment Processor for AR Payments 
  Some AR Automation users encountered an error when setting the Global Default Payment Processor on the Payment Settings page. This issue has been resolved.
• Cash Receipt Refund Confirm button   
  For users who had taken the Memo field off the Refund field set, the Refund component was not responding when the Confirm button was clicked. This issue has been resolved.
• French Translation – Apply screens issue  
   On an org with Canadian French translations enabled, selecting any values in the Apply screens' Posting Status field (Statut de Comptabilisation) did not display existing billings with those statuses.  This has been resolved on both the Cash Receipt and Credit Memo apply screens.

Accounts Payable 

• An issue affecting the voiding of Cash Disbursements and Cash Receipts in archived accounting periods has been addressed. Users now see a clear error message when attempting to void a record in an archived period, ensuring closed periods are protected.
• A file access issue caused an error to be sent to the Cash Disbursement from Mulesoft, even though the issue does not affect the actual payment. This issue has been resolved. 
• An error was caused when multiple payables were paid by one Cash Disbursement and some Payables did not have a file associated. This has now been fixed. 
• In the Payment Proposals Basic Search results section, the Vendor and Ledger columns were displaying incorrect information. This has now been addressed. 
• Issue with the Add Row button on the Payment Proposal Line Manager 
  The Add Row button did not create a new row on the Payment Proposal (PP) when the record had Aggregate by Payee checked and an existing saved row with a payable record. This issue has been resolved. 
• Transactions on Discounted Foreign Currency Cash Disbursements   
  In a multi-currency org when foreign currency payables with a discount were paid, the resulting Cash Disbursements did not calculate the discount transaction correctly.  This has been rectified so that the Cash Disbursement transactions are generated using the currency conversion rate on the Cash Disbursement.

Large Data Optimizer (LDO) 

• Billing Cash Receipts (BCR) not deleted on Cash Receipt Screen 
  For Large Data Optimizer users, Billing Cash Receipts were not deleted after clicking the Delete BCRs button on the Cash Receipt detail page. A batch failure error message was shown in the Apex Job. Both issues have been fixed. 
• BillingCashReceiptLDVUnpostBatch continues to run after BCRs are deleted  
  Sometimes, the BillingCashReceiptLDVUnpostBatch job continued to run, even after BCRs, deleted using the Delete button, were deleted. This issue has been resolved and no additional jobs run after the BCRs have been deleted.

Multi-book Accounting

• Expense GL Account on Payable Not Updating on Cash/Multi-Book Ledgers
  On Cash or Multi-Book Ledger configurations, if the GL Account on a Payable Line was updated after a Cash Disbursement was applied to the Payable, it did not also update the Expense Transactions on the related Cash Disbursement. This has been corrected.
• Switching from the Accrual to Accrual & Cash Accounting method caused Billing Cash Receipt transactions with a negative applied amount to be incorrect.  This issue has been resolved in Spring '26 Preview version 3.377.
• Error message displayed when clearing required field on Accrual & Cash ledger 
  A field custom validation exception was displayed when users attempted to clear a required field on the Accrual and Cash Ledger. This has been corrected.

General Ledger and Other

• Create Accounting Periods Skipping First Period
  When using the Create Accounting Periods function with a fiscal year that does not match the calendar year, the first accounting period in the range was skipped. This issue has been resolved.
• Unposting After Switching Between Header Level Posting and Line Level Posting
  When a record was posted under one type of Post Setting (Header Level Posting or Line Level Posting) and this was later changed, unposting a record posted in the prior Post Setting left orphaned transactions. This has been fixed, and all associated transactions are now properly removed on unpost regardless of the current Post Setting.
• Project Task Selection During Amortization  
  When adding a project/project task through the amortization wizard on a payable, the project task field was not filtered to the specific project selected. This issue has been resolved. 
• Improved error handling on Payroll File Import 
  The Payroll Import utility now displays the appropriate error message when a AR/AP GL Account is specified in the CSV file without the required Account field entered.
• Deployment errors related to the AcctSeed.ContentDocumentLink trigger 
  Some users encountered deployment errors tied to the ContentDocumentLink trigger. These errors have been resolved.

Orders & Inventory

• Inventory Balance History Batch Error
  Users with a large number of Inventory Movements encountered a “Too many query rows” error when the Inventory Balance History batch job ran, preventing Inventory Quantity Available History records from being created. This has been fixed to handle larger record sets.

Return to top