The record every agent and model acts on, from quote to ledger, on ERPNext.

The software bill stays flat as you hire.

ERPNext is released under the GNU General Public License v3 and built on the Frappe framework, which carries the MIT licence. Frappe, its publisher, says ERPNext is free and open source and always will be, and it prices its own cloud hosting by site or server instead of by user. Odoo and Microsoft Dynamics 365 Business Central both charge per user per month.

One data model covers accounting, order management, stock, manufacturing, assets and projects. Every document type gets a REST API, so an agent or an integration reads the same record a person does, and the whole system can run on your own servers. The current line is version 16, and v16.35.0 was published on 15 September 2026.

We run our own company on it. Our accounts, proposals, contracts and invoices sit in ERPNext v16, and the portal our clients sign in to reads from the same record.

We are not a Frappe partner and we resell nothing, which leaves us free to tell you when your current system should stay.

Replacing a working system needs numbers.

Three numbers make the case: the licence over the years ahead, the hours lost retyping between that system and everything else, and the cost and risk of the migration. Often they point the other way, and the better answer is to keep the system and connect it through workflow automation.

We implement ERPNext and say so. Our comparison of ERPNext and Odoo declares that bias in its first paragraph.

The figure shown is the figure booked and charged.

One ERPNext record produces the quote, the contract, the invoice and the ledger entry, so the client, the books and the payment all carry one number, typed once. When a money check cannot run, the step halts before anything is billed.

1. Quote.

   Built from your price list, with margins shown only to the roles allowed to see them.

2. Contract.

   Generated from the quote, signed in the browser and filed with its signature record.

3. Invoice.

   Raised from the signed payment schedule, and issued as PINT AE where the UAE mandate applies.

4. Payment.

   Matched to the schedule. A duplicate payment is refused outright.

5. Ledger.

   Posted from the invoice, so the books hold the same figure.

Sales, finance and operations work from one record.

• Sales pipeline.

  Leads, opportunities, quotes and the follow-ups that used to depend on somebody remembering.

• Contracts and e-signature.

  Generated from the record, read and signed in the browser, filed against the customer.

• Invoicing and tax.

  Tax categories, credit notes and payment matching, set up with your accountant. For UAE VAT, Frappe's ERPNext UAE app adds the settings and the VAT 201 report.

• A client portal.

  Your customers see their own documents, invoices and requests, and only their own.

• Operations.

  Projects, milestones, stock or service records, whatever your company tracks between the sale and the payment.

• Reports people trust.

  They read the same records as the invoices, so nobody keeps a parallel spreadsheet to check them.

The old system runs until the new one agrees.

1. Chart of accounts and process fit.

   Settled with your accountant in the room, because a mistake here is expensive to unpick.

2. Data migration, dry run first.

   Customers, items, open balances and history go into a staging copy and are reconciled before anyone relies on them. Data readiness and migration covers moves from QuickBooks, Zoho Books, Tally or spreadsheets.

3. Documents and templates.

   Quote, contract, invoice and statement in your identity, with the legal blocks each document needs.

4. Roles and access.

   Who sees what is enforced in the database query, so a salesperson who may not see margins never receives them.

5. Parallel run.

   One full cycle in both systems, so any difference shows up while the old one is still running.

6. Go-live and warranty.

   We cut over, watch and fix what surfaces. The warranty runs 12 months while we host the system and 90 days if you host it yourself.

How much history you bring across moves the dates most, and the proposal fixes each one.

The standard scope runs from pipeline to payment.

Backups run under a paid hosting plan once the system is delivered.

Hosted in Germany by default, owned by you.

That hosting is run to the GDPR. Your own servers are an option too, and the contract names the choice.

If your ERP will issue UAE e-invoices, plan where their archive lives. The Ministry of Finance requires e-invoices and their data to be kept for the period the Tax Procedures Law sets and produced to the FTA on request. Its guidelines treat that as a test of access, irrespective of where the servers are. The proposal names the location, and your tax adviser confirms it.

Code we write for you becomes yours once it is paid for, and §06 of the agreement lets you ask for the source at any time. ERPNext itself stays open source, so there is nothing to buy back.