ISV Solution Certification Guidance

Reviewed: Aug 25th, 2026

Intro

Acumatica ISV solution certification evaluates whether a solution meets applicable technical, functional, documentation, and quality requirements. Certification helps confirm that the solution follows Acumatica development standards and is prepared to deliver a reliable experience for customers.

How long certification takes depends on the solution’s type, size, complexity, integrations, and the completeness of the submission. ISVs can help reduce delays by registering the solution correctly, preparing all required files, validating the customization package, and testing key functionality before opening a certification case.

This guide explains how to prepare and submit an Acumatica ISV solution for certification. Requirements may vary by solution, so always consult the current official Acumatica ISV Software Certification Guidelines before submitting.

At a glance: To submit an Acumatica ISV solution for certification, register the solution, prepare the required documentation and packages, validate the customization in a clean Acumatica instance, test the solution’s key functionality, and create a certification case through the Acumatica Partner Portal.

What Is Acumatica ISV Solution Certification?

Acumatica ISV solution certification is a review process for solutions developed to extend or integrate with Acumatica ERP. Depending on the solution, the review may cover customization code, API integrations, documentation, installation procedures, developer qualifications, security practices, and functional testing.

The purpose is to identify technical or operational risks before the solution is made broadly available to Acumatica customers. Certification can also strengthen a solution’s credibility by demonstrating that it has been reviewed against applicable Acumatica standards.

How Long Does Acumatica ISV Certification Take?

There is no single certification timeline for every solution. The time required depends on factors such as:

• The type and complexity of the solution.
• Whether it customizes Acumatica or connects through APIs.
• The number and quality of the submitted files.
• The results of code validation and functional testing.
• How quickly the ISV responds to questions or requested changes.

A complete, well-tested submission generally requires less back-and-forth than one with missing documentation, validation warnings, or unclear test instructions.

This should be a standalone section because the existing introduction identifies it as the most common question but does not answer it clearly.

Step 1: Register Your ISV Solution

Before beginning certification, register the solution with Acumatica. Contact the Acumatica certification team at certification@acumatica.com and provide the required solution information.

Solution code

Provide a unique solution code in uppercase Latin characters. The code and supported version information are used in the name of the deployment package.

The current article uses this format:

SOLUTIONCODE[XX.XXX.XXXX][YY.YY.YY].zip

In this format:

• XX.XXX.XXXX identifies the minimum supported Acumatica build.
• YY.YY.YY identifies the ISV’s internal solution or package version, when applicable.

Use a current, generic example rather than the existing 2019 and 2020 build numbers.

Solution initials

Provide the two-to-four-letter uppercase prefix assigned to the solution. Objects introduced by the customization package should follow the required naming conventions.

Depending on the solution, this may include:

• Graphs and graph extensions.
• Data access classes and DAC extensions.
• Public data views and actions.
• Web services endpoints.
• Screen IDs.
• Generic inquiries and reports.
• Elements added to customized Acumatica screens.

Solution name and focus area

Provide a clear, human-readable solution name that identifies the product and its purpose. This is the name customers may see in the Acumatica Marketplace.

You should also describe the solution’s capabilities so Acumatica can assign it to the appropriate category or focus area.

After registration, sign in to the Acumatica Partner Portal and open Manage ISV Solutions. Confirm that the solution code, initials, name, and other information are correct before preparing the certification submission.

Step 2: Prepare the Certification Materials

Submission requirements vary depending on whether the solution customizes Acumatica, communicates through web services, or operates as an external application. The following materials may be required.

1. Solution Objects file

If your solution customizes Acumatica, provide a Solution Objects file that documents the objects introduced or modified by the solution, referenced entities, and related integration scenarios.

This information helps the certification team compare the documentation with the implemented solution and identify possible compatibility risks. For example, two solutions could create a conflict by overriding the same Acumatica action.

Complete this file carefully and use the available prefilled file or automated export, when applicable, to reduce manual work and improve accuracy.

2. Integration Scenarios file

If the solution uses Acumatica web services or APIs, document:

• The requests being made.
• The Acumatica entities involved.
• The purpose of each request.
• The order of interdependent requests.
• Filtering conditions.
• Expected request frequency or volume.

Group sequential or dependent requests into logical integration scenarios. This helps reviewers understand how the integration operates and evaluate it against applicable integration requirements.

3. Proof of developer certification

Provide the names and applicable Acumatica certification badges of the developers who participated in building the solution.

Developers should complete the training and certifications required for the solution type before the certification case is submitted. Confirm that the required badges remain current and that the developer information matches Acumatica’s education records.

The certification review may not begin until participating developers have completed the applicable certification requirements.

4. Installation and Configuration Guide

Provide step-by-step instructions that take the reviewer from installation through a ready-to-use configuration. Include screenshots where they clarify the process.

The guide should address:

• Prerequisites
• Installation
• Initial configuration
• Verification
• Upgrades
• Maintenance
• Uninstallation
• Credential and sensitive-data handling

