Parsimony — Learn / ERP

What is an ERP system? An operator's explanation.

What an ERP system is for a small business, in plain terms: one database that acts as the system of record for accounting, inventory, orders, and — as the business grows — purchasing, manufacturing, CRM, and HR. ERPNext, an open-source ERP built on the Frappe framework, is the example used throughout.

  • ERPNext · open source · frappe.io
  • Parsimony: ERPNext on Frappe Cloud · US/EU/APAC
  • Frappe HR: separate app, AGPL-3.0

01 / The system of record

One database everyone believes.

Most small businesses don't start with an ERP. They start with accounting software — usually QuickBooks — plus whatever else the business needs: a spreadsheet for inventory, another for open orders, maybe a separate tool for the sales pipeline. Each one is fine on its own. The trouble starts when two of them are supposed to agree and don't.

An ERP system solves that by being the system of record: the one database an organization treats as the authoritative answer for a given fact. A Sales Order isn't re-entered into an inventory spreadsheet — it draws from the same stock record the warehouse uses. An invoice isn't re-typed into accounting — it posts directly to the same chart of accounts the ERP already holds. The word "system" in ERP is doing real work: it's one connected system, not a folder of tools that each hold a piece of the truth.

That single database is also what makes an ERP different from a bigger, better spreadsheet. A spreadsheet stores data; it doesn't enforce that a Sales Order can't ship more than what's in stock, or that an invoice has to trace back to a real delivery. An ERP encodes the actual business process — quote, order, ship, bill, collect — as connected documents, which is the subject of the document flow below.

02 / The modules

What's actually inside an ERP.

ERPNext ships as a set of modules that share the same database. A small business might run three of these; a manufacturer might run all seven. Every module below is a standard part of ERPNext except HR, which moved into its own open-source app, Frappe HR, starting with ERPNext version 14 — it still shares ERPNext's accounting.

Table 1 — ERPNext modules, what each one covers, and example documents
ModuleWhat it coversExample documents
AccountingChart of accounts, journal entries, payables and receivables, bank reconciliation, financial statements.Journal Entry, Payment Entry, GL Entry
InventoryStock on hand by warehouse, stock transfers, valuation, reorder points.Stock Entry, Item, Warehouse
Sales / ordersThe quote-to-cash cycle — see the document flow below.Quotation, Sales Order, Sales Invoice
PurchasingMaterial requests, supplier quotes, purchase orders, goods receipt.Material Request, Purchase Order, Purchase Receipt
ManufacturingBills of materials, work orders, job cards, capacity planning.BOM, Work Order, Job Card
CRMLeads, opportunities, and the pipeline that feeds a Sales Order.Lead, Opportunity, Contact
HR (Frappe HR)Recruitment, onboarding, attendance, leave, payroll, expense claims — a separate open-source app that shares ERPNext's accounting.Employee, Leave Application, Salary Slip

Source: frappe.io/erpnext and frappe.io/hr. Parsimony configures the modules a given business needs — see Cloud ERP and enterprise ERP modules.

03 / The document flow

Quote to cash, as five connected documents.

This is the order-to-cash cycle every sales-capable ERP encodes. In ERPNext, each document is created from the one before it and carries its values forward, so nothing gets re-typed and every step is traceable back to the quote it started from.

The order-to-cash document flowFive connected documents in sequence: Quotation, Sales Order, Delivery Note, Sales Invoice, and Payment Entry. The first three arrows are the data path, in teal. The last arrow, from Sales Invoice to Payment Entry, is the money path, in gold.01QUOTATIONPROPOSE02SALES ORDERCOMMIT03DELIVERY NOTESHIP04SALES INVOICEBILL05PAYMENT ENTRYCOLLECTDATA PATHMONEY PATH
Fig. 1 — The order-to-cash document flow. Teal marks the data path (quote through delivery); gold marks the money path (invoice to payment).

Flow

QuotationSales OrderDelivery NoteSales InvoicePayment Entry

A Quotation proposes terms to a customer. Once accepted, it converts into a Sales Order without re-entering its lines — the order becomes the central reference for everything that fulfills and bills it. A Delivery Note records goods leaving the warehouse and updates stock on hand; a single order can produce several delivery notes if it ships in parts.

The Sales Invoice is created from the order or the delivery note and posts income and receivables to the accounts — it's the point where the fulfillment side of the business hands off to the accounting side. The Payment Entry records what the customer actually paid, closing the loop from quote to cash. Every step keeps a link back to the one before it, so a bookkeeper — or an auditor — can trace any invoice back to the order, and the order back to the quote that started it.

