Overview

The Summer ’26 Push release builds on Summer ’26 Preview with significant new capabilities including Report Folders and Total and Grand Total Columns in the Financial Reports Hub, AR Prepayments for Sola and Stripe users, expanded Cash Receipt Apply functionality with line-level Billing application and Credit Memo balance application, a new universal Bank Direct Connect institution search, and Salt Edge Non-regulated bank support. This release also introduces two new features: the Ramp Integration and Salesforce Hosted MCP Support.

Summer '26 Prerequisites

⚠️ In order to upgrade your org to Summer '26, the following configurations are required: 

• Update Lightning Web Security setting - review steps here.
• Update your GL Account Mapping object to Allow Activities and Track Field History - review steps here.

Installation Notes

Installation links for Summer '26 are available here.

Configuration Changes

Review configuration changes related to this release here.

In this article

• New Features and Enhancements
  • Ramp Integration
  • Salesforce Hosted MCP Support
  • Financial Reports Hub
    • Report Folders
    • Total and Grand Total Columns
    • GL Drill Down: Clickable Transaction Names
    • Delete Reports
    • Support for Large Transactions Volume
    • Variance and Variance % Columns
    • Translated GL Variable Names in Reports
  • Accounts Receivable
    • AR Prepayments for Sola and Stripe
    • Apply Credit Memo Balance to a Cash Receipt
    • Cash Receipt Apply: Line-Level Billing Application
    • Master Billing Defaulting Enhancements
    • Cash Receipt Apply Screen: Set Applied Date in Bulk
    • Adjust a Remaining Cash Receipt Balance
    • Stripe ACH: Pre-populated Contact Information
  • Accounts Payable & AP Automation
    • Payment Failure Alerts
    • Payable Discount Reduction on Check Void
    • New Permission Sets
    • AP Automation: Vendor Enrollment Status Updates
    • Disable Bank Account Defaulting on Pay Screens
    • Paid Payment Status on $0 Payables
  • Bank Direct Connect
    • Salt Edge Support for “Non-regulated” Providers
    • New Financial Institution Search
  • Reports
    • Accounting Dashboard
• Software Corrections

New Features and Enhancements

Ramp Integration

This integration connects Ramp, a corporate spend management platform, with Accounting Seed. The integration automates the flow of spend data between the two systems across six sync pipelines in two directions: master data (GL accounts, accounting variables, and vendors) is pushed from Accounting Seed to Ramp so cardholders have the correct coding options, and transactional data (card transactions, bills, and reimbursements) is pulled from Ramp into Accounting Seed as journal entries, payables, and cash disbursements, without manual data entry. For further details on the Ramp Integration, see Ramp Overview. Note that this is a separate package.

Salesforce Hosted MCP Support

Accounting Seed now supports Salesforce Hosted Model Context Protocol (MCP), enabling AI agents to connect directly to your financial data and custom business logic in Salesforce. With MCP configured, your accounting team can interact with your data in Accounting Seed through natural language in AI clients such as Claude or ChatGPT, querying financial records, generating reports, processing payables, calculating tax, and automating workflows without leaving the AI interface.

For setup instructions and the full list of available tools, see Setting Up Salesforce Hosted MCP with Accounting Seed.

Financial Reports Hub

Report Folders

You can now organize your financial reports into folders in the Financial Reports Hub. Folders allow you to group related reports together, control who can view or manage each folder, and keep your report library organized as it grows. You can create folders, move reports between them, and manage folder-level access from within the hub. For more information see the Financial Reports Hub Grid article.

Total and Grand Total Columns

You can now add Total and Grand Total columns to the Profit & Loss in the Financial Reports Hub. Total columns display a subtotal at each column grouping level, and the Grand Total column appears at the far right to provide a consolidated view across all groupings. Pivot Mode must be enabled to use these columns. Column settings are saved with the report when you save or use Save As. Review the Financial Reports Hub Grid article for more details.

GL Drill Down: Clickable Transaction Names

Transaction names on the GL Drill Down and GL Detail reports in the Financial Reports Hub are now clickable, linking directly to the related Transaction record. This lets you navigate from a report row to the source transaction without leaving the report. For more information, see the 'Drill down to a Transaction or Source record' section in this article.

Delete Report(s)

