Release Frequency and Schedule
Updates to our release frequency and schedule include doing our best to have three major (Push) releases each year (Spring, Summer and Winter). These releases will be automatically pushed to sandbox and production environments. Each Push release will be preceded by two Preview releases that will be made generally available and are not automatically pushed. Since all our releases (previews and pushes) are cumulative, the latest release will contain all the changes from the prior releases.
Our Release Notes for each Push release will be updated with the changes from each Preview release as they become available. Before the Push release is automatically pushed to sandboxes, these Release Notes will be updated with the changes made in that release as well. A good way to see incremental changes in each Preview and Push release is to view the respective “What’s New” video below.
As part of the Spring ‘24 release, Accounting Seed is pleased to inform you of our Spring ‘24 Preview 1 release. This article presents information about the enhancements available in this release. To print a copy of the Release Notes, right-click and select Print. In the Destination drop-down list, select a specific printer name or select Save as PDF. Then, click Save.
This preview release is now available to be installed in your org. We recommend that you first install the release into your sandbox environment and test it before installing it into your production environment. For more information on best practices with testing sandboxes, refer to Sandboxes: Staging Environments for Customizing and Testing and Considerations for Creating Sandboxes with Accounting Seed.
When you are ready to install this release, click here to access the installation link.
Our Convenience Fees feature includes some new fields on the related screens, which will automatically be added for new and existing customers. Configuration changes are only required if you have custom changes. For information about the related screens, please refer to the AR Automation – Convenience Fees section in these release notes.
- Auto-Reverse Journal Entries
- Receive Multiple Payments – Payment Method with long names
- Accounting Home Enhancements
- getSalesforceBaseUrl() Deprecated
AR Automation - Convenience Fees
With this release, if Cardknox is your Payment Processor, you can now include Convenience Fees on payments that are processed in Accounting Seed.
When configured, Convenience Fees will automatically calculate when you create a payment from an Account record, as well as on the Billing payment screens (detail and list view) based upon the selections that are made in the Payment Processor screen.
When a payment is processed with Convenience Fees charged, a Cash Receipt will be created that includes the Convenience Fee amount. This amount cannot be applied to Billings.
Convenience Fee Posting Changes
When the Merchant Download job runs, in addition to the other records created, two new Journal Entry Lines will be created on the Merchant Funds Journal Entry. These lines will post the Convenience Fees amount to the Convenience Fee GL Account and relieve the Unapplied AR GL Account. This posting change also applies to Convenience Fees that are charged via the PaymentSite.
Important: Due to the way in which Convenience Fees are now posted, we recommend installing the Spring ’24 Preview 1 release after settlement batch completes (in other words, after all customer payments have been recorded for the day).
New Convenience Fee Fields
New Convenience Fee fields have been added to the screens below. If you are using our default Lightning record pages for these screens, the new fields will automatically display. Otherwise, if you are using a custom version, the new fields will need to be added manually.
- Payment Processor
- Create Payment
- Receive Payment (Single Billing)
- Receive Payments (Multiple Billings)
- Cash Receipt (Appy/Unapply)
For more information about using Convenience Fees, refer to the Cardknox Convenience Fees article. Additionally, you can view Convenience Fees information in the Merchant Funds and T-Accounts article to see an Excel spreadsheet with T-Accounts that include Convenience Fees.
New Convenience Fee related Custom SObject Fields
New SObject fields that were added as part of this release have been included in the Custom Metadata Types and Fields article.
Financial Analytics Updates
Our Accounting Seed Financial Analytics app, which was introduced in the Winter ’24 release has been updated to include the following:
- The Profit & Loss Dashboard includes a visual indicator (values in green and red) to clearly distinguish increase and decrease amounts for the selected Accounting Period and the Last Period for Revenue, Expenses, and Net Profit / Loss.
- For the Revenue and Expense Dashboards, if you have a Sub Type 1 that is explicitly defined as “Other,” this category will include the “Other” transactions, as well as uncategorized (Sub Type 1 not selected) transactions.
- For the Balance Sheet Dashboard, if you have a Sub Type 2 that is explicitly defined as “Other,” this category will include the “Other” transactions, as well as uncategorized (Sub Type 2 not selected) transactions. The Transaction Listing will include “Other” transactions for both (if available) Assets & Liabilities.
- As with other Dashboards, the Expense Dashboard is interactive. Therefore, when you click an Expense category in the right chart, the Operating Ratio and Total Expenses on the left will be updated based upon the selected category, and the Transaction Listing will also be updated.
- The Transaction Listing on the Ledger Inquiry has been updated to include Inquiry Statistics (Opening Balance, Inquiry Amount and Balance) and Inquiry Result Count (total number of transactions).
Customer Requested Enhancements
Financial Institution Account field hover over
In Bank Direct Connect, from the Bank Transactions tab, you can now hover over the selected Financial Institution Account to view the full name of the institution.
Receive up to 200 Payments
With this release, the batch Receive Payments screen has been enhanced to support up to 200 payments.
Auto-Reverse Journal Entries
A new validation rule (No_Reversal_Period_for_Auto_Reverse) has been added to the Journal Entry object. When you attempt to create a Journal Entry from a Recurring Journal Entry record (with Auto-Reverse selected), if the subsequent Accounting Period does not already exist, an error message will display, which prevents the Journal creation.
Important Best Practices:
- To avoid issues with using the Auto-Reverse feature, it is recommended that the related validation rules NOT be disabled. For more information, refer to the Auto-Reversal information in the Create or Clone a Journal Entry article.
- If using the Auto-Reverse feature, future Accounting Periods should always already exist.
Receive Multiple Payments – Payment Method with long names
From the Billings list view, when receiving multiple payments, if the Payment Method includes long names, the characters will be truncated to between 90-100 depending upon the text. You can hover over the Payment Method to view the Bank/Card type and the last four digits.
Accounting Home Enhancements
We have enhanced our homepage to display information about new features, and we moved the release information to an in-app prompt. For this release, the new section focuses in on our AR Automation feature. Click the Learn how today link for more information. Also, please note that there is a hyperlink to access the Release Notes at the bottom of this new section.
We have also added the in-app prompt to our homepage, which provides a brief look at what is available in this release. You can click the available hyperlinks for more information. For example, click the Convenience Fees hyperlink in the prompt for more information about these fees. The in-app prompt includes a hyperlink to our Release Notes, as well as a link to our online community where you can provide feedback and product suggestions.
The in-app prompt will be updated with relevant information for each release.
In support of Salesforce’s deprecation of the getSalesforceBaseUrl() method in favor of the getOrgDomainUrl() method to get your org URL or getCurrentRequestUrl() to get the URL of an entire request on a Salesforce instance, we have followed the same path. This only affects Apex version 59.0 and above. In Accounting Seed, getSalesforceBaseUrl() has been deprecated on the following packages:
- Financial Suite
Activity Statement - Running Balance
The Running Balance on the Activity Statement was being calculated incorrectly in the Winter ’24 release. This issue has been resolved so that it calculates correctly starting from the first row as Amount + Running Balance from the previous row.
Note: We have had to remove sorting on the Amount field, which was added in the Winter ’24 Preview 1 release. This sorting option will be added back in a later release.
Unposted Billing records using AvaTax
There was an issue that occurred when a Billing was unposted in Accounting Seed, the record in Avalara’s AvaTax continued to display as “Committed.” This issue occurred because the Active AvaTax Endpoint field that is a part of Tax Settings was pointing to the old Accounting Settings record instead of the actual Tax Settings record. This issue has been resolved. With this release, when you unpost a Billing, the record will display as “Uncommitted” in AvaTax.
Recurring Billing – Clone w/Lines
When a user with the Standard User Profile and AS Full Admin permission set attempted to clone a Recurring Billing with Lines, the “You do not have access to the Apex class named DeepCloneHelper” error message displayed. This issue has been corrected. You can now Clone w/Lines on a Recurring Billing without receiving an error message.
Purchase Order Lines on PDF
Prior to this release, Purchase Order Lines on a Purchase Order PDF file could not be sorted by the Product field. In order to sort by Product, edit the PDF Format on your Purchase Order and specify “AcctSeedERP__Product__r.Name” in the Sort Field.
Salesforce Platform Licenses Error
In the previous release, users with Salesforce Platform licenses were seeing an erroneous message requiring them to give permissions to the Product object. This issue has been corrected.