Overview

The Winter '27 Preview release introduces Enhanced PDF Formats, a new no-code way to generate PDF documents for Salesforce records, along with a combined PDF report option for Bank Reconciliation, expanded Balance Sheet and Trial Balance reporting, and several enhancements to Sales Order allocation and Pack/Shipment workflows. It also includes a number of software corrections across Accounts Receivable, Accounts Payable, Banking, Financial Reports, and General Ledger. Most of these changes are optional and won't affect your current workflows unless you choose to use them. See Configuration Changes below for anything that does require setup.

Installation Notes

Installation links are available here.

Configuration Changes

Review configuration changes related to this release here.

In this article:

• New Features & Enhancements
  • Enhanced PDF Formats
  • Bank Reconciliation PDF Report
  • Financial Reports Hub
    • Budget vs Actual by GL Variable
    • Total and Grand Total Columns
  • Orders & Inventory
    • Allocation and Pack/Shipment Enhancements
• Important Update for Stripe Payment Link Users
• Software Corrections

New Features & Enhancements

Enhanced PDF Formats

Accounting Seed now offers Enhanced PDF Formats (EPF), a new way to generate PDF documents for Salesforce objects without writing code, as an alternative to the existing Visualforce based PDF system. You can upload a Word (.docx) template, map merge tags (placeholders you name yourself, like {{Billing.Name}}) to Salesforce fields, and generate customized PDFs for Billings, Master Billings, Bank Reconciliations, and virtually any other Salesforce object with a single click. Enhanced PDF Formats works alongside Visualforce rather than replacing it, so your existing Visualforce PDF formats and workflows remain fully functional and unchanged.

Bank Reconciliation PDF Report

You can now generate a combined PDF report directly from the Bank Reconciliation screen using the new Generate PDF Report option. It includes the reconciliation summary along with detailed lists of cleared and uncleared deposits and payments, each linked back to the underlying records. This is available alongside the existing Create PDF Summary and Create CSV File options, so your current export process is unaffected unless you choose not to use it. See this article for more information here.

Financial Reports Hub

Budget vs Actual by GL Variable

When you group a Financial Reports Grid report by Accounting Period, GL Variable (such as Department or Region), and Ledger, with Each Period to Prior selected, the Actual, Budget, Variance, and Variance % columns now display correctly for each GL Variable value within each Accounting Period. This makes it possible to compare budget to actual results by Department or Region within the same report.

Total and Grand Total Columns

Balance Sheet and Trial Balance (As Of) reports in the Financial Reports Grid have been updated to display a Total column that subtotals values at each grouping level below any time based grouping, such as Accounting Period, Quarter, or Year. Because Balance Sheet and Trial Balance accounts don't share a single normal balance, overall Grand Totals are not applicable for these report types and remain specific to Profit & Loss reports. See this article for more information here.

Orders & Inventory

Allocation and Pack/Shipment Enhancements

