Winter '25 Release Notes

Body

Overview

Accounting Seed is pleased to inform you of our Winter ‘25 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.

For information about our release frequency and schedule, please refer to the Release Schedule article.

In addition to reviewing these notes, please review the Winter '25 Release "What's New" video below.

Installation Notes

Our Winter ‘25 release was deployed to sandbox environments on Sunday, November 3, 2024. We will begin production upgrades in December. The installation links can be accessed by clicking here, if necessary.

Configuration Changes

This release includes configuration changes that can be performed by existing Accounting Seed users. For more information, refer to the Winter ’25 Configuration Changes article.

Important: If you have Salesforce Platform license users, please refer to the Provide Product object access to Salesforce Platform License users information in the Winter ’25 Configuration Changes article.

Features and Enhancements

AvaTax - Canadian Sales Tax
UK Bank Support for Bank Direct Connect
Bank Disbursements
Void a Cash Receipt
AP Automation
Multi-book Accounting and Cash Basis Accounting
Large Data Optimizer
AR Automation

Customer Requested Enhancements

Delete Billing Cash Receipts from a Cash Receipt
Advanced Line Manager - Re-order Line Number
Receive Payment - Custom Payment Type
Orders & Inventory - Duplicate Inventory Quantity Available
Bank Reconciliation (Auto-Clear Job)
Amortization for more than 60 Accounting Periods
Stripe Version Update
Support from Accounting Home

Software Corrections

Return to top

Features and Enhancements

AvaTax - Canadian Sales Tax

Tax Settings
Calculate Tax on a Billing with Avalara’s AvaTax
Calculate/Estimate Tax on an Opportunity
Estimate Tax on an Opportunity with Avalara’s AvaTax
Create or Clone a Billing
Set up a Customer or Vendor

Avalara’s AvaTax, which has been available to our US customers for some time is now available to our Canadian customers. Avalara provides through its different product offerings, end-to-end sales tax compliance solutions. Their AvaTax tax engine provides the capability to automatically calculate tax based upon the most current tax rules and legislation. You can use AvaTax to estimate sales tax on Opportunities and calculate sales tax on Billings. The Set Up Avalara AvaTax Integration article provides information to begin the Tax Settings process, assign an Avalara Tax Code to a Product(s), and configure the Account object for Avalara. Refer to the Sales Tax section of our Knowledge Base to view additional articles that are related to AvaTax.

When using AvaTax, the address validator will validate addresses for both the United States and Canada.

Supported Tax Currencies

Related to the AvaTax Canadian Sales Tax, a new custom metadata type was added, which is "Supported Tax Currencies." The currency settings (USD and CAD) for this custom metadata type are automatically set to Active.

Best Practice: If using AvaTax, we recommend that these settings not be deactivated.

New Warning Messages with AvaTax

Since cross-border tax rules and regulations change over time, we added new warning messages to remind you that if you have Nexus in a country that you are shipping to, where tax should be calculated in that country, the currency should be updated for that country. Therefore, when using AvaTax to calculate tax in either the US or Canada, the system will check the Billing Currency against the Destination Address, and display the following warning messages if the:

Billing Currency is USD and the Destination Address is in Canada - “When calculating tax using AvaTax, if the Destination Address is in Canada and you have Nexus for this address, you should update the currency to CAD.“
Billing Currency is CAD and the Destination Address is in the US - “When calculating tax using AvaTax, if the Destination Address is in the US and you have Nexus for this address, you should update the currency to USD."

UK Bank Support for Bank Direct Connect

BDC – Bank Settings
BDC – Unmatched Bank Transactions
BDC – All Bank Transactions

This release includes Salt Edge as an Aggregation Provider for integration with Bank Direct Connect for our United Kingdom and EMEA customers. As a UK or EMEA customer, when you access the Bank Direct Connect – Bank Settings tab, you will need to set up the provider through Bank Direct Connect. For assistance with completing this information, as well as the remainder of the fields on the Bank Settings tab, refer to the Bank Direct Connect – Bank Settings article.

The Bank Direct Connect functionality for Salt Edge includes the ability to add Bank Rules, add and match Unmatched Bank Transactions, and view All Bank Transactions. This is exactly the same functionality as with our other Aggregation Providers (Plaid and Yodlee).

