Overview

Knowing the difference between your Production, Sandbox, and Developer orgs, and understanding how Accounting Seed's Preview and Push releases work, helps you plan upgrades with confidence. This article walks through the types of Salesforce orgs, Accounting Seed's release schedule and cadence, and answers to the most common questions about staying current on your version.

In this article:

• Types of Salesforce Orgs
• Accounting Seed Release and Frequency
• FAQs

Types of Salesforce Orgs

A Salesforce org is a single, private instance of Salesforce software with its own unique database.

Core Concepts:

• Unique ID: Every org has a specific 15-character Organization ID
• Data boundary: Your data, user logins, and customizations live only here

Three main types of Salesforce orgs

Production Org: Your live, real-data instance where business transactions are recorded.

• URL: yourname.salesforce.com

Sandbox Org: A copy of production for testing configuration changes, customizations, and upgrades before deploying to production.

• URL: Contains "test" in the URL
• Partial Sandbox: Copies a subsection of your production data
• Full/UAT Sandbox: Complete duplicate of your production org, including all data. (Note: Additional purchase may be required)

Developer Org: A playground for learning and experimentation.

• URL: Typically contains "develop.lightning" in the URL

Tip: Check your URL. It's the quickest way to know which instance you're in.

Why sandboxes matter for Accounting Seed users

Accounting Seed releases three times per year (Winter, Spring, Summer) on the same cadence as Salesforce. Each release includes new features and functionality and may include configuration changes.

These changes are pushed to sandboxes first to give you the opportunity to test them with your customizations, workflows, and data.

If you are not on the latest release, you may miss new features and functionality. Additionally, Salesforce updates could cause issues in your org.

For a walkthrough of best practices for upgrading your organization to a new Accounting Seed release, review Upgrading to a New Release: Best Practices.

Accounting Seed Release and Frequency

Accounting Seed delivers three major releases each year: late Spring, late Summer, and Winter. Each release follows a two-stage rollout: a Preview release followed by a Push release a few weeks after the Preview is available.

If you're unsure of what release your app is on, Find Your Release and Version Number will help you identify your current release.

Preview Release

What is it?
A Preview Release gives users early access to some of the features, enhancements, and fixes that will be included in the next Production Release. This release is not automatically deployed to any org. Customers can install it in their sandbox, test their workflows, and then manually upgrade their production org once testing is complete.

How do I know it's a Preview Release?
The release name has the word "preview" after the season and year naming convention. For example: "Spring '26 Preview".

How do I get it?
The Preview Release is a "pull" release, meaning you must proactively download it to your sandbox and/or production org. The latest installation links can be found in Product Installation Links.

How do I know when it's available?
Preview Release availability is announced in Accounting Seed's Bloom newsletter. If you're not receiving Bloom, you can sign up here.

Why do I want it?
A Preview Release is for users who would like early access to some of the features, enhancements, and fixes that will be included in the next push Release.

Why haven't I received the latest version automatically?
Preview Releases must be proactively installed. Depending on your permissions, you may need to contact your Salesforce Administrator to perform the update for you.

Push Release

What is it?

• The "Push" release comes after the Preview release
• It is cumulative and usually includes more features, enhancements, and fixes than the Preview
• It is automatically deployed or "pushed" to all customers enrolled in automatic upgrades
• It is first pushed to sandboxes to give you time to test your customizations and workflows, then pushed to your production orgs
• Accounting Seed will email you about both the sandbox and production pushes about a week before your scheduled push

How do I know if a release is a Push Release?
The release name has just the season and year naming convention. For example: "Winter '26".

How do I get it?
The Push Release is automatically deployed to your production org if you have enrolled in automatic upgrades.

How do I know when it's available?
Push Release is communicated by email to all Accounting Seed users.

Why do I want it?
Both Preview and Push releases contain new features, enhancements, and software corrections. All releases are cumulative, meaning each release includes everything from prior releases. All changes are documented in the release's Release Notes. Features and enhancements that require configuration steps are documented in the accompanying Configuration Changes article.

Why haven't I received the latest version automatically?
Install may fail if you're too far behind on your release version. If you're getting an error code, search this troubleshooting article for the error and solution. If you still need help, submit a case.

FAQs

How many releases are there per year?

Accounting Seed follows the same release schedule as Salesforce with three major releases per year:

1. Winter
2. Spring
3. Summer

How do I know what version I'm on?

You can find your version on the Accounting Home page. See the KB article Find Your Release and Version Number for more details.

I'm not on the most current version. How do I get it?

See the KB article Product Installation Links, which includes prerequisite information for each release version. You can also refer to the Previous Releases article which lists older ones.

Can I skip to the latest version, or do I have to go version by version?

You generally cannot skip too many versions without hitting an install failure. The best practice is to follow the sequential upgrade path in the Product Installation Links KB article.

I would like to stay on my current version. Is that an option?

To do this, please reach out to your customer engagement team or submit a support case request.

My org is set up for automatic upgrades. Why wasn't my org upgraded?

For production and sandbox orgs, the install may have failed. Common failures and the steps to resolve them are documented in the Troubleshooting Guide article. Reach out to our Support team for guidance if you are unable to resolve the issue.

For sandboxes, if it was recently refreshed, you need to send your Sandbox Org ID to our team so we can associate it with your account to receive future upgrades.

My installation failed with an error. What should I do?

Submit a case through the Help Center and include the error message, your Org ID, and the version you were attempting to install.

My sandbox didn't receive the automatic push. Why not?

Your Sandbox Org ID must be registered with Accounting Seed to receive push updates. Note that if you refresh your sandbox, the org ID changes. When this happens, let us know the new Org ID so we can make sure your sandbox is pushed to at the appropriate time. Submit the new ID to customersuccess@accountingseed.com.

My sandbox was refreshed. Will it still receive automatic updates?

No. A refresh generates a new Org ID. Submit the new ID to customersuccess@accountingseed.com to re-register for push updates.

Should I install in my sandbox before production?

Yes, always install and test in your sandbox org first before pushing to production. Review Upgrading to a New Release: Best Practices.

Can I install the Preview Release in production?

Yes. Preview Releases are early access to features and enhancements as well as important fixes. Best practice is to test in sandbox first before installing in production.

Is there a cost to update to the latest version or release?

No. Updates are included in all active Accounting Seed subscriptions.

Safe Harbor Statement

The documents presented on (or directly accessible from) this page may contain forward-looking statements. These statements relate to future events or Accounting Seed's future performance. Any statements that are not statements of historical fact (including without limitation statements to the effect that the Company or its management "believes", "expects", "anticipates", "plans" and similar expressions) should be considered forward-looking statements. There are a number of important factors that could cause Accounting Seed's actual results to differ materially from those indicated by the forward-looking statements. Accounting Seed disclaims any obligation to update any forward-looking statement.

SOC (Service Organization Controls)

As an Accounting Seed customer, your data is exclusively on the Salesforce platform. Salesforce carries an SOC 2 certification.

Related Articles

• Upgrading to a New Release: Best Practices
• Product Installation Links
• Find Your Release and Version Number

Return to top