You can now delete one or more reports directly from the Financial Reports Hub home page. A new Delete Report(s) button has been added next to the View Report button. Select one or more reports, click Delete Report(s), and confirm in the dialog to permanently remove the selected reports.

Support for Large Transactions Volume

For organizations with a large volume of transactions, the Financial Reports Hub now supports the ability to query and render large datasets with greater speed and scalability. Contact Accounting Seed Support if you have more than 1M transactions and would like to set up Financial Reports Hub. This is currently supported for US customers.

Variance and Variance % Columns

You can now add Variance and Variance % columns to Profit & Loss, Balance Sheet, and Trial Balance reports in the Financial Reports Hub. These columns calculate the amount change and percentage change between time periods, such as month-over-month or quarter-over-quarter, without any manual calculations. When multiple periods are selected, in the Variance Mode, choose between Prior Period Only mode (shows just the most recent comparison) or Each Period to Prior mode (compares every consecutive pair). For Balance Sheet reports, Variance columns reflect the change in ending balance between periods. Variance columns also support Actual vs. Budget comparisons when a Budget Ledger record (with Ledger Type = Budget and posted Budget transactions) is selected in the Columns panel. Column settings are saved with the report.

See image below of Variance and Variance % columns and Variance Mode:

Translated GL Variable Names in Reports

The Financial Reports Hub now reflects any changes to GL Variable (GLAV) names made through the Salesforce Translation Workbench. Renamed GLAV labels appear throughout the hub in the Columns panel, Filters panel, Column grouping area, and Row grouping area, so your reports display the terminology your organization uses rather than the default GLAV names.

See example of GL Variables that have been renamed:

Accounts Receivable

AR Prepayments for Sola and Stripe

Organizations using our Sola or Stripe integrations now have the ability to request prepayments from customers. Using the new Receive Payment button on the Account record page, you can send your customer a payment link without requiring a Billing. A “draft” Cash Receipt is created; then when the customer completes payment, the system attempts to post the Cash Receipt for you. For more information review the AR Prepayments article.

Apply Credit Memo Balance to a Cash Receipt

You can now apply a Credit Memo balance directly to a Cash Receipt on the Cash Receipt Apply screen, then use this increased balance to apply to your Billings/Master Billings. Use the new Credit Memos option to find and select credit memos to apply. For more information, see the Apply Cash Receipts article.

Updated calculated fields: The screen now displays Cash Receipt Amount, Credit Memos Applied, Total Applied to Billings, and Available Balance to Apply, so you can see the complete application picture in one view. 

 

Cash Receipt Apply: Line-Level Billing Application

When applying a Cash Receipt, you can now search for and apply to individual Billing Lines using the Billings and Billing Lines option on the Cash Receipt Apply screen. This allows you to apply payments at the line level for greater precision when a customer's payment corresponds to specific line items on an invoice. This is available for all ledger types: Accrual, Accrual & Cash, and Cash.

• Accrual ledgers: No configuration required. Line-level apply is available immediately.
• Cash and Accrual & Cash ledgers: For Cash Basis ledgers, this enhancement allows you to apply cash to the specific GL Account on a Billing Line when the Cash Application Method is set to Manual on the Enablements page.

See the Configuration Changes article for steps to update the Cash Application Method and the two field sets related to this enhancement. Review the Apply Cash Receipts article for more information.

Master Billing Defaulting Enhancements

When creating a new Master Billing record, Accounting Seed now automatically defaults the Billing Contact, Payment Processor, and PDF Format from the associated Account and Ledger records, consistent with how these fields are defaulted on standard Billing records. Administrators can configure a default Master Billing PDF format on the Ledger record or in the Multi Ledger Defaults page.

The Master Billings list view now includes additional columns for better at-a-glance tracking. The PDF Email Status field defaults based on the default picklist value that is set.  See the Configuration Changes article for steps to make these updates. The Customer lookup has been amended to an optional filter, similar to the one on the Billing; there are no configurations for this change.

Cash Receipt Apply Screen: Set Applied Date in Bulk

You can now set the Applied Date for multiple Billing rows at once on the Cash Receipt Apply screen. Select one or more rows, enter a date in the new date field, and click Update Dates to apply the same date across all selected rows in a single action. The entered date must fall within an open Accounting Period.

 