Best Practice: It is recommended that you schedule the Bank Download job to automatically update Bank Transactions each day at a selected time. For more information, refer to the Schedule the Bank Download article.

Note: Existing Accounting Seed customers in the UK and EMEA who plan to use Salt Edge as an Aggregation Provider for integration with Bank Direct Connect will need to activate the Remote Site and Trusted URL settings for Salt Edge. For more information, refer to the Activate the Salt Edge Remote Site and Trusted URL Settings in the Winter ’25 Configuration Changes article.

Bank Direct Connect APIs

When Plaid, Salt Edge, or Yodlee does not support your banks, you can write a custom integration using our Bank Direct Connect APIs (Application Programming Interface) to drop in another Bank Aggregation Service. For more information, refer to the Bank Direct Connect Implementation Guide in the API section of our Knowledge Base.

Bank Disbursements

Similar to Bank Deposits for Cash Receipts and Journal Entry Lines, you now have the ability to create Bank Disbursements for Cash Disbursements and Journal Entry Lines. This allows you to group multiple Cash Disbursements and/or Journal Entry Lines that cleared the bank as one lump sum. These outgoing expense payments that appear on your bank statement as one combined amount, might also display on the Bank Direct Connect – Unmatched Bank Transactions tab as a possible match or be automatically matched based upon Bank Settings. When you are ready to perform a Bank Reconciliation, a Bank Disbursement will display as one single line item, which can be cleared on the reconciliation.

A new Lightning web page has been added for Bank Disbursements, which includes filter criteria such as a date range, record type, and amount. Records that match the search criteria will display on the Unassociated tab in the data grid on the Bank Disbursement. Then, just as you would on a Bank Deposit, you can associate records to be included on a Bank Disbursement.

Cash Disbursements and Journal Entries must be posted in order for the records to display in the data grid on a Bank Disbursement. To learn more about Bank Disbursements, including how to create one, refer to the Bank Disbursements article.

Existing Accounting Seed users will need to add the Bank Disbursement field onto the page layout on the Cash Disbursement and Journal Entry Line objects. For more information, refer to the Winter ’25 Configuration Changes article.

Important: For existing AP Automation customers who are using automated payments through Edenred pay:

Bank Disbursement records that were created prior to the Winter ’25 release will need to be migrated. Contact your AP Automation onboarding team, and grant subscriber access so that a migration script can be run.
After the Winter ’25 release has been installed, when Bank Reconciliations are performed on Cash Disbursements, and the Bank Disbursement field is NOT blank, you will need to clear the Bank Disbursement on the Bank Reconciliation instead of on the Cash Disbursement.

Return to top

Void a Cash Receipt

Void a Cash Receipt
Issue Refund from a Cash Receipt

With this release, you can now quickly and easily void a Cash Receipt. Voiding a Cash Receipt reverses the associated transactions. You might need to void the related transactions for a payment that was inadvertently processed, or perhaps a customer makes a payment, and later contacts you to request that the payment be voided. Voiding a Cash Receipt is available to all Accounting Seed users.

Void a Cash Receipt with AR Automation

When Cardknox is your Payment Processor, you can void a Cash Receipt in Accounting Seed, which will also automatically be voided in Cardknox. Additionally, if you void a Cash Receipt in Cardknox, when the Merchant Download Automation job runs as part of the normal nightly processes or run manually, it will be voided in Accounting Seed.

The ability to void a Cash Receipt in both Accounting Seed and Cardknox is dependent upon the related batch in Cardknox still being open. For more information about this process, refer to the Void a Cash Receipt with AR Automation section in the Void a Cash Receipt article.

Important: If Stripe is your Payment Processor, while you can void Cash Receipts in Accounting Seed, you will need to manually void the transactions in Stripe.

Void a Refund Cash Receipt

If you need to void a Refund Cash Receipt, use the steps that are available in the Void a Cash Receipt article. Voiding the Refund Cash Receipt will increase the balance on the related Credit Memo. If you still need to refund the payment amount, access the Credit Memo, and Issue a Refund from a Credit Memo.

Existing Accounting Seed customers will need to add the new Void button and Void information section to the Cash Receipt object. For more information, refer to the Winter ’25 Configuration Changes article.

Return to top

AP Automation Updates

