Skip to main content

Release Notes March 11, 2025 [1.272]

Corey Syrnyk
  • Updated

With Spring around the corner, this release brings a "bulk" bouquet of enhancements and a sprinkle of bug fixes. Here are some highlights of this March 11, 20025 [1.272] release.

 

Enhancements

Manual Payment Edit Import

You can now edit the settlement of payments using the bulk import feature.

Use the Payment Import Type and select Edit to download the starting file.

See Editing Payment Status Details for more information.

 

Customer Bulk Import Avalara Support

You can now include an Avalara ID in the Customer Import bulk job.

See Creating Customers for more details.

 

NetSuite Bulk Manage Job

You can now use the bulk jobs feature to manage NetSuite customers. This allows you to bulk import into NetSuite.

NEtSuite.png

Check out Latching Customers in NetSuite.

 

Netsuite

You can now edit the location or bin information on a Historical Purchase Invoice.

If you have previous invoices that have not synced with NetSuite due to an error, you can edit the invoice to change or add a location or bin and resync the invoice with NetSuite.

 

PO Numbers and Avalara

When entering PO numbers, Avalara would accept a limit of 50 characters. If the PO number was longer, it would produce an error.

Now, when the PO is longer than 50 characters, Stax Bill will send Avalara only the first 50 characters so that no error is created. This allow you to store more than 50 characters in the Stax Bill system and still send over the PO to Avalara. 

 

BuGs

  • Bug 56953: The invoice view on SSP for an invoice with scheduled Payments lists the full invoice instead of the payment total.
  • Bug 57288: View invoice as PDF in Salesforce prompts users to login to Stax Bill.
  • Bug 60923: The coupon fails to be applied when applied in a migration and the related discount is set to continue for one period.
  • Bug 60926: Subscription Edit starting data file does not allow selecting Retired Plans with Active Subscriptions.
  • Bug 61160: Venmo Unknown Payment error.
  • Bug 61187: Offerings page address settings overwrite Enforce Full Address.
  • Bug 61407: Link to source subscription from a child goes to wrong customer.

 

 

Related articles