In this guide
ERPNext v16 at a Glance
ERPNext v16 went stable around the turn of 2026, almost two years after v15. Frappe calls it its most stable major release so far. Most of the investment went into two places: financial reporting and period close, and manufacturing planning and traceability.
| Area | What changed in v16 | Who benefits most |
|---|---|---|
| Financial statements | Financial Report Templates: formula-driven P&L and Balance Sheet layouts | Groups, CFOs, anyone rebuilding reports in Excel |
| Consolidation | Consolidated Trial Balance across child companies with currency conversion | Multi-company and multi-country groups |
| Purchase costing | Purchase Expense Booking and COGS validation in the buying cycle | Traders and manufacturers with service purchases |
| Periodic inventory | Automatic closing stock posting to the general ledger | Businesses not on perpetual inventory |
| Planning | Dedicated MRP workflow using forecasts, delivery schedules and lead times | Make-to-stock and mixed-mode manufacturers |
| Job work | Native inward subcontracting (customer-supplied material) | Job workers and contract manufacturers |
| Traceability | Serial and Batch Traceability report, backward and forward | Pharma, chemicals, food, auto components |
Accounting: Reports You No Longer Rebuild in Excel
Ask most ERPNext finance teams where their month-end goes and the answer is the same: exporting the standard P&L into a spreadsheet and regrouping it into the format the board, the bank or the auditor wants. v16 goes after exactly that.
Financial Report Templates
Define your own statement layout - rows, groupings and formulas - once, and run it for any period. The format your bank asks for in a CMA submission, or the IFRS layout a parent company wants, becomes a saved template rather than a monthly spreadsheet.
Consolidated Trial Balance
Child companies roll into one trial balance with currency conversion applied. For a group with an Indian manufacturing entity and a UAE trading arm, this replaces a manual consolidation workbook.
Purchase Expense Booking
Freight, handling and other service costs attached to purchases are easier to book and validate against cost of goods sold, with fewer separate vouchers.
Closing Stock Posting
Businesses on periodic inventory can post the closing stock difference straight to the ledger, instead of a hand-calculated journal entry at year end.
Manufacturing: MRP, Job Work and Traceability
In v15, planning in ERPNext meant the Production Plan: pull in sales orders or material requests, explode BOMs, create work orders and purchase requests. That still exists. v16 adds a dedicated Material Requirements Planning workflow that takes forecasts, delivery schedules and lead times into account, which is what make-to-stock manufacturers had been building around.
- Inward subcontracting: Receive raw material from your customer, manufacture for them, and return finished goods, with the customer's stock tracked separately from yours. In v15 this was a manual workaround. If you do job work for others, this alone can justify the upgrade.
- Stock reservation for work orders: Material earmarked for a work order cannot be picked for another one. This ends the classic shop-floor fight where two jobs both "had" the same stock on screen.
- Landed cost on subcontracting receipts: Freight and handling on goods coming back from a job worker now land in the item's valuation, not in a general expense account.
- Serial and Batch Traceability report: Trace a batch backward to the inputs and supplier lots that went into it, or forward to the customers who received it. For a recall or an audit, that is the report you want to produce in minutes.
See how we set up ERPNext for discrete and process manufacturing →
Everything Else Worth Knowing
Beyond the headline features, v16 brings refinements to POS, TDS handling, budgeting and print formats, plus interface and performance work across the desk. Individually these are small. Together they mean fewer support tickets for day-to-day users.
The underlying platform also moves forward: v16 needs newer Python, Node and database versions than v15. Check the official migration guide for the exact versions before planning server work. On self-hosted servers this is often the longest part of the upgrade.
Should You Upgrade Now?
Upgrade soon if:
- • You plan production from forecasts and need real MRP.
- • You do job work for customers and track their material on paper.
- • You run several companies and consolidate in Excel.
- • Batch traceability is an audit or customer requirement.
- • You are starting a new implementation - start on v16, not v15.
Wait a few months if:
- • v15 is stable and none of the features above matter to you yet.
- • You depend on custom apps whose authors have not confirmed v16 support.
- • You are close to financial year end or a GST audit.
- • Your team is mid-rollout of a new module on v15.
There is no deadline pressure. Frappe has said existing sites will not be pushed to v16 automatically for at least six months after release, and v15 keeps receiving fixes during that time. Upgrade because a feature is worth it, not because a version number went up.
A Safe v15 to v16 Upgrade Path
-
1
Inventory every customisation
List custom apps, server scripts, client scripts, custom print formats and integrations. Confirm India Compliance and any marketplace apps have v16-compatible releases.
-
2
Take baseline reports
For the last closed period, export the Trial Balance, Stock Balance, Accounts Receivable and Accounts Payable ageing, and GSTR-1 summary. These are your proof that nothing moved.
-
3
Upgrade a staging copy first
Restore a recent production backup to a separate site, upgrade it, and run the migrations. Fix every error there. Production is never the test environment.
-
4
Reconcile and run user tests
Re-run the baseline reports on staging. Figures must match to the rupee. Then have each department run its daily transactions - a sales invoice, a purchase receipt, a work order, a payment - end to end.
-
5
Upgrade production in a planned window
Freeze transactions, take a fresh backup, upgrade, re-run the reconciliation, and only then reopen to users. Keep the pre-upgrade backup until the next month is closed.
Coming from v14 or older? Upgrades move one major version at a time, so v14 goes to v15 first. Sites on v13 or earlier are usually cleaner as a fresh v16 build with a structured data migration. Explore our ERPNext upgrade and migration service →
Frequently Asked Questions
What is new in ERPNext v16?
Accounting gets Financial Report Templates, a Consolidated Trial Balance, Purchase Expense Booking and automatic closing stock posting. Manufacturing gets a dedicated MRP workflow, native inward subcontracting, stock reservation for work orders, landed cost on subcontracting receipts and a serial and batch traceability report.
Should I upgrade from ERPNext v15 to v16?
Upgrade when a v16 feature solves a real problem for you and your custom apps are confirmed compatible. If v15 is stable and none of the new features matter yet, waiting a few months costs nothing.
Can I upgrade directly from ERPNext v14 or v13 to v16?
Upgrades move one major version at a time, so v14 goes to v15 and then v16. Sites on v13 or older are often better rebuilt on v16 with a data migration.
Will my customisations break on ERPNext v16?
Custom fields, print formats and workflows usually carry across. Custom apps and server scripts that call internal ERPNext functions are where breakage happens, so test them on a staging copy first.
How do I know the upgrade did not change my accounts?
Export the Trial Balance, stock balance and ageing reports for a closed period before upgrading, run them again afterwards, and confirm the figures match exactly.
Final Verdict
v16 is a substantial release for manufacturers and multi-company groups, and the right starting point for any new implementation. For a stable v15 site, the upgrade is worth doing once a specific feature earns it - and only with a staging rehearsal and a reconciled trial balance on both sides.