Sales Order allocation now supports filtering Allocate All (on the Sales Order's Allocate tab) by Warehouse and Location, giving multi-location businesses more control over which inventory is used to fulfill an order. See Allocate Inventory to a Sales Order (Standard Cost) or Allocate Inventory to a Sales Order (Average Cost) for details. Allocation behavior for serialized and kit products (bundles of multiple items sold as one line) has also been refined to work correctly with the new Warehouse/Location filter. On the Pack screen, Quantity to Pack and Quantity Shipped/Packed field calculations have been corrected, and the Ship? checkbox behavior has been refined for greater accuracy when packing and shipping orders. Review the Configuration Changes article for optional setup.

Important Update for Stripe Payment Link Users

Stripe Payment Link Connects Through the Accounting Seed Hub

Stripe Payment Link now connects through the Accounting Seed Hub (AS Hub) instead of its own separate connection. This change meets Salesforce's updated security requirements for connected apps.

• Payment links that you've already sent out to customers continue to work.
• On Payment Settings: the Configure Payment Link and Reconfigure Payment Link buttons are replaced by Authorize in Accounting Seed Hub and Re-Authorize in Accounting Seed Hub. On earlier releases, the old buttons no longer work.
• What to do:
  • Make sure the AS Hub is authorized.
  • If your org is on an earlier release, we recommend upgrading to Winter '27 Preview as soon as possible.

For details, see Stripe Payment Link Connects Through Accounting Seed Hub.

Software Corrections

Accounts Receivable and AR Automation

• When running the Payment Activities Job, Stripe ACH transactions that were declined or canceled by Stripe could remain stuck in a "Pending" status rather than updating to "Declined." Status mapping has been corrected to ensure failed Stripe ACH payments update to "Declined" as expected.
• Setting up Payment Link for Stripe in Accounting Settings no longer requires a separate authorization step. It now shares the central Accounting Seed Hub authorization, streamlining setup for administrators managing online customer payments.
• On the Request Prepayment screen, recently viewed records could remain visible in a GL Variable lookup field after the field was cleared. This has been resolved.
• When an automated prepayment payment failed in an open accounting period and the system could not automatically post and void the related cash receipt, the failure reason was not recorded on the cash receipt's Payment Reference field. This has been resolved.
• In the Cash Receipt Apply screen, search results for the Adjustment GL Account field on a billing line could render behind the billing lines grid, making them impossible to see or select. This has been corrected so search results display above the grid.
• In the Cash Receipt Apply screen, clicking the apply arrow on a billing line could display a "cash receipt balance cannot be less than zero" error even when the cash receipt had no remaining balance to apply. This no longer occurs.
• In the Cash Receipt Apply screen, clicking the unapply arrow on a billing line with both a Received Amount and an Adjustment Amount populated cleared the Received Amount but left the Adjustment Amount in place. Both fields are now cleared correctly.
• Users with the Accounting Manager or Cash In Accountant permission set (without AS Full Admin) could not apply or unapply a cash receipt to a billing, due to a missing field-level security grant on the Billing Cash Receipt object's Billing Line field. This has been resolved.
• When a chargeback was processed, the automated cash receipt process could incorrectly void the associated cash receipt, resulting in incorrect journal entries and bank deposits for both the original settlement day and the chargeback day. This issue has been resolved.
• A Cash Receipt that was the only unmatched transaction for its merchant and settled more than seven days after its payment date could remain permanently stuck, with no bank deposit or journal entry ever generated. This no longer occurs, as the matching window now widens automatically until the transaction is found.
• When a prepayment request email failed to send because of an invalid contact email address, the cash receipt could be applied and posted even though payment was never received. A task on the Cash Receipt now guides the user to delete the Cash Receipt and fix the email address whenever a prepayment email fails to send.
• Creating a Billing Credit Memo or Billing Cash Receipt in some organizations could trigger a "Too many SOQL queries" error. This has been corrected by removing unnecessary processing during that operation.
• When a cash receipt was applied to a billing line with an applied amount of zero under the Manual cash application method, unwanted zero dollar transactions were generated on the Cash ledger. This no longer occurs.
• On Cash ledgers, the Unapplied Revenue transaction created when applying a cash receipt incorrectly carried the Product, Project, and Project Task from the billing line instead of the values entered on the cash receipt itself. This has been fixed.

Accounts Payable and AP Automation

• When a new vendor invoice email arrived as part of an existing email thread, Email to Payable could attach it to an already posted and paid payable instead of creating a new draft payable, causing the new invoice to go unnoticed. This has been corrected so a new draft payable is created whenever the matched payable is already posted.
• When creating a payable from a recurring payable failed due to an underlying validation error, users saw a confusing "field not editable" error instead of the actual cause, making the real issue difficult to identify. This has been resolved so the original, more informative error message is now displayed.
• Vendors could be submitted for ACH payment processing without a remittance email on file, leaving them accepted but unable to be processed with no clear error shown, and bulk vendor uploads sometimes displayed no success or failure confirmation at all. These issues have been resolved. An AP Remittance Email is now required prior to ACH upload, a "Submitted to Repay" activity note is logged on the vendor record, and bulk uploads display an on-screen confirmation banner with itemized results.
• Uploading eligible vendors for ACH payment processing could fail with a "Read timed out" error, and the vendor information was never actually sent to the payment processor. This issue has been resolved.

Banking

• Bank Direct Connect's transaction sync could occasionally create duplicate transactions due to how it re-fetched data by date window. This has been resolved by moving to a newer sync method that tracks changes precisely and prevents duplicates, with no other change to the sync experience.
• Completing a bank reconciliation whose statement date fell two or more periods after the last closed accounting period could display an incorrect GL Ending Balance, resulting in an inaccurate GL difference. This has been fixed.
• Starting a new bank connection could fail with a "This content is blocked" error when the bank's consent screen would not load inside an embedded frame, affecting new connections to certain banks. This issue has been resolved by restoring a standalone consent flow.

Financial Reports

• Repeatedly expanding and collapsing line items while drilling down into a Financial Reports Hub profit and loss report could cause the browser tab to run out of memory and crash, even on reports with very few transactions. This issue has been resolved.

GL and Transactions

• Billing Cash Receipts and AP Disbursements (application records) could be deleted in accounting periods where Close AR or Close AP was enabled, even though posting and unposting were correctly blocked. These records can no longer be deleted in soft-closed periods.
• With Large data optimizer enabled, when a Transaction's amount was adjusted for a rounding plug during posting, the related Financial Cube Transaction record was not always updated to match, causing the Transaction and its Financial Cube Transaction to fall out of sync by a small amount. This issue has been resolved.

Ramp Integration

• Reimbursement Payables now use the Ramp Reimbursement Id as the Payee Reference, so a second reimbursement from the same merchant for the same employee no longer fails the uniqueness check. (Version 0.16.0-1)

Return to top