Source: docs.frappe.io/erpnext/selling

04 / Outgrowing QuickBooks

Watch for signals, not revenue.

There's no revenue line where a business needs an ERP. The honest signal is process friction: work-arounds accumulating around the edges of QuickBooks and spreadsheets because they were never built to be the system of record for anything but accounting.

  1. 01

    Two spreadsheets — or a spreadsheet and QuickBooks — can give two different answers to “how many do we have of this right now.”

  2. 02

    Someone re-types the same order into a second tool (inventory, shipping, or a CRM) after it's already in QuickBooks.

  3. 03

    Month-end close takes longer each cycle because reconciling systems is manual, not because the business got more complex.

  4. 04

    You've added a warehouse, a second entity, or a second sales channel that your accounting software wasn't built to consolidate.

  5. 05

    Purchasing, production, or fulfillment decisions wait on someone pulling numbers from three places and stitching them together by hand.

  6. 06

    A report an executive wants “right now” actually takes a day, because it lives in someone's head or someone's export.

05 / Open source vs proprietary

Who owns the code you run your business on.

A proprietary ERP — NetSuite, SAP, Microsoft Dynamics — is licensed software. The vendor owns the code, sets the per-user or per-module pricing, and controls the release schedule. You can configure it within the boundaries the vendor built, but you can't see or change the underlying source.

An open-source ERP is different in kind, not just in price. ERPNext is published as fully open-source software on the Frappe framework — the code is public, you can modify any module, and running it never carries a per-user license fee. What you pay for instead is the work around the code: hosting, migration, customization, training, and support. That's the entire business model behind managed ERPNext, including Parsimony's.

The trade-off runs the other way too. Proprietary vendors typically bundle more of the polish — official mobile apps, first-party integrations, a support desk with an SLA baked into the license. Open source hands you the code and expects you (or a partner) to assemble the rest. Neither model is universally right; it's a question of whether you'd rather pay for a finished product or own the one you build.

Parsimony publishes an architecture-level comparison of ERPNext against Odoo — another open-source ERP with a different philosophy — on /vs-odoo, attributed to a third-party source.

06 / Cloud vs self-hosted

Same software, three ways to run it.

Because ERPNext is open source, running it isn't one decision — it's three, and all three run the identical code. Self-hosted means renting your own server and operating Linux, the database, backups, and upgrades yourself — the most control, and the most operational work. Frappe Cloud self-serve is the official platform-as-a-service from Frappe Technologies: you deploy a site and they handle the infrastructure, but you're still the administrator. Managed hosting — what Parsimony provides — puts a team between you and the infrastructure entirely: they configure, monitor, back up, and support the instance as part of the relationship.

Parsimony's own facts, already published on /erp: managed ERPNext on Frappe Cloud, a custom quote rather than a public monthly price, a 99.95% uptime SLA, and deployments in US, EU, and APAC regions. A full breakdown of what each hosting path costs — with dollar figures attributed to the third parties that publish them — is on /erpnext-hosting.

Cloud ERP

We run the ERPNext instance. You run the business.

Managed ERPNext on Frappe Cloud — custom quote, 99.95% uptime SLA, US/EU/APAC regions. Open source, so nothing about your data is locked to us.

07 / Implementation

What implementation actually involves.

Five phases, in order. How long each one takes depends on the business — the phases don't.

  1. 01

    Discovery and scoping

    Map how the business actually operates — the modules you need on day one, the ones you'll add later, and the workflows that don't fit an out-of-the-box default.

  2. 02

    Data migration

    Extract and clean the historical data — customers, items, open orders, balances — from QuickBooks, spreadsheets, or whatever ran the business before, and load it into the new system.

  3. 03

    Configuration

    Set up the chart of accounts, item and warehouse structure, user roles, and any custom fields or workflows the discovery phase surfaced.

  4. 04

    Training

    The team that will use the system every day learns it before go-live, not after — the point where an ERP is judged is whether people can run it without calling support.

  5. 05

    Go-live and support

    Cut over, run both systems in parallel for the first close if the business wants a safety net, and keep support in place for the questions the first weeks always raise.

Parsimony's own go-live timeline for managed ERPNext is published on /erp. Read the HumanityNow migration for what these phases looked like on one real cutover, or the implementation services page for what Parsimony staffs on each phase.

