Primary market
Ireland
- PAYE Modernisation and ROS submissions
- VAT3, RTD and RCT for construction
- Euro-denominated multi-company ledgers
Odoo and ERPNext implementation, Ireland, UK, Europe
Your accounts are in one system. Your stock is in another. Payroll is a spreadsheet.
We implement and optimise Odoo for small and mid-sized businesses in Ireland and the UK, configured for the rules you actually file under: Revenue and ROS, HMRC Making Tax Digital, and EU VAT.
A working session on your current stack and what a move would actually involve. No sales deck.
Revenue and ROSHMRC MTD EU VAT and SEPAGDPR
Period 05 / 2026Ready to file
- T1, VAT on sales
- € 48,210.00
- T2, VAT on purchases
- € 31,884.50
- E1, Intra-EU supplies
- € 12,400.00
- T3, Payable
- € 16,325.50
Generated from live ledger entries. No spreadsheet step.
The real cost
Every manual filing is a process your software should already be doing.
Today
- Payroll re-keyed and submitted to ROS by hand every month.
- VAT return rebuilt in a spreadsheet each quarter.
- Chasing SEPA collections across separate bank portals.
- Customer data spread across inboxes, sheets and a CRM.
Configured properly
- PAYE submissions generated from live payroll data.
- MTD-compliant digital links from ledger to filing.
- Direct debit files and reconciliation in one ledger.
- One governed record, EU-hosted, GDPR-documented.
Where we work
Three jurisdictions, three separate rulebooks
One configuration cannot satisfy Revenue, HMRC and an OSS return at the same time. We build per jurisdiction.
Cross-border
United Kingdom
- Making Tax Digital VAT with digital links
- Payroll RTI and pension auto-enrolment
- Post-Brexit customs and NI protocol flows
Multi-entity
Europe
- VAT OSS and distance-selling thresholds
- SEPA credit transfer and direct debit
- Peppol e-invoicing and ViDA readiness
Two platforms
Odoo and ERPNext are separate products. We scope them separately.
Different licensing, different module architecture, different upgrade paths. Which one fits depends on what you already run and who has to maintain it.
Primary platformOdoo implementation
A commercially licensed suite with a large app catalogue: accounting, inventory, manufacturing, CRM, payroll and website in one vendor's stack. We scope, configure and localise it end to end, and build custom modules only where the standard apps genuinely stop short.
- Full implementation from discovery to go-live
- Irish, UK and EU financial localisation
- Migration from Sage, QuickBooks or Xero
- Custom module and integration development
Open sourceERPNext optimisation
An open-source ERP from Frappe, usually self-hosted and often already in place before we arrive. We audit existing instances, fix the configuration and take on ongoing support, so the compliance output holds up without a re-platform.
- Configuration audit of a live instance
- VAT, PAYE and MTD output corrected at source
- Version upgrades and self-hosting review
- Ongoing support for teams already committed
Services
From first scoping call to the fifth year of support.
01
Odoo implementation
Scoped, configured and localised from discovery through go-live.
02
Migration
Moving off Sage, QuickBooks or Xero with the ledger history intact.
03
Customisation and development
Custom modules and integrations where standard Odoo stops short.
04
Training
Role-based sessions so the system survives the people who built it.
Process
Five stages. Compliance signed off before go-live.
Most failed ERP projects go wrong at stage two, when nobody maps the process that actually happens.
01
Discovery
Current stack, filing calendar, where the manual work sits.
02
Process mapping
Quote to cash, purchase to pay, hire to retire, as they really run.
03
Configuration and migration
Chart of accounts, tax codes, opening balances, master data.
04
UAT and compliance sign-off
A test filing cycle run end to end before anyone commits.
05
Go-live and support
Hypercare through the first close, then a standing support line.
Typical SMB implementation: 8 to 16 weeks from discovery to go-live.
Sectors we know well
Four sectors we have configured repeatedly.
Wholesale and distribution
Multi-warehouse stock, landed costs, EDI.
Light manufacturing
Bills of materials, work orders, shop-floor routing.
Professional services
Timesheets, project margin, retainer billing.
Construction and field services
RCT, subcontractors, job costing.
Before you ask
The five questions everyone asks.
Answered here rather than three emails in.
What does an implementation cost?
It depends on scope: how many modules you switch on, how much data has to move and how much of it needs localising. We price against a fixed, written scope rather than open-ended days, so the figure you approve is the figure you pay.
How long does it take?
A single-entity finance and inventory rollout is the quickest route; each additional country adds a cycle for its own filing rules. You get a dated plan at the end of discovery, before any work is committed.
How disruptive is it day to day?
Your team’s time goes into discovery and user acceptance testing. We schedule go-live against your filing calendar, never mid-VAT-period.
What happens to our existing data?
Open items, master data and opening balances migrate. Historic detail stays archived and readable rather than force-fitted.
What support exists after go-live?
Hypercare through your first month-end close, then a support agreement covering upgrades, regulatory changes and new modules.
Start with an audit of what you actually run.
Tell us what you run today and what breaks. We will tell you honestly whether Odoo is the right answer.