As a part of this release, the AP Automation feature that was introduced with our Spring ’24 release includes the updates that are listed below.

Payment Services / Cash Disbursement Updates

When a Cash Disbursement is posted, the system will check to determine if the Alternate Payee Name field is populated. If this field is populated, it will be used in the Payee field on the transaction. Otherwise, the Vendor’s name will be used.
The Set Cash Disbursement to Approved setting has been added to the Payment Settings screen. This new setting is an On/Off toggle button, which defaults to “On.” When this is set to “On,” once a Payment Proposal is approved, Cash Disbursements that are created will automatically have a Posting Status of Approved. When this setting is turned “Off,” the Posting Status on Cash Disbursements that are created from approved Payment Proposals will be set to the default Posting Status that is configured on your org.
When using Payment Services, the AP Remittance Email field on the Account record is required in order to post a Cash Disbursement with Virtual Card as the Payment Services Type. Otherwise, an error message will display when you attempt to post a Cash Disbursement from the detail page or batch posting from the list view.
On a Cash Disbursement that is created from a Payment Proposal, for ACH payments, if the Vendor’s default ACH Payment Method is being verified (has a Verification Status, such as Pending), the Cash Disbursement cannot be posted. However, you can use the Payment Services Type Override field to manually change the Payment Services Type on the Cash Disbursement to Check. Then, post the record.
The “Non-Participating” status in the Payment Services Enrollment Status drop-down list in the Payment Services section on the Account object has been relabeled to “Not Accepting VC.” The VC indicates Virtual Card.

Email to Payable

If you are using the Email to Payable feature that is a part of AP Automation, this information is only applicable if your company’s email is hosted by Google (Gmail). As a part of the process, when you configure a forwarding email address, Gmail expects you to verify the email address that is being forwarded to. Since the Salesforce Email Service email address does not have an “Inbox” as such, we have included steps in the Email to Payable article for the Forwarding Email Verification for Gmail.

Payment Method Update

The Account Number field on the Payment Method screen cannot contain any spaces or dashes. Additionally, the Routing Number must be 9 digits.

AP Automation Declarative Updates

The Field Label on the AcctSeed__Payment_Notifications_Email__c field on the Ledger custom field definition detail has been changed from Payment Notifications Email to Application Email.
The Cash Disbursement Batch field was removed from the Payment Proposal Lightning record page and page layout.
An inactive validation rule specific to AP Automation has been added to the Account object with the rule name of "Payment Services Required Fields." Before activating the validation rule, make sure to discuss this with the AP Automation onboarding team so that any changes can be made.

Return to top

Multi-book Accounting and Cash Basis Accounting Updates

Multi-book Accounting Overview
Cash Basis Accounting Overview

As a part of this release, Multi-book and Cash Basis Accounting that we introduced with our Summer ’24 release includes the updates that are listed below.

The Default Ledger can now be changed even if there are associated posted transactions on the old and/or new Ledger.
In the Cash Basis Accounting article, we mentioned that if you currently have an Accrual Ledger, and want to switch to a Cash Basis only, the Accrual Ledger would be deactivated. Be aware that if you have outstanding Billings that include a PaymentSITE link (Cardknox) or Payment Link (Stripe), your existing Accrual Ledger should NOT be deactivated.
On the Cash Ledger, when records are posted/unposted and/or applied/unapplied, sequential order is very important. With this release, when you attempt to unapply records out of sequential order, an error message will display. Similarly, when applying both a Credit Memo and a payment(s) in the same Accounting Period, the Credit Memo must be applied first. For more information, refer to the Post and Apply Order (on Cash Ledgers) section of the Multi-book and Cash Basis articles.
Once a Journal Entry and/or Amortization Entry has been posted, the Accrual and/or Cash field cannot be edited. An error message will display if you attempt to change this field after posting.
An error message will display if you attempt to select Accrual and Cash (Multi-book Accounting) as the Accounting Method on a Consolidations-Transactional Ledger or Consolidations-Budget Ledger. Additionally, the Accounting Method on the Eliminations Ledger must be the same as the Accounting Method on the related Consolidations-Transactional Ledger.
If you have Accrual and Cash (Multi-book Accounting) as the Accounting Method, with the NPSP Connection, source documents will only be created on the (primary) Accrual Ledger. They will NOT also be automatically created on the Related Cash Ledger. Additionally, you cannot manually add source documents to the Related Cash Ledger.

