2574c4c18c
# [15.100.0](https://github.com/frappe/erpnext/compare/v15.99.1...v15.100.0) (2026-03-03) ### Bug Fixes * **accounts receivable:** include invoice payment terms template (backport [#51940](https://github.com/frappe/erpnext/issues/51940)) ([#53105](https://github.com/frappe/erpnext/issues/53105)) ([f5f40db](f5f40dbcc3)) * allow allowed roles to bypass over billing validation ([8e59fe9](8e59fe90cc)) * correct sle voucher_type comparison in get_ref_doctype ([a587b6a](a587b6a57c)) * ensure cache is cleared on fiscal year update and trash ([7278166](7278166b2c)) * ensure contacts are processed only if present in create_prospect_against_crm_deal ([e2b6179](e2b6179b17)) * handle html email template separately in RFQ to avoid jinja context error ([90169a3](90169a39bb)) * item description html validation error ([3c6a120](3c6a120c5c)) * old stock reco entries causing issue in the stock balance report ([b712467](b712467049)) * opening qty in stock balance ([470a9b3](470a9b38b1)) * **payment entry:** round unallocated amount ([76a1907](76a19076bf)) * populate mr owner and set po owner as fallback ([c1f2991](c1f2991694)) * **pricing_rule:** strict validation of `transaction_type` ([5f82db2](5f82db200e)) * resolve conflicts ([6846f02](6846f02cea)) * **selling:** handle selling price validation for FG item ([d5cc51b](d5cc51b426)) * serial no status for Disassemble entry ([8ce541b](8ce541bf46)) * set company based expense account ([74e71f3](74e71f3868)) * **stock:** validate company for receipt documents and expense accounts ([4462088](44620884c1)) * **trial-balance:** totals with filter `show_group_accounts` enabled ([eabaef2](eabaef2f0b)) * use conversion factor when creating stock entry from pick list ([f2e1482](f2e1482f63)) * use stock qty instead of qty when creating stock entry from MR ([2984f79](2984f79a69)) * use the correct precision value in stock reco ([6d726e4](6d726e4b64)) * validate warehouse of SABB for draft entry ([d5e2515](d5e25153f8)) * Variant Items, List View Enabled to Variant Status Change ([#38468](https://github.com/frappe/erpnext/issues/38468)) ([25b1690](25b169059d)) * voucher detail no in SABB ([6e5738e](6e5738e95c)) ### Features * UOM query filter for opportunity items ([f6a05ec](f6a05ec85e)) ### Performance Improvements * add index on reference_purchase_receipt column ([0766c0e](0766c0ea43))
ERPNext as a monolith includes the following areas for managing businesses:
- Accounting
- Warehouse Management
- CRM
- Sales
- Purchase
- HRMS
- Project Management
- Support
- Asset Management
- Quality Management
- Manufacturing
- Website Management
- Customize ERPNext
- And More
ERPNext is built on the Frappe Framework, a full-stack web app framework built with Python & JavaScript.
Installation
Login for the PWD site: (username: Administrator, password: admin)
Containerized Installation
Use docker to deploy ERPNext in production or for development of Frappe apps. See https://github.com/frappe/frappe_docker for more details.
Manual Install
The Easy Way: our install script for bench will install all dependencies (e.g. MariaDB). See https://github.com/frappe/bench for more details.
New passwords will be created for the ERPNext "Administrator" user, the MariaDB root user, and the frappe user (the script displays the passwords and saves them to ~/frappe_passwords.txt).
Learning and community
- Frappe School - Learn Frappe Framework and ERPNext from the various courses by the maintainers or from the community.
- Official documentation - Extensive documentation for ERPNext.
- Discussion Forum - Engage with community of ERPNext users and service providers.
- Telegram Group - Get instant help from huge community of users.
Contributing
License
GNU/General Public License (see license.txt)
The ERPNext code is licensed as GNU General Public License (v3) and the Documentation is licensed as Creative Commons (CC-BY-SA-3.0) and the copyright is owned by Frappe Technologies Pvt Ltd (Frappe) and Contributors.
By contributing to ERPNext, you agree that your contributions will be licensed under its GNU General Public License (v3).
Logo and Trademark Policy
Please read our Logo and Trademark Policy.