Get a Free Quote

How To Update ERPNext: The Complete Guide 2026

Table of Contents

Enjoying Our Insights


Visit our Blog to Read More
of Our Thoughts and Best
Practices

https://deliverydevs.com/blogs

Our Sevices
Accelerate Your Software Goals. Contact Deliverydevs
Simplify Your ERPNext Upgrade With Specialists
Contact Us
ERPNext version update involves backing up your database, switching ERPNext and Frappe Framework update to the required version branch, pulling latest updates, migrating database, rebuilding assets, and restarting the service to update ERPNext to the latest version.
Using an outdated version for a long time can lead to security vulnerabilities, failed integrations, and limited access to new features. Especially for users in Saudi Arabia, ERPNest version update is not just optional; it’s a necessity to meet Saudi Vision 2030.
This detailed ERPNext update tutorial tells you how to update ERPNext 2026 and meet ZATCA and FATOORAH compliance guidelines in KSA.

How to Update ERPNext 2026: A Brief Checklist

Before we share a detailed guide on ERPNext update without downtime, here’s a straightforward checklist to ensure seamless upgradation to the new ERPNext version:
  • Check your current ERPNext and Frappe versions
  • Review ERPNext release notes for compatibility
  • Take a full ERPNext backup before updates, including database and files
  • Set up or verify a staging environment before production update
  • Pull latest ERPNext updates from the official repository
  • Run bench update and database migration commands
  • Restart all services after update completion
  • Verify core modules (Accounts, HR, Inventory, CRM)
  • Test VAT 15% calculations, ZATCA Phase 2 / FATOORAH compliance
  • Check payroll workflows for WPS and GOSI (التأمينات الاجتماعية) compliance
  • Review system logs for errors or failed processes
  • Perform end-user testing before going live
  • Schedule post-update monitoring for stability and performance

Why Businesses in Saudi Arabia Must Update ERPNext?

Saudi Arabia’s economy is rapidly expanding under Saudi Vision 2030 (رؤية 2030), with strong growth across multiple industries such as manufacturing, retail, construction, trading, and healthcare. ERPNext is the top open-source ERP for Saudi SMEs to manage operations, financial reporting, and regulatory compliance, especially with ZATCA e-invoicing and VAT requirements becoming stricter every year. It is customizable, affordable, and compliant with local regulations in different regions.
Updating ERPNext ensures that POS systems and invoicing tools remain fully compliant with FATOORAH regulations, especially as enforcement tightens ahead of the June 30, 2026 compliance deadline in accordance with ZATCA Phase-2.
Here are some of the major driving factors to update EPRNext 2026 for SMEs in Saudi Arabia:
Alignment with Saudi Vision 2030 Digital Transformation (رؤية 2030)
Saudi Vision 2030 emphasizes digital transformation, automation, and paperless government systems. A major pillar of Saudi Vision 2030 is the empowerment and growth of Small and Medium Enterprises (SMEs), which form the backbone of the Kingdom’s private sector expansion.
Updating ERPNext helps businesses adopt cloud-ready ERP infrastructure, reduce manual compliance processes, integrate with modern Saudi digital platforms, and improve automation across finance, HR, and operations.
ZATCA Phase 2 Compliance (Real-Time E-Invoicing Requirements)
One of the most critical reasons to keep ERPNext updated is compliance with ZATCA’s Phase 2 e-invoicing requirements (فاتورة المرحلة الثانية). These regulations require businesses to generate and transmit structured electronic invoices in real time.
Older ERPNext versions may not fully support updated ZATCA APIs or compliance logic, which can lead to invoice rejection, reporting errors, or system integration failures. For businesses in Riyadh, Jeddah, and Dammam, where compliance audits are increasingly strict, failing to update ERPNext ZATCA compliance becomes a major operational risk.
Build Your Saudi Business Website With Experts
GET STARTED
FATOORAH Compliance and the June 30, 2026 Deadline
FATOORAH compliance fines deadline of June 30, 2026 is a key regulatory milestone for ERPNext update Saudi Arabia, after which non-compliant systems may face penalties or enforcement actions. This deadline is a part of Phase 2 of Saudi Arabia’s ongoing ZATCA e-invoicing compliance framework aimed at improving tax transparency and digital reporting standards.
Saudi Arabia’s FATOORAH (فاتورة) e-invoicing framework is a mandatory electronic invoicing system introduced and regulated by the Zakat, Tax and Customs Authority (ZATCA). Under FATOORAH, invoices must follow strict technical and compliance requirements, including structured XML formats, QR codes, cryptographic stamps, and secure archiving rules.
Payroll Compliance with WPS and GOSI
ERPNext is widely used in Saudi HR and payroll operations across multiple organization, and updates are essential to maintain compatibility with:
  • WPS (Wage Protection System) salary file requirements
  • GOSI (التأمينات الاجتماعية) contribution calculations
  • Updated labor law formats and reporting rules