Large Data Optimizer Updates

As a part of this release, the Large Data Optimizer (LDO) feature that was introduced with our Spring ’24 release includes the updates that are listed below.

After a Cash Receipt is created, it might need to be refunded and have the related Billing Cash Receipt (BCR) deleted. When you have the Large Data Optimizer (LDO) feature enabled, on a negative Cash Receipt that has been refunded, you can use the new Delete BCR button to delete the related Billing Cash Receipt (BCR). You cannot directly delete the related Billing Cash Receipt under LDO because it requires running an asynchronous process. For more information, refer to the Delete a Billing Cash Receipt(s) with LDO Enabled article.
Note: Existing Large Data Optimizer users should add the Delete BCR button onto the AR Cash Receipt page layout. For more information, refer to the Winter ’25 Configuration Changes article.
The pagination bar on the Advanced Line Manager has been enhanced to include the Go to page textbox, which allows you to enter a specific page number, and click Go to access that page. This is very helpful if you have the LDO feature enabled, which may include a large number of rows.
On the Recurring objects (Billing, Payable, and Journal Entry), with the LDO feature enabled, on the Create intermediate screen when Create/Create & Post is clicked:
- With AS Native Tax, and more than one line on a record with no changes to the date (or Journal Entry Name), the default message displays to indicate the records will process asynchronously. If the Create & Post button was clicked, the records will post after the asynchronous job completes.
- With AS Native Tax, if there is a change to the date (or Journal Entry Name), the header record will process immediately, and the lines will process asynchronously. Later, you can review the Automated Job Results for details about the completed asynchronous job.
- With Avalara’s AvaTax (Recurring Billings only), the records will process immediately (the same as without LDO).
New LDO limits around the Recurring object (Billings, Payables, and Journal Entries) have been added. For more information, refer to the table in the Large Data Optimizer article.
If you have source documents with either of these two Posting Statuses (Posting in Progress or Unposting in Progress), the Accounting Period cannot be closed. An error message will display, which prevents closing while source documents are in these statuses.
On the Reset LDO Source Document Interim Posting Status purge, when it completes, an email will be sent to the email address of the user who ran the purge, which will include details about the purge.

AR Automation Updates

Payment Activity Status

With Cardknox, the Payment Activity Status job is included when the Merchant Download Automation job runs, so that the latest Payment Activity information is available when viewing the Payment Activities screen. With this release, when this job runs, if the Status on a “Pending” ACH payment changes to “Chargeback,’ the Status on the related Payment Activity record will be updated to “Error,” and the related Cash Receipt in Accounting Seed will be voided after the normal nightly job process completes. If the Status on an ACH payment changes from “Pending” to “Settled,” the Status on the related Payment Activity record will be updated to “Success.” Additionally, if a payment has been voided in Cardknox, the Status on the Payment Activity record will be updated to “Void,” and the related Cash Receipt will be voided (after the normal nightly job process) with a Void Description of “Voided by the Merchant Download job.”

When a Payment Activity record is created as part of the Merchant Download Automation job, the Payment Date field on the record will automatically populate with the date the payment was made.

Existing Accounting Seed customers will need to add the Payment Date field to the Payment Activity object, as well as add “Void” as a picklist value to the Status field on the Payment Activity object. For more information, refer to the Winter ’25 Configuration Changes article.

Payment Processors

A Lookup filter was added to the Default Payment Processor field on the Ledger object and the Account object, which prevents AP Payment Processor types from displaying. This is a way to make sure that an AP Payment Processor is not being used when only an AR Payment Processor should be used. If an AP Payment Processor was previously entered in the Default Payment Processor field on either of these two objects prior to this release, it will be ignored during the Billing creation process.

ACH Payments on Bank Deposits

On a Bank Deposit record, the Deposit Reference and Merchant Batch ID fields will display a system generated number for ACH payments (instead of a Cardknox reference number and batch number). Additionally, the Reference field on the related Journal Entry (Merchant Funds Transfer) will include the same system generated number. This is for system purposes only and does not need to be tracked. This change is related to the ACH Payments on Weekends and Holidays software correction below.

Return to top

Customer Requested Enhancements

Delete Billing Cash Receipts from a Cash Receipt