Adjust a Remaining Cash Receipt Balance

You can now adjust the remaining balance on a Cash Receipt to correct records where the balance is inaccurate. See the Apply Cash Receipts article for steps.

Stripe ACH: Pre-populated Contact Information

When adding an ACH payment method, the name and email fields in the Stripe payment form are now automatically pre-filled with the contact information from the Primary Contact field on the Account record. Users can edit either value before saving. If no Primary Contact is set on the Account, the user can enter these values.

Accounts Payable & AP Automation

Payment Failure Alerts

When a Repay payment fails, has a Needs Attention status, or is Canceled, the system now creates a Salesforce Task on the Cash Disbursement and assigns it to the Cash Disbursement Owner. The Task includes troubleshooting details in the comment so your team can resolve payment issues quickly.

Payable Discount Reduction on Check Void

When you void a Check (Cash Disbursement) that included an early payment discount, the system now automatically reduces the Discount Amount on the related Payable record to reflect the reversal.

AP Automation: Vendor Enrollment Status Updates

Accounting Seed now automatically receives and records vendor enrollment status updates from Repay. When a vendor’s enrollment status changes, a standard Salesforce Task is created on the vendor’s Account record and appears in the Activity Timeline, capturing the Type, Activity Date, Status, and Description of the enrollment event. This feature is active automatically for all organizations with AP Automation configured.

Disable Bank Account Defaulting on Pay Screens

A new optional setting, Disable Bank Account Defaulting, is now available on the Enablements page. When enabled, the Bank GL Account field no longer auto-populates on the Payable Pay and Pay Batch screens, requiring users to explicitly select a Bank GL Account each time. This gives organizations greater control over payment accuracy. To enable this, review the Configuration Changes.

Paid Payment Status on $0 Payables

Payables with a total amount of $0 are now automatically set to a Payment Status of Paid when posted. If your organization requires that a $0 Payable also have at least one AP Disbursement applied before it moves to Paid status, you can enable the AP Disbursement Required setting on the Enablements page. Review the Configuration Changes for steps to do this.

New Permission Sets

Two new permission sets are available in Summer ’26 Preview 

Note: These out of the box permission sets have permissions to Accounting Seed classes, objects, etc. If the feature being configured requires permissions to standard Salesforce objects, fields or other permissions, you would need to create a custom permission set to add them.  This is because Salesforce does not permit packaging standard Salesforce permissions with our out of the box permission sets.

• AS Hub Authorization: an out of the box permission set for the Salesforce user designated to authorize the Accounting Seed Hub connected app.
  • Related to the note above: Financial Reports Hub users will need to add permissions to the Account object (standard Salesforce object) as a custom permission set.
• AS Invoice Automation User: an out of the box permission set for users who work with invoice automation. Both permission sets are additive and should be assigned alongside existing Accounting Seed permission sets. See the Configuration Changes for steps to assign them.

Bank Direct Connect

Salt Edge Support for “Non-regulated” Providers

Saltedge API Documentation defines “regulated” as Whether the Provider is integrated via a regulated channel under Open Banking/PSD2. For banks that don’t meet this requirement, Salt Edge offers connectivity using secure tokens or screen-scraping. Financial institutions that were not supported earlier by our Salt Edge integration may now be supported. If you previously attempted to connect to your bank and received an “unsupported bank” message, review the related New Financial Institution Search release note below and then search for your bank.

New Financial Institution Search

Bank Direct Connect’s Bank Settings now features a unified institution search experience. A New Connection button replaces the Manage Providers button; instead of selecting a connection provider first, you can search for your financial institution by name and results are shown across all supported providers (Plaid, Yodlee, Salt Edge Regulated, and “Unregulated”). When you select your bank, you are routed directly to the provider’s connection widget with your institution pre-loaded. All four providers are now active by default, eliminating the need to manually enable them.

Reports

Accounting Dashboard

The Accounting Dashboard now defaults to View Dashboard As: Me instead of running as the logged-in user. This change prevents installation failures for organizations that have reached Salesforce’s limit on dynamic dashboards. If your organization has not reached that limit and prefers the dashboard to run as the logged-in user, you can change this setting manually within the dashboard. See the Configuration Changes article for steps to do this.