Updated ERPNext versions help ensure accurate salary calculations, automated GOSI deductions, and properly formatted WPS salary files that meet Saudi banking and regulatory standards. In major cities, where workforce sizes are often large and multi-branch operations are common, automation through ERPNext significantly reduces payroll errors and administrative overhead.
VAT 15% Accuracy and Tax Reporting Compliance
In Saudi Arabia, Value Added Tax (VAT) at the standard rate of 15% (15% ضريبة القيمة المضافة) is a critical compliance requirement for all VAT-registered businesses. For SMEs in particular, maintaining accurate VAT calculations and reporting is essential to avoid financial penalties, reporting discrepancies, and audit risks under the supervision of ZATCA.
Under ZATCA’s Phase 2 e-invoicing requirements, businesses are expected to maintain real-time or structured invoice reporting capabilities through compliant ERP and accounting systems. Outdated ERP systems can create serious compliance challenges by generating inaccurate tax calculations, mismatched invoice data, or incomplete VAT reports.
Keep ERPNext Secure, Stable, And Updated
GET STARTED
Arabic Language Support and System Stability
Arabic language support and system stability are non-negotiable for businesses using ERPNext in Saudi Arabia. ERPNext supports Arabic interfaces, but updates ensure:
  • Proper RTL (right-to-left) rendering improvements
  • Better Arabic PDF invoice formatting
  • UI consistency across modules
  • Fewer localization bugs after upgrades
Post-update verification is especially important for bilingual teams in Saudi Arabia to ensure smooth usability.
Security, Performance, and Compliance Risk Reduction
Older ERP versions often contain unpatched security vulnerabilities that can expose sensitive financial, payroll, and customer data to cyber threats, unauthorized access, or system breaches. For businesses handling VAT records, payroll information, and ZATCA-linked invoice data, these risks can have serious financial and reputational consequences.
Regularly updating ERPNext is essential for maintaining system security, operational efficiency, and overall business continuity in Saudi Arabia’s increasingly digital business environment.

ERPNext Patch Updates Vs Minor Updates Vs Major Version Upgrades

When talking about “how to update ERPNext,” understanding the difference between patch updates, minor updates, and major version upgrades is important. Each type of update affects the system differently in terms of features, stability, compatibility, and maintenance requirements.
Patch updates are low-risk and can be done in 15 minutes or less. Minor updates are moderate-risk, whereas major version upgrades are high-risk and may take a few hours.
Patch Updates
Patch updates are small maintenance releases designed to fix bugs, improve security, and resolve performance issues without significantly changing the system’s functionality. These updates are usually low-risk and are recommended regularly to keep ERPNext stable and secure.
Minor Updates
Minor updates introduce moderate feature enhancements, usability improvements, and compatibility upgrades while remaining within the same major ERPNext version.

For example, ERPNext v15.1 → v15.5 is a minor update that may include:

  • Improved dashboards and UI changes
  • Better Arabic language support
  • Enhanced FATOORAH e-invoicing compatibility
  • New HR or accounting features
  • Updates to integrations and APIs
Major Version Upgrades
Major version upgrades involve significant architectural, functional, and framework-level changes to ERPNext and often require careful planning, testing, and migration procedures.

A common example is ERPNext v15 → ERPNext v16

Major upgrades often include:

  • New features and module redesigns
  • Database structure changes
  • Updated security architecture
  • Improved performance and scalability
  • Changes to workflows, APIs, and customization compatibility