The new Delete BCRs button allows you to delete Billing Cash Receipts (BCRs) directly from a Cash Receipt record. This provides a quick and easy way to delete the related BCRs without having to manually open each BCR record to delete one by one. For additional information, refer to the Delete Billing Cash Receipts from a Cash Receipt article.

Note: For Large Data Optimizer (LDO) orgs, as mentioned above, there is now another similar button (Delete BCR on the Billing Cash Receipt object). You cannot directly delete the related Billing Cash Receipt under LDO because it requires running an asynchronous process.

Existing Accounting Seed users can review the Winter ’25 Configuration Changes article to add the Delete BCRs button onto the Cash Receipt page layout.

Advanced Line Manager – Re-order Line Number

Advanced Line Manager

When you click the Pencil icon to re-order the line number on the data grid in the Advanced Line Manager, the re-ordered line will adjust to the correct numbering sequence after you click the Save button.

Receive Payment – Custom Payment Type

Receive Payment Directly from a Billing

On the Receive Payment intermediate screen for a single Billing, if you add a custom option to the Payment Type drop-down list (for example Bitcoin), it now displays and can be selected as a Payment Type. The same fields that display for the Check and Other options will be available for the custom option. The selected custom option will also display in the Payment Type field on the related Cash Receipt.

Note: From the Receive Payments screen on the list view, Payment Method is the only supported Payment Type for multiple Billings, which includes payments through Cardknox or Stripe. Therefore, the Payment Type on all of the related Cash Receipts will be Payment Method.

Orders & Inventory - Duplicate Inventory Quantity Available

Check Inventory Quantity Available (Average Cost)
Check Inventory Quantity Available (Standard Cost)

With this release, we have switched from using an aggregated query to check for duplicate Inventory Quantity Available (IQA) to a standard SOQL query. This allows for the validation of a significantly larger dataset. When you Check Inventory Quantity Available, and click New to add quantities, the system will check up to 50,000 records for duplicates. If found, an error message will display to indicate the same Product, Warehouse, Location and Ledger already exists.

Bank Reconciliation (Auto-Clear Job)

Create a New Bank Reconciliation
Enablements

Multiple Bank Reconciliations can be created at the same time using the Salesforce Data Loader App (web-based Data Import Wizard tool) or a script. With this release, when creating one or more Bank Reconciliations, the automatic clearing of records on the saved Bank Reconciliations will depend upon the new Disable Auto-Clear job setting in the Enablements screen. When this setting is turned “On,” records on the saved Bank Reconciliations will not be automatically cleared. When this setting is turned “Off,” if multiple Bank Reconciliations were imported/created and saved at the same time, records on the first saved one will automatically be cleared. On the remaining Bank Reconciliations that were imported/created at the same time, the records will need to be manually cleared. The default for this setting is “Off.”

Amortization for more than 60 Accounting Periods

Within the UI (User Interface), the selected Amortization period of time can be up to 60 Accounting Periods. If you need to amortize for a longer period of time, the Amortization API supports up to 360 Accounting Periods. This is applicable when you Amortize Revenue for a Billing, Amortize Expense for a Payable, and also when you Depreciate a Fixed Asset. To learn more, refer to the Amortization for more than 60 Accounting Periods information.

Stripe Version Update

For all callouts to Stripe, our software has been updated to use the latest Stripe API version. This does not require any changes for our Stripe users.

Support from Accounting Home

The Accounting Home page has been updated to include a Support hyperlink, which allows you to access a page with all available user assistance resources. This includes the ability to open a case, if necessary.

Note: Click here to view the above image in full screen.

Return to top

Software Corrections

Billings and Payables - Currency Conversion Rate

On Multi-currency orgs, when a Currency Conversion Rate with more than two decimal places (for example, 0.878550) was being used, the posted transactions were generated using a rounded conversion rate. This issue has been resolved so that posted transactions generate using the actual user-defined Currency Conversion Rate.

If you have upgraded to Winter '25 release, version 3.304, in order to locate Billings and Payables that will need to be unposted and reposted because the amounts are incorrect due to rounding on the conversion rate, click here for more information.

Salesforce Platform License Users

Some users were experiencing Field Level Security (FLS) error messages that were related to the Product and other fields on the Cash Receipt. This issue has now been resolved. No change in licensing is required.

