* fix(accounts): key the payment ledger CTEs on account, not Max(account) QueryPaymentLedger builds two CTEs -- voucher amount and outstanding -- and joins them on account among other columns. Both sides selected Max(account) while grouping without it, so the join key was an aggregate over two different row sets. A voucher posting ledger entries against two party accounts could have the two sides pick different accounts, the join miss, and the outstanding come back NULL. Max() over text is a sort, so which account wins is also collation-dependent, and the engines sort text differently. Group both CTEs by account instead. That makes the join key a real column and scopes each Sum() to a single account -- so amount_in_account_currency is no longer summed across accounts that may not share a currency. Row shape only changes for a voucher that genuinely spans two party accounts for one party, where today's single row is already an arbitrary pick over mixed currencies. cost_center and remarks stay descriptive but genuinely vary per entry, and were aggregated independently, so they could be stitched together from different entries into a row that was never posted. They now come off one real entry, picked by Min(name) -- Payment Ledger Entry declares no autoname rule, so frappe names it by hash, and those are lower-case, which keeps the pick free of the collation divergence. * test(accounts): cover payment ledger metadata coherence A Journal Entry posting two receivable lines for one customer with different cost centers and remarks. Whatever row the ledger returns, its cost center and remarks must be a pair that was actually posted. Guards the fixture itself, so it cannot pass by posting only one distinct pair. * test(accounts): cover the account-keyed payment ledger aggregation The coherence test posts both party lines to one account, so it exercises the representative-row metadata but not the account-keyed grouping or the CTE join. Adds a Journal Entry posting to two receivable accounts for one customer and asserts each account comes back as its own row, with its own amount and a non-null outstanding.
ERPNext
100% Open-Source ERP System to help you run your business.
Motivation
Running a business is a complex task - handling invoices, tracking stock, managing personnel, and other daily operations. In a market where software is sold separately to manage each of these tasks, ERPNext does all of the above and more, for free.
Key Features
- Accounting: All the tools you need to manage cash flow in one place, right from recording transactions to summarizing and analyzing financial reports.
- Order Management: Track inventory levels, replenish stock, and manage sales orders, customers, suppliers, shipments, deliverables, and order fulfillment.
- Manufacturing: Simplifies the production cycle, helps track material consumption, exhibits capacity planning, handles subcontracting, and more!
- Asset Management: From purchase to disposal, IT infrastructure to equipment. Covers every branch of your organization, all in one centralized system.
- Projects: Deliver both internal and external projects on time, budget and profitability. Track tasks, timesheets, and issues by project.
Under the Hood
-
Frappe Framework: A full-stack web application framework written in Python and JavaScript. The framework provides a robust foundation for building web applications, including a database abstraction layer, user authentication, and a REST API.
-
Frappe UI: A Vue-based UI library, to provide a modern user interface. The Frappe UI library provides a variety of components that can be used to build single-page applications on top of the Frappe Framework.
Production Setup
Managed Hosting
You can try Frappe Cloud, a simple, user-friendly, and sophisticated open-source platform to host Frappe applications reliably and securely.
It handles installation, setup, upgrades, monitoring, maintenance, and support of your Frappe deployments. It is a fully featured developer platform with an ability to manage and control multiple Frappe deployments.
Self-Hosted
Docker
See Frappe Docker Documentation for full documentation & FAQ on Docker setup
Prerequisites
For Docker basics and best practices refer to Docker's documentation
Try on your environment
⚠️ Disposable demo only
This setup is intended for quick evaluation. Expect to throw the environment away. You will not be able to install custom apps to this setup. For production deployments, custom configurations, and detailed explanations, see the full documentation.
First clone the repo:
git clone https://github.com/frappe/frappe_docker
cd frappe_docker
Then run:
docker compose -f pwd.yml up -d
Wait for a couple of minutes for ERPNext site to be created or check the create-site container logs before opening browser on port 8080. (username: Administrator, password: admin)
See Frappe Docker for ARM based docker setup
Development Setup
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).
Local
To setup the repository locally follow the steps mentioned below:
-
Setup bench by following the Installation Steps and start the server
bench start -
In a separate terminal window, run the following commands:
# Create a new site bench new-site erpnext.localhost -
Get the ERPNext app and install it
# Get the ERPNext app bench get-app https://github.com/frappe/erpnext # Install the app bench --site erpnext.localhost install-app erpnext -
Open the URL
http://erpnext.localhost:8000/appin your browser, you should see the app running
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 the community of ERPNext users and service providers.
- Telegram Group - Get instant help from huge community of users.
Contributing
Logo and Trademark Policy
Please read our Logo and Trademark Policy.