These upgrades usually also involve updates to the underlying Frappe Framework, which powers ERPNext. Since ERPNext and the Frappe Framework are closely connected, upgrading ERPNext often means updating both simultaneously to maintain compatibility and system stability.
For Saudi businesses relying on ZATCA Phase 2 integrations, VAT reporting, WPS payroll workflows, and Arabic localization, major upgrades should always be tested in a staging environment before deployment to production systems to avoid issues in live systems.
What Should I Do Before Updating ERPNext?
1. Check Your Current ERPNext Version

Before updating, identify your installed ERPNext and Frappe versions. This helps determine whether you need a patch update, minor update, or a major version update.

Check your current ERPNext version by running:

bench version
python3 –version
node –version
mysql –version
redis-server –version

2. Thoroughly Check ERPNext Latest Version Release Notes

To understand everything new in the latest update and ensure compatibility, check the release notes by ERPNext to discover modifications and bugs. They help you ensure if your current version is compatible with the new version requirements.

ERPNext v16 upgrade requirements:

  • OS: Ubuntu 20.04 LTS
  • Python version ERPNext upgrade: 3.10 or higher
  • Node.js version ERPNext: 18.x or higher
  • MariaDB ERPNext compatibility: 10.6 or higher
  • Redis: 6.x or higher
  • RAM: 4GB – 8 GB
  • Storage: 20 GB at least
Ensure these requirements are met before you update to the latest ERPNext version.
3. Put ERPNext Into Maintenance Mode
Putting the system into maintenance mode prevents users from modifying data during the update.
bench --site your-site-name set-maintenance-mode on
This reduces the risk of errors including database conflict, incomplete transactions, and invoice generation issues.
4. ERPNext Backup Before Update q

Before you actually update ERPNext, it is important to backup all your important assets to avoid data loss in case of a rollback. Create a backup of your system using bench backup to save your files and database. It is better to store it in a different environment for added protection.

Run the following ERPNext bench commands reference: cd ~/frappe-bench bench --site mycompany.com backup --with-files

You can ensure and confirm backup by:

ls -lh sites/mycompany.com/private/backups/

Once you create the backup, make sure to store it safely. You can do it by:

Alignment with Saudi Vision 2030 Digital Transformation (رؤية 2030)

Option 1: Copy to another server via SCP

