ERPNext Consultant in the UK

Making Tax Digital and VAT: the questions to settle first

HMRC expects VAT records to be held digitally and returns to reach it through MTD-compatible software, with no manual retyping between systems along the way. ERPNext keeps the digital records well: every sales invoice, purchase invoice and journal carries its tax template, and the figures for each VAT box can be derived from posted transactions. The open question is the submission itself.

I do not assume core ERPNext submits returns to HMRC. Instead, I establish which route you will use and test it end to end:

• A community app built on the Frappe framework that submits returns, checking how it is maintained and who supports it.
• Bridging software fed digitally from an ERPNext report, if your accountant is comfortable with that approach.
• A separate MTD-compatible accounting product, which only makes sense in unusual setups.

VAT code design comes before any of this. Standard, reduced, zero-rated and exempt supplies need clear templates, along with reverse charge, postponed import VAT and sales to and purchases from the EU. Construction businesses also need to consider the domestic reverse charge and CIS, which ERPNext does not handle out of the box. Please confirm current rules with your accountant. My ERP consultant in the UK page covers the wider compliance picture.

Leaving Sage 50, Xero or QuickBooks for ERPNext

Most UK ERPNext migrations start from Sage 50, Xero or QuickBooks. The accounting package usually works; the trouble is the stock spreadsheets, job sheets and approval emails around it. The move is less about copying data and more about deciding how the business should run once everything is in one system.

I start with the structure. Nominal codes become an ERPNext chart of accounts, often simplified and supported by cost centers and accounting dimensions instead of dozens of near-duplicate accounts. Customers and suppliers move with VAT numbers, addresses and payment terms. Stock items, which often live outside the accounts entirely, need units, valuation method, reorder levels and warehouse locations agreed before import.

Then the cutover plan:

• Migrate opening balances and open invoices at a VAT quarter end, which keeps the first return clean.
• Keep the old system available read-only for history and audit queries.
• Reconcile trial balance, aged debtors, aged creditors and stock value after each trial load.

Where you sell through Shopify or Amazon, I also map how orders, refunds and fees will reach ERPNext. The ERP data migration service and the QuickBooks migration guide describe the approach in more depth.

Manufacturers, wholesalers and EU trade

ERPNext fits a particular kind of UK business well: small and mid-sized manufacturers, engineering workshops, wholesalers and distributors that hold real stock and want production, purchasing and accounts on one database.

For manufacturers, ERPNext manufacturing covers multi-level bills of materials, work orders, job cards, routing and subcontracting. I check how batch and serial traceability, quality inspections and scrap are recorded, because those are often where spreadsheets survive after go-live.

For wholesalers trading with Europe, sterling is the base currency, but many suppliers invoice in euros or dollars. Foreign currency invoices carry their own rate in ERPNext, gains and losses post when you pay, and landed cost vouchers can add freight, duty and customs agent charges to the cost of stock. Trade with the EU involves customs declarations and VAT treatment that differ from domestic sales, so I design those flows with your accountant and freight forwarder rather than treating them as a simple tax code.

Payroll is a different matter. Frappe HR does not provide UK RTI submissions or statutory pay calculations as a standard feature, so most UK clients keep a specialist payroll product and post summarized journals into ERPNext. Frappe HR can still be useful for leave, attendance and expenses. Industry context is on the manufacturing and wholesale pages.

Hosting under UK GDPR and working with implementers

ERPNext holds customer contacts, supplier representatives and, if you use Frappe HR, employee records, so hosting is a data protection decision as well as a technical one. If you choose Frappe Cloud, read its data processing terms and confirm where your site would physically sit. If you would rather install on a UK region with a cloud provider you already use, you gain direct control over location and access, and take on patching, monitoring and upgrades yourself or through a support firm. Either way, role permissions in ERPNext should be designed so people see only the personal data they need.

The pool of ERPNext specialists in Britain is modest: some freelance Frappe developers, a handful of focused implementers and agencies that work across several platforms, with varying cover in UK hours. That makes it more important to choose carefully and to keep good documentation, so you are not dependent on one person.

My role is to be the independent voice on your side. I write the requirement list and fit-gap analysis, help you compare implementers, review custom apps for upgrade risk and run UAT with your team. Sessions run in British business hours, and colleagues on the continent can usually join the same calls. My ERP implementation page explains how I oversee a build without doing the vendor's job for them.

UK scenarios where ERPNext is hard to justify

I raise these points with British clients early, because each one can tip the decision away from ERPNext:

• You want MTD inside one vendor-supported product: if your finance team or accountant will not accept a community app or bridging step for VAT submission, a commercial UK accounting or ERP product is simpler.
• Construction subcontracting at scale: CIS deductions, verification and returns, combined with the domestic reverse charge, need significant custom work on ERPNext.
• Your accountant runs on the Xero or Sage ecosystem: if advisors and bookkeepers expect direct access to a familiar product, the change cost can outweigh the benefits.
• Payroll inside the ERP is a requirement: UK statutory payroll is best kept in a specialist product.
• No technical ownership: without a developer or provider on call, upgrades and fixes become a risk.

For a manufacturer weighing open source against a mainstream product, ERPNext versus Dynamics 365 is the comparison most UK boards ask for, and Odoo versus ERPNext covers the other open-source route. You will find platform basics on the ERPNext consulting page and my approach to British projects on the UK hub.