Multi-book Accounting - JEs on Cash GL Accounts

With Multi-book Accounting, Journal Entries (JEs) that post ONLY to Cash Ledgers (such as the Opening Cash Balances Journal Entry) were being incorrectly included on a Bank Reconciliation. This issue has been resolved so that when "Cash" is selected in the Accrual and/or Cash field on a JE, if there are Journal Entry Lines with a GL Account where the Bank/Credit Card checkbox is selected, the entries will not be included on a Bank Reconciliation.

Delete an AP Payment Method

When the Delete button is clicked on an AP Payment Method record, a Visualforce page displays with a Force Delete button. Clicking the Force Delete button deleted the Payment Method. However, at times another Payment Method was automatically created. This issue has been resolved so that when a Payment Method is deleted a new one will not be created.

Payment Services with Multi-Ledgers

Customers who use Payment Services with multiple Ledgers, on system-generated Bank Disbursements, the Ledger was always set as the Default Payment Services Ledger. This issue has been corrected to reflect the Ledger on the associated Cash Disbursement.

Bank Reconciliation stuck in "Working" Status

In some instances, there was an issue with a Bank Reconciliation getting stuck in “Working” status without displaying any error message. We have added an Error field to the Bank Reconciliation object. This new Error field (displays from the Detail tab on a Bank Reconciliation record) will include information to indicate that an error has occurred, and the necessary steps to correct. The error message will display in the Error field, as well as at the top of the Bank Reconciliation record. This Error field will display any error messages that may be encountered while a Bank Reconciliation is transitioning from an “In Progress” to “Completed” status. This change reduces the likelihood of a Bank Reconciliation getting stuck in “Working” status.

Existing Accounting Seed users will need to add the Error field onto the Bank Reconciliation page layout. For more information, refer to the Winter ’25 Configuration Changes article.

AR Automation (Cardknox)

ACH Payments on Weekends and Holidays – when ACH payments were received from Cardknox on weekends and holidays, there was an issue with more than one Journal Entry being created. For example, in Accounting Seed, a Journal Entry was created for the Saturday ACH payments, and one was also created for the Sunday ACH payments. However, Cardknox sent the combine ACH payments for both Saturday and Sunday as one lump sum amount to your bank account. This created an issue when it was time to reconcile your Bank Statement since the Bank Deposit was the lump sum amount from Cardknox, but there were separate Journal Entries. This issue has been corrected so that now only one Journal Entry is created, which allows you to reconcile your Bank Statement.
Merchant Download Automation Job – in a specific situation, the CxTrxnslImportBatch job, which is an Apex job that imports transactions from Cardknox as part of the Merchant Download Automation job process was failing and creating record locking issues. One of two error messages displayed. Either the “AcctSeed: Too many query rows: 50001” message or the “Apex CPU time limit exceeded” message. This issue has been resolved so that the batch job now runs successfully without errors.

Large Data Optimizer (LDO)

Delete APDs button on a Cash Disbursement – when the Delete APDs button was clicked on a Cash Disbursement record, an error message displayed, which prevented deletion. This issue has been resolved, and the Delete APDs button functions as expected when the LDO feature is enabled.
Records Stuck in interim Posting Status – there was an issue with a Billing Cash Receipt (BCR) and AP Disbursement (APD) record getting stuck in the Posting in Progress status when a Cash Receipt or Cash Disbursement was unapplied and applied at the same time. This issue has been resolved.
Pay Batch Payables from the List View – when attempting to pay Payables from the list view, the Pay Batch job was failing. This issue has now been resolved.
Merchant Download Automation job – when the Merchant Download Automation job was scheduled to run with the Billing Cash Receipts (BCRs) set to Auto-Post, the job did not run successfully. This issue has been resolved with the job running as expected, along with convenience fees being recorded correctly.

Bank Direct Connect (BDC)