Software Corrections

Accounts Receivable & AR Automation

• In Cash Basis ledgers, applying a Cash Receipt to a Billing Line that used a Tax Group did not generate the associated tax transactions on the Billing Cash Receipt record. This has been resolved.
• When a Cash Receipt, with the Check Number populated, is refunded, the same Check Number is now also populated on the related refund Transaction’s Check Number field.
• Master Billing email drafts showed HTML tags when the Send to Contact field was manually populated. This has been fixed.
• An error occurred when adding Stripe ACH payment methods, preventing users from saving new payment methods to an account. This has been resolved.
• When posting a large batch of Billing Cash Receipts with Proportional Distribution cash application on a multi-book ledger, the system was looking up each receipt’s billing line details one at a time, and large batches could exceed Salesforce’s limit on database queries and cause the entire batch to fail. This is now fixed: we retrieve all the needed line details for the batch in a single query up front, so batches of any size approve and post successfully.
• When voiding a Cash Receipt on a ledger using the Accrual and Cash accounting method, the Cash Ledger Transactions on the voided Billing Cash Receipt record were not properly balanced, meaning the cash-basis sub-ledger did not net to zero on the reversal. This could cause the cash-basis General Ledger to reflect incorrect balances. This issue has been resolved.
• When creating a refund for a posted Cash Receipt that had a non-default Cash Flow category, the refund Cash Receipt incorrectly defaulted to the system-wide Cash Flow category instead of inheriting the category from the original Cash Receipt. This has been fixed.
• The automated Billing email job failed when processing invoices with large PDF attachments. The job had its size set to 40 billing PDFs processed per batch transaction. With standard invoices this was not an issue, but with large PDFs (e.g. 2–3 MB due to embedded images in a custom VF page) a Salesforce limit was reached (Apex heap limit), causing an error. This has now been fixed with a new setting added to the Enablements page that controls this batch size. See Configuration Changes if you email large billing PDFs.
• When posting a Billing Cash Receipt on a Cash Basis ledger (or the Cash ledger of an Accrual & Cash setup) with an Adjustment amount and no Billing Line selected, the system incorrectly generated GL transactions for the Adjustment amount and distributed it across billing lines. Since no cash is exchanged for an adjustment, this has been resolved so Adjustment amounts on Cash ledgers only reduce the Billing balance and do not generate GL transactions. This applies whether the Cash Application Method is set to Proportional Distribution or Manual.

Accounts Payable & AP Automation

• When posting a set of Cash Disbursements (67 or more) using Line Level Post with an Accrual & Cash ledger, the system was looking up each record’s line details separately, one database query per record. This ran into a Salesforce SOQL limit on how many queries can run in a single transaction, causing the entire batch to fail to post. This has now been resolved.
• On an Accrual ledger an error occurred when trying to update the Expense GL Account on a Payable with a Cash Disbursement applied. This has been fixed for Billings and Payables on Accrual ledgers. Note: on Cash Basis ledgers this action is still not permitted.
• The help text on the Invoice Comment field on Payable Lines was incorrect. This has been corrected. To fix this in your org, see Configuration Changes.
• An overflow and overlap issue affected the File Preview Carousel, causing display problems when previewing files. This has been resolved.
• Payable Discount Reduction on Check Void: When you void a Check (Cash Disbursement) that included an early payment discount, the system now automatically reduces the Discount Amount on the related Payable record to reflect the reversal.
• Automated payments were failing to submit due to an issue with how phone numbers were validated during payment processing. This has been resolved.
• The Payee Reference field was enforcing an incorrect character limit during payment processing, causing payments with longer payee reference values to fail. This has been fixed.
• Phone numbers containing an extension were causing payment submission errors. This has been fixed so that payments with extension-formatted phone numbers process correctly.
• In the Advanced Line Manager, clicking the edit icon on a field did not activate edit mode on the first click. Users had to click a second time to enter edit mode. This was found to be the result of the number of fields displayed in the ALM Columns field set and the length of the Expense GL Account and GL Variable record names. This issue has been resolved.
• When a user without record-update permissions performed certain actions, an unhandled system error occurred instead of a clear error message. This has been resolved.

Banking/Bank Direct Connect (BDC)