08 / Glossary

Twelve terms worth knowing.

01

ERP (Enterprise Resource Planning)

Software that runs a business's core operations — accounting, inventory, orders, and usually purchasing, manufacturing, CRM, and HR — from one shared database instead of separate tools.

02

System of record

The one database an organization treats as the authoritative answer for a given fact. When accounting, inventory, and orders share a system of record, there's one number for “how many do we have,” not several.

03

Module

A functional area inside an ERP — Accounting, Inventory, Manufacturing, CRM — that can usually be turned on or off independently while still sharing the same underlying records.

04

DocType

The Frappe framework's term for a record type — a Sales Order, an Item, an Employee. Every DocType is a table in the database plus the form, permissions, and workflow around it.

05

Sales Order

The document that records a customer's committed order. In ERPNext it's the hub the delivery and the invoice are both created from.

06

Delivery Note

The document that records goods leaving the warehouse against a Sales Order. Creating it updates stock on hand.

07

Sales Invoice

The document that bills the customer and posts income and receivables to the accounts — created from the Sales Order or the Delivery Note.

08

Bill of materials (BOM)

The recipe for a manufactured item: the components, quantities, and operations required to build one unit. Manufacturing modules use it to plan work orders and cost the finished good.

09

Chart of accounts

The structured list of every account a business's accounting runs through — assets, liabilities, income, expenses — that every transaction ultimately posts to.

10

Multi-tenant vs. single-tenant

Multi-tenant hosting runs many customers' data on shared application infrastructure, isolated by account. Single-tenant gives one customer a dedicated instance. Frappe Cloud offers both; Parsimony runs managed single-tenant sites.

11

Self-hosted

Running the ERP on infrastructure you rent and operate yourself — a VPS or your own servers — rather than on a vendor's managed cloud.

12

Open source

Software whose source code is publicly available to inspect, modify, and run without a per-user license fee. ERPNext is open source; what you pay for is hosting, migration, and support, not the code.

09 / Questions

Common questions about ERP.

01

What's the difference between an ERP and QuickBooks?

QuickBooks is accounting software: it records what money moved. An ERP is a system of record for the whole operation — accounting plus inventory, orders, purchasing, and often manufacturing, CRM, and HR — so those numbers come from one database instead of being re-typed between separate tools.

02

Is ERPNext really free?

ERPNext is open source, so the software itself carries no license fee if you self-host it. What you pay for is hosting and implementation — server infrastructure, migration, configuration, and support. Frappe Cloud and managed providers charge for that work; the code stays open.

03

How long does ERP implementation take?

It depends on how many modules you turn on and how much historical data you bring, not on a fixed calendar. A single-entity business moving from QuickBooks and spreadsheets can go live in weeks; a multi-entity or manufacturing rollout takes longer. Parsimony's own managed ERPNext go-live timeline is published on the Cloud ERP page.

04

Is an ERP overkill for a small business?

Not by revenue size — by process. If one spreadsheet and one accounting login still answer every question about stock, orders, and cash, you don't need one yet. Once two systems can give two different answers to “how many do we have,” the coordination cost already exists, whether or not you've bought software for it.

05

What's the difference between ERP and CRM?

A CRM tracks the relationship: leads, contacts, deals, communication history. An ERP tracks the transaction: the order, what's in stock to fill it, what it costs, and what was invoiced and paid. Most ERPs, including ERPNext, ship a CRM module so the two share one customer record.

06

Does Frappe HR come with ERPNext?

No — HR and payroll moved out of ERPNext core into Frappe HR, a separate open-source application, starting with ERPNext version 14. It's built by the same team and integrates with ERPNext's accounting, but it's installed and run as its own app rather than a built-in module.

Read next: Cloud ERP · ERPNext vs Odoo · ERPNext hosting · ERP selection checklist

Pricing

Automate is public.
ERP and agents are quoted.

Parsimony Automate has public monthly plans — see Automate pricing. Chat agents, voice agents, and Cloud ERP are quoted to the job. Call or send the form and we put a package together.

  1. 01

    Cloud ERP

    Managed ERPNext on Frappe Cloud. Quoted to the job.

    Quoted
  2. 02

    Automate

    CRM, funnels, two-way text, workflows, and websites on one login.

    $59 / $199 / $497 a month · self-serve
  3. 03

    AI chat and voice agents

    Chat on your site and help desk, voice on your phone line. Quoted to the job.

    Quoted