Update Bank Transactions with Yodlee – with Yodlee as the Aggregation Provider in BDC, when a Financial Institution Account (FIA) was selected from the drop-down list, and Refresh Connection or Refresh Credentials was clicked, only the first bank in the drop-down list was being refreshed (and not the selected one). This issue has been resolved so that the selected FIA is refreshed.
Plaid Missing Bank Transactions older than 90 days – in a specific situation, there was a problem with Plaid missing bank transactions that were older than 90 days. This issue has been resolved so that transactions that are older than 90 days can be downloaded and/or imported.
Bank Description Missing on Debit GL Account – with the Enable Global Automated Add checkbox selected in Bank Settings so that a Journal Entry and Journal Entry Lines (JEL) are automatically created when bank transactions are imported, and the Account and GL Accounts are assigned by the Bank Rules, there was an issue with the Description missing on the Journal Entry Line. This issue has been resolved so that the Description now displays on both Journal Entry Lines.

Post/Unpost Billings with AvaTax

When attempting to post a Billing using AvaTax, if the Destination Address was a country other than the United States or Canada, a currency related message displayed, which prevented posting. This issue has been resolved so that a Billing using AvaTax with a Destination Address outside of the US or Canada can be successfully posted or unposted. The Sales Tax amount on the Billing will be zero (0.00).
In some circumstances, an “unexpected character” related error message displayed when attempting to unpost a Billing using AvaTax. This issue has been resolved so that a Billing can now be successfully posted or unposted.

Apply/Unapply a Credit Memo

When the Apply/Unapply Credit Memo button was clicked from a Payable record to access the intermediate screen, the Payee (Vendor) hyperlink was not functioning as expected. This issue has been corrected so that you can now click the Payee hyperlink to access the Vendor (Account) record.

Apply a Negative Cash Receipt to a Billing

When attempting to apply a negative Cash Receipt to a Billing to restore the Balance, the Billing Cash Receipt (BCR) was not created. Instead, an error message displayed. This issue has been corrected.

Consolidations Routine for Accrual and Cash Ledgers

The Consolidations routine for a Parent Consolidations Ledger with Children (Accrual and Cash Ledgers) was including the sum amount from both the primary Accrual and the related Cash Ledger. This issue has been corrected so that the routine for a Parent Consolidations with Children (Accrual and Cash Ledgers) includes only the amounts from the primary Ledger.

Pay Batch Screen - Aggregate by Payee

There was an issue on the Pay Batch screen when the Aggregate by Payee checkbox was de-selected, the Payables that belonged to one Payee were not disaggregated and only one Cash Disbursement was created. This issue has been resolved so that de-selecting this checkbox works as expected.

Billing Cash Receipts - Adjustment GL Account

When the Adjustment GL Account was updated on the Default GL Accounts page, the Receive Payment intermediate screen (from a Billing) was still displaying the old GL Account. This issue has been corrected to display the Adjustment GL Account that is set on the Default GL Accounts page.

Billings and Payables - Foreign Currency

When performing currency conversion on a Billing/Payable Line from the Foreign Currency Amount to the Ledger Currency Amount, rounding issues could possibly occur, which resulted in unequal transaction debits and credits. Or, the Ledger Amount on the header record did not equal the amount on the Billing/Payable Line transaction record. The rounding issues have been resolved so that the transaction debits and credits will be equal amounts, and the Ledger Currency Amount will match the transaction amount.

Advanced Line Manager (ALM) Lookup search results

When a comma (,) was included as a part of the text in the Internal Comment or Invoice Comment fields on the ALM for a Payable, and any Lookup field was clicked to find search results, the available search results did not display. This issue has been resolved so that a comma can be used in text fields without affecting the Lookup fields.

Partially Apply a Cash Disbursement

When partially applying a Cash Disbursement to a Payable by manually entering the specified amount, there was an issue with saving the changes. This issue has been corrected.

Create Billing From Sales Order

When a Billing was created from a Sales Order, the Accounting Period was defaulting to the current Accounting Period. This issue has been corrected so that the new Billing defaults to the Accounting Period on the Billing Date.

AS Financial Analytics

The Last Period and Last Year Key Performance Indicators (KPIs) displayed incorrectly on the Financial Analytics Profit & Loss Dashboard when Accounting Periods were set up with a financial year that started in a month other than January. This issue has been resolved.

Apply/Unapply Credit Memo

When the Apply/Unapply Credit Memo button was clicked on a Payable to access the intermediate screen to apply/unapply a Credit Memo, in the Payee field, the hyperlink to the Account (Vendor) record was not functioning. This has been corrected so that the hyperlink functions as expected.

Return to top

Title

Winter '25 Release Notes

URL Name

573872727