• When you run the Update All action in BDC for Salt Edge to bring in new bank transactions, the system now tracks the last transaction it successfully processed so the next run can pick up where it left off. Previously, if a transaction was still reserved (pending or not yet finalized by the bank) when a batch was processed, the system at times moved past it, causing that transaction to get skipped on later runs once it was finalized. This issue has now been fixed.
• When a Bank Transaction was matched to a Bank Deposit, the Bank Deposit’s Reference field was overwritten by the Bank Transaction’s description. This has been fixed.
• Bank transactions (of credit/debit type) with a $0.00 amount and/or an empty currency code caused an error in Yodlee and resulted in the transaction being skipped. This issue has been resolved.
• A change we added to email users about BDC failures had the unintended consequence of a Salesforce limit to be reached. This in turn caused some bank transactions not to be refreshed. We have removed the email functionality for now; Automated Job Result records continue to flag any failures.
• After upgrading to the Spring ’26 release, Bank Direct Connect integrations began running a full historical import instead of the expected incremental scheduled download job, causing unexpected transaction data to appear. This has been resolved so that scheduled jobs run as incremental downloads.

Financial Reports

• For some customers the General Ledger Detail did not allow the expansion of GL Account rows to see the underlying transactions. This was a permissions issue for the AS Hub user, specifically for fields on the Account object. Review the Configuration Changes article for steps to do this if you are experiencing a similar issue.
• The General Ledger Detail report was displaying incorrect totals for the sum of Debits and Credits columns due to certain posted transactions being excluded from the column calculations. The calculation has been corrected and now accurately reflects all posted transactions.
  Recommendation: Re-generate and re-export the General Ledger Detail report.
• Orgs that did not have Lightning Web Security enabled failed to be upgraded to Summer '26 with a “Dynamic imports are not allowed” error.  We have removed this dependency so that the Summer '26 release can be installed on orgs without this setting enabled. Note: the setting must be enabled in order to use Financial Reports Hub.
• Journal Entries posted to the Retained Earnings GL Account were not reflected in the Financial Reports Hub. This issue has been fixed.

GL and Transactions

• When posting Payables or Billings in organizations using Line Level Posting, the Description field on the resulting GL Transaction records was left blank. This has been fixed so the Description is populated correctly on the transaction.
• Switching accounting methods and then voiding/reversing a Cash Disbursement that was applied in a different accounting method caused reversing transactions not to be created. For example:
  • When the Ledger of the original AP Disbursement (APD) is Accrual & Cash basis, but the Cash Disbursement Void or reversing APD is done after switching to Accrual basis, the Void APD now only has accrual transactions, since the cash ledger is not being used.
  • When the Ledger of the original APD is Accrual basis, but the Cash Disbursement Void or reversing APD is done after switching to Accrual & Cash basis, the Void APD now only has accrual transactions because there are no cash transactions to reverse.
  Recommendation: If your organization switched accounting methods and reversed or voided Cash Disbursements, review those transactions.
• When batch posting multiple Journal Entries with a combined total of more than 1,000 Journal Entry Lines, depending on the number of lines, the Journal Entries were sometimes marked as Posted, but some transactions failed to post to the GL. This has been resolved so that the selected Journal Entries are posted with the correct number of transactions. (Fixed in version 3.401)
  Recommendation: If your organization batch posted multiple Journal Entries with a high line count prior to this release review those records and re-post as needed. Contact Accounting Seed Support if you have questions.
• On Cash Basis ledgers, the GL Variable from the Billing Line was not getting set on the Billing Cash Receipt transaction that posts to the GL Account on the Billing Line. This has been addressed.

Ramp

• Ramp Version 0.15.0-1
  • Bills with descriptions longer than 255 chars in Ramp were not getting synced into Accounting Seed.  A new 'Ramp Description' field (long text -131072 chars) has been added on the Payable Line to accommodate longer descriptions.  See configuration changes.
  • When a user, without access to the Account Number field on the Account object, attempted to sync Vendors, an error prevented normal syncing. This has been addressed. See configuration changes.

Other

• Creating a new Ledger in a developer sandbox failed at times with an error because the system was trying to look up default ledger information that didn’t exist yet. This is now fixed so creating a Ledger in an empty org no longer errors.
  
  

Return to top