scp sites/mycompany.com/private/backups/*.sql.gz user@backup-server:/backups/

Option 2: Upload to S3

aws s3 cp sites/mycompany.com/private/backups/*.sql.gz s3://your-backup-bucket/erpnext/

How to Update ERPNext Without Losing Data: Step by Step
The next step of this ERPNext upgrade guide is running the right commands to update ERPNext without losing data. Check this simple tutorial on how to upgrade ERPNext from v15 to v16:
Step 1: Run ERPNext Update Commands

Once you’re done with the prerequisites, it’s time to get to the main part: ERPNext version update. Follow these ERPNext v16 upgrade commands for ERPNext minor updates and ERPNext major version upgrades.

Update Frappe Framework to v16:

bench switch-to-branch version-16 frappe --upgrade

Update ERPNext to v16:

bench switch-to-branch version-16 erpnext --upgrade
Or use:
bench switch-to-branch version-16 frappe erpnext --upgrade

Step 2: Bench Migrate ERPNext

After you run the ERPNext update command, it is time to migrate data.

bench --site [your-site-name] migrate

Step 3: Clear Cache & Rebuild Assets

This step is especially important for businesses using Arabic interfaces, custom dashboards, or ZATCA/FATOORAH integrations, as frontend inconsistencies can affect invoice generation, RTL rendering, and user workflows.

bench clear-cache

bench clear-website-cache

bench build

Step 4: Restart ERPNext Services
Once the update and asset rebuild are complete, all ERPNext services should be restarted to apply the new changes properly. Use any of these to restart all benches: bench restart Or supervisorctl reload
Step 5: Disable Maintenance Mode
Disabling maintenance mode signals that the system is stable and ready for production use. Run:

bench --site your-site-name set-maintenance-mode off

Step 6: Verify the Upgrade

Once updated, make sure you have the latest version.

bench version

You can also check any inconsistencies with:

bench –site mycompany.com doctor

Bonus: ERPNext Update Command for ERPNext Staging Environment
The ERPNext staging environment is helpful for major version upgrades to avoid issues when updating your primary system.
  1. Repeat the installation on your staging server and restore your production backup into the environment, using:

    bench new-site staging.mycompany.com

  2. Now, restore the database backup as well on the same server:

    bench --site staging.mycompany.com restore \ /path/to/your-production-backup.sql.gz

  3. Switch the staging environment to ERPNext v15 and test the upgrade, using:

    bench switch-to-branch version-15 frappe erpnext hrms

  4. Use this ERPNext update command to update the version and run ERPNext database migration after update:

    bench update --pull

This will find errors that could have appeared after updating ERPNext v15 to v16 step by step. Test the workflows mentioned in the post-update checklist, and if the ERPNext staging environment passes all tests, apply the updates to the primary system (if using a staging environment).
ERPNext Post-upgrade Checklist
Once you have updated ERPNext to the latest version, the major work is done. However, you need to test and ensure that the system is working smoothly. Here are some of the most important post-upgrade checks for Saudi businesses:
  • Make sure that the dashboard loads without JavaScript errors by checking for red errors in the browser console.
  • Ensure that all fields in an existing Sales Invoice and a new test Sales Invoice are visible and correct.
  • Create sales orders and process payroll to ensure compliance with Saudi labor regulations for KSA users.
  • Run the Trial Balance report for the last month to verify the figures.
  • Validate XML invoice structures to confirm they meet ZATCA formatting requirements.
  • Verify that tax templates correctly apply the standard 15% VAT rate (15% ضريبة القيمة المضافة) across all transactions.
  • Confirm correct Arabic UI rendering, proper RTL (right-to-left) formatting, consistency in bilingual invoice layouts, and accurate Arabic PDF generation.
  • Create automatic backups to ensure data safety.
  • Train employees on the new updates to prevent confusion and performance issues.
How To Rollback After a Failed Update?

Even after considering all the important elements, the update may not always go as planned. In such cases, you should act quickly to return to the previous version before attempting the ERPNext version upgrade again.Here’s how you can perform an ERPNext rollback after an update in six simple steps:

 

Step 1:

sudo supervisorctl stop all

Step 2:

bench switch-to-branch version-15 frappe erpnext hrms

(Replace version-15 with your previous version number.
Step 3:

bench --site mycompany.com restore \
sites/mycompany.com/private/backups/20260405_020000-mycompany_com-database.sql.gz

Step 4:

bench build

Step 5:

sudo supervisorctl start all

Step 6:

bench --site mycompany.com doctor

Common ERPNext Update Errors and Troubleshooting

While updating EPRNext, the system may not pass all the tests and you might see one or more of these errors after EPRNext update.

Missing Modules
If you’re unable to find certain modules after the ERPNext update in Saudi Arabia, your application may be missing a required file, dependency, or database patch. You can identify and apply pending patches by running:

bench upgrade --patch

ERPNext Update Custom Apps After Upgrade
In many cases, custom apps may fail to install, show errors during bench update, or stop working entirely due to version mismatches. To avoid disruptions, custom apps should always be reviewed and upgraded alongside ERPNext.
Migration Errors
Migration errors are among the most common issues encountered during an ERPNext update. If your ERPNext database migration fails after an update, you can either repair any corrupted tables or run the following command to retry the upgrade process and help prevent data loss:

bench retry-upgrade

Compatibility Problems

If compatibility of custom apps, scripts, or modules is not checked before upgrading, it may lead to system errors or broken functionality. In such cases, temporarily disable the affected app, review the logs to identify conflicts, and update the custom code to match the new version requirements before re-enabling it.

Login Issues

After upgrades, sometimes, users may experience issues such as being unable to log in, repeated login redirects, blank login screens, or “Invalid Login” errors even when credentials are correct. You can try again after clearing browser cache, or reset passwords if it does not work.

Missing Arabic Fonts or RTL Issues
Arabic UI or RTL layouts may break due to missing assets or frontend changes. You may see Arabic text not rendering correctly in PDFs, broken right-to-left alignment, and poor user experience for Saudi users.
ZATCA Integration Errors
Common issues include incorrect XML invoice structures and API endpoint changes from ZATCA, which can lead to non-compliance with local KSA regulations. To resolve XML formatting issues, run the following commands:

bench --site your-site-name clear-cache bench --site your-site-name migrate bench restart

After completing these steps, regenerate the invoice to verify that the issue has been resolved.
Conclusion

When learning how to update ERPNext in 2026, it is important to understand both the prerequisites and post-upgrade checks to ensure optimal functionality and avoid unnecessary rollbacks.

An ERPNext update in Saudi Arabia is not just a technical maintenance task—it is a critical requirement for security, performance, and local regulatory compliance. For businesses operating in the Kingdom, ERPNext updates carry even greater importance due to strict compliance requirements, including ZATCA Phase 2 (فاتورة المرحلة الثانية), FATOORAH e-invoicing regulations, accurate 15% VAT reporting, WPS payroll processing, and GOSI contributions.

Whether you are planning minor ERPNext updates or major version upgrades, working with experienced local ERPNext partners in Riyadh, Jeddah, and Dammam can help ensure a smooth implementation process. Delivery Devs specializes in ERPNext deployments, upgrades, and support for businesses across Saudi Arabia.

Get in touch with our ERPNext experts in Saudi Arabia to discuss your ERPNext 2026 upgrade and implementation requirements.

FAQs

Here’s how to upgrade ERPNext to the latest version:

  • Check your current ERPNext and Frappe versions and review ERPNext release notes.
  • Take a full ERPNext backup before updating, including the database and files.
  • Pull the latest ERPNext updates from the official repository.
  • Run the bench update and database migration commands.
  • Restart all services after the update is complete.
  • Verify core modules such as Accounts, HR, Inventory, and CRM.
  • Review system logs for errors or failed processes.
  • Perform end-user testing before going live.
  • Schedule post-update monitoring to ensure stability and performance.
Frappe has released ERPNext v16 with many new features, including Custom Financial Report, Automatic Closing Stock Posting, Material Requirements Planning (MRP), Serial and Batch Traceability Report, Customizable Financial Statements, and many more.
While ERPnext v15 offered good baseline performance for SMEs, core production workflows, and ZATCA & VAT support via configurations, ERPNext v16 focuses on faster navigation, system stability, enhanced financial reports, better UI, and optimal performance.
You can check your current ERPNext version by going to your bench and running “bench version” to see what version the installed apps are. You can also check one bench’s version by running “bench –version.”
In terms of licensing, ERPNext is a free and open-source software. You do not have to pay to download or use the software. However, it is not entirely free as organizations need to pay for hosting, implementation, integrations, and technical ERPNext support.
The basic cost of the software is free; no licensing or per-user fees. However, you have to pay for hosting (self-hosted or Frappe Cloud), which may cost between $5 and $200+. The implementation, customization, and on-going support costs depend on the complexity and service provider.
Yes, updating ERPNext can affect ZATCA compliance. These updates help businesses stay aligned with the latest Saudi e-invoicing regulations.If updates are performed incorrectly or without testing, they can temporarily disrupt ZATCA API communication, XML formatting, or invoice generation.
Patch updates are recommended every two to four weeks or as soon as they are released. Major version upgrades come every 12 to 18 months, and must be implemented to ensure latest features and compliance.
Frappe and ERPNext are not exactly the same. Frappe is the framework and ERPNext is the application built on top of Frappe. While ERPNext handles business processes, Frappe ensures the system is customizable and scalable for local compliance needs.
You require Node.js at least 18 or higher for ERPNext v15 and v16. Python should be 3.10 or higher, Maria DB 10.6 or higher, and Redis 6.x or higher.
Expert ERPNext Support For Seamless Upgrades
GET STARTED
recent Blogs
How To Select The Best Web Development Company In Saudi Arabia For Your Business

How To Select The Best Web Development Company In Saudi Arabia For Your Business

Blog Web Development
⏱ 18 minutes read
READ MORE

The DevSecOps Checklist 2026: Building Secure-by-Default AI Apps

Blog DevOps
⏱ 7 minutes read
READ MORE

Beyond Headless: The Rise of Multi-Sensory B2B Web Experiences

Blog Web Development
⏱ 6 minutes read
READ MORE

Tell Us About Your Project