Services
Odoo implementation, financial localisation and ERPNext optimisation for SMBs across Ireland, the UK and Europe. A standard install covers most of what a business needs. The remainder is Revenue submissions, MTD digital links, SEPA mandates and the way your operation actually runs, and that is the part we build.
Three engagement types. Most SMBs start at one and stay on three.
A full Odoo build scoped against how your business runs, not how the demo data runs. Chart of accounts, tax codes, warehouses, approval chains and reporting set up once, properly.
The jurisdiction layer. Odoo ships generic accounting; filing to Revenue or HMRC from live data is configuration work, and getting it wrong is expensive in a way the other modules are not.
For teams already on Odoo or a legacy ERP that nobody trusts. We audit what was built, document what is actually happening, and fix the configuration rather than restarting the project.
Second platform, separate product
Odoo is our primary platform, but a large number of Irish and UK SMBs are already running ERPNext, often self-hosted, often configured by someone who has since left. We audit, fix and support those systems rather than telling you to start again.
The compliance work is the same problem in a different frame: an ERPNext instance still has to produce a Revenue-ready payroll submission, an MTD-compliant VAT return and a SEPA batch your bank accepts. That is where most installs fall short.
Request an ERPNext auditA written report on what was built, what is misconfigured and what each fix costs. Yours to take elsewhere if you prefer.
ROS and PAYE Modernisation, HMRC Making Tax Digital, EU VAT and SEPA mandates configured and tested in staging.
Frappe framework upgrades without losing custom apps, and migration to EU-hosted infrastructure where data residency matters.
If ERPNext is genuinely the wrong fit, we will say so and cost the move. If it is not, we will tell you that too.
PlatformsOdooERPNext by Frappe
Method
Discovery to local support. Stage four is the one most implementations skip and most failures trace back to.
01
We map the current stack, the filing calendar and every place a human retypes something a machine already knows. If you are already on an ERP, this is a written audit of what was built and what it costs you.
You receive
A process map, a gap list and a fixed-scope proposal.
02
Quote to cash, purchase to pay, hire to retire, documented as they really run, including the exceptions your team handles by memory. The system gets configured against this, not against a template.
You receive
Signed-off workflow definitions and a module list.
03
Chart of accounts, tax codes, warehouses, pricelists and master data. Open items and opening balances move across; historic detail is archived and readable rather than force-fitted.
You receive
A populated staging instance with reconciled balances.
04
A full filing cycle run end to end in staging before anyone commits: a test payroll submission, a test VAT return, a test SEPA batch. Your accountant signs off, not us.
You receive
A signed compliance checklist per jurisdiction.
05
Cutover scheduled against your filing calendar, never mid-period. Hypercare through the first month-end close, then a standing agreement covering upgrades, regulatory change and new modules.
You receive
A live system, trained users and a named contact.
Questions
If your question is not here, it is probably the interesting one. Send it over.
Ask an ERP architectNothing moves without a reconciled staging instance first. We migrate open items, master data and opening balances into a parallel environment, reconcile it against your existing trial balance, and only then schedule cutover. Historic detail stays archived and readable rather than being force-fitted into the new chart of accounts. Your old system stays available read-only for as long as your auditor wants it.
That is the part we test before go-live rather than after. Stage four of the process runs a full filing cycle in staging: a test PAYE submission against Revenue, a test MTD VAT return with the digital links in place, a test SEPA batch. Your accountant signs the checklist. If something in your setup cannot file cleanly, you find out in staging, not on a deadline.
Training is role-based and runs during user acceptance testing, not after go-live. Finance users typically need two half-day sessions, warehouse and sales users one each, and administrators a longer handover covering configuration. Budget roughly a week of cumulative team time across the project. Recorded walkthroughs of your own configured system are included.
Fixed scope, quoted before work begins. After discovery you get a written proposal with the module list, the migration scope and a fixed figure. Odoo licensing is separate and paid directly to Odoo. Change requests during the build are quoted individually before any work starts.
This is a large share of what we do. It starts with a configuration and data-integrity audit: what was built, what is misconfigured, what is costing you time, and whether the fastest path is remediation or a clean rebuild with your data carried across. You get that as a written report with a cost against each fix, and you are free to take it elsewhere.
Yes, with a caveat worth stating plainly. Odoo handles multi-company and multi-currency well, so a group with Irish and UK entities runs on one database with separate ledgers, tax configurations and filing paths. The caveat is that each jurisdiction needs its own localisation work and its own sign-off cycle. It is one system, but it is not one configuration job.
Tell us what you run today and what breaks. We will tell you honestly whether Odoo or ERPNext is the right answer.