If the solution manages credentials or other sensitive information, explain how that information is encrypted, stored, transmitted, and protected. Do not include active production credentials in the guide.

5. Customization package

If the solution contains an Acumatica customization, submit the required ZIP package using the approved naming convention.

Before exporting the package:

• Confirm that the solution code and version are correct.
• Compile applicable code items into DLLs.
• Remove unnecessary development files.
• Validate the package in a clean Acumatica instance.

6. User guide

Provide a user guide if the solution introduces screens, processes, settings, or workflows that are not adequately explained in the customization package.

The guide should explain the solution’s functionality from the end user’s perspective. It may be combined with the Installation and Configuration Guide if the resulting document remains clear and easy to navigate.

7. Source code

If the customization deploys custom DLLs, provide the applicable Visual Studio solution in a ZIP archive.

Include a list of third-party libraries used by the solution and identify their applicable licenses. Before packaging the source code, run the current version of Acuminator and Visual Studio code analysis.

Resolve applicable warnings before submission. If a warning cannot reasonably be corrected, document the warning, explain why it remains, and describe any related risk or mitigation.

Acumatica uses Acuminator to identify code that may not follow Acumatica Framework rules and development best practices. Using the tool throughout development can help identify issues before the certification review begins.

8. Functional test scenarios

Provide test scenarios that explain how the certification team can verify the solution’s key functionality.

Each scenario should include:

• The steps a reviewer should perform.
• The expected result of each step.
• The data required to run the test.
• Any prerequisites or configuration.
• Any required interaction with an external system.

If the standard demonstration data does not contain the records needed to test the solution, provide an appropriate test snapshot or dataset.

If the solution interacts with a third-party system, follow Acumatica’s approved process for providing sandbox access. Alternatively, arrange a guided verification session in which your team demonstrates the functionality through screen sharing.

Depending on the solution’s type or complexity, the certification team may request additional information or testing.

Step 3: Validate the Solution Before Submission

A self-test can identify issues before the certification team begins its review.

Using a new Acumatica instance:

• Import the customization project.
• Run the available project validation.
• Open the project’s item list.
• Validate the project prefix using the initials assigned to the solution.
• Validate the project items.
• Review all warnings and errors.
• Correct identified issues and repeat the validation.

Create the certification case only after the project completes the required validation without unexplained warnings or exceptions.

Step 4: Create the Certification Case

After preparing and validating the submission:

1. Sign in to the Acumatica Partner Portal.
2. Navigate to Partner Program > Manage ISV Solutions.
3. Select the solution you want to certify.
4. Open the Solution/Repository tab.
5. Select Upload Solution.
6. Enter the supported Acumatica build and the ISV solution version.
7. Upload the customization package and applicable documentation.
8. Confirm that the uploaded solution and version appear correctly.
9. Select the uploaded version and choose Create Certification Case.
10. Select the applicable ISV contract and submit the case.

Use the case’s Add Comment function for subsequent communication and revised packages. When replying by email, retain the case identifier in the subject line and follow the current instructions provided by the certification team.

Acumatica ISV Certification Checklist

Registration

• Solution registered with Acumatica.
• Solution code and initials confirmed.
• Solution name and focus area verified in the Partner Portal.

Documentation

• Solution Objects file, if applicable.
• Integration Scenarios file, if applicable.
• Proof of developer certification.
• Installation and Configuration Guide.
• User Guide, if applicable.
• Functional test scenarios.

Solution files and testing

• Correctly named customization package, if applicable.
• Source code for custom DLLs, if applicable.
• Third-party library and license information.
• Required test data or snapshot.
• Acuminator and Visual Studio checks completed.
• Project prefix and project items validated.
• Key functionality tested in a clean instance.

Frequently Asked Questions

What is Acumatica ISV solution certification?

Acumatica ISV solution certification is a review of an ISV solution’s applicable technical, functional, documentation, and testing requirements. The exact review depends on whether the solution customizes Acumatica, integrates through APIs, or connects as an external application.

How long does Acumatica ISV certification take?

The timeline varies based on the solution’s complexity, integration methods, submission quality, and any issues discovered during review. Complete documentation and successful pre-submission validation can help reduce delays.

What documents are required for certification?

Requirements may include a Solution Objects file, an Integration Scenarios file, proof of developer certification, installation instructions, a user guide, source code, and functional test scenarios. Not every item applies to every solution.

Do developers need Acumatica certifications?

Developers participating in the solution may need current certification badges appropriate to the solution type. Confirm the current badge and course requirements before opening the certification case.

Should I run Acuminator before submitting?

Yes. Use the current Acuminator release throughout development and before submission to identify code that may not follow Acumatica development standards. Review and resolve applicable warnings before packaging the solution.

Where do I submit an Acumatica ISV solution?

Registered ISV solutions are submitted through Manage ISV Solutions in the Acumatica Partner Portal. Upload the applicable files and create a certification case for the relevant solution version.

Who should I contact with certification questions?

Contact the Acumatica certification team at certification@acumatica.com or use the communication options associated with an existing certification case.